---
schema_version: 1
rubric_version: "1.1"
kind: pair
canonical_url: "https://onaihq.com/compare/agents/glean-vs-langdock/"
data_url: "https://onaihq.com/compare/agents/glean-vs-langdock/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 Langdock

> 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 49 criteria with sourced findings for both products, including 49 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.
- Langdock source checks: 2026-10-21 to 2026-10-26.

- Canonical HTML: https://onaihq.com/compare/agents/glean-vs-langdock/
- Machine-readable JSON: https://onaihq.com/compare/agents/glean-vs-langdock/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

#### Langdock

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

Curated multi-provider models and a task-complexity Auto mode are documented; catalogue publication is not a tested picker.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- current_models: Published text catalogue: Gemini 3.1 Pro Preview, 3 Flash Preview, 3.5/3.6/3.7/3.8 Flash, 4 Argon; GPT-5/5.1/5.1 Thinking Fast/5.2/5.2 Pro/5.4/5.4 Mini/5.5/5.6 Luna/Sol/Terra/5 Mini/5 Pro, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol, GPT oss 120b; Fable 5/5.1, Haiku 4.5/5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.5/4.6/5/5.5; Llama 3.3 70B/4 Maverick; Mistral Large 3/4; DeepSeek v3.1. Plan/admin/region settings can narrow this list; API availability is listed alongside chat, not independently observed.
- auto_routing: Auto analyzes the first message and estimates complexity to select a conversation model; exact final model disclosure was not verified.
- Unverified multimodal_input: A model-by-model image/audio input matrix and authenticated model picker were not inspected.

- providers — Which model providers are available? [supported]: OpenAI, Anthropic, Google, Meta, Mistral and DeepSeek have named current catalogue entries. Sources: langdock:langdock:models.
- current_models — Which current models are selectable on this plan? [partial]: Published text catalogue: Gemini 3.1 Pro Preview, 3 Flash Preview, 3.5/3.6/3.7/3.8 Flash, 4 Argon; GPT-5/5.1/5.1 Thinking Fast/5.2/5.2 Pro/5.4/5.4 Mini/5.5/5.6 Luna/Sol/Terra/5 Mini/5 Pro, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol, GPT oss 120b; Fable 5/5.1, Haiku 4.5/5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.5/4.6/5/5.5; Llama 3.3 70B/4 Maverick; Mistral Large 3/4; DeepSeek v3.1. Plan/admin/region settings can narrow this list; API availability is listed alongside chat, not independently observed. Sources: langdock:langdock:models.
- user_choice — Can users pick the model per chat? [supported]: Per-chat selection and mid-chat switching are documented. Sources: langdock:langdock:model-guide.
- auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Auto analyzes the first message and estimates complexity to select a conversation model; exact final model disclosure was not verified. Sources: langdock:langdock:model-guide.
- multimodal_input — Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. A model-by-model image/audio input matrix and authenticated model picker were not inspected.

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

Sources: langdock:langdock:models, langdock:langdock:model-guide

### 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

#### Langdock

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

Public dated model additions exist, but release-lag medians and guaranteed retirement notice remain unknown.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- Unverified release_lag_days, deprecation_notice, version_pinning: No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established.

- 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. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established.
- changelog — Is there a dated public model changelog? [supported]: Changelog includes Gemini 4 Argon on 13 October, Haiku 5.5 on 8 October and GPT-6.1 Sol on 30 September 2026. Sources: langdock:langdock:changes.
- deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established.
- version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established.

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

Sources: langdock:langdock:changes

### 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

#### Langdock

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

BYOK supports customer credentials, named cloud providers and custom compatible HTTPS endpoints.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business BYOK and individually contracted Enterprise BYOK; customer provider charges separate; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- Cloud BYOK requires separately configured completion, embedding and image routes; local/private endpoints are not implied by a cloud key.

- own_api_keys — Can the customer use its own provider API keys? [supported]: Customer keys can replace managed completion, embedding and image keys; BYOK can be selected at upgrade or enabled later by support. Sources: langdock:langdock:byok.
- own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [supported]: Guides cover customer Azure deployment settings, Google cloud and AWS Bedrock, separately from simple direct provider keys. Sources: langdock:langdock:byok-routes.
- custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Manual OpenAI-compatible endpoints include vLLM, LiteLLM, Ollama, TGI and LocalAI. Cloud requires public HTTPS; private/local hostnames are blocked by default. Sources: langdock:langdock:byok-routes.
- byo_pricing — Does BYO change the licence price? [partial]: Customer model usage is billed by the customer provider under BYOK. The applicable Business/Enterprise BYOK licence rate is unknown: the public Standard headline and calculator do not reconcile, and the prior hashed asset is not a stable tariff source. No BYOK seat-rate arithmetic is retained. Sources: langdock:langdock:byok, langdock:langdock:billing.
- byo_restrictions — Which features stop working with BYO? [supported]: Completion, embeddings and image models must all be configured. Deep Research needs reasoning/fast-reasoning/backbone routes; absent categories leave features non-functional. Sources: langdock:langdock:byok, langdock:langdock:research.

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

Sources: langdock:langdock:byok, langdock:langdock:byok-routes, langdock:langdock:billing, langdock:langdock:research

### 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

#### Langdock

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

Self-hosted compatible inference is a documented BYOK route with network and capability requirements.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- self_hosted_embeddings: BYOK requires a configured embedding model for search; custom model setup includes embeddings. A private customer-hosted embedding network path was not independently verified.
- feature_parity: Manual setup needs correct image, tool and editor capability flags. Missing embeddings/images or research routes disables their corresponding features; there is no universal parity guarantee.
- vendor_hosted_open_models: Catalogue includes Llama, GPT oss, Mistral and DeepSeek; terms identify Azure/Mistral EU routes, with global opt-ins separately described.

- self_hosted_chat — Can chat use a customer-hosted model? [supported]: vLLM/Ollama/TGI/LocalAI routes work through OpenAI-compatible HTTPS endpoints, not localhost/private addresses on default SaaS. Sources: langdock:langdock:byok-routes.
- self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [partial]: BYOK requires a configured embedding model for search; custom model setup includes embeddings. A private customer-hosted embedding network path was not independently verified. Sources: langdock:langdock:byok, langdock:langdock:byok-models.
- feature_parity — Which features fail with self-hosted models? [partial]: Manual setup needs correct image, tool and editor capability flags. Missing embeddings/images or research routes disables their corresponding features; there is no universal parity guarantee. Sources: langdock:langdock:byok-models, langdock:langdock:research.
- vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: Catalogue includes Llama, GPT oss, Mistral and DeepSeek; terms identify Azure/Mistral EU routes, with global opt-ins separately described. Sources: langdock:langdock:models, langdock:langdock:terms.

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

Sources: langdock:langdock:byok-routes, langdock:langdock:byok, langdock:langdock:byok-models, langdock:langdock:research, langdock:langdock:models, langdock:langdock:terms

### 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

#### Langdock

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

Workspace model defaults and usage/fallback behavior are documented; per-group model/data boundaries remain unverified.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- user_limits: Five-hour session and Monday-reset weekly limits depend on model-priced token consumption; numeric included budget is shown per account, not fully published. Spam protection is 250 messages/3h. Max is five times Standard.
- Unverified model_allowlist_by_group, data_bound_models: Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run.

- model_allowlist_by_group — Can admins limit models per group? [unknown]: Can admins limit models per group? Unknown. Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run.
- 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. Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run.
- default_model — Can admins set the default model? [supported]: Admins set a default across new chats and agents; users can have their own default. Sources: langdock:langdock:workspace.
- user_limits — What per-user message or token limits apply, and are they published? [partial]: Five-hour session and Monday-reset weekly limits depend on model-priced token consumption; numeric included budget is shown per account, not fully published. Spam protection is 250 messages/3h. Max is five times Standard. Sources: langdock:langdock:limits, langdock:langdock:pricing.
- limit_behaviour — What happens when a limit is reached? [supported]: With no usable extra usage, Cloud falls back to GPT-6 Luna; BYOK/dedicated use configured fallback. Current responses finish, so spend can slightly overshoot. Personal API calls error rather than fall back. Sources: langdock:langdock:extra.

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

Sources: langdock:langdock:workspace, langdock:langdock:limits, langdock:langdock:pricing, langdock:langdock:extra

## 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

#### Langdock

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

Format/count limits and direct previews differ from semantic search paths.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- spreadsheets: Spreadsheets use direct reading and file tools, not chunk embeddings; source formula/structure accuracy was not fixture-tested.
- Unverified ocr: No shared scanned-PDF OCR or multilingual file fixture was uploaded.

- formats — Which formats are accepted? [supported]: PDF/Word/PowerPoint and text, Excel/CSV/TSV/Parquet, listed image, audio and video types are documented; Knowledge bases exclude tabular/media. Sources: langdock:langdock:files.
- limits — What size and count limits apply per file and chat? [supported]: Web 50 files/message, mobile five; agent 50 files. PDF/Office 256 MB, text 10 MB, tabular 100 MB, images 20 MB; text 8M characters and PDF 5000 pages. Sources: langdock:langdock:files, langdock:langdock:file-count.
- ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. No shared scanned-PDF OCR or multilingual file fixture was uploaded.
- spreadsheets — Are Excel tables read with structure intact? [partial]: Spreadsheets use direct reading and file tools, not chunk embeddings; source formula/structure accuracy was not fixture-tested. Sources: langdock:langdock:files, langdock:langdock:retrieval.
- full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: Small direct files are previewed in full where possible; agent knowledge above 20 documents uses lists/tools. Knowledge-base/synced text uses up to 50 chunks of up to 2000 characters. Sources: langdock:langdock:retrieval.

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

Sources: langdock:langdock:files, langdock:langdock:file-count, langdock:langdock:retrieval

### 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

#### Langdock

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

Persistent knowledge bases and library folders have separate limits and access roles.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

- persistent_collections — Can users keep document collections across chats? [supported]: Knowledge bases persist for chat, agents, workflows and API use. Sources: langdock:langdock:knowledge.
- sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Owner/Editor/Viewer roles; share with persons, groups or workspace, subject to workspace-sharing permission. Sources: langdock:langdock:knowledge.
- size_limits — What are the collection limits? [supported]: Cloud Knowledge bases support 1000 files, 8M characters/file. Normal folders have 100 files and 250 MB total; dedicated limits are configurable. Sources: langdock:langdock:knowledge, langdock:langdock:file-count.
- assistant_binding — Can collections be bound to an assistant? [supported]: Agent Folders attach knowledge bases/library folders/synced folders. Sources: langdock:langdock:agents.

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

Sources: langdock:langdock:knowledge, langdock:langdock:file-count, langdock:langdock:agents

### 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

#### Langdock

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

Native tools, daily folder sync and customer MCP/API integrations are distinct routes.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- on_prem_sources: Confluence Data Center and customer API/MCP endpoints can connect; private network access is restricted by default in Cloud, so generic local shares are not established.

- microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [supported]: Directory includes SharePoint, OneDrive, Outlook Email/Calendar and Teams. SharePoint/OneDrive also support indexed folder sync. Sources: langdock:langdock:integrations, langdock:langdock:sync.
- google_workspace — Which Google sources are connected? [supported]: Drive, Gmail, Calendar, Docs, Sheets, Slides and Meet are listed; Drive supports folder sync. Sources: langdock:langdock:integrations.
- atlassian — Confluence and Jira? [supported]: Confluence Cloud, self-hosted Confluence Data Center and Jira are in the native directory. Sources: langdock:langdock:integrations.
- other_systems — Which other business systems? [supported]: Named routes include Salesforce, ServiceNow, HubSpot, Slack, Notion, Airtable, Asana, GitHub, Azure AI Search, Kendra and Databricks; see directory for authentication and actions. Sources: langdock:langdock:integrations.
- on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Confluence Data Center and customer API/MCP endpoints can connect; private network access is restricted by default in Cloud, so generic local shares are not established. Sources: langdock:langdock:integrations, langdock:langdock:mcp.
- connector_provider — Who builds and maintains each connector? [supported]: Langdock provides native integrations; customers build custom actions or connect official third-party MCP servers. Sources: langdock:langdock:integrations, langdock:langdock:mcp.

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

Sources: langdock:langdock:integrations, langdock:langdock:sync, langdock:langdock:mcp

### 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

#### Langdock

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

Folder Sync checks each user source access; Purview labels add a separate, qualified control.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- source_permissions_respected: Synced folder retrieval checks the user source rights in real time and requires the user connection. Static shared knowledge follows Langdock sharing instead. No fixture test was run.
- sensitivity_labels: Request-enabled policy covers five Microsoft integrations, with exceptions for certain Outlook actions/copy attachments, unlabeled/new labels, custom MCP and uploaded files; saved-policy enforcement is conditional on integration rollout.
- Unverified revocation_delay: A two-user restricted-file/revocation test was not run; no measured source-permission revocation latency is asserted.

- source_permissions_respected — Are source permissions enforced per user? [partial]: Synced folder retrieval checks the user source rights in real time and requires the user connection. Static shared knowledge follows Langdock sharing instead. No fixture test was run. Sources: langdock:langdock:sync, langdock:langdock:knowledge.
- enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: A copied content index is searched while access is checked live against the source system for synced files. Sources: langdock:langdock:sync.
- revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unknown. A two-user restricted-file/revocation test was not run; no measured source-permission revocation latency is asserted.
- admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins choose integrations/actions; synced folders scope imported content and labels can exclude documents. Sources: langdock:langdock:actions, langdock:langdock:labels, langdock:langdock:sync.
- sensitivity_labels — Are Microsoft Purview or similar labels respected? [partial]: Request-enabled policy covers five Microsoft integrations, with exceptions for certain Outlook actions/copy attachments, unlabeled/new labels, custom MCP and uploaded files; saved-policy enforcement is conditional on integration rollout. Sources: langdock:langdock:labels.

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

Sources: langdock:langdock:sync, langdock:langdock:knowledge, langdock:langdock:labels, langdock:langdock:actions

### 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

#### Langdock

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

Folder Sync copies indexed text and refreshes daily, with live access checks and manual refresh.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- deletion_propagation: Daily sync removes source-deleted files; no measured end-to-end deletion delay is available.
- index_location: Terms place customer files/embeddings in EU Azure storage, with default Frankfurt hosting. Per-index backup copies are not separately mapped.

- live_or_indexed — Is content searched live or copied into an index? [supported]: Folder Sync downloads supported text into an index; spreadsheets remain direct-read files. Other integration actions query source APIs. Sources: langdock:langdock:sync, langdock:langdock:integrations.
- sync_interval — How often does an index refresh? [supported]: Daily updates, manual refresh and up to one hour initial sync. Sources: langdock:langdock:sync.
- deletion_propagation — How quickly does a deleted document disappear? [partial]: Daily sync removes source-deleted files; no measured end-to-end deletion delay is available. Sources: langdock:langdock:sync.
- index_location — Where is indexed content stored? [partial]: Terms place customer files/embeddings in EU Azure storage, with default Frankfurt hosting. Per-index backup copies are not separately mapped. Sources: langdock:langdock:terms.

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

Sources: langdock:langdock:sync, langdock:langdock:integrations, langdock:langdock:terms

### 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

#### Langdock

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

Citations are documented; retrieval outcomes remain untested.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- citations: Agent responses cite sources by default; source-access restriction can hide click-through while still using content.
- Unverified citation_accuracy, cross_language, no_answer_behaviour, observed_accuracy: No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown.

- citations — Are answers linked to specific sources? [partial]: Agent responses cite sources by default; source-access restriction can hide click-through while still using content. Sources: langdock:langdock:agents.
- citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain 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. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown.
- no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown.
- observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown.

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

Sources: langdock:langdock:agents

### 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

#### Langdock

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

Regular-chat instructions and memory have user and workspace controls.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

- custom_instructions — Can users set persistent instructions? [supported]: Personal instructions apply in regular chat; agent/project instructions replace them. Sources: langdock:langdock:account.
- cross_chat_memory — Does the product remember facts across chats? [supported]: Regular chats use a personal store of up to 50 memories; projects/agents do not use this memory. Sources: langdock:langdock:memory.
- user_memory_controls — Can users view, edit and delete memories? [supported]: Users inspect, edit, delete or disable memories in account settings and can update/forget through chat. Sources: langdock:langdock:memory, langdock:langdock:account.
- admin_memory_controls — Can admins turn memory off? [supported]: Memory availability requires workspace and personal enablement. Sources: langdock:langdock:chat.

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

Sources: langdock:langdock:account, langdock:langdock:memory, langdock:langdock:chat

## 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

#### Langdock

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

Agents combine reusable knowledge and tools with creation/sharing controls.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- sharing_scope: Workspace/group resources and permissioned agent configuration are documented; no fixture was shared.

- create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Agents configure model, instructions, files, folders, integrations, subagents, skills and workflows. Sources: langdock:langdock:agents.
- creator_permissions — Can admins limit who creates them? [supported]: System/custom roles and extra permissions control agent creation/sharing. Sources: langdock:langdock:roles.
- sharing_scope — Can assistants be shared with users, groups or everyone? [partial]: Workspace/group resources and permissioned agent configuration are documented; no fixture was shared. Sources: langdock:langdock:workspace, langdock:langdock:agents.
- catalogue — Is there an internal assistant directory? [supported]: Workspace agent management has All/Unassigned/Verified views. Sources: langdock:langdock:workspace.
- prompt_library — Are shared prompt templates available? [supported]: The workspace guide documents group/workspace prompt-library sharing. Sources: langdock:langdock:workspace.

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

Sources: langdock:langdock:agents, langdock:langdock:roles, langdock:langdock:workspace

### 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

#### Langdock

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

Remote MCP and custom actions have admin access controls and optional confirmations.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- tool_approval: Admins share integrations/actions by user/group/key, but native core actions cannot be disabled. New MCP tools default to no confirmation; per-tool/agent confirmations can be configured.

- builtin_tools — Which tools are built in? [supported]: Search, images, file work, document editor, memory, research and company knowledge are governed tools. Sources: langdock:langdock:chat.
- custom_actions — Can admins add API actions? [supported]: Custom API integrations and shareable individual actions are documented. Sources: langdock:langdock:actions.
- mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Streamable HTTP/SSE with OAuth CIMD/DCR/manual PKCE, API key or none; private network URLs blocked by default. Sources: langdock:langdock:mcp.
- tool_auth — Do tools act as the user or as a shared account? [supported]: Native integrations use personal OAuth or service credentials per provider; MCP supports user OAuth or API headers. Sources: langdock:langdock:integrations, langdock:langdock:mcp.
- tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins share integrations/actions by user/group/key, but native core actions cannot be disabled. New MCP tools default to no confirmation; per-tool/agent confirmations can be configured. Sources: langdock:langdock:actions, langdock:langdock:mcp, langdock:langdock:changes.

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

Sources: langdock:langdock:chat, langdock:langdock:actions, langdock:langdock:mcp, langdock:langdock:integrations, langdock:langdock:changes

### 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

#### Langdock

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

Cited search and public-web Deep Research are available; provider/region details remain incomplete.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- admin_toggle: Workspace admins disable web search and separate agent capabilities. Per-group search-toggle coverage was not established.
- Unverified search_provider: Search/crawl provider contracts and query-processing region were not established in the public tool documentation.

- web_search — Is web search available? [supported]: Chat tool generates a query and can open URLs; sources are inspectable. Sources: langdock:langdock:web.
- admin_toggle — Can admins disable it per organisation or group? [partial]: Workspace admins disable web search and separate agent capabilities. Per-group search-toggle coverage was not established. Sources: langdock:langdock:workspace.
- search_provider — Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? Unknown. Search/crawl provider contracts and query-processing region were not established in the public tool documentation.
- deep_research — Is multi-step research with a report available? [supported]: Regular chat only, public web only, cited PDF reports; standard keys allow 15 researches per rolling 30 days. BYOK needs research models. Sources: langdock:langdock:research.
- web_citations — Are web sources cited? [supported]: Search sources link to corresponding paragraphs and Deep Research has activity/source lists. Sources: langdock:langdock:web, langdock:langdock:research.

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

Sources: langdock:langdock:web, langdock:langdock:workspace, langdock:langdock:research

### 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

#### Langdock

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

Multi-step workflows support automatic triggers and human review.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=Workflow run package; model usage separately metered; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- builder_audience: Quickstart and conversational Workflow Builder guide non-developers, with code/HTTP nodes for technical users.

- workflow_builder — Is there a workflow or chain builder? [supported]: Workflows chain agents, integrations, logic, loops and custom code after workspace activation. Sources: langdock:langdock:workflows.
- scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Schedule triggers are documented for workflows; the public API index also exposes recurring saved tasks. Sources: langdock:langdock:workflows.
- event_triggers — Can external events start a workflow? [supported]: Connected-app events, forms and webhooks start runs; dated composable-workflow release supports multiple triggers. Sources: langdock:langdock:workflows, langdock:langdock:changes.
- builder_audience — Is building aimed at business users, IT or developers? [partial]: Quickstart and conversational Workflow Builder guide non-developers, with code/HTTP nodes for technical users. Sources: langdock:langdock:workflows.

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

Sources: langdock:langdock:workflows, langdock:langdock:changes

### 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

#### Langdock

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

Agents execute actions/subagents; workflow and add-in confirmation behavior is explicit.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock Excel and Outlook add-ins; version=Public documentation checked 2026-10-26; plan=Business Chat & Agents/Workflows; Outlook add-in for paid plans and trials, enabled by workspace admin; add_ons=Workflow package as needed; compatible Microsoft Outlook/Exchange Online subscription; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- visible_steps: Deep Research shows search/page-read activity; workflows expose run history and nested run links. General agent step-display completeness was not independently observed.
- side_effect_confirmation: Configurable per-agent confirmations and workflow action review exist. Newly saved MCP actions default to no confirmation; Office add-ins ask before edits by default.
- stop_control: Deep Research has a stop button; general external side effects already committed cannot be inferred reversible.

- agent_mode — Is there an agent mode for multi-step tasks? [supported]: Agents can call integrations, subagents and workflows to carry out multiple steps. Sources: langdock:langdock:agents.
- visible_steps — Are steps and tool calls shown? [partial]: Deep Research shows search/page-read activity; workflows expose run history and nested run links. General agent step-display completeness was not independently observed. Sources: langdock:langdock:research, langdock:langdock:changes.
- side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Web agents can require configured action confirmation; workflow action review is separate. Newly saved MCP actions default to no confirmation. In the Outlook add-in, edits ask by default, users can allow subsequent edits for the chat, and sending requires a requested action plus confirmation. Sources: langdock:langdock:changes, langdock:langdock:hitl, langdock:langdock:mcp, langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace.
- stop_control — Can the user stop a running task? [partial]: Deep Research has a stop button; general external side effects already committed cannot be inferred reversible. Sources: langdock:langdock:research.

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

Sources: langdock:langdock:agents, langdock:langdock:research, langdock:langdock:changes, langdock:langdock:hitl, langdock:langdock:mcp, langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:agents-20261026, langdock:langdock:research-20261026, langdock:langdock:changes-20261026, langdock:langdock:hitl-20261026, langdock:langdock:mcp-20261026, langdock:langdock:excel-20261026

### 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

#### Langdock

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

Public APIs include knowledge and agent MCP, with distinct personal/workspace governance boundaries.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-21; plan=API/Agent/Knowledge scopes; workspace activation may apply; add_ons=Metered API usage; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- api_governance: Personal API keys share member/workspace spend limits and error on exhaustion; workspace API keys and workflow costs use separate limits.

- chat_api — Is there an API for chat and assistants? [supported]: Public Completion and Agent APIs use scoped bearer keys. Workspace/personal key access is controlled by admins. Sources: langdock:langdock:workspace.
- knowledge_api — Can documents be loaded through an API? [supported]: Knowledge Folder API supports upload/update/delete/retrieve/search with API-key sharing roles. Sources: langdock:langdock:knowledge.
- api_governance — Do audit, budgets and model rules apply to API use? [partial]: Personal API keys share member/workspace spend limits and error on exhaustion; workspace API keys and workflow costs use separate limits. Sources: langdock:langdock:billing, langdock:langdock:extra.
- mcp_server — Does the product expose itself to other agents over MCP? [supported]: https://api.langdock.com/mcp exposes find_agent/ask_agent/ask_custom_agent under Agent API key scope; dedicated URL differs. Sources: langdock:langdock:mcp-server.

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

Sources: langdock:langdock:workspace, langdock:langdock:knowledge, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock:mcp-server

## 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

#### Langdock

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

Web, desktop and mobile clients are documented, with IT deployment guidance.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock Windows/macOS desktop, Langdock iOS/Android; version=Public documentation checked 2026-10-21; plan=Business or contracted Enterprise workspace clients; the same subscription/approved models apply; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=Windows, macOS, iOS, Android.

Limitations:
- Native-client and SSO parity beyond the documented file limit was not tested. The source is installation guidance, not proof of a paid Enterprise-only client entitlement.

- web — Is a full web client available? [supported]: The core platform is a browser workspace. Sources: langdock:langdock:terms.
- desktop_apps — Windows and macOS apps? [supported]: Official Windows/macOS downloads use the same workspace and approved models as web. This is documented availability, not a hands-on parity test. Sources: langdock:langdock:desktop-product.
- mobile_apps — iOS and Android apps with SSO? [partial]: The vendor publishes iOS/Android clients and official store links. Mobile-specific SSO and managed-access compatibility were not independently tested. Sources: langdock:langdock:mobile-rev2, langdock:langdock:mobile-product.
- browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. A general browser extension and exhaustive mobile/SSO/Intune parity matrix were not established.
- managed_deployment — Can IT deploy and configure clients through MDM? [partial]: Windows machine-wide MSIX/Intune and deployment kits are documented. macOS PKG/DMG works with Jamf, Kandji and Intune. These are client installation methods; separate mobile MAM/dedicated entitlements are not established by this finding. Sources: langdock:langdock:desktop-rev2.
- client_feature_gaps — Which features are missing on mobile? [partial]: Mobile permits five files per message versus 50 on web; other parity gaps were not tested. Sources: langdock:langdock:file-count.

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

Sources: langdock:langdock:terms, langdock:langdock:desktop-product, langdock:langdock:mobile-rev2, langdock:langdock:mobile-product, langdock:langdock:desktop-rev2, langdock:langdock:file-count

### 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

#### Langdock

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

Excel and Outlook add-ins and a Teams bot are documented; broad Office-suite coverage is not inferred.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock Excel and Outlook add-ins, Langdock Teams bot; version=Public documentation checked 2026-10-26; plan=Business or Enterprise workspace; Outlook available on paid plans/trials, Excel/Teams require workspace-admin enablement; add_ons=Compatible Microsoft licences not priced; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- word_excel_powerpoint: Excel add-in reads/writes workbooks with formulas/charts; no Word or PowerPoint add-in was established.
- licence_prerequisites: Excel web/Windows/Mac version matrix and Outlook Exchange Online requirement are explicit; workspace admin access controls apply and extra M365 seat costs were not priced.
- Unverified google_workspace_apps: Google in-editor apps were not established; Google content integrations are recorded separately.

- word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [partial]: Excel add-in reads/writes workbooks with formulas/charts; no Word or PowerPoint add-in was established. Sources: langdock:langdock:excel.
- outlook — Does it work inside Outlook? [supported]: Outlook reads connected mailbox/calendar and edits drafts; sending requires a requested action and confirmation. Exchange Online is required. Sources: langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace.
- teams — Is there a Teams app or bot? [supported]: Admin-installed Teams bot supports private chat and collaborative channel mentions. Sources: langdock:langdock:teams, langdock:langdock:teams-20261026.
- google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Google in-editor apps were not established; Google content integrations are recorded separately. Rechecked 2026-10-26 in Outlook Add-in, Excel Add-in, How to use the Teams Bot. The Teams Markdown guide was retrieved with HTTP 200; Google in-editor app coverage remains undocumented in these sources.
- licence_prerequisites — Which licences or consents are needed? [partial]: Excel web/Windows/Mac version matrix and Outlook Exchange Online requirement are explicit; workspace admin access controls apply and extra M365 seat costs were not priced. Sources: langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:teams, langdock:langdock:outlook-marketplace, langdock:langdock:teams-20261026.

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

Sources: langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:teams, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:excel-20261026, langdock:langdock:teams-20261026

### 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

#### Langdock

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

DeepL integration offers document translation and glossaries; end-to-end layout quality is untested.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- document_translation: Native DeepL integration lists document translation; its supported layout guarantees were not verified in a trial.
- glossaries: DeepL integration lists glossary management; full enterprise glossary rollout was not tested.
- Unverified formality_and_variants: Formality/de-CH configuration and DE-to-FR/IT layout-preservation fixtures remain unverified.

- document_translation — Can whole documents be translated with formatting kept? [partial]: Native DeepL integration lists document translation; its supported layout guarantees were not verified in a trial. Sources: langdock:langdock:integrations.
- translation_engine — Which engine translates? [supported]: The dedicated DeepL integration uses the customer DeepL API key; ordinary chat rewriting uses the chosen model. Sources: langdock:langdock:integrations.
- glossaries — Are company glossaries supported? [partial]: DeepL integration lists glossary management; full enterprise glossary rollout was not tested. Sources: langdock:langdock:integrations.
- formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Formality/de-CH configuration and DE-to-FR/IT layout-preservation fixtures remain unverified.
- writing_tools — Are dedicated rewrite and proofreading tools available? [supported]: DeepL integration includes writing polish; Document Editor supports selected-text and whole-document AI edits. Sources: langdock:langdock:integrations, langdock:langdock:editor.

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

Sources: langdock:langdock:integrations, langdock:langdock:editor

### 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

#### Langdock

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

Image generation and model-specific editing are documented with workspace controls.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- image_generation: Image-generation tool invokes a chosen available image model; dated September release names EU GPT-Image 2.5 Flare and Sunburst.
- image_editing: The release describes image editing and BYOK model setup has an image-editing capability flag; exhaustive per-model editing limits were not verified.
- usage_terms: As between customer/vendor, customer content rights belong to the customer; third-party model terms and rights restrictions remain applicable.

- image_generation — Can users generate images, with which models? [partial]: Image-generation tool invokes a chosen available image model; dated September release names EU GPT-Image 2.5 Flare and Sunburst. Sources: langdock:langdock:images, langdock:langdock:changes.
- image_editing — Can users edit uploaded images? [partial]: The release describes image editing and BYOK model setup has an image-editing capability flag; exhaustive per-model editing limits were not verified. Sources: langdock:langdock:changes, langdock:langdock:byok-models.
- admin_control — Can admins restrict image generation? [supported]: Workspace admins can disable image generation and manage available models. Sources: langdock:langdock:workspace.
- usage_terms — What usage rights apply to output? [partial]: As between customer/vendor, customer content rights belong to the customer; third-party model terms and rights restrictions remain applicable. Sources: langdock:langdock:terms.

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

Sources: langdock:langdock:images, langdock:langdock:changes, langdock:langdock:byok-models, langdock:langdock:workspace, langdock:langdock: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

#### Langdock

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

Audio/meeting-source integrations are documented; live voice and Swiss German remain unverified.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- read_aloud: ElevenLabs integration offers text-to-speech using a customer API key; this is not a guaranteed native read-aloud control.
- meeting_summaries: Google Meet/Zoom and ElevenLabs integrations can retrieve transcripts; source recordings and processing depend on the connected service. No native meeting-bot transcription fixture was run.
- Unverified dictation, voice_conversation, swiss_german_speech: Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages.

- dictation — Can users dictate prompts? [unknown]: Can users dictate prompts? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages.
- read_aloud — Can answers be read aloud? [partial]: ElevenLabs integration offers text-to-speech using a customer API key; this is not a guaranteed native read-aloud control. Sources: langdock:langdock:integrations.
- voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages.
- meeting_summaries — Are meetings transcribed and summarised? [partial]: Google Meet/Zoom and ElevenLabs integrations can retrieve transcripts; source recordings and processing depend on the connected service. No native meeting-bot transcription fixture was run. Sources: langdock:langdock:integrations.
- swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages.

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

Sources: langdock:langdock:integrations

### 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

#### Langdock

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

File analysis, charts and editable document generation are documented; execution-location detail is incomplete.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- data_analysis: The data-analysis guide documents spreadsheet metrics/calculations; exact executed-code sandbox/model configuration was not verified.
- canvas_editing: Document Editor replaces Canvas; it exports Markdown/Word/PDF but cannot directly edit imported Word/PDF files.

- data_analysis — Can it analyse spreadsheets with executed code? [partial]: The data-analysis guide documents spreadsheet metrics/calculations; exact executed-code sandbox/model configuration was not verified. Sources: langdock:langdock:analysis.
- charts — Can it produce charts? [supported]: Charts and downloadable chart images are supported in the guide. Sources: langdock:langdock:analysis.
- office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Analysis lists Excel/CSV/Word/PDF/JSON; changelog and agent file templates also describe PowerPoint. Sources: langdock:langdock:analysis, langdock:langdock:changes.
- canvas_editing — Is there a document or canvas editor for iterating on output? [partial]: Document Editor replaces Canvas; it exports Markdown/Word/PDF but cannot directly edit imported Word/PDF files. Sources: langdock:langdock:editor.

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

Sources: langdock:langdock:analysis, langdock:langdock:changes, langdock:langdock:editor

### 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

#### Langdock

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

Shared projects expose chats/files, and Teams channels support group interaction.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock Teams bot; version=Public documentation checked 2026-10-21; plan=Business/Enterprise workspace sharing; Teams bot requires workspace-admin setup and Microsoft tenant installation; add_ons=Microsoft Teams access; bot installed and permitted by tenant admin; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- Unverified share_permission_boundary: No cross-group source-boundary sharing fixture was run; project sharing does not by itself prove permission-safe redistribution of generated answers.

- share_chats — Can chats be shared inside the organisation? [supported]: Workspace chat-link sharing is managed under account shared chats. Sources: langdock:langdock:account.
- team_spaces — Are shared projects or workspaces available? [supported]: Projects shared with users/groups include all current and future project chats, files and instructions; cannot share a project to the whole workspace. Sources: langdock:langdock:projects.
- group_chat — Can several people chat together with the AI? [supported]: Teams channel threads allow several people to participate with @Langdock. Sources: langdock:langdock:teams.
- 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 source-boundary sharing fixture was run; project sharing does not by itself prove permission-safe redistribution of generated answers.

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

Sources: langdock:langdock:account, langdock:langdock:projects, langdock:langdock:teams

### 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

#### Langdock

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

Five interface languages are documented; quality and accessibility have not been audited.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- Unverified dach_language_quality, accessibility_statement, admin_ui_languages: No authenticated language-quality/admin-translation inspection or WCAG conformance report was established.

- ui_languages — Which UI languages are offered? [supported]: English, German, Spanish, French and Italian are listed in Account Preferences. Sources: langdock:langdock:account.
- 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 language-quality/admin-translation inspection or WCAG conformance report was established.
- accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established.
- admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established.

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

Sources: langdock:langdock:account

## 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

#### Langdock

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

Business includes SAML SSO and verified domains; MFA relies on the identity provider.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- mfa: No standalone Langdock MFA; SAML identity provider enforces MFA.
- Unverified conditional_access: OIDC/LDAP enterprise options and a tested Entra Conditional Access compatibility matrix were not established.

- sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML 2.0 with Entra ID, Google Workspace and Okta; account docs also name Google/Microsoft SSO. Sources: langdock:langdock:saml, langdock:langdock:account.
- sso_plan — Which plan includes SSO? [supported]: Business up to 1000 users includes SSO, SCIM and SAML. Sources: langdock:langdock:billing.
- mfa — Can MFA be enforced? [partial]: No standalone Langdock MFA; SAML identity provider enforces MFA. Sources: langdock:langdock:saml.
- conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. OIDC/LDAP enterprise options and a tested Entra Conditional Access compatibility matrix were not established.
- domain_capture — Can the company claim its email domain? [supported]: Join by domain and verified email domains are prerequisites for SAML; SAML remains required on those verified domains. Sources: langdock:langdock:saml.

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

Sources: langdock:langdock:saml, langdock:langdock:account, langdock:langdock:billing

### 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.

#### Langdock

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

SCIM synchronizes users/groups and preserves functioning ownerless agents.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- deprovisioning: Entra Update removes unassigned/blocked/soft-deleted memberships when enabled. Agents become unassigned, continue to work and need a new owner before editing; sync-folder owner removal can interrupt refresh.
- seat_assignment: Admins assign roles/plans in member management; exact reclaimed-seat billing rules depend on subscription.
- Unverified jit_provisioning: Just-in-time first-login provisioning and complete user-chat/knowledge ownership effects were not tested or fully specified.

- scim — Is SCIM provisioning supported? [supported]: SCIM 2.0 via Entra, with prior SAML and verified domains. Sources: langdock:langdock:scim.
- group_sync — Are identity-provider groups synced? [supported]: Entra SCIM group sync is documented and can be disabled; default group roles are separately configurable. Sources: langdock:langdock:scim-entra, langdock:langdock:workspace.
- jit_provisioning — Are users created at first login? [unknown]: Are users created at first login? Unknown. Just-in-time first-login provisioning and complete user-chat/knowledge ownership effects were not tested or fully specified.
- deprovisioning — What happens to a removed user's data and shared assets? [partial]: Entra Update removes unassigned/blocked/soft-deleted memberships when enabled. Agents become unassigned, continue to work and need a new owner before editing; sync-folder owner removal can interrupt refresh. Sources: langdock:langdock:scim-entra, langdock:langdock:leaver, langdock:langdock:sync.
- seat_assignment — Can admins assign and reclaim seats? [partial]: Admins assign roles/plans in member management; exact reclaimed-seat billing rules depend on subscription. Sources: langdock:langdock:workspace.

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

Sources: langdock:langdock:scim, langdock:langdock:scim-entra, langdock:langdock:workspace, langdock:langdock:leaver, langdock:langdock:sync

### 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

#### Langdock

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

System/custom roles and delegated groups govern product and action permissions.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- feature_toggles: Role permissions plus integration/action sharing can target people/groups. Global chat/agent capabilities include search, images and file work; universal per-group toggle parity was not established.
- Unverified multi_entity: Subsidiary/contract-level isolation beyond group and workspace boundaries was not established.

- admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Member, Editor, Admin, up to five custom roles and extra permissions; group admins are separate from workspace admins. Sources: langdock:langdock:roles.
- groups — Can permissions be set per group? [supported]: Groups can be SCIM-synced, admin-created or user-created if allowed; group rights and resources are distinct from system roles. Sources: langdock:langdock:workspace.
- feature_toggles — Which features can be switched on or off per group? [partial]: Role permissions plus integration/action sharing can target people/groups. Global chat/agent capabilities include search, images and file work; universal per-group toggle parity was not established. Sources: langdock:langdock:roles, langdock:langdock:actions, langdock:langdock:workspace.
- multi_entity — Can subsidiaries or departments be separated within one contract? [unknown]: Can subsidiaries or departments be separated within one contract? Unknown. Subsidiary/contract-level isolation beyond group and workspace boundaries was not established.

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

Sources: langdock:langdock:roles, langdock:langdock:workspace, langdock:langdock:actions

### 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

#### Langdock

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

Analytics and exports cover adoption and consumption with user-detail controls.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

- adoption_dashboard — Is there an adoption dashboard? [supported]: Active users, message trends, agent/group counts and leaderboards are documented. Sources: langdock:langdock:workspace.
- breakdowns — Can usage be broken down by group, model, feature and assistant? [supported]: Products, models, users, groups, API keys, agents, workflows, projects and add-ins have dashboard/export breakdowns. Sources: langdock:langdock:workspace, langdock:langdock:exports.
- export — Can usage data be exported? [supported]: CSV and Usage Export API, up to 12 months, one million rows per export and 15-minute generation limit. Sources: langdock:langdock:exports.
- privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: User-level data toggle omits listed identifying fields from CSV; whole analytics can be disabled via support. Sources: langdock:langdock:exports, langdock:langdock:workspace.

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

Sources: langdock:langdock:workspace, langdock:langdock:exports

### 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

#### Langdock

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

Chat/BYOK, workspace API and workflows have separate spend controls.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- budget_enforcement: Chat/agents fall back; personal API errors; workflow AI runs stop. Current response overshoot, unpriced models and excluded backbone/workspace API/workflow costs limit a single-budget interpretation.
- chargeback: Usage CSV/API include cost and department/company grouping fields; a full accounting chargeback integration was not established.

- cost_visibility — Can admins see cost or consumption per user and group? [supported]: BYOK analytics show estimated USD from configured custom-model rates; API/extra usage has billed costs. These can differ from provider invoices. Sources: langdock:langdock:workspace, langdock:langdock:byok.
- budgets — Can budgets be set per user or group? [supported]: Workspace, plan, group, user and agent BYOK limits; personal extra limits; workflow workspace and individual limits. Sources: langdock:langdock:byok-limits, langdock:langdock:extra, langdock:langdock:workflow-limits.
- budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: Chat/agents fall back; personal API errors; workflow AI runs stop. Current response overshoot, unpriced models and excluded backbone/workspace API/workflow costs limit a single-budget interpretation. Sources: langdock:langdock:extra, langdock:langdock:byok-limits, langdock:langdock:workflow-limits.
- chargeback — Can costs be exported per cost centre? [partial]: Usage CSV/API include cost and department/company grouping fields; a full accounting chargeback integration was not established. Sources: langdock:langdock:exports.

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

Sources: langdock:langdock:workspace, langdock:langdock:byok, langdock:langdock:byok-limits, langdock:langdock:extra, langdock:langdock:workflow-limits, langdock:langdock:exports

### 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

#### Langdock

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

Enterprise dedicated deployment documents separate administrative-event and conversation-content export APIs. Cloud content export requires workspace enablement and is outside this dedicated finding.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-26; plan=Enterprise dedicated deployment: administrative and resource APIs plus separately enabled Compliance API; Business Cloud outside this finding; add_ons=Dedicated Enterprise deployment and relevant API scopes; Compliance API deployment enablement; deployment_mode=dedicated-instance; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- Audit events, usage rows and conversation-content exports are distinct API functions. The dedicated-deployment behavior is not universal Business Cloud availability.

- admin_events — Are admin and security events logged? [partial]: API logs workspace/model/role/skill/action/workflow changes and failed logins with actor/IP/diff; immutable storage guarantees were not verified. Sources: langdock:langdock:audit.
- content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: Dedicated deployments serve the Compliance API unless disabled for that deployment. A key with the Compliance API scope is required. Conversation message content and tool inputs/outputs are included only when include_message_content=true and include_action_results=true are both set. On Cloud the scope is hidden and requests return 404 until workspace enablement; Business Cloud entitlement is not inferred. Sources: langdock:langdock:compliance-rev2-20261026.
- siem_export — Can logs stream to a SIEM or be exported? [supported]: Cursor-paginated event API is documented for SIEM ingestion, under AUDIT_LOG_API scope. Sources: langdock:langdock:audit.
- ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Unknown. Native legal hold/eDiscovery and audit integrity guarantees were not established. Rechecked 2026-10-26 in Audit Logs API Overview, Export tool parameters and outputs.
- log_retention — How long are logs kept? [supported]: Administrative audit events have documented90-day retention. Conversation data follows the deployment workspace retention settings. A separate SaaS workflow pricing retention period is not asserted for this dedicated deployment. Sources: langdock:langdock:audit, langdock:langdock:workspace, langdock:langdock:pricing.

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

Sources: langdock:langdock:audit, langdock:langdock:compliance-rev2, langdock:langdock:workspace, langdock:langdock:pricing, langdock:langdock:compliance-rev2-20261026, langdock:langdock:audit-20261026, langdock:langdock:workspace-20261026, langdock:langdock:pricing-20261026

### 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

#### Langdock

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

Purview source filtering is documented; generic prompt/file PII redaction remains unverified.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- dlp_integration: Request-enabled Purview label policy can withhold content before AI access for supported Microsoft integrations, with substantial documented exclusions.
- filter_location: The label check runs in Langdock integration code before permitted content reaches the AI; it is not a generic AHV/IBAN detector.
- Unverified pii_detection, pii_action, custom_patterns: The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run.

- pii_detection — Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run.
- pii_action — Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run.
- custom_patterns — Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run.
- dlp_integration — Does it integrate with an existing DLP product? [partial]: Request-enabled Purview label policy can withhold content before AI access for supported Microsoft integrations, with substantial documented exclusions. Sources: langdock:langdock:labels.
- filter_location — Where does filtering run? [partial]: The label check runs in Langdock integration code before permitted content reaches the AI; it is not a generic AHV/IBAN detector. Sources: langdock:langdock:labels.

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

Sources: langdock:langdock:labels

### 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

#### Langdock

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

Instructions, disclaimers and agent compliance checks exist; prompt-level topic enforcement remains incomplete.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- org_instructions: Company description supplies up to 10000 characters in regular chats; agent/project instructions replace that field.
- usage_notice: Admins can set chat/folder disclaimers and custom guidance links; required acceptance is not established.
- content_filters: Governance rules evaluate agent configurations when created/published, not every prompt; failure can lead to manual flag/disable.
- violation_reporting: Rule severity/results and per-rule failure analytics are visible in Governance; runtime prompt-policy reporting was not established.

- org_instructions — Can admins set organisation-wide instructions? [partial]: Company description supplies up to 10000 characters in regular chats; agent/project instructions replace that field. Sources: langdock:langdock:workspace.
- usage_notice — Can users be required to accept a usage policy? [partial]: Admins can set chat/folder disclaimers and custom guidance links; required acceptance is not established. Sources: langdock:langdock:workspace.
- content_filters — Are content filters configurable? [partial]: Governance rules evaluate agent configurations when created/published, not every prompt; failure can lead to manual flag/disable. Sources: langdock:langdock:gov.
- violation_reporting — Are policy hits visible to admins? [partial]: Rule severity/results and per-rule failure analytics are visible in Governance; runtime prompt-policy reporting was not established. Sources: langdock:langdock:gov.

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

Sources: langdock:langdock:workspace, langdock:langdock:gov

## 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

#### Langdock

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

Default Azure Frankfurt/EU storage and provider-specific inference are contractually distinguished.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- backups_logs_region: DPA Appendix 2 places Sentry diagnostic data in EU; full backup/telemetry physical region matrix was not disclosed.
- swiss_hosting: Custom model setup allows CH region on some dedicated deployments, which does not prove end-to-end Swiss platform/support residency.
- support_access_region: User-granted Support sharing expires after 72 hours and is unavailable on dedicated deployments; staff access geography is not specified.

- storage_region — Where are chats, files and indexes stored? [supported]: Terms Appendix 1 places files, prompts, outputs and embeddings in selected EU Azure data centres; Frankfurt named. Sources: langdock:langdock:terms.
- inference_region — Where do model calls run, per provider? [supported]: Azure, OpenAI, Google, AWS Bedrock and Mistral have described EU routes. Opt-in Global Azure/Google/AWS/OpenAI routes can infer worldwide, including US; default model enablement is EU only. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:workspace.
- backups_logs_region — Where are backups, logs and telemetry? [partial]: DPA Appendix 2 places Sentry diagnostic data in EU; full backup/telemetry physical region matrix was not disclosed. Sources: langdock:langdock:dpa.
- support_access_region — From where can vendor staff access data? [partial]: User-granted Support sharing expires after 72 hours and is unavailable on dedicated deployments; staff access geography is not specified. Sources: langdock:langdock:account.
- swiss_hosting — Is Swiss hosting available? [partial]: Custom model setup allows CH region on some dedicated deployments, which does not prove end-to-end Swiss platform/support residency. Sources: langdock:langdock:byok-models.
- residency_plan — Which plan or option provides residency? [supported]: Standard multi-tenant uses EU Azure; global model activation is a controller instruction under DPA section 8. Sources: langdock:langdock:security, langdock:langdock:dpa.

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

Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:workspace, langdock:langdock:byok-models, langdock:langdock:account, langdock:langdock:security

### 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

#### Langdock

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

Deployment minimums differ from Enterprise subscription entry.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Standard SaaS; Enterprise 1000+; managed dedicated 2000+; own cloud/on-premise 5000+; add_ons=Deployment and operations quoted; deployment_mode=not specified; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- customer_cloud: Customer-cloud dedicated deployment from 5000+ seats; detailed operator and feature allocation are contract-specific.
- on_premise: Custom Kubernetes via Helm from 5000+ seats; operator split and infrastructure requirements are not public here.
- mode_feature_gaps: Dedicated lacks Support chat-sharing and password/profile editing in Langdock; other feature controls depend on deployment configuration. No exhaustive parity list was found.
- Unverified air_gapped: Air-gapped operation was not established. Thresholds are not universal feature or pricing entitlements.

- multi_tenant_saas — Is a shared SaaS offered? [supported]: Standard multi-tenant SaaS is hosted on Microsoft Azure within EU. Sources: langdock:langdock:security.
- dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: Langdock-managed single-tenant SaaS from 2000+ seats. Sources: langdock:langdock:security.
- customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: Customer-cloud dedicated deployment from 5000+ seats; detailed operator and feature allocation are contract-specific. Sources: langdock:langdock:security.
- on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Custom Kubernetes via Helm from 5000+ seats; operator split and infrastructure requirements are not public here. Sources: langdock:langdock:security.
- air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Air-gapped operation was not established. Thresholds are not universal feature or pricing entitlements.
- mode_feature_gaps — Which features are missing outside SaaS? [partial]: Dedicated lacks Support chat-sharing and password/profile editing in Langdock; other feature controls depend on deployment configuration. No exhaustive parity list was found. Sources: langdock:langdock:account, langdock:langdock:chat.

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

Sources: langdock:langdock:security, langdock:langdock:account, langdock:langdock:chat

### 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

#### Langdock

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

Microsoft Azure model routes use the contract-described no-training and Modified Abuse Monitoring configuration. Other providers are outside this finding.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business/Enterprise managed Microsoft Azure model routes only; BYOK and Fable/other-provider routes excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default; explicitly selected global Azure models may infer outside EU; os=not specified.

Limitations:
- Fable5/5.1 and direct/OpenAI image/file exceptions are outside this Azure-only scope; no platform-wide ZDR claim is made.

- vendor_training — Does the vendor train on customer content? [supported]: Terms section9 prohibits Langdock use of customer data for model development, training or improvement. Sources: langdock:langdock:terms-rev2.
- provider_training — Do model providers train on it under this product's contracts? [supported]: Appendix1 Microsoft Azure obligations exclude sharing customer prompts/files/embeddings with model developers and using them to train or improve models. Sources: langdock:langdock:terms-rev2.
- provider_retention — How long do model providers keep prompts, including for abuse monitoring? [supported]: For the scoped Microsoft Azure model route, Langdock states Modified Abuse Monitoring disables provider storage of prompts/outputs for abuse monitoring. Platform conversation storage is separate. Sources: langdock:langdock:terms-rev2.
- zero_retention — Is zero data retention available, and on which plan? [supported]: The Azure route has the Modified Abuse Monitoring zero-retention configuration described in Appendix1. This does not establish ZDR for arbitrary customer keys or other providers. Sources: langdock:langdock:terms-rev2.
- human_review — Can provider staff review content? [supported]: Appendix1 states Azure human abuse review of the scoped prompts/outputs is disabled by Modified Abuse Monitoring. Sources: langdock:langdock:terms-rev2.

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

Sources: langdock:langdock:terms-rev2

### 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

#### Langdock

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

Admins control chat retention; file cleanup depends on all remaining references.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- default_retention: No universal default duration is specified. File retention depends on recent files, chats, agents, folders or knowledge links; workflow pricing lists 30-day run retention.
- user_deletion: Deleted chats become unavailable immediately; files belonging only to them are deleted at overnight cleanup. Files linked elsewhere remain; deleting a folder alone retains its files.

- default_retention — What is retained and for how long by default? [partial]: No universal default duration is specified. File retention depends on recent files, chats, agents, folders or knowledge links; workflow pricing lists 30-day run retention. Sources: langdock:langdock:retention, langdock:langdock:pricing.
- admin_retention — Can admins set retention periods? [supported]: Chat inactivity retention options are seven days, one/three/twelve months or forever, with daily irreversible deletion. Sources: langdock:langdock:workspace.
- user_deletion — Can users delete their chats and files permanently? [partial]: Deleted chats become unavailable immediately; files belonging only to them are deleted at overnight cleanup. Files linked elsewhere remain; deleting a folder alone retains its files. Sources: langdock:langdock:retention.
- contract_end_deletion — What is deleted at contract end, and when? [supported]: DPA section 11 requires deletion within 30 days of termination subject to legal retention, confirmation on request and export access until deletion. Sources: langdock:langdock:dpa.

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

Sources: langdock:langdock:retention, langdock:langdock:pricing, langdock:langdock:workspace, langdock:langdock: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

#### Langdock

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

DPA publishes seven default subprocessors and conditional Global routes with transfer mechanisms.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- parent_jurisdiction: Langdock GmbH, Berlin, Germany is contracting entity. Parent-company ownership was not fully established.
- government_access_policy: Confidentiality clause requires minimizing legally compelled disclosure and notifying where legally permitted; no separate request statistics/transparency report was found.

- subprocessor_list — Is a dated sub-processor list published? [supported]: DPA 2.1 Appendix 2 embeds the current named list; trust-centre subprocessor page needs client rendering and did not return text. Sources: langdock:langdock:dpa.
- subprocessor_countries — Which countries do sub-processors operate in? [supported]: Default entities: Microsoft Ireland, AWS EMEA Luxembourg, Google Cloud EMEA Ireland, OpenAI Ireland, Mistral France, Sentry US and Cloudflare US; default processing column is EU. Global opt-ins include worldwide/US inference and Azure EU storage. Sources: langdock:langdock:dpa.
- change_notification — Are customers notified of sub-processor changes? [supported]: At least 14 days before new/replaced subprocessor via public register and email only if subscribed; objection within 14 days of publication. Sources: langdock:langdock:dpa.
- parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: Langdock GmbH, Berlin, Germany is contracting entity. Parent-company ownership was not fully established. Sources: langdock:langdock:terms.
- transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA lists EU-US/Swiss-US DPF, UK extension and EU/UK SCCs with Swiss addenda per provider; Global OpenAI lists EU/UK SCCs. Sources: langdock:langdock:dpa.
- government_access_policy — Is there a published government-access or transparency policy? [partial]: Confidentiality clause requires minimizing legally compelled disclosure and notifying where legally permitted; no separate request statistics/transparency report was found. Sources: langdock:langdock:terms.

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

Sources: langdock:langdock:dpa, langdock:langdock: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

#### Langdock

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

DPA automatically forms part of German-law terms; Swiss and sector materials need qualification.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- dpa: Terms section 16 automatically incorporates public DPA 2.1; nonstandard instructions require written amendment, and negotiability is not promised.
- revdsg_gdpr: GDPR Article 28 governs; provider transfer table includes Swiss safeguards but a complete revDSG scope/addendum was not established.
- ai_act_materials: Governance templates include EU AI Act/GDPR/security checks of agent definitions; these do not establish a complete product provider/deployer dossier.
- sector_materials: Legal-links page advertises a Professional Secrecy Addendum in Trust Center; no FINMA package was obtained.

- dpa — Is a DPA available, and is it negotiable? [partial]: Terms section 16 automatically incorporates public DPA 2.1; nonstandard instructions require written amendment, and negotiability is not promised. Sources: langdock:langdock:terms, langdock:langdock:dpa.
- revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: GDPR Article 28 governs; provider transfer table includes Swiss safeguards but a complete revDSG scope/addendum was not established. Sources: langdock:langdock:dpa.
- governing_law — Which law and court govern the contract? [supported]: German law, Berlin exclusive jurisdiction; German language version binds over English translation. Sources: langdock:langdock:terms.
- ai_act_materials — Is EU AI Act documentation provided? [partial]: Governance templates include EU AI Act/GDPR/security checks of agent definitions; these do not establish a complete product provider/deployer dossier. Sources: langdock:langdock:pricing, langdock:langdock:gov.
- sector_materials — Are FINMA or other sector materials provided? [partial]: Legal-links page advertises a Professional Secrecy Addendum in Trust Center; no FINMA package was obtained. Sources: langdock:langdock:legal.

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

Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:pricing, langdock:langdock:gov, langdock:langdock:legal

### 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

#### Langdock

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

ISO 27001 and SOC 2 Type II are vendor claims pending certificate/report verification.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- iso_27001: Security page claims Langdock ISO 27001; issuer, exact scope and validity were not retrieved.
- soc2: Security page claims SOC 2 Type II; report period/auditor/service scope was not retrieved.
- report_access: Public legal-links page sends certificate/report requests to the Trust Center, which rendered no text in this access method.
- pentest: Vendor describes frequent independent penetration testing; no test report or bounded result was retrieved.
- Unverified c5, other_certifications: No C5, other product certificate, issuer-register verification or gated report was established.

- iso_27001 — ISO 27001 with scope and validity? [partial]: Security page claims Langdock ISO 27001; issuer, exact scope and validity were not retrieved. Sources: langdock:langdock:security.
- soc2 — SOC 2 type, period and covered service? [partial]: Security page claims SOC 2 Type II; report period/auditor/service scope was not retrieved. Sources: langdock:langdock:security.
- c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No C5, other product certificate, issuer-register verification or gated report was established.
- other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. No C5, other product certificate, issuer-register verification or gated report was established.
- report_access — How can customers obtain reports? [partial]: Public legal-links page sends certificate/report requests to the Trust Center, which rendered no text in this access method. Sources: langdock:langdock:legal.
- pentest — Are independent penetration test summaries available? [partial]: Vendor describes frequent independent penetration testing; no test report or bounded result was retrieved. Sources: langdock:langdock:security.

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

Sources: langdock:langdock:security, langdock:langdock:legal

### 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

#### Langdock

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

Encryption and network restrictions are documented; customer key custody is not established.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- private_networking: CIDR IP allowlists block workspace login/use from unapproved networks; private-link endpoint availability was not established.
- Unverified customer_managed_keys, tenant_isolation: Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept.

- encryption_at_rest — Is data encrypted at rest? [supported]: Vendor states AES-256 storage and TLS 1.2+ transport. Sources: langdock:langdock:security.
- customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept.
- private_networking — Is private connectivity or IP restriction available? [partial]: CIDR IP allowlists block workspace login/use from unapproved networks; private-link endpoint availability was not established. Sources: langdock:langdock:ip.
- tenant_isolation — How are customers separated in shared SaaS? [unknown]: How are customers separated in shared SaaS? Unknown. Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept.

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

Sources: langdock:langdock:security, langdock:langdock:ip

### 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

#### Langdock

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.

## 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

#### Langdock

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

Business uses seats with included managed-chat usage; workflow/API and other add-ons are separate. An applicable Standard/BYOK licence tariff is not established.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents and optional modules; Enterprise quoted at1000+; applicable Standard/BYOK tariff unknown; add_ons=Workflows, Governance, API/Extra Usage; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- Inconsistent price representations are retained as a named price gap, not combined into a synthetic tariff.

- pricing_unit — What is the pricing unit? [supported]: Seat/month platform, per-workspace workflow packages, metered API/workflow AI/extra usage, optional per-seat Governance. Sources: langdock:langdock:pricing-rev2.
- list_prices — What are list prices per plan, with date and currency? [unknown]: Unknown applicable Standard/BYOK seat tariff. The public Business headline is EUR25 while the annual price breakdown starts at EUR23.20; billing docs refer to the same pricing page without reconciling them. Enterprise1000+ is quote-only. Prior hashed-calculator rates are excluded.
- included_usage — What usage is included? [partial]: Standard includes managed chat/agent usage under five-hour and weekly windows; Max has 5x. Precise numerical included cost budgets are not public. Starter includes 2500 workflow runs/month but no workflow model tokens. Sources: langdock:langdock:pricing-rev2, langdock:langdock:limits.
- add_ons — Which features cost extra? [partial]: Workflow Starter includes2500runs/month with AI tokens billed separately. The public add-on page lists40k/100k packages and Governance free until2027-01-01, then separately priced per base-plan seat. The applicable binding package/billing-period amounts are not established here. Sources: langdock:langdock:pricing-rev2.
- overage — What do usage beyond limits and premium models cost? [supported]: Extra usage is charged at API rates. Model page lists GPT-5 Mini EUR 0.22 input/1.78 output per million; workflow and API spend use separate caps. Sources: langdock:langdock:extra, langdock:langdock:models.

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

Sources: langdock:langdock:pricing-rev2, langdock:langdock:limits, langdock:langdock:extra, langdock:langdock:models

### 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

#### Langdock

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

All requested200/1000/5000-user totals are unknown because an applicable Business Standard tariff or Enterprise quote is not verified.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Standard up to1000 users; Enterprise1000+; all applicable scenario licence totals unknown; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- ALM-14 shared cost assumptions v1.4, 2026-10-21:12months, list prices, excluding VAT;60/30/10 users at100/400/1500messages monthly,3000input+600output tokens/message. Only separately billed usage uses this token mix.
- ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Unknown base/variable components prevent totals; no silent conversion.

- cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for200users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix.
- cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for1000users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix.
- cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for5000users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix.
- variable_share — Which part depends on usage? [partial]: Managed Business chat includes model usage subject to usage limits. ExtraUsage,workflow/API,Governance and customer-provider BYOK bills are separate. Missing applicable tariff/allowance components remain unknown; no proxy substitutes for vendor-billed usage. Sources: langdock:langdock:billing, langdock:langdock:extra.
- unknown_parts — Which costs could not be priced? [partial]: Business Standard/BYOK applicable seat rate, Enterprise licence/deployment quote, workload-preserving overage and required modules/services are unknown. This prevents a verifiable EUR/CHF total. Sources: langdock:langdock:pricing-rev2, langdock:langdock:billing.

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

Sources: langdock:langdock:pricing-rev2, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock: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

#### Langdock

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

A seven-day self-serve business trial is advertised without a card.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- free_tier: Terms describe a time-limited trial that ends automatically; permanent business free access is not established.
- trial_scope: Pricing says test all platform features, but enterprise deployments and optional enablement cannot be inferred; SAML/SCIM trial configuration was not run.
- sales_gate: Base trial is self-serve; enterprise deployment and custom terms require an offer.

- free_tier — Is there a free tier for business use? [partial]: Terms describe a time-limited trial that ends automatically; permanent business free access is not established. Sources: langdock:langdock:terms.
- self_serve_trial — Is a self-serve business trial available? [supported]: Seven days, no card, EUR 5 model credit and team invitations. Sources: langdock:langdock:pricing.
- trial_scope — Do trials include SSO, connectors and admin features? [partial]: Pricing says test all platform features, but enterprise deployments and optional enablement cannot be inferred; SAML/SCIM trial configuration was not run. Sources: langdock:langdock:pricing.
- sales_gate — Does meaningful evaluation require sales contact? [partial]: Base trial is self-serve; enterprise deployment and custom terms require an offer. Sources: langdock:langdock:billing.

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

Sources: langdock:langdock:terms, langdock:langdock:pricing, langdock:langdock: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

#### Langdock

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

Monthly/annual contract defaults and EUR invoices are public; some pricing representations conflict.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- minimum_commitment: Calculator starts at one user and Business supports up to1000; Enterprise/deployment minimums differ.
- local_invoicing: Langdock GmbH invoices EUR excl tax; contract specifies market-rate conversion of provider foreign-currency charges. CHF invoices were not established.
- transparency_class: Partially specified public rates and usage rules; Enterprise quote-only and headline/calculator rates differ.

- minimum_commitment — What seat or spend minimum applies? [partial]: Calculator starts at one user and Business supports up to1000; Enterprise/deployment minimums differ. Sources: langdock:langdock:pricing, langdock:langdock:security.
- contract_length — What contract lengths are offered? [supported]: Monthly or annual; annual offers 20% reduction on Standard tiers. Sources: langdock:langdock:billing.
- cancellation — How can the contract be cancelled or reduced? [supported]: Terms specify seven-day notice before monthly end, fourteen days before annual/multiyear end; automatic monthly/12-month renewals; notices by text/email or platform. Sources: langdock:langdock:terms.
- local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Langdock GmbH invoices EUR excl tax; contract specifies market-rate conversion of provider foreign-currency charges. CHF invoices were not established. Sources: langdock:langdock:terms.
- transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified public rates and usage rules; Enterprise quote-only and headline/calculator rates differ. Sources: langdock:langdock:pricing, langdock:langdock:billing.

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

Sources: langdock:langdock:pricing, langdock:langdock:security, langdock:langdock:billing, langdock:langdock:terms

### 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

#### Langdock

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

Commercial platform rights are proprietary and time-limited.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- licence_type: Terms grant a nonexclusive/nontransferable contract-term right, not an OSI source licence. Component-level connector/client licences are not enumerated.
- branding_restrictions: Terms prohibit removing proprietary notices and reselling platform access; admin branding options do not transfer platform IP.
- Unverified enterprise_features_closed: A public component-by-component source licence/current revision and distinct open/closed enterprise edition mapping were not established.

- licence_type — Which licence applies to each component? [partial]: Terms grant a nonexclusive/nontransferable contract-term right, not an OSI source licence. Component-level connector/client licences are not enumerated. Sources: langdock:langdock:terms.
- branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Terms prohibit removing proprietary notices and reselling platform access; admin branding options do not transfer platform IP. Sources: langdock:langdock:terms.
- enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. A public component-by-component source licence/current revision and distinct open/closed enterprise edition mapping were not established.

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

Sources: langdock:langdock:terms

### 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

#### Langdock

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

Enterprise dedicated resource/configuration and conversation-content APIs document exports. A complete source/index/ACL workspace exit bundle has not been established.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace, Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-26; plan=Enterprise dedicated deployment: administrative and resource APIs plus separately enabled Compliance API; Business Cloud outside this finding; add_ons=Dedicated Enterprise deployment and relevant API scopes; Compliance API deployment enablement; deployment_mode=dedicated-instance; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- Configuration/file APIs are separate from conversation export. Dedicated Compliance API availability does not establish a Business Cloud entitlement.

- chat_export — Can admins export all chats? [partial]: The dedicated-deployment Compliance API documents paginated conversation/message exports. include_message_content=true adds messages; both it and include_action_results=true add tool arguments and outputs. A scoped key is required. Cloud workspaces need separate enablement and no Business Cloud entitlement is inferred. Sources: langdock:langdock:compliance-rev2-20261026.
- assistant_export — Can assistants and prompts be exported in a reusable format? [partial]: Agent API Get/Create migration exports configuration; attachments/skills must be handled separately and some fields/ownership do not transfer. Sources: langdock:langdock:migration.
- knowledge_export — Can knowledge bases and their sources be exported? [partial]: Knowledge Folder API can retrieve/list files; a complete original-source/index/ACL export bundle was not demonstrated. Sources: langdock:langdock:knowledge, langdock:langdock:knowledge-20261026.
- export_format — Are formats documented and machine-readable? [partial]: Agent and Compliance API JSON plus usage CSV/JSON are documented; this is not a one-click complete workspace export. Sources: langdock:langdock:compliance-rev2, langdock:langdock:migration, langdock:langdock:exports, langdock:langdock:exports-20261026.
- post_termination_window — How long can data be retrieved after termination? [supported]: DPA permits exports during contract and until deletion, which occurs no later than30 days after termination subject to legal retention. Sources: langdock:langdock:dpa.

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

Sources: langdock:langdock:compliance-rev2, langdock:langdock:migration, langdock:langdock:knowledge, langdock:langdock:exports, langdock:langdock:dpa, langdock:langdock:compliance-rev2-20261026, langdock:langdock:migration-20261026, langdock:langdock:knowledge-20261026, langdock:langdock:exports-20261026, langdock:langdock:dpa-20261026

### 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

#### Langdock

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

Berlin vendor support, public status history and a 99% monthly availability term are documented.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- support_channels: Support email is documented; Enterprise has custom account management/support, and rollout programmes have shared Teams/Slack channels.
- uptime_sla: Terms promise at least99% monthly availability with defined exclusions and up to5h scheduled maintenance/month. Statutory remedy/credit procedure exists, but no fixed percentage-credit schedule is published.
- Unverified support_languages: Contractual DE/FR/IT support languages, full hours/timezone and dedicated response/credit schedules were not established.

- support_channels — Which support channels are available on each plan? [partial]: Support email is documented; Enterprise has custom account management/support, and rollout programmes have shared Teams/Slack channels. Sources: langdock:langdock:billing, langdock:langdock:playbook.
- support_languages — Is support available in German, French or Italian? [partial]: The imprint says users and authorities can contact support@langdock.com in German and English. It does not specify contractual French or Italian support, hours or response times. Sources: langdock:langdock:imprint-20261026.
- regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: Langdock GmbH contracts from Berlin, Germany. Sources: langdock:langdock:terms.
- uptime_sla — Is there an uptime SLA with credits? [partial]: Terms promise at least99% monthly availability with defined exclusions and up to5h scheduled maintenance/month. Statutory remedy/credit procedure exists, but no fixed percentage-credit schedule is published. Sources: langdock:langdock:terms.
- status_page — Is there a public status page with history? [supported]: Public status separates app/API/Workflow/Integration history. Sources: langdock:langdock:status.

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

Sources: langdock:langdock:billing, langdock:langdock:playbook, langdock:langdock:terms, langdock:langdock:status, langdock:langdock:imprint-20261026, langdock:langdock:terms-20261026, langdock:langdock:status-20261026

### 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

#### Langdock

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

Rollout support starts at 250 licences; public learning material and champion guidance are available.

Availability: generally-available
Delivery: native
Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified.

Limitations:
- onboarding_service: Dedicated rollout/workshops/shared channels are available from250 seats; exact included versus chargeable services depends on contract.
- user_training: Public workshops have recordings/slides; the complete delivery-language and included-live-training matrix is not specified.
- service_cost: Enterprise custom onboarding/support is quote-based; public per-workshop fees were not found.

- onboarding_service — Is guided onboarding included? [partial]: Dedicated rollout/workshops/shared channels are available from250 seats; exact included versus chargeable services depends on contract. Sources: langdock:langdock:playbook.
- user_training — Is end-user training offered, in which languages? [partial]: Public workshops have recordings/slides; the complete delivery-language and included-live-training matrix is not specified. Sources: langdock:langdock:training.
- use_case_library — Are role-based use cases and templates provided? [supported]: Playbook recommends role-specific prompts/agents and gives structured use-case discovery material. Sources: langdock:langdock:playbook.
- adoption_programme — Is there a champion or adoption programme? [supported]: Playbook includes department champions, follow-ups, hackathons and AI challenges. Sources: langdock:langdock:playbook.
- service_cost — Which services cost extra? [partial]: Enterprise custom onboarding/support is quote-based; public per-workshop fees were not found. Sources: langdock:langdock:billing.

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

Sources: langdock:langdock:playbook, langdock:langdock:training, langdock:langdock:billing

## 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

### langdock:langdock:models

AI Models | Langdock. Public model table lists current text models and EUR metered prices.

- URL: https://langdock.com/models
- Locator: Provider tables
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:model-guide

Model Guide. Users select models or Auto routing; reasoning levels vary by model.

- URL: https://docs.langdock.com/en/using-langdock/models-and-limits/models.md
- Locator: Selecting a Model, Auto and Thinking
- 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

### langdock:langdock:changes

Product Changelog | Langdock. Dated releases document model additions, desktop apps and per-agent confirmations.

- URL: https://langdock.com/changelog
- Locator: 13 October 2026 model release; 15/10 September feature releases
- Evidence kind: documented
- Source date: Not stated
- 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

### langdock:langdock:billing

https://docs.langdock.com/en/admin/billing/pricing.md. Business covers up to 1000 users, BYOK separates model costs, workflows/API are metered and Enterprise is quoted.

- URL: https://docs.langdock.com/en/admin/billing/pricing.md
- Locator: Products, volume tiers, Enterprise and API
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:byok

https://docs.langdock.com/en/admin/byok/byok.md. BYOK replaces completion, embedding and image routes; missing model categories break relevant features.

- URL: https://docs.langdock.com/en/admin/byok/byok.md
- Locator: Options, requirements, setup and usage export
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:byok-routes

Setup Guides. Named BYOK routes include cloud providers, Vercel Gateway and self-hosted OpenAI-compatible HTTPS endpoints.

- URL: https://docs.langdock.com/en/admin/byok/setup-guides.md
- Locator: Provider setup tabs and OpenAI-compatible endpoints
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:research

Deep Research. Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys.

- URL: https://docs.langdock.com/en/using-langdock/chat/tools/deep-research.md
- Locator: Model configuration, limitations and usage
- 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

### langdock:langdock:terms

Terms of Use | Langdock. Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults.

- URL: https://langdock.com/terms
- Locator: Sections 6/7/9/12/15/16/19 and Appendix 1
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:byok-models

How to add your own models. Admins configure completion, image and embedding models, deployments, capability flags and USD accounting rates.

- URL: https://docs.langdock.com/en/admin/byok/adding-models.md
- Locator: Custom model setup and deployment configuration
- Evidence kind: documented
- 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

### langdock:langdock:pricing

Pricing Plans | Langdock. Business headline prices, annual discounts, workflow packages and Governance promotion are public.

- URL: https://langdock.com/pricing
- Locator: Chat & Agents, price breakdown, add-ons and API
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:workspace

Workspace Settings. Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls.

- URL: https://docs.langdock.com/en/admin/workspace/workspace.md
- Locator: Product Settings, Models, Analytics and Customizations
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:limits

Usage Limits. Five-hour and weekly usage windows trigger extra usage or a fallback; spam protection caps 250 messages per three hours.

- URL: https://docs.langdock.com/en/using-langdock/models-and-limits/fair-usage-policy.md
- Locator: Usage windows and exhaustion
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:extra

Extra Usage. Extra usage has workspace/plan/user caps and fallback behavior with possible final-response overshoot.

- URL: https://docs.langdock.com/en/admin/manage-usage/extra-usage.md
- Locator: Enabling extra usage, spend limits and API exceptions
- 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

### langdock:langdock:files

Which file types does Langdock support?. Supported files have different type-specific size limits and processing restrictions.

- URL: https://docs.langdock.com/en/using-langdock/troubleshooting/faq/supported-file-types.md
- Locator: Format/size tables and processing limits
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:file-count

What are the file limits in the chat and in agents?. Web message uploads allow 50 files, mobile five; agent knowledge and knowledge bases have separate limits.

- URL: https://docs.langdock.com/en/using-langdock/troubleshooting/faq/file-limit.md
- Locator: Chat and agent attachment limits
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:retrieval

Knowledge Basics. Direct file previews differ from semantic search over 2000-character chunks, returning up to 50 passages.

- URL: https://docs.langdock.com/en/using-langdock/guides/knowledge/knowledge-basics.md
- Locator: Direct context and embedding search
- 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

### langdock:langdock:knowledge

Knowledge bases. Persistent shareable knowledge bases accept up to 1000 text documents, search chunks and attach to agents.

- URL: https://docs.langdock.com/en/using-langdock/library/knowledge-bases.md
- Locator: Creation, sharing, limits and agent use
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:agents

Agent Configuration. Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions.

- URL: https://docs.langdock.com/en/using-langdock/agents/configuration.md
- Locator: Agent configuration, knowledge and source restriction
- 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

### langdock:langdock:sync

Folder Sync. Daily folder sync supports SharePoint, OneDrive, Drive and Confluence, with real-time user access checks.

- URL: https://docs.langdock.com/en/using-langdock/guides/integrations/folder-sync.md
- Locator: Setup, permission checks, sync behavior and owner removal
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:integrations

Integration Directory. The native directory lists Microsoft, Google, Atlassian, CRM, BI, vector search, DeepL and audio integrations.

- URL: https://docs.langdock.com/en/using-langdock/integrations/integration-directory.md
- Locator: Native integration directory
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:mcp

Model Context Protocol (MCP). MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default.

- URL: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/mcp.md
- Locator: Transports, authentication and tool confirmation
- 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

### langdock:langdock:labels

Sensitivity Label Policy. A request-enabled Purview label policy filters supported integrations, with documented actions and upload exceptions.

- URL: https://docs.langdock.com/en/admin/manage-integrations/sensitivity-label-policy.md
- Locator: Availability, enforcement, exceptions and unsupported areas
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:actions

Manage Action Access. Admins share integrations and actions with users/groups/API keys; native core actions cannot be disabled.

- URL: https://docs.langdock.com/en/admin/manage-integrations/manage-action-access.md
- Locator: Access settings and native-action exception
- 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

### langdock:langdock:chat

Basic Chat functionalities. Chat supports model selection and governed tools; memory, deep research and agent tool conditions differ.

- URL: https://docs.langdock.com/en/using-langdock/chat/functionalities.md
- Locator: Model selector and tool availability
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:account

Account Settings. Account settings include five UI languages, personal controls and temporary 72-hour Support sharing.

- URL: https://docs.langdock.com/en/using-langdock/account/account.md
- Locator: Preferences, shared chats, custom instructions and memory
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:memory

Memory. Memory works in regular chats only, with a 50-memory cap and view/edit/delete controls.

- URL: https://docs.langdock.com/en/using-langdock/chat/tools/memory.md
- Locator: Availability, management and limits
- 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

### langdock:langdock:roles

Roles and extra permissions. System roles, up to five custom roles and delegated group permissions are configurable.

- URL: https://docs.langdock.com/en/admin/workspace/roles.md
- Locator: System roles, custom roles and group permissions
- 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

### langdock:langdock:web

Web Search. Web search returns inspectable citations and has a separate open-URL tool.

- URL: https://docs.langdock.com/en/using-langdock/chat/tools/web-search.md
- Locator: Search behavior and source inspection
- 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

### langdock:langdock:workflows

Introduction to Workflows. Workflows chain agents, integrations and logic with form, schedule and event triggers after admin activation.

- URL: https://docs.langdock.com/en/using-langdock/workflows/introduction.md
- Locator: Introduction and activation
- 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

### langdock:langdock:hitl

Human in the Loop. Workflow runs can pause for editor approval or per-action confirmation.

- URL: https://docs.langdock.com/en/using-langdock/workflows/fundamentals/human-in-the-loop.md
- Locator: Approval and action confirmation
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:excel

Excel Add-in. The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites.

- URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/excel.md
- Locator: Install, workbook operations and edit permissions
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:outlook-rev2

Outlook Add-in. The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action.

- URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/outlook.md
- Locator: Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:outlook-marketplace

Langdock for Outlook, by Langdock GmbH. Vendor listing offers the add-in to every paid Langdock plan and trials, with draft review before sending.

- URL: https://marketplace.microsoft.com/en-us/product/WA200011534?tab=Overview
- Locator: Overview and eligibility sentence
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:outlook-rev2-20261026

Outlook Add-in. The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action.

- URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/outlook.md
- Locator: Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:pricing-20261026

Pricing Plans | Langdock. Business headline prices, annual discounts, workflow packages and Governance promotion are public.

- URL: https://langdock.com/pricing
- Locator: Chat & Agents, price breakdown, add-ons and API
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:changes-20261026

Product Changelog | Langdock. Dated releases document model additions, desktop apps and per-agent confirmations.

- URL: https://langdock.com/changelog
- Locator: 13 October 2026 model release; 15/10 September feature releases
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:outlook-admin-20261026

Outlook Add-in setup. Admins set Outlook add-in access to Nobody, Everyone or Specific members and groups; Outlook Email and Calendar integrations have separate access/scopes.

- URL: https://docs.langdock.com/en/admin/manage-integrations/add-in-setup-guides/outlook.md
- Locator: Availability and access settings
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:agents-20261026

Agent Configuration. Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions.

- URL: https://docs.langdock.com/en/using-langdock/agents/configuration.md
- Locator: Agent configuration, knowledge and source restriction
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:research-20261026

Deep Research. Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys.

- URL: https://docs.langdock.com/en/using-langdock/chat/tools/deep-research.md
- Locator: Model configuration, limitations and usage
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:hitl-20261026

Human in the Loop. Workflow runs can pause for editor approval or per-action confirmation.

- URL: https://docs.langdock.com/en/using-langdock/workflows/fundamentals/human-in-the-loop.md
- Locator: Approval and action confirmation
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:mcp-20261026

Model Context Protocol (MCP). MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default.

- URL: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/mcp.md
- Locator: Transports, authentication and tool confirmation
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:excel-20261026

Excel Add-in. The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites.

- URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/excel.md
- Locator: Install, workbook operations and edit permissions
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### 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

### langdock:langdock:mcp-server

Langdock Agent MCP Server. A public MCP endpoint exposes workspace agents under Agent API scope.

- URL: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/langdock-agent-mcp-server.md
- Locator: Endpoint, authentication and tools
- 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

### langdock:langdock:desktop-rev2

Enterprise Guide for Langdock Desktop. Managed desktop rollout supports machine-wide Windows packages and signed/notarized macOS installers; these installation instructions do not change subscription entitlements.

- URL: https://docs.langdock.com/en/admin/desktop-app/deploy.md
- Locator: Windows machine-wide MSIX/Intune; macOS PKG/DMG/Jamf/Kandji; HTTP200 Markdown re-read2026-10-21
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:mobile-rev2

Mobile App. HTTP200 Markdown introduction links official Apple App Store and Google Play mobile clients.

- URL: https://docs.langdock.com/en/using-langdock/mobile-app/introduction.md
- Locator: Download routes
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:desktop-product

Langdock Desktop. Windows/macOS desktop clients use the same workspace and approved models as web.

- URL: https://langdock.com/products/desktop
- Locator: Downloads and Q&A
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:mobile-product

Langdock Mobile. Vendor mobile page offers iOS/Android clients using the workspace-approved models.

- URL: https://langdock.com/mobile
- Locator: App Store/Google Play links and Q&A
- Evidence kind: vendor-claimed
- 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

### langdock:langdock:teams

How to use the Teams Bot. Teams has personal bot chats and channel threads with team participation.

- URL: https://docs.langdock.com/en/using-langdock/guides/chatbots/teams-bot.md
- Locator: Private chats, channels and admin install
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:teams-20261026

How to use the Teams Bot. The public Markdown guide was retrieved with HTTP 200. A workspace admin installs the Teams app, which supports private bot chat and channel threads using @Langdock; it is separate from the web chat history.

- URL: https://docs.langdock.com/en/using-langdock/guides/chatbots/teams-bot.md
- Locator: Installation note; Two Ways to Use the Teams Bot; Private Chat; Using Langdock in Channels; Limitations
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:editor

Document Editor. Document Editor replaces Canvas and exports Markdown, Word and PDF; imported Word/PDF cannot be edited directly there.

- URL: https://docs.langdock.com/en/using-langdock/chat/document-editor.md
- Locator: Editor, AI edits, export and limitations
- 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

### langdock:langdock:images

Image Generation. Chat invokes configured image-generation models with a user model selector.

- URL: https://docs.langdock.com/en/using-langdock/chat/tools/image-generation.md
- Locator: Generating images and model choice
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:analysis

Using Langdock for Data Analysis. Tabular analysis produces charts and downloadable spreadsheet and document formats.

- URL: https://docs.langdock.com/en/using-langdock/guides/data-analysis.md
- Locator: Analysis procedure and outputs
- 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

### langdock:langdock:projects

Projects. Shared projects expose all project chats/files to members and can be shared with users/groups, not the whole workspace.

- URL: https://docs.langdock.com/en/using-langdock/chat/projects.md
- Locator: Project sharing and permissions
- 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

### langdock:langdock:saml

https://docs.langdock.com/en/admin/security/saml/saml.md. SAML 2.0 requires a verified domain; MFA comes from the IdP rather than standalone Langdock MFA.

- URL: https://docs.langdock.com/en/admin/security/saml/saml.md
- Locator: Checklist, supported IdPs, external authentication and MFA
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:scim

https://docs.langdock.com/en/admin/security/scim/scim.md. SCIM 2.0 supports Entra provisioning after SAML setup and domain verification.

- URL: https://docs.langdock.com/en/admin/security/scim/scim.md
- Locator: Overview and prerequisites
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:scim-entra

https://docs.langdock.com/en/admin/security/scim/entra.md. Entra target actions control provisioning/deactivation and group synchronization.

- URL: https://docs.langdock.com/en/admin/security/scim/entra.md
- Locator: Target Object Actions and optional group synchronization
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:leaver

Unassign Agents. Agents whose owner is deactivated keep functioning but cannot be edited until reassigned.

- URL: https://docs.langdock.com/en/admin/manage-agents/unassign-agents.md
- Locator: Unassigned agents and reassignment
- 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

### langdock:langdock:exports

Usage Exports. Usage CSV exports span users, agents, keys, projects, models and workflows, with user-detail privacy controls.

- URL: https://docs.langdock.com/en/admin/compliance-and-governance/usage-exports.md
- Locator: Export data types, limits and user-level data
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:byok-limits

Usage and spend limits. BYOK cost limits depend on configured prices and exclude backbone, workflows and workspace API usage.

- URL: https://docs.langdock.com/en/admin/manage-usage/byok/usage-limits.md
- Locator: Scope, unpriced models and spend limits
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:workflow-limits

Workflow limits. Workflow AI use has a separate workspace EUR limit and per-workflow USD limits that block new runs.

- URL: https://docs.langdock.com/en/admin/manage-workflows/spend-limits.md
- Locator: Spend limits and execution step cap
- 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

### langdock:langdock:audit

Audit Logs API Overview. Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion.

- URL: https://docs.langdock.com/en/developer/audit-logs-api/intro-to-audit-logs-api.md
- Locator: Event schema, retention and prerequisites
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:compliance-rev2

Export tool parameters and outputs. Cloud Compliance API is workspace-enable­ment gated; dedicated deployments serve it unless disabled. Conversation exports include messages and tool inputs/outputs only with both explicit flags.

- URL: https://docs.langdock.com/en/developer/compliance-api/export-tool-results.md
- Locator: Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:compliance-rev2-20261026

Export tool parameters and outputs. Cloud Compliance API is workspace-enable­ment gated; dedicated deployments serve it unless disabled. Conversation exports include messages and tool inputs/outputs only with both explicit flags.

- URL: https://docs.langdock.com/en/developer/compliance-api/export-tool-results.md
- Locator: Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:audit-20261026

Audit Logs API Overview. Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion.

- URL: https://docs.langdock.com/en/developer/audit-logs-api/intro-to-audit-logs-api.md
- Locator: Event schema, retention and prerequisites
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:workspace-20261026

Workspace Settings. Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls.

- URL: https://docs.langdock.com/en/admin/workspace/workspace.md
- Locator: Product Settings, Models, Analytics and Customizations
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### 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

### langdock:langdock:gov

Compliance Rules. Custom agent compliance checks produce pass/fail and severity results with per-rule analytics.

- URL: https://docs.langdock.com/en/admin/governance/compliance-rules.md
- Locator: Rule operation, failures and analytics
- 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

### langdock:langdock:security

security. Default Azure EU SaaS, managed dedicated from 2000 and customer-cloud/on-premise from 5000 seats are advertised.

- URL: https://langdock.com/security
- Locator: Deployment, security, BYOK and certifications
- Evidence kind: vendor-claimed
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:dpa

Data Processing Agreement | Langdock. DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table.

- URL: https://langdock.com/dpa
- Locator: Sections 7-12 and Appendices 1/2
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:terms-rev2

Terms of Use | Langdock. Microsoft Azure routes use Modified Abuse Monitoring, disabling provider prompt/output retention and human abuse review. Other provider/model routes require separate assessment.

- URL: https://langdock.com/terms
- Locator: Section9 and Appendix1 Microsoft Azure service terms
- Evidence kind: documented
- Source date: Not stated
- 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

### langdock:langdock:retention

How long are files saved in Langdock?. Deleted chats are immediately unavailable and unreferenced files are cleaned overnight; shared file references survive.

- URL: https://docs.langdock.com/en/using-langdock/troubleshooting/faq/data-retention-for-files.md
- Locator: Retention by object type
- 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

### langdock:langdock:legal

https://docs.langdock.com/en/admin/compliance-and-governance/legal-compliance.md. DPA applies automatically and a Professional Secrecy Addendum and certificates are linked from the Trust Center.

- URL: https://docs.langdock.com/en/admin/compliance-and-governance/legal-compliance.md
- Locator: Legal and compliance links
- 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

### 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

### langdock:langdock:ip

IP Restrictions. CIDR allowlists immediately block unauthorized network access when enabled.

- URL: https://docs.langdock.com/en/admin/security/ip-restrictions.md
- Locator: Prerequisites and enforcement
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### 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

### 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

### langdock:langdock:pricing-rev2

Pricing Plans | Langdock. The page maps Business to up to1000 users and Enterprise to1000+; the Standard headline and breakdown disagree, so no applicable Standard/BYOK tariff is established here.

- URL: https://langdock.com/pricing
- Locator: Business/Enterprise cards; price breakdown; product add-ons
- Evidence kind: vendor-claimed
- 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

### langdock:langdock: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

### langdock:langdock:migration

Agent Migration Guide. Agent API export/import preserves selected configuration; files/skills and some fields require separate migration.

- URL: https://docs.langdock.com/en/developer/agents-api/agent-migration.md
- Locator: Prerequisites, exported settings and field mapping
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:dpa-20261026

Data Processing Agreement | Langdock. DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table.

- URL: https://langdock.com/dpa
- Locator: Sections 7-12 and Appendices 1/2
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:migration-20261026

Agent Migration Guide. Agent API export/import preserves selected configuration; files/skills and some fields require separate migration.

- URL: https://docs.langdock.com/en/developer/agents-api/agent-migration.md
- Locator: Prerequisites, exported settings and field mapping
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:knowledge-20261026

Knowledge bases. The public Markdown guide was retrieved with HTTP 200. The Knowledge Folder API can upload, update, delete, retrieve and search files; Viewer supports retrieval, while writes need Editor. This does not establish a complete index/ACL workspace export bundle.

- URL: https://docs.langdock.com/en/using-langdock/library/knowledge-bases.md
- Locator: Create a Knowledge base and add documents, API upload; Share search access; Convert a Knowledge base to a folder
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:exports-20261026

Usage Exports. The public Markdown guide was retrieved with HTTP 200. Workspace administrators can export usage analytics as CSV or through the Usage Export API, with up to 12 months of history and JSON-valued mapping fields. Usage analytics are distinct from a complete chat/knowledge export.

- URL: https://docs.langdock.com/en/admin/compliance-and-governance/usage-exports.md
- Locator: Accessing Usage Exports; Export Limits; Export Data Structure; Usage Exports; Data Retention
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:playbook

Rollout Playbook. Dedicated rollout support/workshops start at 250 licences and include a champion approach.

- URL: https://docs.langdock.com/en/admin/ai-adoption-and-rollout/getting-started/rollout-playbook.md
- Locator: Programme qualification and rollout phases
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:status

status. The public status page covers the app, APIs, Workflows and Integrations with history.

- URL: https://status.langdock.com/
- Locator: Components and history
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21

### langdock:langdock:terms-20261026

Terms of Use | Langdock. Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults.

- URL: https://langdock.com/terms
- Locator: Sections 6/7/9/12/15/16/19 and Appendix 1
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:imprint-20261026

Langdock imprint and contact point. Users and authorities can contact support@langdock.com in German and English; the imprint identifies Langdock GmbH in Berlin.

- URL: https://langdock.com/imprint
- Locator: Contact Point for Users and Authorities
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:status-20261026

status. The public status page covers the app, APIs, Workflows and Integrations with history.

- URL: https://status.langdock.com/
- Locator: Components and history
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-26

### langdock:langdock:training

Langdock Workshops. Official workshop recordings/slides cover chat, skills, integrations, agents and workflows.

- URL: https://docs.langdock.com/en/using-langdock/resources/langdock-workshops.md
- Locator: Workshop catalogue
- Evidence kind: documented
- Source date: Not stated
- Retrieved: 2026-10-21
