---
schema_version: 1
rubric_version: "1.1"
kind: pair
canonical_url: "https://onaihq.com/compare/agents/glean-vs-meingpt/"
data_url: "https://onaihq.com/compare/agents/glean-vs-meingpt/data.json"
generated_at: 2026-10-27
last_checked_at: 2026-10-26
last_cross_checked_at: 2026-10-26
next_check_at: 2026-12-20
publisher: "onAI"
---

# Glean vs meinGPT

> Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI.

This comparison has 47 criteria with sourced findings for both products, including 47 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent.

- Glean source checks: 2026-10-21 to 2026-10-26.
- meinGPT source checks: 2026-10-21 to 2026-10-26.

- Canonical HTML: https://onaihq.com/compare/agents/glean-vs-meingpt/
- Machine-readable JSON: https://onaihq.com/compare/agents/glean-vs-meingpt/data.json
- Methodology: https://onaihq.com/compare/agents/methodology/

## Models

### MOD-01: Model catalogue and providers

Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Model Hub documents multi-provider choice and Auto routing. New department Auto policies require opt-in rollout as of October 21, with GA scheduled October 29.

Availability: unknown
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=As of 2026-10-21: established model catalog plus opt-in new Auto-policy rollout; no tenant observed; plan=Core Suite + Model Hub Usage with Universal Model Key or Customer Key; new department policies only on Glean-key deployments with rollout enabled. Enterprise Flex billing is separate.; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- This criterion combines established model choice with an opt-in policy rollout; no blanket current GA status is asserted for the new policies. Enabled tenant models and per-request routing were not observed.

- providers — Which model providers are available? [supported]: Model Hub lists OpenAI, Anthropic, Google, Amazon, Glean and open models through Baseten/Fireworks. Availability is conditional on enabled model and route. Sources: glean:glean:models, glean:glean:r2-core-entitlements.
- current_models — Which current models are selectable on this plan? [partial]: Representative listed models include GPT-6.1 Sol, GPT-6 Astra/Sol/Luna, Claude Sonnet 5.5, Opus 5.5, Gemini 3.8 Flash, Waldo and GLM 5.3. Actual tenant-enabled selections were not observed. Sources: glean:glean:models, glean:glean:r2-core-entitlements.
- user_choice — Can users pick the model per chat? [supported]: With Glean Universal Model Key users can select a specific enabled model or Auto. Customer Key uses configured defaults and has separate availability constraints. Sources: glean:glean:models, glean:glean:key-matrix, glean:glean:r2-core-entitlements.
- auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Universal Model Key Auto routes among enabled models. The new department policies require Feature rollouts opt-in from October 15 as of this October 21 check; GA is scheduled October 29. Customer Key Auto uses admin defaults. Per-request selected-model visibility was not established. Sources: glean:glean:models, glean:glean:key-matrix, glean:glean:r2-core-entitlements, glean:glean:r3-october-rollout-migration.
- multimodal_input — Which models accept images, audio or files? [partial]: Uploads, image generation and real-time voice are documented; supported input types vary by model and the key-feature matrix. A complete per-model input matrix was not verified. Sources: glean:glean:uploads, glean:glean:key-matrix, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:models, glean:glean:r2-core-entitlements, glean:glean:key-matrix, glean:glean:r3-october-rollout-migration, glean:glean:uploads

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Curated multi-provider models are selected per chat or by context-length routing; the signed DPA and admin approvals affect availability.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business and individually contracted Enterprise web workspace; permitted models depend on workspace approval and DPA; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- auto_routing: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established.

- providers — Which model providers are available? [supported]: Model authors include OpenAI, Anthropic, Google, Mistral, DeepSeek, Moonshot, Qwen, GLM and MiniMax. Hosts are separate from authors. Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2.
- current_models — Which current models are selectable on this plan? [supported]: Active table lists GPT-4.1, GPT-4o/Mini, GPT-5/mini/Nano/Thinking/5.2/5.4/5.5/5.6 Luna/Sol/Terra, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol; o3; Claude Haiku 5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.6/5/5.5; Gemini 3.5 Flash/Flash-Lite, 3.6/3.7/3.8 Flash and 4 Argon; MeinGPT Web; Mistral Medium 3.5/CodeStral; GPT-OSS 120B; Kimi K2.6/K3; DeepSeek V3.2/V4 Flash/V4 Pro/V4.1 Flash; GLM-5.3/Flash, MiniMax-M3 and Qwen3.8 Max. Duplicate EU/provider routes exist. GPT-6 Astra requires accepted AVV 2.0. Model labels do not guarantee one-to-one public provider variant names. Sources: meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:models-rev2, meingpt:meingpt:rates.
- user_choice — Can users pick the model per chat? [supported]: Users select and switch a permitted model per chat. Sources: meingpt:meingpt:models-rev2.
- auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established. Sources: meingpt:meingpt:models-rev2.
- multimodal_input — Which models accept images, audio or files? [supported]: GPT-4o/5, Claude, Gemini and Mistral Medium/Magistral accept JPEG/PNG/GIF/WEBP; DeepSeek, GPT-OSS, CodeStral and older Kimi K2 do not. Audio uses separate transcription. Sources: meingpt:meingpt:models-rev2.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:rates

### MOD-02: Model freshness

Judgment rule: Measure the days from a provider's general release to availability in the product for the last three major releases from OpenAI, Anthropic and Google (and Mistral where offered). Use dated changelogs or observation. Record deprecation notice for retired models.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Dated release notes and model deprecation guidance are public; comparable release-lag measurements remain unknown.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex Model Hub; Customer Key deprecation policy distinguished from Universal Model Key; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? The release notes were checked, but provider general-release dates and scoped product-availability dates were not paired for the last three releases per provider.
- changelog — Is there a dated public model changelog? [supported]: Public dated release notes include October 15, 2026 and model announcements. Sources: glean:glean:release, glean:glean:r2-core-entitlements.
- deprecation_notice — How much notice is given before a model is removed? [partial]: For Customer Key Assistant, email notices are described at 60 and 15 days. The page also describes automatic migration for deprecated configurations; application to each removal needs confirmation. Sources: glean:glean:deprecation, glean:glean:r2-core-entitlements.
- version_pinning — Can an admin keep an older model version? [partial]: Customer Key admins manage upgrades but deprecated models stop being usable. No indefinite version-pinning entitlement is established. Sources: glean:glean:deprecation, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:release, glean:glean:r2-core-entitlements, glean:glean:deprecation

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

A dated changelog and explicit retirement rules exist; comparative release-lag medians were not established.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- version_pinning: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded.
- Unverified release_lag_days: Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted.

- release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted.
- changelog — Is there a dated public model changelog? [supported]: Public releases include v2.67.0 dated 2026-10-18. Sources: meingpt:meingpt:changes.
- deprecation_notice — How much notice is given before a model is removed? [supported]: Normally four weeks, then reminders at two and one week; provider short notice can shorten this. Opus 4.5 is listed for 23 November retirement; other future dates are in the table. Sources: meingpt:meingpt:lifecycle.
- version_pinning — Can an admin keep an older model version? [partial]: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded. Sources: meingpt:meingpt:lifecycle.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:changes, meingpt:meingpt:lifecycle

### MOD-03: Bring-your-own keys and provider contracts

Judgment rule: Record customer-held API keys, customer cloud accounts (Azure OpenAI, Bedrock, Vertex), and aggregator routes (OpenRouter, LiteLLM) as separate routes. Record what still works without a vendor-provided model, whether prices change with BYO, and documented restrictions. API-key support does not imply support for the customer's own Azure contract.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Customer Key supports named provider accounts; it has documented feature and cloud restrictions.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Customer Key + Glean-family Model Hub Usage; Enterprise Flex Customer Key/private-cloud discounts are separately contractual; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- own_api_keys — Can the customer use its own provider API keys? [supported]: Customer Key supports customer provider credentials including OpenAI and direct Anthropic keys. Sources: glean:glean:models, glean:glean:r2-core-entitlements.
- own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Customer Key supports Azure OpenAI and named provider credentials. The supported-LLMs matrix permits Vertex only on GCP and Bedrock only on AWS; Configure LLMs separately says customer AWS can use Vertex, while its Vertex setup heading says GCP-only. AWS/Vertex eligibility is therefore unknown; no cross-cloud promise is made. Sources: glean:glean:models, glean:glean:key-matrix, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-core-entitlements.
- custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [unknown]: Can an admin add any OpenAI-compatible endpoint? The supported-provider configuration and key matrix were checked; arbitrary OpenAI-compatible customer endpoints are not established.
- byo_pricing — Does BYO change the licence price? [partial]: Core Suite Customer Key limits Glean Model Hub charges to Glean-family usage; customer provider use is paid directly. Enterprise Flex says seats/credits are discounted for own-key/private-cloud customers but publishes no numeric adjustment. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- byo_restrictions — Which features stop working with BYO? [supported]: The key matrix marks Meeting Notes and podcast artifacts unsupported on Customer Key. Text defaults share one provider; image models may differ. Memory depends on deployment readiness. Sources: glean:glean:key-matrix, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:models, glean:glean:r2-core-entitlements, glean:glean:key-matrix, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-flex-entitlements

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Customer LLM API keys, cloud contracts and arbitrary model endpoints are explicitly excluded from the hosted catalogue.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- own_api_keys: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate.
- own_cloud_contract: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts.
- custom_endpoint: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints.
- byo_pricing: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL.
- byo_restrictions: Only DeepL has a documented BYOK exception; it does not replace the workspace model route.

- own_api_keys — Can the customer use its own provider API keys? [unsupported]: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate. Sources: meingpt:meingpt:models.
- own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unsupported]: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts. Sources: meingpt:meingpt:models.
- custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [unsupported]: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints. Sources: meingpt:meingpt:models.
- byo_pricing — Does BYO change the licence price? [partial]: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL. Sources: meingpt:meingpt:models, meingpt:meingpt:translation.
- byo_restrictions — Which features stop working with BYO? [partial]: Only DeepL has a documented BYOK exception; it does not replace the workspace model route. Sources: meingpt:meingpt:models.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:models, meingpt:meingpt:translation

### MOD-04: Local and self-hosted models

Judgment rule: Record support for models running in the customer's environment (vLLM, Ollama, TGI or similar) and which features work with them: chat, RAG, tools, embeddings. Distinguish a documented, supported route from a generic endpoint that happens to work.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

The documented Universal Model Key open models run in the US. Supported customer-operated chat and embedding routes remain unknown.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public open-model guide retrieved 2026-10-26; no deployment observed; plan=Universal Model Key open-model route; current guide does not name a Core Suite/Flex entitlement for customer-operated models; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- The US inference finding is limited to the Universal Model Key open models described by the source. No absence of every conceivable private deployment is inferred.

- self_hosted_chat — Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? The public Model Hub, Customer Key matrix and deployment guides describe named hosted-provider routes. They do not establish supported vLLM/Ollama/TGI chat, customer embeddings, parity or vendor-hosted open-model inference in a named EU/CH region. Creator-region model toggles do not prove inference location.
- self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? The public Model Hub, Customer Key matrix and deployment guides describe named hosted-provider routes. They do not establish supported vLLM/Ollama/TGI chat, customer embeddings, parity or vendor-hosted open-model inference in a named EU/CH region. Creator-region model toggles do not prove inference location.
- feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? The public Model Hub, Customer Key matrix and deployment guides describe named hosted-provider routes. They do not establish supported vLLM/Ollama/TGI chat, customer embeddings, parity or vendor-hosted open-model inference in a named EU/CH region. Creator-region model toggles do not prove inference location.
- vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [unsupported]: For Universal Model Key open models described in the region-control guide, inference is hosted in the US regardless of creator country. That documented route does not provide EU/CH-hosted open-model inference; other private contracts are unverified. Sources: glean:glean:r4-open-model-inference.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25.

Sources: glean:glean:r4-open-model-inference

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Vendor-operated open-model routes exist; customer-hosted LLM and embedding routes were not verified.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- vendor_hosted_open_models: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious.
- Unverified self_hosted_chat, self_hosted_embeddings, feature_parity: Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.

- self_hosted_chat — Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
- self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
- feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference.
- vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious. Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors

### MOD-05: Model control and usage limits

Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Model restrictions and blocking usage limits are documented; new department Auto policies remain an opt-in rollout on October 21.

Availability: unknown
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=As of 2026-10-21: existing controls plus opt-in Auto policies; policy GA scheduled 2026-10-29; plan=Core Suite/Enterprise Flex model governance and usage limits; new Auto policies require Glean-key deployment and Feature rollouts opt-in. Legacy Enterprise exclusions preserved.; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Existing controls and the new policy rollout have different availability. No two-user enforcement test was run; hiding premium models alone does not prevent Auto from using them.

- model_allowlist_by_group — Can admins limit models per group? [supported]: Eligible models can be allowed by department or synced IdP group. Default models cannot carry these restrictions; membership refresh is not immediate. Sources: glean:glean:model-controls, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: Admins can exclude connectors, folders/sites or individual documents from all LLM responses. This is an all-LLM content boundary; per-model data classification rules were not established. Sources: glean:glean:restrictions, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- default_model — Can admins set the default model? [partial]: Customer Key admins set defaults. Universal Model Key admins manage available models; the new department Auto policies require rollout opt-in on October 21, with GA scheduled October 29. They are not a verified generally available policy entitlement on the check date. Sources: glean:glean:model-config, glean:glean:key-matrix, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:r3-october-rollout-migration.
- user_limits — What per-user message or token limits apply, and are they published? [supported]: Core Suite and Enterprise Flex support configurable monthly per-user defaults and overrides. Limits reset each calendar month; legacy Enterprise lacks user/agent limits. Sources: glean:glean:limits, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- limit_behaviour — What happens when a limit is reached? [supported]: Admins select alert-only or block. An in-flight run finishes, then subsequent billable use is blocked until reset; slight overage can occur. Sources: glean:glean:limits, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:model-controls, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:restrictions, glean:glean:model-config, glean:glean:key-matrix, glean:glean:r3-october-rollout-migration, glean:glean:limits

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Admins set model access and defaults; personal category limits have documented exceptions.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- limit_behaviour: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories.
- Unverified data_bound_models: A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run.

- model_allowlist_by_group — Can admins limit models per group? [supported]: Per-team/person allow and deny rules are documented. Workspace admins and free models are exempt; denied chat models fall back, denied API models fail. Sources: meingpt:meingpt:config.
- data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? Unknown. A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run.
- default_model — Can admins set the default model? [supported]: Workspace admins set the default model and chat standards. Sources: meingpt:meingpt:config.
- user_limits — What per-user message or token limits apply, and are they published? [supported]: Six usage levels set monthly EUR limits for text, images, API, other services and meeting bots; no single universal message cap. Sources: meingpt:meingpt:limits.
- limit_behaviour — What happens when a limit is reached? [partial]: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:config, meingpt:meingpt:limits, meingpt:meingpt:api

## Company knowledge

### KNOW-01: Files in chat

Judgment rule: Record supported formats, size and count limits, scanned-PDF OCR, tables and spreadsheets, images inside documents, and whether a file is read in full or retrieved in chunks. Upload the shared fixture set (long German PDF, scanned contract, Excel with formulas, PowerPoint) and record failures.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Chat uploads support common office formats with explicit size limits and OCR prerequisites.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Assistant + Model Hub Usage; Enterprise Flex doc uploads follow its named Assistant mode allowances; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Shared long-PDF, scan, spreadsheet and presentation fixture was not run.

- formats — Which formats are accepted? [supported]: Documented formats include PDF, DOC/DOCX, XLS/XLSX/XLSM, PPT/PPTX, text and image files; audio/video uploads are excluded. Sources: glean:glean:uploads, glean:glean:r2-core-entitlements.
- limits — What size and count limits apply per file and chat? [supported]: 128K models allow 5 files at 64 MB each; 32K models 4 at 32 MB; 8K models 2 at 16 MB. Minimum file size is 1 KB. Sources: glean:glean:uploads, glean:glean:r2-core-entitlements.
- ocr — Are scanned PDFs read? [supported]: Scanned PDFs require OCR enabled by an administrator or support. Sources: glean:glean:uploads, glean:glean:r2-core-entitlements.
- spreadsheets — Are Excel tables read with structure intact? [partial]: Data Analysis handles uploaded spreadsheets, but merged cells, hierarchical tables, charts and complex structures have limited support. Fixture formula and structure fidelity was not tested. Sources: glean:glean:analysis, glean:glean:r2-core-entitlements.
- full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Uploaded analysis files expose full raw content within size limits; referenced indexed spreadsheets may be truncated. Archives are inspected on demand in Thinking mode. Complete visibility into selected chunks was not verified. Sources: glean:glean:analysis, glean:glean:uploads, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:uploads, glean:glean:r2-core-entitlements, glean:glean:analysis

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Chat uploads and direct sandbox processing have different document behavior.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- spreadsheets: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed.
- full_vs_chunked: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context.
- Unverified ocr: No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test.

- formats — Which formats are accepted? [supported]: Text/PDF, images, Word, PowerPoint, Excel, CSV, TXT and URLs are listed; sandbox is needed to read archives and raw mail formats. Sources: meingpt:meingpt:flow.
- limits — What size and count limits apply per file and chat? [supported]: 50 files per chat, 50 MB per non-image file; JPEG/PNG/WEBP/GIF are model-readable images. Provider PDF/page/image limits still apply. Sources: meingpt:meingpt:chat, meingpt:meingpt:models.
- ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test.
- spreadsheets — Are Excel tables read with structure intact? [partial]: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed. Sources: meingpt:meingpt:chat, meingpt:meingpt:sandbox.
- full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context. Sources: meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:pools.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:flow, meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:sandbox, meingpt:meingpt:pools

### KNOW-02: Knowledge bases and shared collections

Judgment rule: Record curated document collections that persist across chats, who can create and share them, size limits, and how they attach to assistants. Distinguish personal, group and organisation-wide scope.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Core Suite includes Library Collections; the replacement Projects rollout and plan entitlement remain qualified.

Availability: unknown
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Library Collections included; current Projects rollout/entitlement not separately established; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Projects are rolling out gradually and may not be enabled for a given deployment. Chat and artifact sharing is separate from project membership.
- Projects is documented as a gradual replacement for Collections, but its current Core Suite/Enterprise Flex entitlement and rollout were not verified.

- persistent_collections — Can users keep document collections across chats? [partial]: Core Suite includes persistent Library Collections. Projects documentation describes a replacement containing chats/documents/files/artifacts, but current Core Suite/Enterprise Flex Projects entitlement and migration rollout were not verified. Sources: glean:glean:r2-core-entitlements, glean:glean:projects.
- sharing_scope — Can collections be shared with users, groups or the whole organisation? [unknown]: The Projects guide describes private-by-default and people/group sharing, but current Projects rollout/entitlement under Core Suite or Enterprise Flex is not separately established. No current plan-scoped project-sharing guarantee is made.
- size_limits — What are the collection limits? [unknown]: What are the collection limits? The Projects guide and agent builder were checked, but a current project size cap and direct knowledge-binding contract are not specified.
- assistant_binding — Can collections be bound to an assistant? [unknown]: Projects and Agent Builder were checked; direct binding of a persistent Project or Collection to an assistant was not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:r2-core-entitlements, glean:glean:projects

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: supported

Cloud pools persist across chats and attach to assistants; Outpost is a separate local index.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

- persistent_collections — Can users keep document collections across chats? [supported]: Persistent cloud data sources index SharePoint/OneDrive, Drive, Confluence, S3, WebDAV and web content. Sources: meingpt:meingpt:pools.
- sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Admins share data sources with teams; workspace admins have broad visibility. Sources: meingpt:meingpt:pools.
- size_limits — What are the collection limits? [supported]: Standard cloud raw-data budget is 300 GB across the workspace; indexing new content stops when full. Sources: meingpt:meingpt:pools.
- assistant_binding — Can collections be bound to an assistant? [supported]: Pools bind to assistants or can be selected in a chat; projects themselves cannot bind pools. Sources: meingpt:meingpt:assistants, meingpt:meingpt:projects.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:pools, meingpt:meingpt:assistants, meingpt:meingpt:projects

### KNOW-03: Enterprise connectors

Judgment rule: List each connector separately with plan, availability and setup owner: SharePoint, OneDrive, Outlook, Teams, Google Drive, Gmail, Confluence, Jira, Notion, Box, Salesforce, ServiceNow, file shares. Record whether the vendor or a third party (or the customer via MCP) provides it, and whether it needs admin consent. A connector listed on a roadmap or partner page is `announced`. An on-prem connector or gateway proves access to local data, not a self-hosted platform (DATA-02).

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Glean documents M365, Google and Atlassian connectors, with indexed and live patterns depending on source.

Availability: generally-available
Delivery: official-integration
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite native connectors included; individual connector setup/consent still required; Enterprise Flex platform connections use applicable feature allowances; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [supported]: SharePoint and OneDrive support indexing and live retrieval. Outlook and Teams are listed separately; Teams includes channels and opt-in private/meeting chats. M365 indexing requires application permissions and admin consent. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:outlook, glean:glean:teams-connector, glean:glean:r2-core-entitlements.
- google_workspace — Which Google sources are connected? [supported]: Google Drive and Gmail have official indexing documentation; Drive setup uses directory delegation. Plan-specific connector entitlements remain contractual. Sources: glean:glean:drive, glean:glean:gmail, glean:glean:r2-core-entitlements.
- atlassian — Confluence and Jira? [partial]: The official catalog lists Confluence and Jira, including Cloud and Data Center documentation. Tenant setup and per-plan limits were not tested. Sources: glean:glean:connectors, glean:glean:r2-core-entitlements.
- other_systems — Which other business systems? [partial]: The catalog includes Box, Salesforce, Notion, Slack, Zendesk and other systems. Individual entitlements, scopes and consent were not verified for every connector. Sources: glean:glean:connectors, glean:glean:r2-core-entitlements.
- on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Deployment guidance supports private connectivity for on-premise connectors. This establishes a network option, not every file share/database or a locally hosted whole platform. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements.
- connector_provider — Who builds and maintains each connector? [partial]: Glean publishes native connector guides; custom connectors and MCP routes are separate. Maintenance ownership for every listed third-party integration was not established. Sources: glean:glean:connectors, glean:glean:gateway, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:outlook, glean:glean:teams-connector, glean:glean:r2-core-entitlements, glean:glean:drive, glean:glean:gmail, glean:glean:connectors, glean:glean:deploy, glean:glean:gateway

#### meinGPT

Verification status: No public information found (not-published)
Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

### KNOW-04: Permission-aware retrieval

Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Permission-aware indexed and live retrieval is documented; the restricted-document test is outstanding.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect permission enforcement and connector access; fine-grained source rules documented per connector; add_ons=Glean Protect+ and account-team enablement for O365 sensitivity-label redlisting only; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Permission claims are documented only; no leak-free outcome or measured propagation delay is claimed.

- source_permissions_respected — Are source permissions enforced per user? [supported]: SharePoint, OneDrive and Teams docs describe per-user permissions checked at query time. This is documentary evidence, not a passed two-user test. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:teams-connector, glean:glean:r2-core-entitlements.
- enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Indexed routes copy source ACLs into Glean and evaluate them at query time; live SharePoint/OneDrive routes avoid a stored content index. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:r2-core-entitlements.
- revocation_delay — How quickly does a removed permission take effect? [partial]: For indexed Drive, activity changes are checked every 10 minutes and group membership hourly. These are crawl schedules, not a measured revocation guarantee. Sources: glean:glean:drive, glean:glean:r2-core-entitlements.
- admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins can include/exclude connectors, containers and documents from LLM access. Changes may take up to an hour. Sources: glean:glean:restrictions, glean:glean:r2-core-entitlements.
- sensitivity_labels — Are Microsoft Purview or similar labels respected? [partial]: Glean Protect+ can exclude SharePoint/OneDrive files by Purview label priority after account-team enablement. It requires crawling, may need days for the first full crawl, and does not cover Teams message text. This is index exclusion, not a passed live-permission test. Sources: glean:glean:r4-purview-label-redlist.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25.

Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:teams-connector, glean:glean:r2-core-entitlements, glean:glean:drive, glean:glean:restrictions, glean:glean:r4-purview-label-redlist

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Live OAuth preserves source access; indexed permissions require a separate, default-off setting.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- source_permissions_respected: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run.
- Unverified revocation_delay, sensitivity_labels: No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown.

- source_permissions_respected — Are source permissions enforced per user? [partial]: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run. Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls.
- enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Live tools execute under user OAuth. Indexed SharePoint/Drive permissions are mirrored and fail closed when stale; source-permission mode is off by default. Sources: meingpt:meingpt:pool-controls.
- revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown.
- admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins select imported sources/folders and control team sharing. Sources: meingpt:meingpt:pools.
- sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls, meingpt:meingpt:pools

### KNOW-05: Freshness and sync model

Judgment rule: Record live (federated) search versus a copied index, sync interval, deletion propagation, and where the index is stored. Edit and delete one fixture document and record when answers change. A copied index adds storage location to DATA-01.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Glean combines indexed and live connector routes; refresh timing is source-specific.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite connector/index platform; Customer Hosted location/contract separately selected; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- live_or_indexed — Is content searched live or copied into an index? [supported]: SharePoint/OneDrive document indexed, live and tool routes. Indexed routes copy content; live routes do not store content in the index. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:r2-core-entitlements.
- sync_interval — How often does an index refresh? [supported]: Drive documents 10-minute activity crawls, hourly people/group crawls, 3-hour incremental crawls and normally 28-day full crawls. Sources: glean:glean:drive, glean:glean:r2-core-entitlements.
- deletion_propagation — How quickly does a deleted document disappear? [partial]: Drive activity processing includes deletions, but no fixture deletion-to-answer interval or universal maximum was verified. Sources: glean:glean:drive, glean:glean:r2-core-entitlements.
- index_location — Where is indexed content stored? [partial]: Indexes run in the selected isolated Glean Hosted or Customer Hosted environment. Exact country and any secondary log/backup locations need deployment confirmation. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:r2-core-entitlements, glean:glean:drive, glean:glean:deploy

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Live connectors query the source; cloud pools copy an index to Germany.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- Unverified deletion_propagation: No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified.

- live_or_indexed — Is content searched live or copied into an index? [supported]: Native connectors fetch live; cloud data pools index imported documents. Sources: meingpt:meingpt:pools.
- sync_interval — How often does an index refresh? [supported]: Cloud import runs every 15 minutes. Sources: meingpt:meingpt:pools.
- deletion_propagation — How quickly does a deleted document disappear? [unknown]: How quickly does a deleted document disappear? Unknown. No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified.
- index_location — Where is indexed content stored? [supported]: Cloud pools run at Hetzner in Germany; local Outpost pools stay in the customer network. Sources: meingpt:meingpt:pools.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:pools

### KNOW-06: Grounding and retrieval quality

Judgment rule: Run the shared question set over the fixture corpus: factual lookups, cross-document questions, German document with an English question, a question with no answer in the corpus. Record citation presence, link accuracy, correct answers and refusals to invent. Disclose model, settings, attempt count and failures. Single runs support a case study, not a ranking.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Linked source citations are documented; named-plan cross-language retrieval and observed grounding quality remain unknown.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Assistant/Deep Research with Model Hub Usage; no verified Core Suite/Enterprise Flex cross-language entitlement; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Citation links do not establish citation accuracy. The Early Access language guide does not map cross-language retrieval to a verified named-plan entitlement.

- citations — Are answers linked to specific sources? [supported]: Assistant documentation describes grounded answers with linked citations; Deep Research produces cited company/web reports. Sources: glean:glean:research, glean:glean:sharing, glean:glean:r2-core-entitlements.
- citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? No shared multilingual question set or restricted corpus was run; citation accuracy, correct-answer count and no-answer behavior remain unmeasured.
- cross_language — Does a question in one language find documents in another? [unknown]: The language guide labels answering across document/query languages Early Access, but its Core Suite/Enterprise Flex entitlement and enabled rollout were not established. Cross-language retrieval for those named plans remains unknown; no multilingual fixture was run.
- no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? No shared multilingual question set or restricted corpus was run; citation accuracy, correct-answer count and no-answer behavior remain unmeasured.
- observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? No shared multilingual question set or restricted corpus was run; citation accuracy, correct-answer count and no-answer behavior remain unmeasured.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:research, glean:glean:sharing, glean:glean:r2-core-entitlements, glean:glean:language

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Source display is documented; grounding quality remains untested.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- no_answer_behaviour: The guide says source search reports no matching result; actual refusals were not tested.
- Unverified citation_accuracy, cross_language, observed_accuracy: The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.

- citations — Are answers linked to specific sources? [supported]: Cloud source answers always display sources and this cannot be disabled. Sources: meingpt:meingpt:pool-controls.
- citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.
- cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.
- no_answer_behaviour — Does it say when the corpus has no answer? [partial]: The guide says source search reports no matching result; actual refusals were not tested. Sources: meingpt:meingpt:pools.
- observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:pool-controls, meingpt:meingpt:pools

### KNOW-07: Memory and personal context

Judgment rule: Record personal custom instructions, cross-chat memory, project or workspace context, and user controls to view, edit, delete or disable memory. Record whether admins can disable memory organisation-wide.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Glean documents personal saved and learned memory with user controls and a limited admin off switch.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite saved memory in seat and learned memory with Model Hub Usage; Enterprise Flex learned-memory rate/temporary waiver separate; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- custom_instructions — Can users set persistent instructions? [supported]: Saved preferences and explicit memories can persist across conversations. Sources: glean:glean:memory, glean:glean:r2-core-entitlements.
- cross_chat_memory — Does the product remember facts across chats? [supported]: Saved and learned memories retain user work context and preferences across chats, subject to deployment availability. Sources: glean:glean:memory, glean:glean:r2-core-entitlements.
- user_memory_controls — Can users view, edit and delete memories? [supported]: Users can view, edit and delete memories and control memory use in a conversation. Sources: glean:glean:memory, glean:glean:r2-core-entitlements.
- admin_memory_controls — Can admins turn memory off? [partial]: Admins can disable learned memory; saved memories are user-controlled and cannot be disabled by admins through this setting. Sources: glean:glean:memory-admin, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:memory, glean:glean:r2-core-entitlements, glean:glean:memory-admin

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Personal instructions and user-specific assistant memory are documented.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- user_memory_controls: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries.

- custom_instructions — Can users set persistent instructions? [supported]: Preferences store a persistent system instruction applied with workspace and assistant context. Sources: meingpt:meingpt:preferences.
- cross_chat_memory — Does the product remember facts across chats? [supported]: Enabled assistants share a personal user memory store across chats, not a team store. Sources: meingpt:meingpt:memory.
- user_memory_controls — Can users view, edit and delete memories? [partial]: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries. Sources: meingpt:meingpt:memory.
- admin_memory_controls — Can admins turn memory off? [supported]: Admins can disable or remove Memory from the permitted tools. Sources: meingpt:meingpt:memory.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:preferences, meingpt:meingpt:memory

## Assistants and agents

### AGT-01: Custom assistants

Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Custom agents combine instructions, models, knowledge and tools and have an internal library.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Building/Governance/Sharing in seat; builder assistance/debugging/runtime use Model Hub as applicable; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Agent Builder configures instructions, model choice, knowledge and tools, with Workflow and Auto modes. Sources: glean:glean:builder, glean:glean:agents, glean:glean:r2-core-entitlements.
- creator_permissions — Can admins limit who creates them? [partial]: Admin role and agent-sharing controls regulate creation and distribution; no trial creation-boundary check was performed. Sources: glean:glean:roles, glean:glean:agent-sharing, glean:glean:r2-core-entitlements.
- sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Agents have controlled sharing/edit access, including department and IdP-group audiences where enabled. Sources: glean:glean:agent-sharing, glean:glean:groups, glean:glean:r2-core-entitlements.
- catalogue — Is there an internal assistant directory? [supported]: The Agent library shows accessible agents for discovery and execution. Sources: glean:glean:library, glean:glean:r2-core-entitlements.
- prompt_library — Are shared prompt templates available? [partial]: The former Prompt Library was retired August 5, 2025. Reusable prompts and apps moved to Agents; use current agents/templates rather than the retired interface. Sources: glean:glean:sunset, glean:glean:library, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:builder, glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:roles, glean:glean:agent-sharing, glean:glean:groups, glean:glean:library, glean:glean:sunset

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: supported

Assistants combine model, instructions, tools and knowledge, with governed creation and sharing.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

- create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: The editor supports instructions, model, files, pools, connectors and built-in tools. Sources: meingpt:meingpt:assistants.
- creator_permissions — Can admins limit who creates them? [supported]: Request-enabled permissions restrict assistant creation/sharing/publication by team or person; admins are exempt. Sources: meingpt:meingpt:permissions.
- sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Team and direct-person assistant sharing are documented; workspace-wide publication is admin-only by default. Sources: meingpt:meingpt:permissions, meingpt:meingpt:roles.
- catalogue — Is there an internal assistant directory? [supported]: The navigation lists personal assistants and shared resources. Sources: meingpt:meingpt:assistants.
- prompt_library — Are shared prompt templates available? [supported]: Prompt folders can be personal, workspace or department scoped. Sources: meingpt:meingpt:prompts.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:assistants, meingpt:meingpt:permissions, meingpt:meingpt:roles, meingpt:meingpt:prompts

### AGT-02: Tools, actions and MCP

Judgment rule: Record built-in tools, custom actions (OpenAPI), MCP client support (local and remote servers), authentication model per tool (shared service account or per-user OAuth), and admin approval of tools. Verify one external-tool call and its access boundary.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Glean supports tools and external MCP with admin access controls; tool identities vary by route.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite native tools/MCP host and Developer Tools; LLM tool/API calls incur Model Hub Usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- External-tool access boundaries were not tested. Customer Key and tool-provider contracts remain separate.

- builtin_tools — Which tools are built in? [supported]: Agents can search knowledge, analyze data and read/write connected records; available tools depend on enabled connectors. Sources: glean:glean:agents, glean:glean:r2-core-entitlements.
- custom_actions — Can admins add API actions? [supported]: The MCP Gateway exposes customer-built read/write tools as well as connector tools. Sources: glean:glean:gateway, glean:glean:r2-core-entitlements.
- mcp_client — Can it use remote MCP servers, and with what admin control? [partial]: Admins register external remote MCP servers and apply role/group controls in Glean. This pass did not execute a server call. Sources: glean:glean:gateway, glean:glean:r2-core-entitlements.
- tool_auth — Do tools act as the user or as a shared account? [partial]: OAuth integrations can use Glean-managed or customer OAuth applications; agent service credentials are a distinct route. Identity must be checked per tool. Sources: glean:glean:oauth, glean:glean:r2-core-entitlements.
- tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins control tool exposure. The Microsoft file-creation guide instructs interactive-agent builders to disable Run without user confirmation when user approval is required. Write confirmation is configurable, not an unconditional enforced rule; a universal approval policy for unattended agents remains unknown. Sources: glean:glean:gateway, glean:glean:r3-microsoft-write-confirmation, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:gateway, glean:glean:oauth, glean:glean:r3-microsoft-write-confirmation

#### meinGPT

Verification status: No public information found (not-published)
Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

### AGT-03: Web search and deep research

Judgment rule: Record web search on/off control per organisation and group, search provider, citation of web sources, deep or multi-step research, and whether queries leave the residency boundary. Admins of regulated companies often need web search off.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Brave is the new web-search default; OpenAI search is a legacy route under migration. Deep Research produces cited read-only reports.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=2026-10-21, after the October 19 start of OpenAI-to-Brave migration; individual migration completion unobserved; plan=Core Suite Deep Research with Model Hub Usage; Brave for new web-search setups, configured Gemini route per setup guide, legacy OpenAI only until migrated; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- The dated release governs the new-versus-legacy route distinction. No per-tenant configuration, migration completion or provider-region test was performed.

- web_search — Is web search available? [supported]: Brave is the default for new web-search setups. The setup guide also documents Google Gemini. OpenAI Web Search is closed to new setups; existing instances work only until Glean migrates them to Brave, beginning October 19. Sources: glean:glean:web, glean:glean:r2-core-entitlements, glean:glean:r3-october-rollout-migration.
- admin_toggle — Can admins disable it per organisation or group? [partial]: Admins select enabled search tools and publication to Assistant, Agents and MCP. Universal per-group disabling was not verified. Sources: glean:glean:web, glean:glean:r2-core-entitlements.
- search_provider — Which search provider handles queries, and where? [partial]: Brave is the new default and the provider named by Deep Research; Gemini is another documented configured route. OpenAI is legacy-only during the migration that began October 19. Per-tenant migration completion and query-processing countries remain unknown. Sources: glean:glean:web, glean:glean:research, glean:glean:r2-core-entitlements, glean:glean:r3-october-rollout-migration.
- deep_research — Is multi-step research with a report available? [supported]: Deep Research writes cited multi-source reports from company sources and the web; it does not write to connected systems. Sources: glean:glean:research, glean:glean:r2-core-entitlements.
- web_citations — Are web sources cited? [supported]: Deep Research reports contain linked web and company citations. Sources: glean:glean:research, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:web, glean:glean:r2-core-entitlements, glean:glean:r3-october-rollout-migration, glean:glean:research

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: supported

Linkup powers cited web search and Deep Research; admins can restrict app access.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

- web_search — Is web search available? [supported]: Search can be switched on in chat, is always on in MeinGPT Web and runs in the Recherche app. Sources: meingpt:meingpt:web.
- admin_toggle — Can admins disable it per organisation or group? [supported]: Request-enabled per-team/person app controls include Web search. Sources: meingpt:meingpt:permissions.
- search_provider — Which search provider handles queries, and where? [supported]: Linkup processes search; the register lists Azure France. Prompt terms can enter generated search queries. Sources: meingpt:meingpt:web, meingpt:meingpt:subprocessors.
- deep_research — Is multi-step research with a report available? [supported]: The research app has a user-controlled multi-step Deep Research mode. Sources: meingpt:meingpt:web.
- web_citations — Are web sources cited? [supported]: Results include source previews and page references. Sources: meingpt:meingpt:web.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:web, meingpt:meingpt:permissions, meingpt:meingpt:subprocessors

### AGT-04: Workflows and automation

Judgment rule: Record no-code or low-code workflows, scheduled prompts, triggers from email, forms or business systems, and multi-step chains. Name where they run and who can build them. A shared prompt template is not a workflow.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: supported

Workflow mode supports multi-step logic with schedule and content-event triggers.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Building, workflow mode and triggers in seat; LLM execution incurs Model Hub Usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

- workflow_builder — Is there a workflow or chain builder? [supported]: Workflow mode supports explicit steps, branches, loops and hand-offs; Auto mode builds from natural-language goals. Sources: glean:glean:agents, glean:glean:r2-core-entitlements.
- scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Published agents can run on schedules after admin enablement; setup differs by Auto versus Workflow mode. Sources: glean:glean:triggers, glean:glean:r2-core-entitlements.
- event_triggers — Can external events start a workflow? [supported]: Content triggers run when supported connected-system content changes; chat and form triggers are separate. Sources: glean:glean:triggers, glean:glean:r2-core-entitlements.
- builder_audience — Is building aimed at business users, IT or developers? [supported]: The builder supports natural-language creation and explicit workflow editing; the documentation includes self-paced Agent Builder training. Sources: glean:glean:agents, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:triggers

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: supported

Multi-step workflows are documented; scheduled/event automations are request-enabled beta.

Availability: beta
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- Workflow editor is documented separately from request-enabled beta scheduled tasks; beta is not universal plan availability.

- workflow_builder — Is there a workflow or chain builder? [supported]: A project editor chains prompts with variables and per-step models, or Buddy drafts the workflow. Sources: meingpt:meingpt:workflows.
- scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Support enables beta tasks with daily, weekly, monthly or selected calendar schedules. Sources: meingpt:meingpt:scheduled.
- event_triggers — Can external events start a workflow? [supported]: Beta tasks accept tokenized webhooks and task-specific email addresses. Sources: meingpt:meingpt:scheduled.
- builder_audience — Is building aimed at business users, IT or developers? [supported]: Members can build with natural-language Buddy help or manual steps, subject to admin rights. Sources: meingpt:meingpt:workflows.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:workflows, meingpt:meingpt:scheduled

### AGT-05: Agentic task execution

Judgment rule: Record an agent mode that plans and carries out multi-step tasks with tools (browser, files, connectors), with visible steps, user confirmation of side effects and stop control. Run one fixture task (gather three documents, draft a summary, propose an email). Record interventions and what ran. A final claim of success is not proof.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Auto mode agents plan and use tools, but end-to-end execution safety was not tested.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Harness/Agent Building with Model Hub Usage for LLM execution; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- agent_mode — Is there an agent mode for multi-step tasks? [supported]: Auto mode agents dynamically choose tools and delegate subtasks; Workflow mode uses explicit steps. Sources: glean:glean:agents, glean:glean:r2-core-entitlements.
- visible_steps — Are steps and tool calls shown? [partial]: Workflow steps and builder preview/debugging are documented. Complete runtime visibility for every Auto action was not verified. Sources: glean:glean:builder, glean:glean:agents, glean:glean:r2-core-entitlements.
- side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Office creation tools describe a confirmation step before writing, without an editable inline preview. This does not establish confirmation for all scheduled operations. Sources: glean:glean:office-output, glean:glean:r2-core-entitlements.
- stop_control — Can the user stop a running task? [partial]: The October 15 release documents that canceling an Assistant response terminates its tool calls and background tasks. Universal cancellation across scheduled/independent agents and every client was not verified by a fixture. Sources: glean:glean:r4-cancellation-release.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25.

Sources: glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:builder, glean:glean:office-output, glean:glean:r4-cancellation-release

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Assistants can execute successive tool calls, show progress and stop; per-action confirmation is absent.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- side_effect_confirmation: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog.

- agent_mode — Is there an agent mode for multi-step tasks? [supported]: Assistant tools run multiple sequential steps within a response and stop at a bounded tool-call budget. Sources: meingpt:meingpt:assistants.
- visible_steps — Are steps and tool calls shown? [supported]: Tool/reasoning steps and progress are shown in chat. Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat.
- side_effect_confirmation — Must the user confirm actions with side effects? [unsupported]: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog. Sources: meingpt:meingpt:tools.
- stop_control — Can the user stop a running task? [supported]: The input button changes to Abbrechen and stops response generation while preserving text. Sources: meingpt:meingpt:chat.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat, meingpt:meingpt:tools

### AGT-06: Programmable access

Judgment rule: Record a public API for chat, assistants and knowledge, SDKs, API authentication, rate limits and whether API use counts against the same governance (audit, budgets, model restrictions). Being an MCP client is different from exposing the product over MCP.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Public platform APIs and a remote MCP server are documented.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean APIs and remote MCP server; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Platform/Admin/Indexing/Tools APIs in seat and LLM Client APIs/MCP with Model Hub Usage; Enterprise Flex Client APIs consume FlexCredits; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- chat_api — Is there an API for chat and assistants? [supported]: Core Suite lists Chat and Agents APIs plus platform APIs and Web SDK; LLM-using calls incur Model Hub consumption. Sources: glean:glean:core-price, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- knowledge_api — Can documents be loaded through an API? [supported]: Core Suite lists the Indexing API and Tools API; document upload APIs are linked from the file-upload guide. Sources: glean:glean:core-price, glean:glean:uploads, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- api_governance — Do audit, budgets and model rules apply to API use? [partial]: Machine-scale API usage can incur extra fees, and MCP uses user permissions. Full audit/budget/model-rule parity across API credentials was not tested. Sources: glean:glean:core-price, glean:glean:mcp, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- mcp_server — Does the product expose itself to other agents over MCP? [supported]: Glean MCP exposes search, chat, document reading and other tools to external AI hosts. Sources: glean:glean:mcp, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:core-price, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:uploads, glean:glean:mcp

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Enterprise-enabled APIs cover chat, assistants and workflows with model and budget enforcement.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Enterprise API, explicitly enabled; no public add-on price; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- api_governance: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established.
- Unverified knowledge_api, mcp_server: A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide.

- chat_api — Is there an API for chat and assistants? [supported]: Bearer-key chat completions, assistants, workflow runs, embeddings and transcription are documented; personal keys require Enterprise enablement. Sources: meingpt:meingpt:api, meingpt:meingpt:outlook.
- knowledge_api — Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide.
- api_governance — Do audit, budgets and model rules apply to API use? [partial]: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established. Sources: meingpt:meingpt:api, meingpt:meingpt:config, meingpt:meingpt:audit.
- mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:api, meingpt:meingpt:outlook, meingpt:meingpt:config, meingpt:meingpt:audit

## Daily work

### WORK-01: Clients and access points

Judgment rule: List web, desktop (Windows, macOS), iOS, Android, mobile browser and browser extension separately. For each, record login with company SSO, feature gaps against web, and MDM/Intune deployability. An installable app is different from a mobile website.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Glean has web, desktop, mobile and extension access, including managed mobile controls.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents, Glean for Desktop Windows and macOS, Glean iOS and Android, Glean browser extension and companion; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Glean surfaces included in seat; individual AI actions may incur Model Hub Usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=Windows, macOS, iOS, Android.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- web — Is a full web client available? [supported]: The full browser app provides chat, Library and agents. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements.
- desktop_apps — Windows and macOS apps? [supported]: Windows and macOS desktop clients are documented. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements.
- mobile_apps — iOS and Android apps with SSO? [supported]: iOS and Android apps require an active SSO-configured tenant. Sources: glean:glean:mobile, glean:glean:r2-core-entitlements.
- browser_extension — Is there a browser extension or sidebar? [supported]: The extension supplies sidebar chat/search and a companion for selected text. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements.
- managed_deployment — Can IT deploy and configure clients through MDM? [supported]: Mobile integrates with Intune App Protection. Managed desktop and extension deployment are linked in official deployment guidance. Sources: glean:glean:mobile, glean:glean:surfaces, glean:glean:r2-core-entitlements.
- client_feature_gaps — Which features are missing on mobile? [partial]: Deep Research is web-only. Real-time voice supports web, desktop and mobile; other complete parity differences were not verified. Sources: glean:glean:research, glean:glean:voice, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements, glean:glean:mobile, glean:glean:research, glean:glean:voice

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

The platform is browser-based; Outlook has a separate centrally deployed add-in.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace, meinGPT Outlook add-in, meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Business/Enterprise web workspace; Outlook add-in requires Enterprise API enablement and personal API key; add_ons=Enterprise API enabled for Outlook add-in; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- managed_deployment: The Outlook add-in can be assigned to users or groups in Microsoft 365 integrated apps; general desktop/mobile MDM configuration was not found.
- Unverified desktop_apps, mobile_apps, browser_extension, client_feature_gaps: No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.

- web — Is a full web client available? [supported]: The terms define a browser-accessible workspace. Sources: meingpt:meingpt:terms.
- desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
- mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
- browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.
- managed_deployment — Can IT deploy and configure clients through MDM? [partial]: The Enterprise API-enabled Outlook add-in can be assigned to users/groups through Microsoft365 integrated apps. It supports Outlook web, Windows classic/new and Mac; each user needs a personal meinGPT API key. General desktop/mobile MDM configuration was not established. Sources: meingpt:meingpt:outlook.
- client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:terms, meingpt:meingpt:outlook

### WORK-02: Office suite and Teams integration

Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

A Microsoft Teams app is documented; connectors and file-generation tools do not establish in-Office add-ins.

Availability: generally-available
Delivery: official-integration
Scope: surfaces=Glean in Microsoft Teams, Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite embedded Microsoft Teams and other listed surfaces; selected Assistant actions incur Model Hub Usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? The Teams app, connector catalog and Office-output guides were checked. An assistant embedded inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; remote content access is not counted as in-app presence.
- outlook — Does it work inside Outlook? [unknown]: Does it work inside Outlook? The Teams app, connector catalog and Office-output guides were checked. An assistant embedded inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; remote content access is not counted as in-app presence.
- teams — Is there a Teams app or bot? [supported]: The Glean Teams app has an admin installation guide and tenant setup/consent requirements. Sources: glean:glean:teams-app, glean:glean:r2-core-entitlements.
- google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? The Teams app, connector catalog and Office-output guides were checked. An assistant embedded inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; remote content access is not counted as in-app presence.
- licence_prerequisites — Which licences or consents are needed? [partial]: Teams requires admin deployment in a configured Glean tenant and Microsoft permissions. Extra licence charges are not numerically specified in the guide. Sources: glean:glean:teams-app, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:teams-app, glean:glean:r2-core-entitlements

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

A documented Outlook add-in operates in the received-message view and needs Enterprise API access.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT Outlook add-in; version=Public documentation checked 2026-10-21; plan=Enterprise API enabled workspace; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- licence_prerequisites: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated.
- Unverified word_excel_powerpoint, teams, google_workspace_apps: Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.

- word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
- outlook — Does it work inside Outlook? [supported]: Outlook Web, Windows classic/new and Mac support summarizing the selected received email and drafting replies; compose view is excluded. Sources: meingpt:meingpt:outlook.
- teams — Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
- google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03.
- licence_prerequisites — Which licences or consents are needed? [partial]: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated. Sources: meingpt:meingpt:outlook.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:outlook

### WORK-03: Translation and writing

Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Browser companion translation and general writing are documented; layout-preserving document translation is unverified.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean browser extension and companion, Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite browser Companion/Sidebar surfaces included; LLM writing/translation uses configured model usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? The companion, file-upload and Office-generation guides were checked. No whole-document layout-preserving translation, company glossary, formality/de-CH control or DE-to-FR/IT fixture result was established.
- translation_engine — Which engine translates? [partial]: The browser companion translates selected text through Glean. A dedicated translation service or exact translation-model route is not named here. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements.
- glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? The companion, file-upload and Office-generation guides were checked. No whole-document layout-preserving translation, company glossary, formality/de-CH control or DE-to-FR/IT fixture result was established.
- formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? The companion, file-upload and Office-generation guides were checked. No whole-document layout-preserving translation, company glossary, formality/de-CH control or DE-to-FR/IT fixture result was established.
- writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Configured agents support drafting; the browser companion explains, summarizes and translates selected text. Dedicated proofreading behavior was not verified. Sources: glean:glean:surfaces, glean:glean:agents, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements, glean:glean:agents

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Dedicated text/document translation uses EU Google/DeepL routes and managed glossaries.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- document_translation: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested.
- writing_tools: Quick Actions rewrite answers, including more formal and improve options.
- Unverified formality_and_variants: Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated.

- document_translation — Can whole documents be translated with formatting kept? [partial]: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested. Sources: meingpt:meingpt:translation.
- translation_engine — Which engine translates? [supported]: Default Google Cloud Translate for text and DeepL for documents; own DeepL key switches both to DeepL. Sources: meingpt:meingpt:translation.
- glossaries — Are company glossaries supported? [supported]: Workspace admins create per-language-pair glossaries and import CSV; exact word forms must match. Sources: meingpt:meingpt:translation.
- formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated.
- writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Quick Actions rewrite answers, including more formal and improve options. Sources: meingpt:meingpt:chat.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:translation, meingpt:meingpt:chat

### WORK-04: Image generation and editing

Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Glean can generate and edit images using enabled image models.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite image generation/editing with Model Hub Usage; provider/key availability remains conditional; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- image_generation — Can users generate images, with which models? [supported]: Universal Model Key uses the managed GPT Image 2.5 or GPT Image 2 default; Customer Key admins select image models and Agents can select enabled models. Sources: glean:glean:images, glean:glean:r2-core-entitlements.
- image_editing — Can users edit uploaded images? [supported]: The image guide documents editing uploaded images. Sources: glean:glean:images, glean:glean:r2-core-entitlements.
- admin_control — Can admins restrict image generation? [supported]: An administrator must enable image generation and a supported image model. Sources: glean:glean:images, glean:glean:r2-core-entitlements.
- usage_terms — What usage rights apply to output? [partial]: Customer rights in outputs are governed by the Terms and AI Addendum together with model-provider terms; no unique or exclusive image-output guarantee was verified. Sources: glean:glean:terms, glean:glean:ai-addendum, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:images, glean:glean:r2-core-entitlements, glean:glean:terms, glean:glean:ai-addendum

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Twelve named image variants include reference editing with administrator model controls.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- image_editing: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing.
- usage_terms: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output.

- image_generation — Can users generate images, with which models? [supported]: FLUX.2 Klein/Pro/Flex/Max, FLUX 1.1 Pro, FLUX.1 Kontext Max; GPT Image 1/Mini/1.5/2; Gemini 2.5 Flash Image and 3 Pro Image. Sources: meingpt:meingpt:images.
- image_editing — Can users edit uploaded images? [partial]: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing. Sources: meingpt:meingpt:images.
- admin_control — Can admins restrict image generation? [supported]: Admins enable models and default; request-enabled permissions can restrict Image app use by teams or persons. Sources: meingpt:meingpt:image-admin, meingpt:meingpt:permissions.
- usage_terms — What usage rights apply to output? [partial]: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output. Sources: meingpt:meingpt:terms, meingpt:meingpt:images.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:images, meingpt:meingpt:image-admin, meingpt:meingpt:permissions, meingpt:meingpt:terms

### WORK-05: Voice and meetings

Judgment rule: Record dictation, read-aloud, live voice conversation, meeting transcription and summarisation, supported languages including Swiss German speech, and where audio is processed.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Real-time voice is available with provider streaming; meeting functionality depends on key mode.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents, Glean for Desktop Windows and macOS, Glean iOS and Android; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite real-time voice/Meeting Notes with Model Hub Usage; Meeting Notes requires Universal Model Key per feature matrix; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Raw voice audio streams to the configured model provider and is not stored according to the voice guide; transcripts follow chat retention.

- dictation — Can users dictate prompts? [unknown]: Can users dictate prompts? The voice guide and key-mode matrix were checked; separate dictation and Swiss German recognition were not established or tested.
- read_aloud — Can answers be read aloud? [partial]: Real-time voice speaks its responses; a separate read-aloud control for arbitrary text responses was not established. Sources: glean:glean:voice, glean:glean:r2-core-entitlements.
- voice_conversation — Is a live voice mode available? [supported]: Interactive voice supports web, desktop and mobile, with interruptible spoken replies and a chat transcript. It does not invoke a chosen published agent. Sources: glean:glean:voice, glean:glean:r2-core-entitlements.
- meeting_summaries — Are meetings transcribed and summarised? [partial]: The key matrix lists Meeting Notes as generally available with Universal Model Key and unsupported with Customer Key. Recording/language behavior was not tested. Sources: glean:glean:key-matrix, glean:glean:r2-core-entitlements.
- swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? The voice guide and key-mode matrix were checked; separate dictation and Swiss German recognition were not established or tested.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:voice, glean:glean:r2-core-entitlements, glean:glean:key-matrix

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Dictation and meeting transcription are documented; speech quality was not tested.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- Unverified read_aloud, voice_conversation, swiss_german_speech: No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.

- dictation — Can users dictate prompts? [supported]: A microphone transcribes prompts into the input field. Sources: meingpt:meingpt:chat.
- read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.
- voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.
- meeting_summaries — Are meetings transcribed and summarised? [supported]: Audio/video/transcript uploads and meeting-bot notes are documented; storage Hetzner Germany, Gladia transcription France, Vertex EU summaries. Sources: meingpt:meingpt:meeting.
- swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:chat, meingpt:meingpt:meeting

### WORK-06: Data analysis and document output

Judgment rule: Record code execution for data analysis, charts, and generation of downloadable Word, Excel, PowerPoint and PDF files. Analyse the fixture Excel and request a PowerPoint summary. Record where code runs and whether files are editable.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Data analysis and Office file output are documented, with spreadsheet and template limitations.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Assistant/Canvas/document output with Model Hub Usage; provider/tool prerequisites apply; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- No fixture analysis or output-file inspection. Code-interpreter provider and retention differ by route.

- data_analysis — Can it analyse spreadsheets with executed code? [supported]: Thinking-mode uploaded spreadsheets can use a per-user/session sandbox. Indexed spreadsheets may be truncated and cross-indexed-file numeric aggregation is not supported by the documented Data Analysis route. Sources: glean:glean:analysis, glean:glean:r2-core-entitlements.
- charts — Can it produce charts? [unknown]: The Data Analysis and Office-output guides were checked, but chart generation and chart-file fidelity were not established or observed in this pass.
- office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Enabled tools create Word documents, Excel workbooks and PowerPoint decks, saved/downloaded through the documented route. Arbitrary Word/Excel template population is not supported by create tools. Sources: glean:glean:office-output, glean:glean:r2-core-entitlements.
- canvas_editing — Is there a document or canvas editor for iterating on output? [supported]: Slide generation creates decks in Canvas for refinement and export; exact themes and embedded elements are not guaranteed. Sources: glean:glean:office-output, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:analysis, glean:glean:r2-core-entitlements, glean:glean:office-output

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

An isolated EU sandbox executes analysis code and generates downloadable Office files.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- canvas_editing: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original.

- data_analysis — Can it analyse spreadsheets with executed code? [supported]: Python/JavaScript sandbox reads original spreadsheets with pandas/openpyxl and executes code. Sources: meingpt:meingpt:sandbox.
- charts — Can it produce charts? [supported]: Executed matplotlib charts can be returned as PNG. Sources: meingpt:meingpt:sandbox.
- office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Sandbox libraries support DOCX/XLSX/PPTX; workflows also generate Word/PDF/Excel/CSV/PowerPoint/JSON. Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows.
- canvas_editing — Is there a document or canvas editor for iterating on output? [partial]: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original. Sources: meingpt:meingpt:sandbox.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows

### WORK-07: Sharing and team spaces

Judgment rule: Record chat sharing (link, user, group), shared projects or team spaces, channels or group chat with AI, and commenting. Test sharing a chat with a colleague in another group and record what the recipient sees, including knowledge they lack access to.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Viewer chat sharing documents recipient-source redaction; current Projects and group-chat plan entitlements remain unknown.

Availability: beta
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Assistant Viewer sharing; current Projects and Team-chat Editor entitlement under Core Suite/Enterprise Flex unverified; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Viewer redaction must not be generalized to Team-chat Editors. Projects and Team-chat commercial/rollout entitlements remain unknown; no two-user fixture was run.

- share_chats — Can chats be shared inside the organisation? [supported]: Users can share chats with users, departments or the organization, with Viewer read-only access. Sources: glean:glean:sharing, glean:glean:r2-core-entitlements.
- team_spaces — Are shared projects or workspaces available? [unknown]: The Projects guide describes gradual enablement but does not establish a current named Core Suite/Enterprise Flex entitlement. Shared-project availability remains unknown.
- group_chat — Can several people chat together with the AI? [unknown]: The Team chat guide describes a beta enabled for selected users, but its current Core Suite/Enterprise Flex entitlement was not established. Multi-user AI chat availability for a named plan remains unknown.
- share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: For Viewer chat sharing, the guide documents redaction of inaccessible citations and content. That finding does not establish the distinct Team-chat Editor entitlement or its availability for a Core Suite/Enterprise Flex tenant. No cross-group sharing test was run. Sources: glean:glean:sharing, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:sharing, glean:glean:r2-core-entitlements, glean:glean:projects, glean:glean:team-chat

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Chat links and shared projects exist; projects preserve private member chat histories.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- group_chat: Each project member has a separate private chat list; shared project chats are not a simultaneous group conversation.
- Unverified share_permission_boundary: No cross-group chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified.
- Project chat privacy does not prove absence of every group-chat surface.

- share_chats — Can chats be shared inside the organisation? [supported]: A share toggle creates a link displaying the shared conversation. Sources: meingpt:meingpt:chat.
- team_spaces — Are shared projects or workspaces available? [supported]: Projects share instructions and workflows with Owner/Editor/Member roles. Sources: meingpt:meingpt:projects.
- group_chat — Can several people chat together with the AI? [partial]: Within Projects,each member has a separate private chat list. Simultaneous multi-user group conversation elsewhere was not established. Sources: meingpt:meingpt:projects.
- share_permission_boundary — Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? Unknown. No cross-group chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:chat, meingpt:meingpt:projects

### WORK-08: Interface languages and accessibility

Judgment rule: Record UI languages, focusing on German, French, Italian and English, with translation quality observed (complete, partial, machine-translated). Record response language handling and WCAG conformance statements.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

German, French, Italian and English end-user UIs are documented; admin setup is not localized.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite client surfaces; detailed language/localization entitlements not separately mapped by plan; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.
- The language/accessibility pages describe the common product, without a separate Core Suite/Enterprise Flex localization entitlement matrix.

- ui_languages — Which UI languages are offered? [supported]: The support matrix lists English, German, French and Italian UI among other locales. Sources: glean:glean:language, glean:glean:r2-core-entitlements.
- dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? The locale matrix and accessibility statement were checked, but translation completeness and naturalness were not observed in a logged-in German/French/Italian UI.
- accessibility_statement — Is there a WCAG conformance statement? [partial]: Glean maintains a VPAT 2.5 ACR covering WCAG 2.0/2.1/2.2 A and AA, obtainable through the Trust Center; the report was not reviewed. Sources: glean:glean:accessibility, glean:glean:r2-core-entitlements.
- admin_ui_languages — Is the admin interface available in German? [unsupported]: The language guide explicitly says external help documentation and admin workspace setup are not yet localized. Sources: glean:glean:language, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:language, glean:glean:r2-core-entitlements, glean:glean:accessibility

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Platform-language choice exists, but the full UI and accessibility matrix remains unverified.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- ui_languages: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page.
- Unverified dach_language_quality, accessibility_statement, admin_ui_languages: No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.

- ui_languages — Which UI languages are offered? [partial]: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page. Sources: meingpt:meingpt:preferences.
- dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.
- accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.
- admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:preferences

## Administration and governance

### ADM-01: Single sign-on and authentication

Judgment rule: Record SAML, OIDC, Microsoft Entra ID, Google, LDAP, MFA enforcement, conditional-access compatibility, domain verification and plan restrictions. Test one SSO login on a trial where possible.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

SSO is mandatory with OIDC/SAML and identity-provider MFA and conditional access.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect includes SSO and role access; detailed IdP policy setup is separately documented; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- No SSO trial login was performed.

- sso_protocols — Which SSO protocols and identity providers work? [supported]: OIDC and SAML work with Entra ID, Google, Okta, OneLogin and generic SAML providers as documented. Sources: glean:glean:sso, glean:glean:r2-core-entitlements.
- sso_plan — Which plan includes SSO? [partial]: SSO is mandatory during deployment setup; no separate SSO price or plan gate is given in this guide. Sources: glean:glean:sso, glean:glean:r2-core-entitlements.
- mfa — Can MFA be enforced? [supported]: Glean recommends enforcing MFA through the configured identity provider. Sources: glean:glean:sso, glean:glean:r2-core-entitlements.
- conditional_access — Do Entra conditional-access policies apply? [supported]: Glean recommends appropriately secure IdP conditional-access policies; mobile documents Intune-compatible sign-in. Sources: glean:glean:sso, glean:glean:mobile, glean:glean:r2-core-entitlements.
- domain_capture — Can the company claim its email domain? [partial]: Glean checks the user email domain against the expected customer domain before issuing a login cookie; broader domain-capture/migration semantics were not established. Sources: glean:glean:sso, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:sso, glean:glean:r2-core-entitlements, glean:glean:mobile

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Microsoft/Google login is included; custom OIDC is enabled on request and SAML is excluded.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- sso_plan: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated.

- sso_protocols — Which SSO protocols and identity providers work? [supported]: Google and Microsoft sign-in plus custom OpenID Connect for Entra, Keycloak, Okta, PingFederate and Authentik. SAML is not supported. Sources: meingpt:meingpt:sso.
- sso_plan — Which plan includes SSO? [partial]: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated. Sources: meingpt:meingpt:sso, meingpt:meingpt:prices.
- mfa — Can MFA be enforced? [supported]: MFA is enforced at the customer IdP; disabling a user prevents new sign-ins but does not immediately invalidate an existing session. Sources: meingpt:meingpt:sso.
- conditional_access — Do Entra conditional-access policies apply? [supported]: Customer IdP controls Conditional Access. Existing sessions expire normally unless separately removing the membership. Sources: meingpt:meingpt:sso.
- domain_capture — Can the company claim its email domain? [supported]: DNS TXT verification enables domain auto-join and optional rejection of invitations into other workspaces; existing external memberships remain. Sources: meingpt:meingpt:sso.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:sso, meingpt:meingpt:prices

### ADM-02: User provisioning and lifecycle

Judgment rule: Record SCIM, just-in-time provisioning, group sync from the identity provider, deprovisioning effects (chats, assistants, knowledge ownership transfer) and licence assignment. Deprovision a test user and record what happens to their content.

#### Glean

Verification status: No public information found (not-published)
Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Governance includes SCIM; user provisioning and login-time group sync have separate effects.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform plus Governance provisioning add-on; add_ons=Governance; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- group_sync: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync.
- deprovisioning: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested.

- scim — Is SCIM provisioning supported? [supported]: Entra SCIM v1 creates/updates/deactivates users, requires a verified domain and workspace enablement, and replaces manual invitations. Sources: meingpt:meingpt:scim, meingpt:meingpt:prices.
- group_sync — Are identity-provider groups synced? [partial]: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync. Sources: meingpt:meingpt:scim, meingpt:meingpt:sso.
- jit_provisioning — Are users created at first login? [supported]: Custom OIDC can join a verified-domain workspace on first authenticated login; plain Microsoft sign-in alone does not grant workspace membership. Sources: meingpt:meingpt:sso, meingpt:meingpt:scim.
- deprovisioning — What happens to a removed user's data and shared assets? [partial]: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested. Sources: meingpt:meingpt:scim.
- seat_assignment — Can admins assign and reclaim seats? [supported]: New SCIM users start as unlicensed viewers unless automatic seat assignment is on; admins can assign seats. Sources: meingpt:meingpt:scim.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:scim, meingpt:meingpt:prices, meingpt:meingpt:sso

### ADM-03: Roles, groups and feature permissions

Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Glean has delegated admin roles, IdP-group permissions and feature access controls.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect/Agent Governance role controls; department and IdP group policy configuration as documented; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- No two-group restriction-enforcement test.

- admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Setup Admin, Admin, Super Admin and specialist moderators have documented scopes; only Super Admin can assign certain privileges. Sources: glean:glean:roles, glean:glean:r2-core-entitlements.
- groups — Can permissions be set per group? [supported]: Direct and IdP-group roles combine, with highest-precedence primary roles and union of secondary roles. Group permission behavior is feature-flag dependent. Sources: glean:glean:groups, glean:glean:r2-core-entitlements.
- feature_toggles — Which features can be switched on or off per group? [partial]: Member permissions include content and agent creation; model access, scheduled triggers and beta features have specific controls. Every feature/group combination was not verified. Sources: glean:glean:users, glean:glean:groups, glean:glean:r2-core-entitlements.
- multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Terms permit affiliates to use or order the service, while separate subsidiary data partitions within one contract were not established. Sources: glean:glean:terms, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:roles, glean:glean:r2-core-entitlements, glean:glean:groups, glean:glean:users, glean:glean:terms

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Role and group controls include request-enabled app permissions and model restrictions.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- multi_entity: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established.

- admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Admin, Member and Viewer; unlimited workspace admins and separate team administrators are documented. Workspace admins consume a seat and bypass restrictions. Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions.
- groups — Can permissions be set per group? [supported]: Teams control shared resources and models; admins see all team-shared assets. Sources: meingpt:meingpt:roles, meingpt:meingpt:config.
- feature_toggles — Which features can be switched on or off per group? [supported]: Request-enabled controls restrict image, meeting notes/bot, translation, web, Voice Agent, Buddy and automation use by teams or persons. Sources: meingpt:meingpt:permissions.
- multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established. Sources: meingpt:meingpt:sso.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions, meingpt:meingpt:config, meingpt:meingpt:sso

### ADM-04: Usage and adoption analytics

Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Insights provides adoption and individual activity reporting with CSV export.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Billing & Insights included in seat; Enterprise Flex Admin console/Insights platform separate from usage rates; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- adoption_dashboard — Is there an adoption dashboard? [supported]: Insights includes daily, weekly and monthly active users and adoption metrics. Sources: glean:glean:insights, glean:glean:r2-core-entitlements.
- breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Department filters and per-person Assistant, search, agent and MCP activity are documented. Model usage is a separate dashboard; a unified breakdown by every requested dimension was not verified. Sources: glean:glean:insights, glean:glean:core-price, glean:glean:r2-core-entitlements.
- export — Can usage data be exported? [supported]: The All signed up users table exports CSV; customer event delivery supports downstream analysis. Sources: glean:glean:insights, glean:glean:events, glean:glean:r2-core-entitlements.
- privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: Departments under five users are grouped. The same guide documents named user activity; an organization-wide pseudonymous mode was not established. Sources: glean:glean:insights, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:insights, glean:glean:r2-core-entitlements, glean:glean:core-price, glean:glean:events

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Adoption metrics and cost CSVs have team and anonymization options.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- breakdowns: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated.

- adoption_dashboard — Is there an adoption dashboard? [supported]: Cockpit lists prompts, active users, daily prompts/workflow runs and popular workflows. Sources: meingpt:meingpt:analytics.
- breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated. Sources: meingpt:meingpt:analytics.
- export — Can usage data be exported? [supported]: User/team cost statistics export to CSV. Sources: meingpt:meingpt:analytics.
- privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: Metric anonymization replaces names with IDs; top-user metrics depend on that setting. Sources: meingpt:meingpt:analytics.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:analytics

### ADM-05: Spend controls and cost allocation

Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Usage limits can alert or block; team limits are per-member defaults rather than pooled team budgets.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite / Enterprise Flex; legacy Enterprise exclusions stated; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- cost_visibility — Can admins see cost or consumption per user and group? [supported]: Usage dashboards expose user/team/agent consumption in dollars or FlexCredits depending on plan. Sources: glean:glean:limits.
- budgets — Can budgets be set per user or group? [supported]: Organization, user, department/IdP-group and agent monthly limits are documented for Core Suite/Enterprise Flex; legacy Enterprise lacks user/agent limits. Sources: glean:glean:limits.
- budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: An optional block stops later billable requests after the running action completes. Alert-only is also available; some overage can occur. Sources: glean:glean:limits.
- chargeback — Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? The usage-limit and pricing guides were checked; cost-center chargeback export and cost allocation outside current department/group metadata were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:limits

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Personal category budgets and pooled credit provide controls with documented exceptions.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- budget_enforcement: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories.
- chargeback: CSV cost exports exist by user/team; formal cost-centre coding is not established.

- cost_visibility — Can admins see cost or consumption per user and group? [supported]: Usage-based plans show EUR costs per user/model and team, separately for platform and API. Sources: meingpt:meingpt:analytics.
- budgets — Can budgets be set per user or group? [supported]: Six personal usage levels configure monthly budgets across five categories and are assigned singly or in bulk. Sources: meingpt:meingpt:limits.
- budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api.
- chargeback — Can costs be exported per cost centre? [partial]: CSV cost exports exist by user/team; formal cost-centre coding is not established. Sources: meingpt:meingpt:analytics.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:analytics, meingpt:meingpt:limits, meingpt:meingpt:api

### ADM-06: Audit logs and compliance export

Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Administrative change logs have documented CSV export and retention. Prompt/response compliance logging remains unknown because source scopes conflict.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect administrative audit logs; no verified prompt/response compliance-logging finding; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Only administrative/configuration events, their export and their stated retention are positive findings. Content logging, its compliance integrity model, eDiscovery and legal hold remain unverified.

- admin_events — Are admin and security events logged? [supported]: Admin Audit Logs record configuration changes by admins and Glean support, excluding end-user events. Default retention is 30 days. Sources: glean:glean:audit, glean:glean:r2-core-entitlements.
- content_logging — Can prompts and answers be retained for compliance, and is it configurable? [unknown]: Prompt/response retention and its configuration remain unknown. The deployment comparison says individual queries/responses are not logged, while Customer Event documentation describes CHAT response content and the history guide separates that logging from history. Their deployment/system scopes were not reconciled.
- siem_export — Can logs stream to a SIEM or be exported? [partial]: The administrative audit-log guide documents self-serve CSV export. For Glean-hosted deployments, ongoing delivery of administrative logs can be configured by the account team and is not enabled by default or self-serve. This finding makes no prompt/response or Customer Event export guarantee. Sources: glean:glean:audit, glean:glean:r2-core-entitlements.
- ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Administrative and Customer Event documentation was checked. eDiscovery/legal-hold behavior, integrity guarantees and per-destination content-log retention were not established.
- log_retention — How long are logs kept? [partial]: Administrative audit logs have a documented 30-day default; extended periods require arrangement. Customer Event/content-log retention is unknown and no common retention term for all logs is inferred. Sources: glean:glean:audit, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:audit, glean:glean:r2-core-entitlements, glean:glean:deploy, glean:glean:events, glean:glean:history

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Administrative change exports and a separate Outpost search log have distinct retention.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- admin_events: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found.
- content_logging: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear.
- siem_export: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established.
- Unverified ediscovery: No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established.

- admin_events — Are admin and security events logged? [partial]: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found. Sources: meingpt:meingpt:audit, meingpt:meingpt:scim.
- content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear. Sources: meingpt:meingpt:audit.
- siem_export — Can logs stream to a SIEM or be exported? [partial]: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established. Sources: meingpt:meingpt:audit-export.
- ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Unknown. No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established.
- log_retention — How long are logs kept? [supported]: Administrative settings changes are retained indefinitely; Governance Outpost query records are retained 90 days from enablement. Sources: meingpt:meingpt:audit.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:audit, meingpt:meingpt:scim, meingpt:meingpt:audit-export

### ADM-07: Data loss prevention and personal data

Judgment rule: Record detection and handling of personal and confidential data before it reaches a model: redaction, masking, blocking, warning. Record integration with Purview, Netskope or similar, and whether filtering runs locally or at a third party. Send a fixture prompt with a Swiss AHV number and IBAN and record the outcome.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Protect+ can flag or block configured sensitive patterns in prompts; file coverage and Swiss-fixture outcomes are unknown.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Enterprise Flex + Protect+ site-wide annual add-on; basic Core Suite CSV protection is a different mechanism; add_ons=Glean Protect+ AI security; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Prompt-only pattern policy is not evidence that file contents are filtered before every model call. No personal-data fixture was run.

- pii_detection — Is personal data detected in prompts and files? [partial]: Prompt-only regex policy covers configured PII, credentials, IBAN and government-ID patterns. Templates start disabled; this policy excludes retrieved data and generated responses. Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- pii_action — Is it redacted, masked, blocked or only warned? [supported]: Admins choose monitoring with findings or immediate blocking of the run; the guide does not promise automatic redaction for this policy. Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- custom_patterns — Can admins add custom patterns or terms? [supported]: Admins can define RE2 pattern groups and test patterns before enabling them. Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- dlp_integration — Does it integrate with an existing DLP product? [partial]: Protect+ documents AI security integrations including Palo Alto Networks in the product/security material. Purview/Netskope integration and exact enterprise entitlement were not verified. Sources: glean:glean:protect, glean:glean:subprocessors, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- filter_location — Where does filtering run? [unknown]: Where does filtering run? Protect+ and prompt-policy guides were checked. Filtering location, upload scanning by this policy and Swiss AHV/IBAN behavior were not observed.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:protect, glean:glean:subprocessors

#### meinGPT

Verification status: No public information found (not-published)
Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

### ADM-08: AI policy and guardrails

Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Enterprise instructions and configurable AI security policies are documented.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Enterprise Flex Assistant instructions; Protect+ site-wide annual add-on for security monitoring/blocking; add_ons=Protect+ for AI security findings; not required for basic custom instructions; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Model-followed instructions are distinct from policy enforcement.

- org_instructions — Can admins set organisation-wide instructions? [supported]: Admins can configure up to five enterprise custom instructions for Assistant. Sources: glean:glean:org-instructions, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? The custom-instruction and AI security guides were checked; a mandatory acceptable-use acknowledgement flow was not established.
- content_filters — Are content filters configurable? [supported]: Protect+ policies can monitor/block configured sensitive prompts and restrict topics; enforcement depends on enabled policy. Sources: glean:glean:pii, glean:glean:protect, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- violation_reporting — Are policy hits visible to admins? [supported]: Monitoring creates admin findings with matched patterns, snippets and conversation links. Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:org-instructions, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:pii, glean:glean:protect

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Workspace instructions and Governance acknowledgements are documented; policy enforcement breadth is limited.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- org_instructions: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer.
- content_filters: Provider content filtering can stop output; configurable organization-wide topic filters were not established.
- Unverified violation_reporting: Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run.

- org_instructions — Can admins set organisation-wide instructions? [partial]: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer. Sources: meingpt:meingpt:config.
- usage_notice — Can users be required to accept a usage policy? [supported]: Governance includes multilingual acceptable-use policies for acknowledgement and mandatory courses that block other pages until complete. Sources: meingpt:meingpt:prices, meingpt:meingpt:audit.
- content_filters — Are content filters configurable? [partial]: Provider content filtering can stop output; configurable organization-wide topic filters were not established. Sources: meingpt:meingpt:api.
- violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:config, meingpt:meingpt:prices, meingpt:meingpt:audit, meingpt:meingpt:api

## Data protection and sovereignty

### DATA-01: Hosting location and data residency

Judgment rule: Record country or region separately for chat storage, files and indexes, model inference, backups, logs and telemetry, and support access. Name the cloud provider. Record whether residency is default, a paid option or plan-dependent. "EU data boundary" programmes are recorded with their documented exceptions.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Hosting is region-selectable, but storage, model processing and remote support must be scoped separately.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Glean Hosted regional single-tenant hosting included; Customer Hosted and provider regions remain contract/key choices; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- storage_region — Where are chats, files and indexes stored? [partial]: Tenant storage and index follow the selected isolated GCP/AWS deployment; the public GCP list includes Netherlands, Belgium and Frankfurt. Actual contracted country was not selected. Sources: glean:glean:deploy, glean:glean:regions, glean:glean:r2-core-entitlements.
- inference_region — Where do model calls run, per provider? [partial]: Model routes depend on cloud and key mode; GCP/AWS Customer Key has cross-cloud restrictions. The subprocessor list allows customer-selected provider locations but does not establish every model remains in EU/CH. Sources: glean:glean:models, glean:glean:subprocessors, glean:glean:r2-core-entitlements.
- backups_logs_region — Where are backups, logs and telemetry? [partial]: Deployment documentation lists backups up to seven days but no full country map for backups, telemetry and central services was established. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements.
- support_access_region — From where can vendor staff access data? [supported]: The subprocessor list names the Indian affiliate for remote support/security/debugging; the SLA names California and Bangalore support locations. Sources: glean:glean:subprocessors, glean:glean:sla, glean:glean:r2-core-entitlements.
- swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Region and deployment pages were checked; Swiss hosting, exact backup/log/telemetry geography and all model-provider regional exceptions were not established.
- residency_plan — Which plan or option provides residency? [partial]: Both vendor-hosted and customer-cloud modes offer region selection. Prices, thresholds and per-model regional conditions remain contractual. Sources: glean:glean:deploy, glean:glean:terms, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:deploy, glean:glean:regions, glean:glean:r2-core-entitlements, glean:glean:models, glean:glean:subprocessors, glean:glean:sla, glean:glean:terms

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Germany platform storage and model-specific EU/global routes must be scoped separately.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- inference_region: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions.
- backups_logs_region: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified.
- residency_plan: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers.
- Unverified support_access_region, swiss_hosting: No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found.

- storage_region — Where are chats, files and indexes stored? [supported]: Hetzner Germany hosts chats, accounts, documents and cloud indexes; register identifies Nürnberg/Falkenstein. Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors.
- inference_region — Where do model calls run, per provider? [partial]: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa.
- backups_logs_region — Where are backups, logs and telemetry? [partial]: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:dpa.
- support_access_region — From where can vendor staff access data? [unknown]: From where can vendor staff access data? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found.
- swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found.
- residency_plan — Which plan or option provides residency? [partial]: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa, meingpt:meingpt:dpa-page

### DATA-02: Deployment options

Judgment rule: Record multi-tenant SaaS, dedicated single-tenant instance, deployment in the customer's cloud account, on-premise and air-gapped as separate options with plan and availability. Record which features are missing in each mode, who operates it, and the documented seat or contract threshold for each mode, which can differ from the enterprise plan threshold (e.g. dedicated SaaS from 2,000 seats, own cloud from 5,000). A local-network connector or gateway that reaches on-prem data from a vendor-hosted platform is KNOW-03, not on-premise deployment.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Glean documents dedicated vendor hosting and Glean-operated deployment in customer cloud accounts.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Glean Hosted single tenant; separately contracted Customer Hosted private-cloud configuration under Core Suite/Enterprise Flex; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- multi_tenant_saas — Is a shared SaaS offered? [unsupported]: Deployment documentation explicitly says Glean uses single-tenant infrastructure in both supported modes. This is not a shared tenant offer. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: Glean Hosted runs isolated customer infrastructure in Glean cloud accounts; the public guide gives no numerical seat threshold. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- customer_cloud — Can it run in the customer's own cloud account, from what size? [supported]: Customer Hosted, formerly Cloud-Prem, runs a Glean-managed tenant in customer GCP or AWS. Glean handles upgrades and keeps support access; seat/contract minimum is not published. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.
- on_premise — Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? The deployment guide and terms describe supported cloud accounts, not a whole-platform on-premises or air-gapped entitlement. Numerical minimums for each mode were not found.
- air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? The deployment guide and terms describe supported cloud accounts, not a whole-platform on-premises or air-gapped entitlement. Numerical minimums for each mode were not found.
- mode_feature_gaps — Which features are missing outside SaaS? [partial]: The guide describes the same product in both modes, but key/provider matrices document cloud and feature differences. Customer Hosted cannot be independently patched or re-architected by the customer. Sources: glean:glean:deploy, glean:glean:key-matrix, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:key-matrix

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

SaaS is offered; terms permit individually agreed on-premise use, while Outpost is a connector.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace, meinGPT Outpost local connector; version=Public documentation checked 2026-10-21; plan=Public SaaS; on-premise only if specifically contracted; add_ons=none stated; deployment_mode=not specified; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- on_premise: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public.
- mode_feature_gaps: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list.
- Unverified dedicated_instance, customer_cloud, air_gapped: Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.

- multi_tenant_saas — Is a shared SaaS offered? [supported]: The public web workspace and shared organization API limits establish the managed SaaS offer. Sources: meingpt:meingpt:terms, meingpt:meingpt:api.
- dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
- customer_cloud — Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
- on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public. Sources: meingpt:meingpt:terms.
- air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes.
- mode_feature_gaps — Which features are missing outside SaaS? [partial]: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list. Sources: meingpt:meingpt:sandbox.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:terms, meingpt:meingpt:api, meingpt:meingpt:sandbox

### DATA-03: Training use and provider retention

Judgment rule: Record whether customer content trains vendor or provider models, by plan and default; zero-data-retention arrangements with model providers; abuse-monitoring retention and human review; and the model provider's terms that apply. A "no training" claim on a marketing page is `vendor-claimed` until the contract or DPA says so.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

The AI Addendum prohibits model training and scopes provider retention commitments to Glean-key use, with exceptions.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Any contracted plan incorporating the AI Addendum; Glean model key unless Customer Key explicitly discussed; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- vendor_training — Does the vendor train on customer content? [supported]: AI Addendum section 3(a)(i) prohibits Glean from using Customer Data to train, retrain, improve or fine-tune AI Models. Sources: glean:glean:ai-addendum.
- provider_training — Do model providers train on it under this product's contracts? [supported]: For Glean model-key service, Glean contracts with providers to prohibit that training. Customer Key access remains the customer responsibility under section 4. Sources: glean:glean:ai-addendum.
- provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: Glean-key section 3(b) prohibits stored/logged inputs and outputs except legal or trust-and-safety necessity. The Data Analysis guide also describes up to 30-day retention for abuse-flagged files. Sources: glean:glean:ai-addendum, glean:glean:analysis.
- zero_retention — Is zero data retention available, and on which plan? [partial]: Zero-day retention is a contractual Glean-key commitment subject to law and trust/safety exceptions; it is not a blanket guarantee for Customer Key or every file-processing tool. Sources: glean:glean:ai-addendum, glean:glean:analysis.
- human_review — Can provider staff review content? [unknown]: Can provider staff review content? The AI Addendum and Data Analysis security text were checked; provider human-review access under each exception was not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:ai-addendum, glean:glean:analysis

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

DPA 2.0.1 prohibits training and marks conditional AI services for no permanent provider content copy.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- provider_retention: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified.
- zero_retention: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version.
- Unverified human_review: Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide.

- vendor_training — Does the vendor train on customer content? [supported]: Section 5(5) restricts processing to service delivery and excludes other purposes. Sources: meingpt:meingpt:dpa.
- provider_training — Do model providers train on it under this product's contracts? [supported]: Section 5(5) states no subprocessor uses customer data to train its own AI model. Sources: meingpt:meingpt:dpa.
- provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified. Sources: meingpt:meingpt:dpa.
- zero_retention — Is zero data retention available, and on which plan? [partial]: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version. Sources: meingpt:meingpt:dpa.
- human_review — Can provider staff review content? [unknown]: Can provider staff review content? Unknown. Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:dpa

### DATA-04: Retention and deletion

Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

User-facing chat/file deletion and contract-end obligations are documented; default and effective admin retention remain unknown.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex user history controls and applicable Terms/DPA; default/effective configured retention and shared-link lifetime unverified; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- User-facing deletion does not establish erasure from every retained copy. Default/effective configured retention, shared-link lifetime and contract-end completion timing remain unknown.

- default_retention — What is retained and for how long by default? [unknown]: Default content retention is unknown. Chat Sharing states a fixed 30-day conversation/link lifetime, while Chat History describes organization-configured periods. The relationship between shared links, stored chats, uploads and other retained copies was not reconciled; no universal default is inferred.
- admin_retention — Can admins set retention periods? [unknown]: The history guide lists Off, 30, 90, 180 and 365 days, but the sharing guide states a fixed 30-day conversation/link lifetime. The effective scope of admin settings versus shared-link/stored-chat retention remains unresolved, so a verified configurable retention entitlement is not asserted.
- user_deletion — Can users delete their chats and files permanently? [partial]: The history guide lets users remove chats from their history; the upload guide allows file removal before the first query or by deleting the chat afterward. Permanent removal from every copy, backup or event log was not established. Sources: glean:glean:history, glean:glean:uploads, glean:glean:r2-core-entitlements.
- contract_end_deletion — What is deleted at contract end, and when? [partial]: Terms section 12.3 and DPA section 7 require deletion at termination subject to legal retention. No fixed completion interval or destruction certificate was established. Sources: glean:glean:terms, glean:glean:dpa, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:history, glean:glean:uploads, glean:glean:r2-core-entitlements, glean:glean:terms, glean:glean:dpa, glean:glean:sharing

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Ordinary chat removal archives; admin retention and contractual deletion use different mechanisms.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- user_deletion: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls.

- default_retention — What is retained and for how long by default? [supported]: Chat/file data stays until instructed deletion; UI Chat löschen archives. Text translations remain until user deletion; document translations persist until account/workspace deletion. Sources: meingpt:meingpt:flow, meingpt:meingpt:translation.
- admin_retention — Can admins set retention periods? [supported]: Release 2.67.0 adds disabled-by-default deletion periods for chats, meetings and automation runs, with a 24-hour wait before a new/shorter period applies. Sources: meingpt:meingpt:changes.
- user_deletion — Can users delete their chats and files permanently? [partial]: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls. Sources: meingpt:meingpt:flow, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt:translation.
- contract_end_deletion — What is deleted at contract end, and when? [supported]: DPA section 12 requires return or requested deletion, including backups, within 30 days after termination or an agreed export window; statutory retention exceptions apply and proof is available on request. Sources: meingpt:meingpt:dpa.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:flow, meingpt:meingpt:translation, meingpt:meingpt:changes, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt:dpa

### DATA-05: Sub-processors and foreign-law exposure

Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

A dated processor list includes US providers and Indian remote support, with DPA transfer and change terms.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex under applicable public Terms, signed DPA and Order Form; no bespoke contract examined; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- subprocessor_list — Is a dated sub-processor list published? [supported]: Public list last updated July 28, 2026 identifies infrastructure, model, support and search subprocessors. Sources: glean:glean:subprocessors, glean:glean:r2-core-entitlements.
- subprocessor_countries — Which countries do sub-processors operate in? [supported]: The table lists US provider entities and India for Glean Search Technologies remote support; selected cloud/provider processing locations can differ. Sources: glean:glean:subprocessors, glean:glean:r2-core-entitlements.
- change_notification — Are customers notified of sub-processor changes? [supported]: DPA section 9 specifies at least 30 days notice before a new processor and a 30-day objection period, with a scoped termination remedy if unresolved. Sources: glean:glean:dpa, glean:glean:r2-core-entitlements.
- parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The Terms identify Glean Technologies, Inc. as a Delaware corporation. A separate parent entity was not established. Sources: glean:glean:terms, glean:glean:r2-core-entitlements.
- transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [supported]: The DPA incorporates EU SCCs, Swiss-recognized clauses and the UK Addendum for applicable transfers; SCC law/jurisdiction is Ireland. Sources: glean:glean:dpa, glean:glean:r2-core-entitlements.
- government_access_policy — Is there a published government-access or transparency policy? [unknown]: Is there a published government-access or transparency policy? DPA, processor list and privacy page were checked. A separate government-access/transparency-request policy was not established; no legal exposure verdict is made.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:subprocessors, glean:glean:r2-core-entitlements, glean:glean:dpa, glean:glean:terms

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

DPA and processing register name providers, conditional use and advance change notices.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- parent_jurisdiction: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified.

- subprocessor_list — Is a dated sub-processor list published? [supported]: DPA Annex 4 is dated 24 September 2026; live function/region register is also public. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors.
- subprocessor_countries — Which countries do sub-processors operate in? [supported]: Contract entities include Germany, Netherlands, Slovenia, Luxembourg, France, Ireland and Finland. Processing register names Germany platform, France backups, Finland, Ireland, Sweden/France and Frankfurt inference routes; EU symbol is processing, not ownership. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors.
- change_notification — Are customers notified of sub-processor changes? [supported]: Section 9 requires notice before additions/replacements and gives two weeks to object on important data-protection grounds, with specified termination rights. Sources: meingpt:meingpt:dpa.
- parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified. Sources: meingpt:meingpt:terms, meingpt:meingpt:subprocessors.
- transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA section 4(3) uses GDPR Article 45 adequacy or Article 46 safeguards for disclosed/instructed transfers; it does not promise a blanket absence of third-country processing. Sources: meingpt:meingpt:dpa.
- government_access_policy — Is there a published government-access or transparency policy? [supported]: Section 7 requires notification where lawful, review/challenge of disproportionate requests, minimization and no compliance with unrecognized third-country requests. Sources: meingpt:meingpt:dpa.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors, meingpt:meingpt:terms

### DATA-06: Contracts and regulatory coverage

Judgment rule: Record DPA availability and form (click-through, negotiable), reference to Swiss revDSG and GDPR, governing law and court, EU AI Act documentation (provider or deployer role, transparency materials), and sector-specific materials (FINMA outsourcing, banking secrecy, public sector). No compliance verdict.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Public contractual and AI-law materials are available, with Swiss/EU data-law scope.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex applicable public Terms/DPA/AI Addendum; signed Order Form controls actual coverage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- dpa — Is a DPA available, and is it negotiable? [supported]: A public DPA form takes effect when signed and can sit under a mutually accepted agreement; negotiability was not tested. Sources: glean:glean:dpa, glean:glean:r2-core-entitlements.
- revdsg_gdpr — Does the DPA cover revDSG and GDPR? [supported]: The DPA defines applicable data-protection law to include Switzerland and GDPR and describes Swiss transfer clauses. Applicability depends on the processing. Sources: glean:glean:dpa, glean:glean:r2-core-entitlements.
- governing_law — Which law and court govern the contract? [partial]: Main Terms section 13.1 specifies New York and US law; SCCs select Ireland for their own governing law/jurisdiction. A specific court for the main contract was not established. Sources: glean:glean:terms, glean:glean:dpa, glean:glean:r2-core-entitlements.
- ai_act_materials — Is EU AI Act documentation provided? [partial]: The AI Addendum includes applicable EU AI Act commitments and allocation of customer/provider responsibilities; a full procurement technical file was not retrieved. Sources: glean:glean:ai-addendum, glean:glean:r2-core-entitlements.
- sector_materials — Are FINMA or other sector materials provided? [partial]: The public legal index links HIPAA BAA forms for Glean as Business Associate and as Subcontractor; actual coverage depends on the applicable agreement. The AI Addendum describes assurance commitments. FINMA/banking-secrecy outsourcing materials were not established. Sources: glean:glean:r3-legal-index, glean:glean:ai-addendum, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:dpa, glean:glean:r2-core-entitlements, glean:glean:terms, glean:glean:ai-addendum, glean:glean:r3-legal-index

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

A public GDPR DPA and German-law terms are available; sector coverage needs qualification.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- dpa: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised.
- revdsg_gdpr: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found.
- ai_act_materials: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established.
- sector_materials: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found.

- dpa — Is a DPA available, and is it negotiable? [partial]: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa.
- revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found. Sources: meingpt:meingpt:dpa.
- governing_law — Which law and court govern the contract? [supported]: DPA section 13 uses German law; terms choose the competent court at the vendor seat. Sources: meingpt:meingpt:dpa, meingpt:meingpt:terms.
- ai_act_materials — Is EU AI Act documentation provided? [partial]: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established. Sources: meingpt:meingpt:prices.
- sector_materials — Are FINMA or other sector materials provided? [partial]: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found. Sources: meingpt:meingpt:prices.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa, meingpt:meingpt:terms, meingpt:meingpt:prices

### DATA-07: Certifications and attestations

Judgment rule: Record each certificate or report separately: ISO 27001, 27017, 27018, 27701, 42001; SOC 2 Type I/II with period; BSI C5; TISAX; national schemes. Record issuer, scope (which product and entity), validity and access route. A cloud provider's certificate does not certify the product.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

SOC 2 and ISO badges are vendor claims; issuer, report scope and validity were not independently checked.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect compliance material; vendor badges only, certificate/report scope and validity unverified; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- No evidence is certificate-verified. Cloud-provider certificates are not treated as Glean certificates.

- iso_27001 — ISO 27001 with scope and validity? [partial]: Glean claims ISO 27001 on its security page. The actual certificate, issuer, service scope and validity dates were not obtained. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements.
- soc2 — SOC 2 type, period and covered service? [partial]: Glean claims SOC 2 Type II, but auditor, examination period and exact covered service were not verified from a report. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements.
- c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? The public security page and trust.glean.com were checked; trust report content was inaccessible. BSI C5, independent pentest summaries and certificate/report validity were not established.
- other_certifications — Which other certificates (27701, 42001, TISAX)? [partial]: The security page lists ISO 42001, HIPAA and TX-RAMP Level 2. These are vendor assertions, not verified certificates in this profile. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements.
- report_access — How can customers obtain reports? [partial]: Security and accessibility material direct evaluators to the public Trust Center, whose report content was not readable without further access. Sources: glean:glean:security-page, glean:glean:accessibility, glean:glean:r2-core-entitlements.
- pentest — Are independent penetration test summaries available? [unknown]: Are independent penetration test summaries available? The public security page and trust.glean.com were checked; trust report content was inaccessible. BSI C5, independent pentest summaries and certificate/report validity were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:security-page, glean:glean:r2-core-entitlements, glean:glean:accessibility

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

ISO and penetration-test documents are advertised behind email access; certificates were not independently verified.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- iso_27001: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim.
- c5: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service.
- pentest: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved.
- Unverified soc2, other_certifications: SOC 2 and other product attestations were not established. No email-gated report was requested.

- iso_27001 — ISO 27001 with scope and validity? [partial]: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim. Sources: meingpt:meingpt:dpa, meingpt:meingpt:trust.
- soc2 — SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested.
- c5 — BSI C5 attestation? [partial]: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service. Sources: meingpt:meingpt:subprocessors.
- other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested.
- report_access — How can customers obtain reports? [supported]: The trust centre asks for email-based access for ISO and SySS 2025 penetration-test documents. Sources: meingpt:meingpt:trust.
- pentest — Are independent penetration test summaries available? [partial]: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved. Sources: meingpt:meingpt:trust.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:dpa, meingpt:meingpt:trust, meingpt:meingpt:subprocessors

### DATA-08: Encryption and key control

Judgment rule: Record encryption at rest and in transit, customer-managed keys (BYOK/HYOK), key location, and private networking (private link, IP allow-lists, VPN).

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Encryption, isolation and network controls are documented. Customer-managed keys are supported for Customer Hosted AWS; other key-custody scopes remain unverified.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect encryption and single-tenant Glean Hosted; separately contracted Customer Hosted network configuration; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- encryption_at_rest — Is data encrypted at rest? [supported]: Deployment comparison documents AES-256 at rest and TLS in transit for both deployment modes. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements.
- customer_managed_keys — Can the customer manage or hold the keys? [supported]: For Customer Hosted AWS, Glean supports KMS customer-managed encryption keys owned and controlled by the customer. The FAQ recommends default managed keys; Glean Hosted/GCP key custody and commercial prerequisites were not established. Sources: glean:glean:r4-aws-cmk-faq, glean:glean:r4-aws-key-control.
- private_networking — Is private connectivity or IP restriction available? [supported]: IP-based access controls and private connectivity for on-prem connectors are documented; customer AWS supports local VPC endpoints. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements.
- tenant_isolation — How are customers separated in shared SaaS? [supported]: Each deployment uses isolated single-tenant infrastructure, including the Glean-managed customer-cloud option. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25.

Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r4-aws-cmk-faq, glean:glean:r4-aws-key-control

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Encryption and logical tenancy are documented; key and private-networking details remain incomplete.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business/Enterprise hosted workspace; CMK entitlement excluded from verified findings; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- CMK is an access/entitlement gap, not an absent capability.

- encryption_at_rest — Is data encrypted at rest? [supported]: Security guide states AES-256 at rest and TLS 1.3; DPA Annex 3 includes encryption at rest/transit. Sources: meingpt:meingpt:security, meingpt:meingpt:dpa.
- customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Unknown for Business or Enterprise. The security FAQ says Customer Managed Keys are on request but does not identify an eligible tier, price, key custody or location. No plan-scoped CMK commitment was verified.
- private_networking — Is private connectivity or IP restriction available? [unknown]: Is private connectivity or IP restriction available? Unknown. A private-link/IP allowlist/VPN product entitlement was not established; Outpost outbound TLS is a source connector rather than a private SaaS endpoint.
- tenant_isolation — How are customers separated in shared SaaS? [partial]: DPA Annex 3 specifies logical tenant separation and network segmentation; no independent isolation test was run. Sources: meingpt:meingpt:dpa.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:security, meingpt:meingpt:dpa

### DATA-09: Professional secrecy

Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

General DPA confidentiality and provider/support access are documented; a specific German or Swiss professional-secrecy undertaking remains unverified.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex public Terms/DPA confidentiality; no verified professional-secrecy-specific package; add_ons=none stated; deployment_mode=not specified; region=Selected hosting/provider regions; listed India support affiliate; no DE/CH-specific undertaking verified; os=not specified.

Limitations:
- DPA confidentiality and no-training provisions alone do not establish a professional-secrecy undertaking.
- No legal suitability or compliance conclusion.

- secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: Glean DPA section4 binds authorized personnel to confidentiality or statutory duties, but no signed/signon German §203 StGB or Swiss Art321 StGB professional-secrecy undertaking was retrieved. General DPA confidentiality is not treated as that undertaking.
- subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: DPA section9 requires no-less-protective written subprocessor obligations and necessary access. No flow-down of a specific §203/Art321 professional-secrecy undertaking was established.
- secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No publicly documented professional-secrecy-specific plan, dedicated package, paid add-on, minimum or regional contract entitlement was established in legal pages, administration docs, pricing or targeted first-party search.
- content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Contractually authorized Glean personnel and necessary subprocessors may process customer personal data; the processor list names India remote support/security/debugging and model/hosting providers. Model routes receive prompts/context for inference. Exact plaintext privileges, exceptional support approval, provider human-access rights and their differences by key/deployment mode are not fully established. Sources: glean:glean:dpa-confidentiality, glean:glean:subprocessors, glean:glean:key-matrix, glean:glean:ai-addendum, glean:glean:r2-core-entitlements.
- secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: A public DPA, AI Addendum, deployment docs and processor list were retrieved. No public §203/Art321 contract template, dedicated professional-secrecy data-flow statement or professional-body guidance for this offer was established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:dpa-confidentiality, glean:glean:subprocessors, glean:glean:key-matrix, glean:glean:ai-addendum, glean:glean:r2-core-entitlements

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

The base AGB contains conditional professional-secrecy duties. Eligibility and executed terms of the separately marketed Governance addendum remain unknown.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked2026-10-21; plan=Business/Enterprise customer contracts incorporating AGB section12(4); only the base-terms obligation is assessed; add_ons=Separate Governance addendum excluded from verified entitlement; contract required; deployment_mode=multi-tenant-saas; region=Germany/EU platform; model route and deployment exceptions apply; os=not specified.

Limitations:
- The base-terms duties and a separately executed Governance addendum are separate legal documents. No claim that one depends on purchase of the other is made.

- secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [partial]: For contracts incorporating the published AGB, section12(4) applies when processed data fall under professional secrecy, including §203. It imposes indefinite confidentiality, access only as necessary to perform services and acknowledgement of criminal duties. The clause states no Governance prerequisite. It does not establish a separately executed addendum or Swiss Art321 coverage. Sources: meingpt:meingpt:secrecy-contract-rev2.
- subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [partial]: Section12(4) requires staff/subcontractors who can access covered data to be bound in at least text form. Subcontracting and services outside the EU require text consent, deemed granted for known providers at contract start. Provider-specific executed undertakings were not retrieved. Sources: meingpt:meingpt:secrecy-contract-rev2.
- secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: Unknown whether the separate Governance §203 addendum is available with self-service Business or only a contracted platform offer. The calculator lists it under Governance at EUR1.35/user/month annually, but this is not proof of eligibility or a fee for the base AGB duties. Sources: meingpt:meingpt:prices-rev2.
- content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The base AGB restrict knowledge of covered data to what is necessary for the contracted service. The clause does not promise that staff or model providers can never see plaintext. Agreement-specific access restrictions beyond section12(4) were not verified. Sources: meingpt:meingpt:secrecy-contract-rev2.
- secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [partial]: The public AGB section12(4) is the verified contract text. A separately executed/template Governance addendum and provider-by-provider undertakings were not obtained. Sources: meingpt:meingpt:secrecy-contract-rev2.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:secrecy-contract-rev2, meingpt:meingpt:prices-rev2

## Commercials and vendor

### VEN-01: Pricing model and list prices

Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Glean publishes pricing mechanics and usage tables, while contracted seat fees remain quote-only.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Unspecified contracted plan unless Core Suite, Enterprise Flex, key mode or add-on is named below; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- pricing_unit — What is the pricing unit? [supported]: Core Suite is per user/month plus committed Model Hub Usage. Enterprise Flex combines seats with pooled FlexCredits; legacy Enterprise terms differ. Sources: glean:glean:core-price, glean:glean:flex-price.
- list_prices — What are list prices per plan, with date and currency? [partial]: On 2026-10-21 no numerical Core Suite/Enterprise Flex seat or platform fee was established. Public model token-rate and credit-consumption tables are available; they are not a complete subscription quote. Sources: glean:glean:core-price, glean:glean:flex-price.
- included_usage — What usage is included? [partial]: Core Suite includes platform/search and human-scale APIs in seats; LLM APIs and advanced work consume model usage. Flex uses plan-specific included capabilities and shared credits. Sources: glean:glean:core-price, glean:glean:flex-price.
- add_ons — Which features cost extra? [partial]: Protect+ is an add-on and Premium Support is paid; Model Hub usage is separate. Public add-on seat/contract fees were not established. Sources: glean:glean:protect, glean:glean:sla.
- overage — What do usage beyond limits and premium models cost? [partial]: Core Suite usage follows provider/model API rates with an upfront commitment; machine-scale API use may cost extra. Flex uses credit rate cards. Currency price per contracted FlexCredit is unverified. Sources: glean:glean:core-price, glean:glean:flex-price.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:core-price, glean:glean:flex-price, glean:glean:protect, glean:glean:sla

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Self-service Business costs EUR29/user/month excluding VAT and includes standard-model use. Enterprise and platform-module pricing are outside this scoped offer.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business, monthly billing only; contracted Enterprise/platform calculator excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- The progressive platform calculator is not used as a Business tariff. Its contract eligibility remains outside this finding.

- pricing_unit — What is the pricing unit? [supported]: Business is sold per user per month through self-service Stripe checkout. Premium/reasoning models, API use and meeting-bot recordings are separately metered. Sources: meingpt:meingpt:billing-rev2.
- list_prices — What are list prices per plan, with date and currency? [supported]: Self-service Business is EUR29/user/month, excluding VAT, on monthly billing. No annual discount or progressive marginal tiers are applied to this offer. Sources: meingpt:meingpt:billing-rev2.
- included_usage — What usage is included? [partial]: Standard-model use in Business is unlimited according to the billing guide. Premium/reasoning models, API and meeting bots remain additional; the exact standard-model catalog and any applicable workload restrictions are not fixed by this page. Sources: meingpt:meingpt:billing-rev2.
- add_ons — Which features cost extra? [unknown]: Unknown for self-service Business. The separate platform calculator has Governance/Outpost modules, but their Business eligibility and package prices were not established.
- overage — What do usage beyond limits and premium models cost? [partial]: Business standard models do not consume additional billed usage under the billing guide. Premium/reasoning, API and meeting-bot use draw on workspace credit; meeting bots cost EUR0.80/audio hour. Other route-specific charges depend on the selected service. Sources: meingpt:meingpt:billing-rev2.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:billing-rev2

### VEN-02: Scenario cost

Judgment rule: Price three workloads for 12 months: 200, 1,000 and 5,000 users with a disclosed light/regular/power usage mix, in CHF and EUR excluding VAT. Include licences, platform fees, add-ons, model usage and, for self-hosted options, a stated operating assumption. Separate fixed, variable, included and unknown costs. No invented discounts.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Core Suite publishes model tariffs, but no public unique routine Auto model or fixed fee; a separate direct-provider Customer Key component is calculable.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Universal Model Key usage unpriced without a fixed/recommended routine model; separate Customer Key direct-API proxy; Enterprise Flex quote/pool unknown; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- The priced Customer Key component is an assumption for direct provider payment, not a complete Glean price or a forecast of Auto routing.
- No signed order, fixed fee, actual tenant defaults or task usage fixture.

- cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4,2026-10-21:12 months exVAT,list prices,no invented discounts;60% light100/30% regular400/10% power1500 messages/user/month =>330;3000 input+600 output tokens/message. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Direct-provider Customer Key comparison uses gpt-6-luna effort none atUSD0.10 input/USD0.50 output per1M,no cache =>USD2.376/user/year. This proxy is not a Glean Universal Model Key tariff/default. For200 Customer Key users: identified direct-model component USD475.20/EUR423.72/CHF391.39 + unknown Core Suite seat fee, Glean-family usage, support/cloud costs. Universal Model Key total and Enterprise Flex total remain unknown. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-customer-default-example, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort, glean:glean:fx-ecb.
- cost_1000 — Year-one cost at 1,000 users? [partial]: Same v1.4 assumptions:1000 Customer Key users, identified direct-model component USD2376/EUR2118.59/CHF1956.94 + unknown seat/Glean-family/support/cloud costs. Not an enterprise quote; Universal Model Key and Flex totals remain unknown. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort, glean:glean:fx-ecb.
- cost_5000 — Year-one cost at 5,000 users? [partial]: Same v1.4 assumptions:5000 Customer Key users, identified direct-model component USD11880/EUR10592.96/CHF9784.71 + unknown seat/Glean-family/support/cloud costs. Not an enterprise quote; Universal Model Key and Flex totals remain unknown. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort, glean:glean:fx-ecb.
- variable_share — Which part depends on usage? [partial]: Core Suite publishes input/output tariffs. Universal Model Key defaults to Balanced Auto, a policy choosing model and effort per request; recommendations are shown in the admin UI, not as a unique public routine model. The Customer Key guide calls GPT5.6 Luna an example, not a recommendation. Under v1.4, vendor-billed usage remains unknown; only the separate direct-API proxy is costed. Enterprise Flex has different mode/credit accounting. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-customer-default-example, glean:glean:r2-flex-entitlements, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort.
- unknown_parts — Which costs could not be priced? [supported]: Unknown: seat/platform quotes, Universal Model Key realized model mix and Auto/tool overhead, FlexCredit purchase price and task consumption, Glean-family calls on Customer Key, Protect+/support fees, cloud operations and implementation. No zero fixed fee, fictitious discount or vendor-billed proxy substitution. Exchange rate is known and explicitly stated; quote-only total is not calculated. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:deploy, glean:glean:fx-ecb.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:r2-core-entitlements, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-customer-default-example, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort, glean:glean:fx-ecb, glean:glean:r2-flex-entitlements, glean:glean:deploy

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Business-only seat floors are EUR69600 / EUR348000 / EUR1740000 for200/1000/5000 users over12months, each plus unknown workload and contract components.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business at EUR29/user/month, paid monthly for12months; Business standard-chat floor only; add_ons=No paid add-ons included; required extras unknown; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- ALM-14 shared cost assumptions v1.4, 2026-10-21:12months, list prices, excluding VAT;60% light100,30% regular400,10% power1500 messages/user/month;3000 input and600 output tokens/message. Weighted330messages,0.99M input/0.198M output per user/month. Token mix is used only on separately billed routes; this Business standard-chat floor has included usage.
- ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Vendor currency EUR is primary. Contract-specific extras remain unknown.

- cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 200 users over12months: from EUR69600.00 / CHF64289.52 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.
- cost_1000 — Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 1000 users over12months: from EUR348000.00 / CHF321447.60 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.
- cost_5000 — Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 5000 users over12months: from EUR1740000.00 / CHF1607238.00 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx.
- variable_share — Which part depends on usage? [partial]: Business standard-model chat is included. A model-preserving workload outside that standard catalog, premium/reasoning models, API and meeting-bot charges cannot be quantified without the actual route and contract; the variable remainder stays unknown. No provider proxy or progressive-platform tariff is substituted. Sources: meingpt:meingpt:billing-rev2.
- unknown_parts — Which costs could not be priced? [partial]: Business eligibility for200/1000/5000 users, standard-model mapping, premium/tool use, required Governance/Outpost, rollout and Enterprise services remain unknown. No progressive-platform amount is mixed into the Business floor. Sources: meingpt:meingpt:billing-rev2.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx

### VEN-03: Evaluation access

Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Public material supports product evaluation, but no unassisted business trial was established.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex prospective customer evaluation; public demo path, no verified self-serve trial entitlement; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.
- Core Suite/Enterprise Flex trial and evaluation entitlements were not publicly verified; a demo CTA is not proof of a mandatory sales gate.

- free_tier — Is there a free tier for business use? [unknown]: Is there a free tier for business use? The live product/security site, documentation setup and pricing guides were checked. No public business free-tier entitlement, self-serve trial terms, card/duration/seat limits or SSO/connector trial scope was established. No sales contact or account registration was attempted.
- self_serve_trial — Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? The live product/security site, documentation setup and pricing guides were checked. No public business free-tier entitlement, self-serve trial terms, card/duration/seat limits or SSO/connector trial scope was established. No sales contact or account registration was attempted.
- trial_scope — Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? The live product/security site, documentation setup and pricing guides were checked. No public business free-tier entitlement, self-serve trial terms, card/duration/seat limits or SSO/connector trial scope was established. No sales contact or account registration was attempted.
- sales_gate — Does meaningful evaluation require sales contact? [partial]: Public Glean pages route prospective customers to Get a demo; meaningful tenant provisioning may require commercial access. This is not proof that every trial is sales-only. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:security-page, glean:glean:r2-core-entitlements

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

A self-serve 10-day trial exists, while several enterprise features still need enablement.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- free_tier: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace.
- trial_scope: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed.
- sales_gate: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made.

- free_tier — Is there a free tier for business use? [partial]: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace. Sources: meingpt:meingpt:billing.
- self_serve_trial — Is a self-serve business trial available? [supported]: 10 days, EUR 5 after phone verification, no payment details or automatic paid conversion, up to ten emailed invitees. Sources: meingpt:meingpt:billing.
- trial_scope — Do trials include SSO, connectors and admin features? [partial]: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed. Sources: meingpt:meingpt:billing.
- sales_gate — Does meaningful evaluation require sales contact? [partial]: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made. Sources: meingpt:meingpt:billing.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:billing

### VEN-04: Contract terms and pricing transparency

Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Contract periods and fees depend on orders, with cancellation restricted during the subscription term.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex under Order Form and public Terms; seat commitments/prices and selected currency contractual; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- minimum_commitment — What seat or spend minimum applies? [unknown]: What seat or spend minimum applies? Terms and pricing guides were checked; minimum seat/spend commitment and plan-specific currency invoicing remain unpriced.
- contract_length — What contract lengths are offered? [partial]: Terms define Subscription Term through the Order Form. No universal monthly or annual term is specified. Sources: glean:glean:terms, glean:glean:r2-core-entitlements.
- cancellation — How can the contract be cancelled or reduced? [supported]: Except contractual causes and remedies, customers cannot cancel during the subscription term; each order ends at expiry unless otherwise stated. Sources: glean:glean:terms, glean:glean:r2-core-entitlements.
- local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Terms default to USD or the currency in the order and allow Glean affiliates/resellers. CHF/EUR invoicing by a European entity was not confirmed. Sources: glean:glean:terms, glean:glean:r2-core-entitlements.
- transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified: public pricing units and consumption tables, but subscription fees, minimum commitments and purchased-credit prices need an order/quote. Sources: glean:glean:core-price, glean:glean:flex-price, glean:glean:terms, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:terms, glean:glean:r2-core-entitlements, glean:glean:core-price, glean:glean:flex-price

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Public price fields and German contract defaults exist; customer-specific terms and CHF invoicing remain open.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- minimum_commitment: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated.
- local_invoicing: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed.
- transparency_class: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs.

- minimum_commitment — What seat or spend minimum applies? [partial]: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated. Sources: meingpt:meingpt:prices.
- contract_length — What contract lengths are offered? [supported]: Public calculator has annual/monthly options; terms default to one year absent another agreement. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms.
- cancellation — How can the contract be cancelled or reduced? [supported]: Absent other terms, three months before term-end, text/email or admin cancellation; downgrades/user reductions effective following month, no current-month refund. Price changes require the stated notice/consent procedure. Sources: meingpt:meingpt:terms.
- local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed. Sources: meingpt:meingpt:terms.
- transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs. Sources: meingpt:meingpt:prices, meingpt:meingpt:billing.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:prices, meingpt:meingpt:terms, meingpt:meingpt:billing

### VEN-05: Source licence

Judgment rule: Record licence per component (client, server, connectors, hosted extensions) and revision. Distinguish OSI open source, source-available with restrictions (branding clauses, user caps), and closed. Repository visibility is not a licence classification. Licences change between releases: record the current terms, and never carry a fork's historical licence over to the upstream product or the reverse.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

The hosted platform is provided under restricted commercial terms; public SDK licences are separate.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex proprietary hosted/managed Service under Terms; no public core-source licence inferred; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- licence_type — Which licence applies to each component? [supported]: Terms grant subscription access and prohibit deriving source code, modifying or redistributing the Service. This establishes a proprietary service contract, not an OSI licence for the platform. Sources: glean:glean:terms, glean:glean:r2-core-entitlements.
- branding_restrictions — Do licence terms restrict branding or user counts? [supported]: Terms prohibit removing proprietary notices and limit use to licensed users/orders; no numerical standard user cap is given. Sources: glean:glean:terms, glean:glean:r2-core-entitlements.
- enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Platform terms and the public gleanwork organization were checked; a complete component licence inventory or separate open/closed enterprise edition split was not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:terms, glean:glean:r2-core-entitlements

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

The public AGB establish a commercial subscription/rental use licence with contract-limited rights. Public component source licences and a distinct enterprise source-edition mapping remain unverified.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- Contractual service-use rights do not establish the licence of every server/client/connector dependency.
- No public implementation repository or enterprise source-edition map was identified.

- licence_type — Which licence applies to each component? [partial]: SelectCode AGB describe the software as a subscription/rental and grant a non-exclusive use right limited to the contract term. Public display, adaptation, translation and decompilation of the software are restricted subject to statutory rights. This establishes the commercial service-use licence; a client/server/connector source-licence inventory and current implementation revision remain unpublished. Sources: meingpt:meingpt:terms-20261026.
- branding_restrictions — Do licence terms restrict branding or user counts? [partial]: AGB require purchased licences for majority-owned affiliates and give no independent right to sublicense or transfer usage rights. They restrict adapting the software. A numerical user cap or a component-specific branding licence is not established by these clauses. Sources: meingpt:meingpt:terms-20261026.
- enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. The public commercial terms describe rented software, but no public client/server/connector source licence or current repository revision was located. Repository visibility was not treated as a licence. Rechecked 2026-10-26 in Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. Official links and targeted first-party searches yielded no further plan-scoped specification for the remaining atom.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25.

Sources: meingpt:meingpt:terms-20261026

### VEN-06: Data export and exit

Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Workflow agent configurations are portable as JSON; full tenant chat/knowledge export remains unverified.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Governance import/export in seat; limited Auto ZIP export and complete organization exit separately unverified; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.
- Core Suite includes agent import/export, but limited Auto ZIP rollout and complete tenant-export entitlements remain unverified.

- chat_export — Can admins export all chats? [unknown]: Can admins export all chats? Agent export and contractual termination pages were checked. No trial admin export was run; all-chat export, knowledge/source completeness and a post-termination retrieval window were not established.
- assistant_export — Can assistants and prompts be exported in a reusable format? [supported]: Workflow-mode agent configuration exports to JSON and imports into another deployment; missing target tools must be reconfigured. Auto-mode ZIP export is limited availability for admins. Sources: glean:glean:builder, glean:glean:r2-core-entitlements.
- knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Agent export and contractual termination pages were checked. No trial admin export was run; all-chat export, knowledge/source completeness and a post-termination retrieval window were not established.
- export_format — Are formats documented and machine-readable? [supported]: Workflow exports use JSON; limited Auto exports contain spec.yaml and instructions.md in ZIP. Admin logs have CSV export. Sources: glean:glean:builder, glean:glean:audit, glean:glean:r2-core-entitlements.
- post_termination_window — How long can data be retrieved after termination? [unknown]: How long can data be retrieved after termination? Agent export and contractual termination pages were checked. No trial admin export was run; all-chat export, knowledge/source completeness and a post-termination retrieval window were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:builder, glean:glean:r2-core-entitlements, glean:glean:audit

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Individual downloads exist but a bulk chat export is explicitly unavailable.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- chat_export: Security FAQ explicitly says there is currently no function to export all chats at once.
- export_format: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export.
- post_termination_window: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it.
- Unverified assistant_export, knowledge_export: No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run.

- chat_export — Can admins export all chats? [unsupported]: Security FAQ explicitly says there is currently no function to export all chats at once. Sources: meingpt:meingpt:security.
- assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run.
- knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run.
- export_format — Are formats documented and machine-readable? [partial]: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export. Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export.
- post_termination_window — How long can data be retrieved after termination? [partial]: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it. Sources: meingpt:meingpt:terms, meingpt:meingpt:dpa.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export, meingpt:meingpt:terms, meingpt:meingpt:dpa

### VEN-07: Support and service levels

Judgment rule: Record support channels, languages (German, French, Italian), hours and time zone, local or regional presence, documented response times, uptime SLA and credits, public status page and incident history. Popularity is not a reliability score.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Support tiers are documented; a credited 99.9% SLA applies only to paid Premium Support.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Unspecified contracted plan unless Core Suite, Enterprise Flex, key mode or add-on is named below; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.

- support_channels — Which support channels are available on each plan? [supported]: The support portal is the channel eligible for response targets; Standard Support is included and Premium paid. Other channels do not have trackable SLA response times. Sources: glean:glean:sla.
- support_languages — Is support available in German, French or Italian? [partial]: The SLA explicitly provides a Japanese support option for Japan and names California/Bangalore operations; German/French/Italian language commitments were not established. Sources: glean:glean:sla.
- regional_presence — Is there a DACH or Swiss entity, team or partner? [unknown]: Is there a DACH or Swiss entity, team or partner? The SLA, site and status.glean.com were checked. The status URL returned HTTP 403, so incident history was not verified; DACH/Swiss support presence was not established.
- uptime_sla — Is there an uptime SLA with credits? [supported]: Paid Premium Support has 99.9% monthly uptime. Credits are 10% below 99.9% down to 99.0%, and 20% below 99.0%, subject to exclusions and claim deadlines. Sources: glean:glean:sla.
- status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? The SLA, site and status.glean.com were checked. The status URL returned HTTP 403, so incident history was not verified; DACH/Swiss support presence was not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:sla

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

German vendor support and a public incident history are documented; an uptime credit schedule was not found.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- support_channels: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated.
- Unverified support_languages, uptime_sla: Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage.

- support_channels — Which support channels are available on each plan? [partial]: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated. Sources: meingpt:meingpt:terms.
- support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage.
- regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: SelectCode GmbH contracts from Unterhaching, Germany. Sources: meingpt:meingpt:terms.
- uptime_sla — Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage.
- status_page — Is there a public status page with history? [supported]: Public status.meingpt.com lists the platform and historical incidents; uptime is not an SLA. Sources: meingpt:meingpt:status.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:terms, meingpt:meingpt:status

### VEN-08: Onboarding, training and adoption

Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings.

#### Glean

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Public training and templates exist; exact onboarding-service entitlements and prices remain open.

Availability: generally-available
Delivery: native
Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Library/templates and public Academy links; contracted onboarding and Premium Support separately scoped; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified.

Limitations:
- Documented findings only; unestablished atomic questions remain explicit gaps.
- Exact Academy access, included onboarding, language coverage and support/professional-services entitlement under the customer Order Form remain unknown.

- onboarding_service — Is guided onboarding included? [unknown]: Is guided onboarding included? Academy, agent library, SLA and legal service links were checked; included vendor-led onboarding, champion/adoption programme terms and localized end-user training were not established.
- user_training — Is end-user training offered, in which languages? [partial]: Glean documentation links self-paced Agent Builder training through Glean Academy; German/French/Italian course availability was not established. Sources: glean:glean:agents, glean:glean:r2-core-entitlements.
- use_case_library — Are role-based use cases and templates provided? [supported]: The internal Agent library and documented templates support reusable role/task examples. Sources: glean:glean:library, glean:glean:r2-core-entitlements.
- adoption_programme — Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Academy, agent library, SLA and legal service links were checked; included vendor-led onboarding, champion/adoption programme terms and localized end-user training were not established.
- service_cost — Which services cost extra? [partial]: Premium Support is priced separately under the SLA. The legal index directly lists the Technical Services Addendum and named Outcomes Packages. Those listings do not establish included onboarding or complete professional-services fees. Sources: glean:glean:sla, glean:glean:r3-legal-index, glean:glean:r2-core-entitlements.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:library, glean:glean:sla, glean:glean:r3-legal-index

#### meinGPT

Verification status: Agent cross-checked (agent-cross-checked)
Support: partial

Learning paths and business examples are built in; personal rollout services are quote-based.

Availability: generally-available
Delivery: native
Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified.

Limitations:
- onboarding_service: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised.
- user_training: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated.
- adoption_programme: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found.

- onboarding_service — Is guided onboarding included? [partial]: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised. Sources: meingpt:meingpt:prices.
- user_training — Is end-user training offered, in which languages? [partial]: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated. Sources: meingpt:meingpt:academy, meingpt:meingpt:audit.
- use_case_library — Are role-based use cases and templates provided? [supported]: Role/department personalization and business-use-case material are documented. Sources: meingpt:meingpt:academy.
- adoption_programme — Is there a champion or adoption programme? [partial]: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found. Sources: meingpt:meingpt:billing.
- service_cost — Which services cost extra? [supported]: Personal guidance is quote-only; terms bill services by time/person-days or individually agreed fixed price. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20.

Sources: meingpt:meingpt:prices, meingpt:meingpt:academy, meingpt:meingpt:audit, meingpt:meingpt:billing, meingpt:meingpt:terms

## Sources

### glean:glean:models

Supported LLMs. The Model Hub lists text and image models, manual choice and Auto routing, with provider availability dependent on key and cloud.

- URL: https://docs.glean.com/administration/llms
- Locator: Supported models; availability by hosting environment and provider
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:key-matrix

Feature availability by LLM key, provider, and cloud. Customer Key restricts cloud-provider routes and excludes Meeting Notes and podcast artifacts; some defaults must use the same provider.

- URL: https://docs.glean.com/administration/llm-key-feature-availability
- Locator: Provider and feature matrices
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:uploads

Upload files in Assistant. Uploads support Office documents, PDFs, images and text, with context-dependent file caps and OCR prerequisite.

- URL: https://docs.glean.com/user-guide/assistant/file-upload
- Locator: Formats; upload limits; security; limitations
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:r2-core-entitlements

Glean Core Suite entitlements and Model Hub rates. Core Suite separates included platform seats from Model Hub usage, names client/API surfaces, and publishes token rates.

- URL: https://docs.glean.com/glean-core-suite-pricing
- Locator: Seat capabilities, surfaces, APIs, Model Hub Usage and rate table updated10/20/2026
- Evidence kind: documented
- Source date: 2026-10-20
- Retrieved: 2026-10-21

### glean:glean:r3-october-rollout-migration

October 15, 2026 release, version 563. Auto policies require rollout opt-in from October 15 with GA scheduled October 29; Brave is the new search default and existing OpenAI search migrates from October 19.

- URL: https://docs.glean.com/release-notes/releases/2026-10-15-october-release
- Locator: AI & Model Updates, Auto mode policies; Deprecations & Sunsets, OpenAI Web Search
- Evidence kind: documented
- Source date: 2026-10-15
- Retrieved: 2026-10-21

### meingpt:meingpt:rates

Alle Modelle | MeinGPT Docs. Public EUR token and service rates include GPT-5 mini at EUR 0.30 input and EUR 2.40 output per million tokens.

- URL: https://meingpt.com/docs/admin-guide/pricing
- Locator: Text-generation, translation, images and other-functions tables
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:models-rev2

Modelle | MeinGPT Docs. Current documentation lists selectable non-Meta model families, per-chat selection and context-length routing; the lifecycle table contains no current selectable Meta model.

- URL: https://meingpt.com/docs/platform/models
- Locator: Model picker, model tables and own-LLM-key FAQ
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:lifecycle-rev2

Modell-Lifecycle | MeinGPT Docs. Active models, future retirement dates and automatic replacement rules are published.

- URL: https://meingpt.com/docs/admin-guide/model-lifecycle
- Locator: Phases, notice period and current-model table
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:deprecation

Model deprecation. Customer Key deprecation emails are specified at 60 and 15 days, with removal and replacement behavior.

- URL: https://docs.glean.com/administration/model-deprecation
- Locator: Customer Key notice schedule; deprecated models
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:release

October 15, 2026 release notes. Glean publishes dated release notes covering product and model changes.

- URL: https://docs.glean.com/release-notes/releases/2026-10-15-october-release
- Locator: Release entry
- Evidence kind: documented
- Source date: 2026-10-15
- Retrieved: 2026-10-21

### meingpt:meingpt:lifecycle

Modell-Lifecycle | MeinGPT Docs. Active models, future retirement dates and automatic replacement rules are published.

- URL: https://meingpt.com/docs/admin-guide/model-lifecycle
- Locator: Phases, notice period and current-model table
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:changes

Was wir zuletzt released haben | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. Release 2.67.0 on 18 October adds Gemini 4 Argon, retires named models and adds configurable deletion periods.

- URL: https://meingpt.com/changelog
- Locator: v2.67.0, model retirement and deletion periods
- Evidence kind: documented
- Source date: 2026-10-18
- Retrieved: 2026-10-21

### glean:glean:r2-flex-entitlements

Glean Enterprise Flex entitlements. Enterprise Flex separates seat allowances, metered client APIs/agent runs, included platform governance and annual Protect+/support add-ons.

- URL: https://docs.glean.com/glean-enterprise-flex-pricing
- Locator: Seats, Developer Tools, Platform, Protect+ and Premium Support
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:r2-auto-policy-and-cloud-conflict

Configure LLMs in the Model Hub. Balanced is the default Auto policy with per-request model choice; the AWS Vertex note conflicts with the supported-provider matrix and GCP-only Vertex setup heading.

- URL: https://docs.glean.com/administration/configure-llms
- Locator: Auto policies; AWS Vertex note; provider setup headings
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:models

Modelle | MeinGPT Docs. Users choose models per chat; automatic selection is based on context length; customer LLM keys and endpoints cannot be added.

- URL: https://meingpt.com/docs/platform/models
- Locator: Model picker, model tables and own-LLM-key FAQ
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:translation

Übersetzer | MeinGPT Docs. Default text translation uses Google Cloud Translate and document translation uses DeepL through EU endpoints; glossaries and layout preservation are documented.

- URL: https://meingpt.com/docs/platform/translation
- Locator: Engine/hosting, formats and glossary management
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:r4-open-model-inference

Glean open models by region. Universal Model Key open models are served through LLM providers under zero-retention agreements. Creator-region grouping is not inference location; the page states these models are hosted in the US.

- URL: https://docs.glean.com/administration/open-models-by-region
- Locator: Creator-region controls; Operational details
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### meingpt:meingpt:subprocessors

Subdienstleister & Verarbeitungsregionen | MeinGPT. The register separates Germany platform storage, France backups and provider-specific EU inference regions.

- URL: https://meingpt.com/sicherheit/subdienstleister
- Locator: Register by function and processing region
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:model-controls

Exclude or restrict models. Admins can restrict eligible models by department or IdP group, but default models cannot be restricted and hiding premium pickers does not block Auto.

- URL: https://docs.glean.com/administration/model-exclusion
- Locator: Department and team allow-lists; premium-model toggle
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:model-config

Configure LLMs in the Model Hub. Admins configure default models and department Auto policies.

- URL: https://docs.glean.com/administration/configure-llms
- Locator: Default models and Auto mode policies
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:restrictions

Restrict LLM access to content. Admins can exclude connectors, containers and documents from LLM use; changes may take up to one hour.

- URL: https://docs.glean.com/administration/assistant/configuration/content-restrictions
- Locator: Exclusion and inclusion rules
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:limits

Set usage limits and alerts. Core Suite and Enterprise Flex limits can alert or block later billable usage after the current run finishes; team defaults are not pooled budgets.

- URL: https://docs.glean.com/administration/management/usage/set-usage-limits-and-alerts
- Locator: Enforcement; organization, user, team and agent limits
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:config

Workspace-Konfiguration | MeinGPT Docs. Admins can restrict models by teams or people and supply workspace-wide instructions; denied API models return an error.

- URL: https://meingpt.com/docs/admin-guide/workspace-configuration
- Locator: Model access, default settings and additional chat context
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:limits

Nutzungslimits | MeinGPT Docs. Personal category budgets block new use at zero; running meeting bots can overrun limits and scheduled runs are outside personal categories.

- URL: https://meingpt.com/docs/admin-guide/usage-limits
- Locator: Usage levels, meeting limits and user consumption table
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:api

Einführung | MeinGPT Docs. Chat, embeddings, assistants, workflows and transcription APIs use bearer keys and published token rate limits; translation is UI-only.

- URL: https://meingpt.com/docs/api
- Locator: API overview, rate limits and errors
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:analysis

Data analysis overview. Uploaded spreadsheets can be analyzed in per-session sandboxes; indexed files can be truncated, and abuse-flagged files may be retained up to 30 days.

- URL: https://docs.glean.com/administration/assistant/data-analysis/about-data-analysis
- Locator: Known limitations; code interpreter security
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:pools

Datenquellen & RAG | MeinGPT Docs. Cloud pools index six source types in Germany, refresh every 15 minutes and share a 300 GB raw-data budget.

- URL: https://meingpt.com/docs/integrations/data-pools-rag
- Locator: Cloud-source table, connector comparison and normal-chat search
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:chat

Eingabefeld | MeinGPT Docs. Chat has stop, model choice, file upload, dictation and sharing links, with 50 files and 50 MB per non-image file.

- URL: https://meingpt.com/docs/platform/chats/eingabefeld
- Locator: Input controls, file limits, dictation and sharing
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:flow

Datenfluss bei MeinGPT Chats | MeinGPT Docs. Chat deletion archives content; prompts have provider-dependent processing, and platform data stays until instructed deletion.

- URL: https://meingpt.com/docs/privacy-security/faq-chats-datenfluss
- Locator: Processing steps, providers and deletion rights
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:sandbox

Code-Sandbox | MeinGPT Docs. Python/JavaScript analysis and Office generation run in an isolated Unikraft Cloud VM in Frankfurt, including for on-premise customers.

- URL: https://meingpt.com/docs/platform/code-sandbox
- Locator: Execution flow, hosting, lifetime and limitations
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:projects

Organize content with Projects. Projects persist chats and documents, are private by default and replace Collections through a gradual rollout.

- URL: https://docs.glean.com/user-guide/knowledge/projects/how-projects-work
- Locator: Create; sharing; access; migration
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:assistants

Assistenten | MeinGPT Docs. Assistants combine model, instructions, files, pools, connectors, tools and memory.

- URL: https://meingpt.com/docs/platform/assistants
- Locator: Creation guide and editor sections
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:projects

Projekte | MeinGPT Docs. Projects share instructions and workflows while each member keeps a private chat history.

- URL: https://meingpt.com/docs/platform/projects
- Locator: Collaboration, roles and deletion
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:deploy

Glean deployment models. Both modes use single-tenant infrastructure operated by Glean; Customer Hosted runs in customer GCP or AWS accounts with Glean support access.

- URL: https://docs.glean.com/get-started/prepare/about-deployment
- Locator: Glean Hosted; Customer Hosted; comparison table
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:connectors

Connectors hub. The official catalog lists M365, Google, Atlassian and other business-system connectors.

- URL: https://docs.glean.com/connectors
- Locator: Native connector catalog
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:sharepoint

SharePoint overview. SharePoint supports indexed and live retrieval; indexing uses certificate-based application permissions and admin consent.

- URL: https://docs.glean.com/connectors/native/sharepoint/about
- Locator: Access patterns; permissions and security
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:onedrive

OneDrive overview. OneDrive offers indexed and live search under the Microsoft 365 parent connector, with certificate-based application permissions.

- URL: https://docs.glean.com/connectors/native/onedrive/about
- Locator: Access patterns; permissions and security
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:outlook

Outlook overview. The Outlook connector supports access to Outlook content through Glean.

- URL: https://docs.glean.com/connectors/native/outlook/about
- Locator: Connector overview
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:teams-connector

Teams overview. Teams indexes channels and optionally private and meeting chats, with mirrored membership checked at query time.

- URL: https://docs.glean.com/connectors/native/teams/about
- Locator: Supported content; permissions and security
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:drive

Google Drive overview. Drive content and permissions are indexed with directory delegation; documented activity and group-sync schedules are distinct.

- URL: https://docs.glean.com/connectors/native/gdrive/about
- Locator: Permissions; crawling and updates
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:gmail

Gmail overview. Gmail has indexed search with source-specific crawl scope and controls.

- URL: https://docs.glean.com/connectors/native/gmail/about
- Locator: Indexed content and scope
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:gateway

Set up external tools with MCP Gateway. Admins proxy external MCP servers and custom tools with role and group controls and OAuth 2.1.

- URL: https://docs.glean.com/administration/platform/mcp/external-gateway-tools
- Locator: Prerequisites; external servers; access control
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:r4-purview-label-redlist

Glean O365 sensitivity-label restrictions. Protect+ can exclude SharePoint/OneDrive items by Purview label priority. Glean configures the redlist after account-team enablement; initial full crawl and later recrawls govern propagation. Teams message text is excluded.

- URL: https://docs.glean.com/administration/protect/sensitive-findings/restrict-content-via-sensitivity-labels
- Locator: Glean Protect+; setup; label-processing FAQ
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### meingpt:meingpt:m365

Microsoft 365 | MeinGPT Docs. Separate Outlook, Teams, SharePoint and OneDrive connectors run under user OAuth; Outlook can write, the other three read.

- URL: https://meingpt.com/docs/integrations/connectors/microsoft365
- Locator: Overview, setup, tenant consent and permission model
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:pool-controls

Sucheinstellungen am Datenpool | MeinGPT Docs. Source-permission import is off by default and request-enabled for SharePoint and Drive only; answers always show sources.

- URL: https://meingpt.com/docs/integrations/data-pool-search-settings
- Locator: Settings table and source-permission section
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:language

Glean language support. German, French, Italian and English end-user UIs are listed; cross-language retrieval is early access and admin setup is not localized.

- URL: https://docs.glean.com/administration/management/features/glean-language-support
- Locator: Language support matrix; cross-language warning
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:research

Use Deep Research. Deep Research creates cited read-only reports from company sources and Brave web search; key modes differ.

- URL: https://docs.glean.com/user-guide/assistant/deep-research
- Locator: Key modes; citations; limitations
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:sharing

Share chats. Viewer chat sharing describes citation redaction and states a fixed 30-day duration.

- URL: https://docs.glean.com/user-guide/assistant/chat-sharing
- Locator: Viewer controls; uploaded files; retention note
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:memory

Memory and personalization. Users can manage saved and learned memory in settings and chat.

- URL: https://docs.glean.com/user-guide/assistant/memory-personalization
- Locator: Saved and learned memories; user controls
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:memory-admin

Configure memory settings. Admins can disable learned memory but not user-controlled saved memory; pricing differs for legacy customers.

- URL: https://docs.glean.com/administration/assistant/configuration/memory-personalization
- Locator: Configure memory; billing
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:memory

Memory | MeinGPT Docs. Memory persists per user across enabled assistants; users can inspect/delete it and admins can disable the tool.

- URL: https://meingpt.com/docs/platform/memory
- Locator: How memory works, management and admin controls
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:preferences

Präferenzen | MeinGPT Docs. Users can set persistent system instructions and a platform-language preference.

- URL: https://meingpt.com/docs/platform/preferences
- Locator: Chat settings and appearance
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:builder

Agent Builder. Agents combine configured steps and models; Workflow JSON export is generally available while Auto ZIP export has limited availability.

- URL: https://docs.glean.com/agents/concepts/agent-builder
- Locator: Instructions, tools and models; import and export
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:agent-sharing

Sharing and permissions. Agents have controlled sharing and edit access.

- URL: https://docs.glean.com/agents/concepts/sharing-permissions
- Locator: Agent sharing permissions
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:library

Agent library. Users discover and run accessible agents through the internal library.

- URL: https://docs.glean.com/agents/concepts/agent-library
- Locator: Browse and discover agents
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:agents

How agents work. Agents support dynamic tool use and structured steps, loops and branches.

- URL: https://docs.glean.com/agents/how-agents-work
- Locator: Auto and Workflow modes; tools; steps
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:groups

Group-based permissions. Glean syncs Entra, Google and Okta group membership with integration-dependent timing; feature flag controls group-derived roles.

- URL: https://docs.glean.com/administration/identity/roles/group-based-permissions
- Locator: Supported providers; sync behavior; limitations
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:roles

Administrator Roles. Setup Admin, Admin, Super Admin and specialized moderators have distinct permissions.

- URL: https://docs.glean.com/administration/identity/roles/admin-roles
- Locator: Role matrix
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:sunset

Product and feature retirements. The retirement page records November 13, 2026 end of Glean Assist embedded integrations, past Prompt Library migration and legacy billing-dashboard removal.

- URL: https://docs.glean.com/release-notes/sunset
- Locator: Embedded support integrations; Prompt Library; legacy billing dashboard
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:roles

Rollen & Zugriffsmodell | MeinGPT Docs. Admin, Member and Viewer roles differ in settings access and seat use; admins see all team-shared assets.

- URL: https://meingpt.com/docs/admin-guide/roles-and-access-model
- Locator: Role table, admin exception and support visibility
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:permissions

Berechtigungen | MeinGPT Docs. Support-enabled permissions control creation, sharing and app use per person or team.

- URL: https://meingpt.com/docs/admin-guide/permissions
- Locator: Availability, permissions table and app restrictions
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:prompts

Prompt-Bibliothek | MeinGPT Docs. Saved prompt folders have private, workspace or department visibility.

- URL: https://meingpt.com/docs/platform/prompt-library
- Locator: Core functions, visibility and sharing
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:oauth

OAuth options for tools. Connector tools support Glean-managed or customer OAuth applications.

- URL: https://docs.glean.com/administration/actions/setup-actions/choose-central-or-custom-oauth
- Locator: Central and custom OAuth
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:r3-microsoft-write-confirmation

Create Microsoft 365 files. Interactive-agent builders can require write confirmation by disabling Run without user confirmation; confirmation is configurable.

- URL: https://docs.glean.com/agents/generate-files-from-templates
- Locator: Recommended agent instructions, Human approval
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:web

Web Search tools setup. Admins configure OpenAI, Brave or Google search tools and publish them to selected Glean interfaces.

- URL: https://docs.glean.com/administration/tools/setup-tools/web-search-tools-setup
- Locator: Providers; surface enablement; data sent
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:web

Websuche | MeinGPT Docs. Linkup powers chat search and a multi-step Deep Research app with cited sources.

- URL: https://meingpt.com/docs/platform/web-search
- Locator: Three routes, query creation, Linkup and research app
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:triggers

Types of agent triggers. Agents can start from messages, forms, connected-system content changes and schedules, subject to admin access.

- URL: https://docs.glean.com/agents/concepts/triggers
- Locator: Content and schedule triggers
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:workflows

Workflows erstellen und ausführen | MeinGPT Docs. Project workflows support multiple models, variables, documents and downloadable Office, PDF or JSON output.

- URL: https://meingpt.com/docs/platform/workflows-create
- Locator: Workflow editor and output format
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:scheduled

Geplante Aufgaben | MeinGPT Docs. Scheduled tasks are support-enabled beta with schedule, webhook and email triggers under the creator account.

- URL: https://meingpt.com/docs/platform/scheduled-tasks
- Locator: Beta availability, triggers and execution account
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:office-output

Create Microsoft 365 files with agents. Enabled tools create Office files, with limitations on arbitrary templates and output fidelity.

- URL: https://docs.glean.com/agents/generate-files-from-templates
- Locator: Word, Excel and PowerPoint; template limitations
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:r4-cancellation-release

Glean October 15 release notes. Canceling or interrupting an Assistant response also stops tool calls and background tasks started by that response. This is a documented Assistant run behavior, not a tested universal stop guarantee.

- URL: https://docs.glean.com/release-notes/releases/2026-10-15-october-release
- Locator: Canceled Assistant responses now stop cleanly
- Evidence kind: documented
- Source date: 2026-10-15
- Retrieved: 2026-10-26

### meingpt:meingpt:tools

Tool-Zugriffsrichtlinien | MeinGPT Docs. Tool methods are intersected across admin and assistant policies; there is no interactive per-action permission dialog.

- URL: https://meingpt.com/docs/admin-guide/tool-access-policy
- Locator: Security warning and four enforcement layers
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:mcp

About Glean MCP server. Glean exposes enterprise search, chat, documents and agents to external hosts through MCP.

- URL: https://docs.glean.com/administration/platform/mcp/about
- Locator: Server capabilities; authentication
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:core-price

Glean Core Suite. Core Suite combines per-user monthly licensing with committed Model Hub consumption; the seat amount is not given.

- URL: https://docs.glean.com/glean-core-suite-pricing
- Locator: Seat fee; Model Hub Usage; provider rate table
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:audit

Compliance Controls | MeinGPT Docs. Administrative settings logs exclude chat contents and are retained indefinitely; Governance Outpost search records are retained 90 days.

- URL: https://meingpt.com/docs/admin-guide/compliance-controls
- Locator: Core controls and Outpost search log
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:outlook

Outlook Add-in | MeinGPT Docs. The Outlook add-in requires Enterprise API enablement and a personal API key and works in the received-mail reading view.

- URL: https://meingpt.com/docs/integrations/connectors/outlook-addin
- Locator: Prerequisites, supported clients and central deployment
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:mobile

iOS and Android. Mobile clients use enterprise SSO and integrate with Intune App Protection.

- URL: https://docs.glean.com/administration/management/features/mobile
- Locator: SSO prerequisites; Intune MAM
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:surfaces

Choose where to use Glean. Glean has web, desktop, extension and embedded access points.

- URL: https://docs.glean.com/user-guide/apps/choose-where-to-use-glean
- Locator: Surface table; browser; desktop; extension
- Evidence kind: documented
- Source date: 2026-10-19
- Retrieved: 2026-10-21

### glean:glean:voice

Use real-time voice. Real-time voice works on web, desktop and mobile; raw audio streams to the configured model provider while transcripts follow chat retention.

- URL: https://docs.glean.com/user-guide/assistant/real-time-voice
- Locator: Where to access; privacy; limitations
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:terms

Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination.

- URL: https://meingpt.com/agb
- Locator: Sections 1a, 2, 3, 5 and final provisions
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:teams-app

Glean in Microsoft Teams: Admin guide. The Microsoft Teams app requires tenant admin setup and consent.

- URL: https://docs.glean.com/administration/platform/embedded-integrations/glean-in-teams/glean-in-microsoft-teams--admin-guide
- Locator: Installation prerequisites and deployment
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:images

Image Generation in Glean. Glean generates and edits images using enabled image models, independently of the text model.

- URL: https://docs.glean.com/user-guide/assistant/image-generation
- Locator: Model choice; editing; admin controls
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:terms

Glean Terms of Service v5Jun2026. The contract defines customer-cloud hosting, restricted proprietary access, order-specific fees, termination deletion and New York governing law.

- URL: https://www.glean.com/legal/terms
- Locator: Sections 1, 2, 5, 12 and 13
- Evidence kind: documented
- Source date: 2026-06-05
- Retrieved: 2026-10-21

### glean:glean:ai-addendum

Glean AI Addendum v5Jun2026. No-training commitments and Glean-key zero-day retention have legal and trust-and-safety exceptions; Customer Key responsibilities remain with the customer.

- URL: https://www.glean.com/legal/ai-addendum
- Locator: Sections 3 and 4
- Evidence kind: documented
- Source date: 2026-06-05
- Retrieved: 2026-10-21

### meingpt:meingpt:images

Bilder Generieren | MeinGPT Docs. The image app supports FLUX, GPT Image and Gemini image models with reference images and downloadable files.

- URL: https://meingpt.com/docs/platform/image-generator
- Locator: Model list, references and output management
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:image-admin

Bildmodelle verwalten | MeinGPT Docs. Admins enable image models and set a default; the table distinguishes manufacturer, host and EU/global processing.

- URL: https://meingpt.com/docs/admin-guide/image-models
- Locator: Image-model controls and complete table
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:meeting

Meetings | MeinGPT Docs. Recordings and transcripts become searchable meeting notes; Hetzner, Gladia and Vertex EU form the processing path.

- URL: https://meingpt.com/docs/platform/meetings
- Locator: Formats/limits, data flow and prices
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:team-chat

Team chat. Beta shared Editor chats run each request as its author but expose already-generated answers to all participants.

- URL: https://docs.glean.com/user-guide/assistant/team-chat
- Locator: How permissions work; behavior and limits
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:accessibility

Accessibility Statement. Glean says a VPAT 2.5 ACR covering WCAG 2.0, 2.1 and 2.2 A/AA is available through its trust center.

- URL: https://docs.glean.com/user-guide/about/accessibility
- Locator: Conformance status
- Evidence kind: documented
- Source date: 2026-09-25
- Retrieved: 2026-10-21

### glean:glean:sso

About Glean SSO. SSO is mandatory through OIDC or SAML; identity-provider policies enforce authentication conditions.

- URL: https://docs.glean.com/administration/identity/sso/about
- Locator: Mandatory SSO; identity providers; access controls
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:prices

prices. The public calculator uses marginal seat tiers plus model consumption and optional Governance and Outpost fees.

- URL: https://meingpt.com/preise
- Locator: Annual price tiers, included functions, add-ons and model-cost sections
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:sso

Access & Login Security | MeinGPT Docs. OIDC, Google and Microsoft login, verified domains and additive Entra group synchronization are documented; SAML is explicitly excluded.

- URL: https://meingpt.com/docs/admin-guide/access-and-login-security
- Locator: Own identity provider, authentication methods and Entra synchronization
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:scim

Entra ID SCIM-Provisionierung | MeinGPT Docs. SCIM v1 provisions users only; deactivated accounts retain data and release their seat.

- URL: https://meingpt.com/docs/admin-guide/entra-scim-provisioning
- Locator: SCIM versus SSO, prerequisites, effects and seat assignment
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:users

Managing Users. Admins assign roles and feature permissions and can revoke user sessions.

- URL: https://docs.glean.com/administration/identity/roles/manage-users
- Locator: Member permissions; sign out all sessions
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:insights

Insights overview. Adoption metrics and per-person activity are available; small departments are grouped and CSV export is documented.

- URL: https://docs.glean.com/administration/insights/overview
- Locator: Metrics; department filters; CSV; privacy
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:events

Glean Customer Event log overview. Customer Event logs include chats and responses separately from administrative logs and export as an unfiltered stream.

- URL: https://docs.glean.com/administration/gce-logs/data-dictionary
- Locator: CHAT events; unified export stream
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:analytics

KI-Cockpit | MeinGPT Docs. Adoption and cost reports include user, model, API/platform and team breakdowns with CSV and ID-based anonymization.

- URL: https://meingpt.com/docs/admin-guide/ai-cockpit
- Locator: Typical metrics, user/team costs and knowledge search
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:audit

Audit Logs. Admin configuration logs have CSV export and 30-day default retention; ongoing delivery needs account-team configuration.

- URL: https://docs.glean.com/administration/management/audit-logs/admin-audit-logs
- Locator: Coverage; export; default retention
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:history

Chat History. Admins choose Off or 30/90/180/365-day conversation retention, independently of Customer Event logging.

- URL: https://docs.glean.com/administration/assistant/configuration/chat-history
- Locator: Retention choices; Customer Event logs
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:audit-export

Änderungsprotokoll exportieren | MeinGPT Docs. Admins export filtered administrative changes as CSV or JSON, capped at 10000 entries, 20 MiB and two minutes.

- URL: https://meingpt.com/docs/admin-guide/admin-settings-map
- Locator: Export procedure, fields and limits
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:pii

Sensitive content in user prompt. Configured prompt-only regex policies can flag or block credentials, PII, IBANs and government IDs; built-in patterns start disabled.

- URL: https://docs.glean.com/administration/protect/ai-security/sensitive-content-user-prompt
- Locator: Prerequisites; regex templates; enforcement
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:protect

About Glean Protect and Protect+. Protect+ adds recurring sensitive-content scanning and AI security guardrails to baseline Protect.

- URL: https://docs.glean.com/administration/protect/overview
- Locator: Capability comparison; AI security add-on
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:subprocessors

Glean Subprocessors. The list names US providers and an Indian affiliate for remote support, security and debugging.

- URL: https://www.glean.com/legal/subprocessors
- Locator: Provider table; affiliate remote support
- Evidence kind: documented
- Source date: 2026-07-28
- Retrieved: 2026-10-21

### glean:glean:org-instructions

Configure custom instructions. Admins can configure up to five enterprise instructions for Assistant.

- URL: https://docs.glean.com/administration/assistant/configuration/custom-instructions
- Locator: Five custom instructions
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:regions

Supported GCP regions. The GCP region list includes Netherlands, Belgium, Frankfurt and other regions, subject to required services.

- URL: https://docs.glean.com/get-started/prepare/self-hosted-deployment/gcp/supported-gcp-regions
- Locator: Preferred regions; EMEA
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:sla

Glean Customer Support SLA v6Mar2026. Standard and paid Premium support differ; only Premium includes 99.9% monthly uptime and 10% or 20% service credits.

- URL: https://www.glean.com/legal/sla
- Locator: Sections 2, 4, 7 and 8
- Evidence kind: documented
- Source date: 2026-03-06
- Retrieved: 2026-10-21

### meingpt:meingpt:dpa-page

Auftragsverarbeitungsvertrag | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. DPA 2.0.1 dated 24 September 2026 needs signature or recorded electronic acceptance; existing customers retain their agreed version.

- URL: https://meingpt.com/avv
- Locator: Version and effectiveness
- Evidence kind: documented
- Source date: 2026-09-24
- Retrieved: 2026-10-21

### meingpt:meingpt:dpa

MeinGPT DPA 2.0.1. The signed-form DPA prohibits training, lists conditional subprocessors, defines authority-request handling and requires return or deletion within 30 days.

- URL: https://meingpt.com/legal/avv/v2.0.1.pdf
- Locator: Version 2.0.1; sections 4, 5(5), 7, 9, 12, 13 and Annexes 3/4, pages 3-12
- Evidence kind: documented
- Source date: 2026-09-24
- Retrieved: 2026-10-21

### glean:glean:dpa

Glean Data Processing Addendum v6Mar2026. The DPA covers applicable Swiss and EU law, termination erasure, SCCs and 30-day subprocessor notice.

- URL: https://www.glean.com/legal/dpa
- Locator: Sections 1, 7, 9 and 10; SCC annexes
- Evidence kind: documented
- Source date: 2026-03-06
- Retrieved: 2026-10-21

### meingpt:meingpt:security

Sind meine Daten sicher? | MeinGPT Docs. Security documentation states TLS 1.3, AES-256, customer-managed keys on request, and no bulk chat/file export.

- URL: https://meingpt.com/docs/privacy-security/faq-data-security
- Locator: Technical security, deletion and data portability
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:r3-legal-index

Glean legal. The index links both Business Associate Agreement forms, the Technical Services Addendum and named Outcomes Packages; inclusion and pricing depend on the applicable contract.

- URL: https://www.glean.com/legal
- Locator: Glean Customer Agreements and Policies
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:security-page

Glean Protect security page. Glean claims SOC 2 Type II, ISO 27001 and ISO 42001; no issuer-scoped certificate was retrieved.

- URL: https://www.glean.com/platform/security
- Locator: Enterprise security and compliance badges
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:trust

Sicherheitsnachweise & Trust Center | MeinGPT. ISO 27001 and a 2025 SySS penetration-test certificate are listed behind email-gated access.

- URL: https://meingpt.com/sicherheit/nachweise
- Locator: Certificates, assessments and document access
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:r4-aws-cmk-faq

Glean customer-hosted AWS FAQ. Customer-managed CMKs are supported for AWS, although the FAQ recommends default AWS-managed KMS keys and documents SCP-based emergency controls.

- URL: https://docs.glean.com/security/cloud-prem/aws/faq
- Locator: Are customer managed keys supported?
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### glean:glean:r4-aws-key-control

Glean AWS account access and deployment model. The customer-hosted AWS deployment guide says customers own and control KMS customer-managed keys used for data at rest. This does not establish key control for Glean Hosted or GCP.

- URL: https://docs.glean.com/security/cloud-prem/aws/account-access-and-deployment-model
- Locator: Customer controls
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### glean:glean:dpa-confidentiality

Glean DPA. General DPA confidentiality binds authorized personnel and no-less-protective subprocessor agreements; no specific §203/Art321 undertaking was retrieved.

- URL: https://www.glean.com/legal/dpa
- Locator: Section4 authorized personnel confidentiality; section9 subprocessor written agreement and necessary access
- Evidence kind: documented
- Source date: 2026-03-06
- Retrieved: 2026-10-21

### meingpt:meingpt:prices-rev2

Preise für Plattform, Add-ons und KI-Nutzung | MeinGPT. The contracted platform is offered with optional Governance and Outpost modules; local files are Early Access and local MCP/PostgreSQL Private Beta. The price calculator requires a binding individual offer.

- URL: https://meingpt.com/preise
- Locator: Feature table: Outpost release states; Governance separate agreement; calculator explicitly nonbinding
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:secrecy-contract-rev2

meinGPT terms: professional secrecy. Section12(4) itself imposes indefinite professional secrecy and text-form staff/subcontractor obligations when covered data are processed; it does not state a Governance prerequisite. A separate addendum is outside the verified base-terms finding.

- URL: https://meingpt.com/agb
- Locator: Section12(4), conditional duties for professional-secret data; no Governance prerequisite stated
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:flex-price

Glean Enterprise Flex. Enterprise Flex pools credits and separately meters advanced features and premium models; learned-memory billing starts November 7, 2026 for the stated scope.

- URL: https://docs.glean.com/glean-enterprise-flex-pricing
- Locator: Enterprise Flex seats; FlexCredits; rate card
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:billing-rev2

Abrechnung verwalten | MeinGPT Docs. Self-service Business is EUR29 per user/month excluding VAT, billed monthly, with unlimited standard-model use; premium/reasoning, API and meeting-bot use are separately metered.

- URL: https://meingpt.com/docs/admin-guide/billing
- Locator: Workspace types; Business upgrade card; standard-model inclusion
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:fx-ecb

ECB historical euro reference rates. The 2026-10-20 reference is EUR 1 = USD 1.1215 = CHF 0.9237.

- URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml
- Locator: Cube time=2026-10-20, USD and CHF
- Evidence kind: documented
- Source date: 2026-10-20
- Retrieved: 2026-10-21

### glean:glean:r2-customer-default-example

Change your default model on Customer Key. Customer Key admins choose defaults; GPT5.6 Luna is expressly an example, not a fixed or recommended routine model.

- URL: https://docs.glean.com/administration/change-default-model
- Locator: Opening note and prerequisites
- Evidence kind: documented
- Source date: 2026-10-19
- Retrieved: 2026-10-21

### glean:glean:r2-direct-provider-proxy

OpenAI direct API pricing. The shared direct-provider comparison uses USD0.10 input andUSD0.50 output per1M tokens; vendor usage is not replaced by this proxy.

- URL: https://developers.openai.com/api/docs/pricing
- Locator: Standard short-context gpt-6-luna
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### glean:glean:r2-proxy-lowest-effort

GPT6 Luna model documentation. Lowest effort none is used only for the direct-provider comparison assumption.

- URL: https://developers.openai.com/api/docs/models/gpt-6-luna
- Locator: Reasoning effort
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:ecb-fx

ECB historical euro reference rates, 20 October 2026. ECB2026-10-20 reference rates:EUR1=USD1.1215=CHF0.9237, implying USD1=EUR0.89166206.

- URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml
- Locator: Cube time=2026-10-20, USD and CHF currency entries
- Evidence kind: documented
- Source date: 2026-10-20
- Retrieved: 2026-10-21

### meingpt:meingpt:billing

Abrechnung verwalten | MeinGPT Docs. A separate Business offer includes standard models; the trial lasts 10 days with EUR 5 credit and no payment details.

- URL: https://meingpt.com/docs/admin-guide/billing
- Locator: Workspace types, trial differences and Business upgrade
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:terms-20261026

Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination.

- URL: https://meingpt.com/agb
- Locator: Sections 1a, 2, 3, 5 and final provisions
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### meingpt:meingpt:status

status. A public service-status page exposes incident history.

- URL: https://status.meingpt.com/
- Locator: Platform component and incidents
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### meingpt:meingpt:academy

Lernen & Entdecken | MeinGPT Docs. The learning area includes guided learning paths and business use cases.

- URL: https://meingpt.com/docs/platform/academy
- Locator: Learning area content and personalization
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21
