--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/dust-vs-glean/" data_url: "https://onaihq.com/compare/agents/dust-vs-glean/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" --- # Dust vs Glean > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 47 criteria with sourced findings for both products, including 47 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - Dust source checks: 2026-10-21. - Glean source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/dust-vs-glean/ - Machine-readable JSON: https://onaihq.com/compare/agents/dust-vs-glean/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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust offers per-message model choice and ordered auto-model lists, with access-tier and region controls. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit plan (Free/Pro/Max); Enterprise model access inherits the published catalogue; model-tier and EU eligibility separately constrained; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - The catalogue finding is restricted to named documentation entries; conflicting Gemini4 Argon EU eligibility is an explicit gap. - providers — Which model providers are available? [supported]: Docs list OpenAI, Anthropic, Google, Mistral and Fireworks-served models; exact enabled models depend on workspace and tier. Sources: dust:dust:models, dust:dust:eu-models. - current_models — Which current models are selectable on this plan? [partial]: The model-selection document lists GPT6.1 Sol, Claude Opus5.5/Sonnet5.5, Gemini3.8 Flash and Mistral models. Gemini4 Argon is excluded from this current-EU availability finding: its release note conflicts with the EU table, and the documented authoritative picker flag was not observed. No complete current tenant catalogue is claimed. Sources: dust:dust:models, dust:dust:changelog, dust:dust:eu-models, dust:dust:pricing. - user_choice — Can users pick the model per chat? [supported]: The composer chooses a model for the next message; Agent Builder sets a persistent agent default. Sources: dust:dust:models. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [supported]: Basic/Standard/Premium use ordered candidate lists and availability fallback, not prompt-dependent task routing. A replacement indicator names the fallback during a detected outage. Sources: dust:dust:models. - multimodal_input — Which models accept images, audio or files? [partial]: Conversation files support images, documents and audio transcripts; the exact input capability for every current model is not fully tabulated. Sources: dust:dust:files. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:models, dust:dust:eu-models, dust:dust:changelog, dust:dust:pricing, dust:dust:files #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public changelog and exact agent model selection are documented; release-lag and removal notice remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; 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 dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established. - changelog — Is there a dated public model changelog? [supported]: The public changelog contains dated model releases including Gemini 4 Argon on October 14, 2026. Sources: dust:dust:changelog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? The dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established. - version_pinning — Can an admin keep an older model version? [partial]: An agent can select a specific model and keeps it until changed, subject to continued provider/workspace availability. No indefinite old-version entitlement is established. Sources: dust:dust:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog, dust:dust: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 ### 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. #### Dust 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. #### 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 ### 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. #### Dust 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. #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins cap models by workspace, group and member, with explicit published-agent exceptions and credit limits. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No two-user enforcement test. Published agents can run above member tiers if the separate admin setting permits it. - model_allowlist_by_group — Can admins limit models per group? [supported]: Model access ceilings apply to the workspace, groups or individuals and cover reasoning efforts as well as auto selections. Sources: dust:dust:tiers. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: EU-only mode restricts all active agents and pickers to EU-hosted models. Spaces bound knowledge and agent access; arbitrary per-data-class model rules were not established. Sources: dust:dust:eu-models, dust:dust:spaces. - default_model — Can admins set the default model? [supported]: Builders configure an agent default, which may be exact or Basic/Standard/Premium. Composer changes do not edit it for others. Sources: dust:dust:models. - user_limits — What per-user message or token limits apply, and are they published? [supported]: Free seats have 500 lifetime credits, Pro 8,000/month and Max 40,000/month, plus applicable shared-pool rules and member spend limits. Sources: dust:dust:credits, dust:dust:credit-management. - limit_behaviour — What happens when a limit is reached? [supported]: Members block when applicable sources/caps are exhausted. A message begun under a cap can finish above it; new messages then block. A separate root-task checkpoint can pause at 600 AWU. Sources: dust:dust:credit-management, dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:tiers, dust:dust:eu-models, dust:dust:spaces, dust:dust:models, dust:dust:credits, dust:dust:credit-management #### 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 ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Conversation files and code/OCR handling are documented; conflicting effective upload caps are explicitly unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No common PDF/scan/Excel/PowerPoint fixture run. - Do not use either disputed cap set as the effective Business upload limit. - formats — Which formats are accepted? [supported]: Conversation uploads accept documents/PDF, text/code, Excel/CSV/TSV, images and supported audio. Direct video uploads are explicitly excluded by the limits FAQ. Sources: dust:dust:files, dust:dust:file-limits. - limits — What size and count limits apply per file and chat? [unknown]: Effective image/audio/tabular maximums and file counts are unknown: Conversation Files lists5/25/50MB while File size limits lists20/100/350MB. Both mention50MB general data files, but neither resolves the actual current per-plan upload route. No logged-in upload test was performed. - ocr — Are scanned PDFs read? [partial]: Computer documents OCR for English, French and mixed scans with page-level caveats. Drive connector itself ignores image-only files; upload to a conversation is the documented route. Sources: dust:dust:computer, dust:dust:drive. - spreadsheets — Are Excel tables read with structure intact? [partial]: Computer can read, calculate and edit uploaded Excel with code. Formula/style preservation must be checked; no fixture fidelity result is available. Sources: dust:dust:computer. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Conversation uploads are not indexed in workspace sources. Computer can inspect full files, while knowledge search retrieves relevant context; complete chunk visibility was not verified. Sources: dust:dust:files, dust:dust:computer, dust:dust:search. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:files, dust:dust:file-limits, dust:dust:computer, dust:dust:drive, dust:dust:search #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Spaces persist shared knowledge and bind it to agent tools. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - persistent_collections — Can users keep document collections across chats? [supported]: Open and restricted Spaces retain connected sources, folders and other data across conversations. Sources: dust:dust:spaces. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Open Spaces are workspace-wide; restricted Spaces have explicit members or provisioned groups. Sources: dust:dust:spaces. - size_limits — What are the collection limits? [partial]: Business supports five Spaces and Enterprise 100. Complete per-Space storage/document quotas were not established. Sources: dust:dust:spaces. - assistant_binding — Can collections be bound to an assistant? [supported]: An agent tool can use selected Space data; Space membership governs agent visibility and use. Sources: dust:dust:spaces. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:spaces #### 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 ### 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). #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Managed content connectors coexist with MCP tools and beta imports; Microsoft content indexing is account-scoped. Availability: generally-available Delivery: official-integration Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business: up to3 connections and5 remote MCP servers; Enterprise: unlimited connection/MCP packaging; beta imports identified separately; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - Managed sources, metadata/table-query connections, MCP tools and beta imports are separate routes; no all-systems managed-index promise. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: The Microsoft connection syncs selected SharePoint drives/documents within the connecting account permissions. Teams-associated SharePoint content is described; this does not establish Outlook mail or all Teams messages as indexed sources. Sources: dust:dust:microsoft. - google_workspace — Which Google sources are connected? [partial]: Drive documents, Sheets, Slides and text PDFs can sync. Gmail is separately available as an MCP tool in the credits/tool catalog, not established as the same managed content index. Sources: dust:dust:drive, dust:dust:credits. - atlassian — Confluence and Jira? [partial]: Confluence indexes selected global spaces, excluding restricted pages. Jira has a beta custom import and MCP tool route; do not count the beta import as a general managed connector. Sources: dust:dust:confluence, dust:dust:jira, dust:dust:credits. - other_systems — Which other business systems? [partial]: Documented routes include managed Slack/Notion/GitHub and Salesforce/Zendesk/Snowflake sources/tools. BigQuery specifically uses a dedicated-service-account table-query connection: Dust keeps metadata, not a synchronized table-content index; queries stay within the chosen BigQuery dataset location and Space admins select tables. General Business/Enterprise connection limits apply; a BigQuery-specific commercial add-on is not separately specified. Sources: dust:dust:sources, dust:dust:credits, dust:dust:r2-bigquery, dust:dust:pricing. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Admins can connect a customer-hosted MCP server at a reachable secured URL. This is tool access, not evidence of a native SMB/file-share connector or on-premises Dust deployment. Sources: dust:dust:tools. - connector_provider — Who builds and maintains each connector? [supported]: Dust manages built-in connections; external MCP servers can be vendor/community/customer hosted and authenticated separately. Sources: dust:dust:permissions, dust:dust:tools. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:credits, dust:dust:confluence, dust:dust:jira, dust:dust:sources, dust:dust:r2-bigquery, dust:dust:pricing, dust:dust:tools, dust:dust:permissions #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge access is documented through connection-account scope and Dust Spaces; per-user source-ACL mirroring is unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Connector access through one account is not counted as demonstrated per-user source permission preservation. - source_permissions_respected — Are source permissions enforced per user? [partial]: Drive and Microsoft content available to Dust follows the connecting account and admin-selected data. Users then access agent knowledge through Space membership. Individual source ACL inheritance for each querying user was not established. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Managed content is synchronized under the connection identity and gated through open/restricted Spaces; personal tool credentials are a separate per-user route. Sources: dust:dust:permissions, dust:dust:credentials. - revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins choose connector folders/documents/sites and control restricted Space membership. Sources: dust:dust:spaces, dust:dust:microsoft. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions, dust:dust:credentials, dust:dust:spaces #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Managed connectors copy and synchronize content, with source-specific refresh and deletion timing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; 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]: Connections synchronize content into Dust; conversation uploads remain scoped to the chat. MCP tools can access live services separately. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools. - sync_interval — How often does an index refresh? [supported]: Microsoft describes five-minute sync cycles; Drive says a few minutes; Confluence describes event updates plus an approximate hourly check. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:confluence. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Microsoft changes/deletions appear on a subsequent sync and large batches can take longer. Drive deletions occur during its sync. No measured end-to-end bound was tested. Sources: dust:dust:microsoft, dust:dust:drive. - index_location — Where is indexed content stored? [partial]: Dust markets EU or US hosting; exact per-index country, cloud provider and backup location were not established. Sources: dust:dust:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools, dust:dust:microsoft, dust:dust:drive, dust:dust:confluence, dust:dust:security #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge and research tools cite sources; observed retrieval quality remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - citations — Are answers linked to specific sources? [supported]: Deep-dive documents citations to documents, web pages and data queries. Sources: dust:dust:deep. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agent-specific private memory persists across chats and can be viewed or deleted. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - custom_instructions — Can users set persistent instructions? [partial]: Agent instructions persist in the agent configuration and saved memory can contain user preferences; a separate personal global-instructions setting was not established. Sources: dust:dust:builder, dust:dust:memory. - cross_chat_memory — Does the product remember facts across chats? [supported]: The Memory tool retains user-specific information across conversations per agent. Sources: dust:dust:memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users can view and delete agent memories, which persist until deletion. Direct editing or a global personal off switch was not established. Sources: dust:dust:memory. - admin_memory_controls — Can admins turn memory off? [unknown]: Can admins turn memory off? The Agent Memory and governance guides were checked; an admin-wide switch to disable all memory was not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:memory #### 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 ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Custom agents have instructions, models, knowledge and tools with group-governed creation and sharing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; 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, models, knowledge and tools. Sources: dust:dust:builder. - creator_permissions — Can admins limit who creates them? [supported]: Create/publish agent and skill permissions can be Everyone, Groups or Admin only. Sources: dust:dust:governance. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Agents and their knowledge access are controlled by sharing and Space memberships; group governance regulates publishing. Sources: dust:dust:builder, dust:dust:spaces, dust:dust:governance. - catalogue — Is there an internal assistant directory? [partial]: Published/shared agents and default agents are discoverable in the workspace; exact catalog configuration was not observed. Sources: dust:dust:builder, dust:dust:models. - prompt_library — Are shared prompt templates available? [partial]: Reusable agents and skills package instructions, knowledge and tools. A separate legacy prompt-library feature is not assumed. Sources: dust:dust:governance, dust:dust:builder. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:spaces, dust:dust:models #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust supports built-in tools, customer MCP servers and personal or shared credentials. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No external-tool call or access-boundary fixture was run. - builtin_tools — Which tools are built in? [supported]: Documented tools include knowledge search, table queries, web search, Computer, images, speech and agent orchestration. Sources: dust:dust:credits, dust:dust:computer. - custom_actions — Can admins add API actions? [supported]: Admins can connect customer-written MCP tools over secured publicly reachable URLs. Sources: dust:dust:tools. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Admins add remote MCP servers with automatic/static OAuth or bearer-token authentication and can restrict tools to skills. Sources: dust:dust:tools. - tool_auth — Do tools act as the user or as a shared account? [supported]: Shared credentials act as one service account; personal credentials use each user OAuth after initial admin setup. Sources: dust:dust:credentials. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Computer network domains can require user approval; dated connector releases describe approval for writes. A universal confirmation rule for every tool and unattended trigger was not established. Sources: dust:dust:computer, dust:dust:changelog. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:computer, dust:dust:tools, dust:dust:credentials, dust:dust:changelog #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents can search the web and run multi-step Deep-dive research. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web_search — Is web search available? [supported]: Web Search & Browse runs Google queries and reads result pages. Sources: dust:dust:web. - admin_toggle — Can admins disable it per organisation or group? [partial]: Web tools are selected in agent configuration; default Deep-dive can be disabled by admins. A universal per-group web-off rule was not established. Sources: dust:dust:web, dust:dust:deep. - search_provider — Which search provider handles queries, and where? [partial]: The guide calls the search a Google query. The intermediary provider and countries handling queries/crawling were not established. Sources: dust:dust:web. - deep_research — Is multi-step research with a report available? [supported]: Deep-dive plans, spawns parallel specialists and produces a research report. It searches Company Data and cannot use Table Query. Sources: dust:dust:deep. - web_citations — Are web sources cited? [supported]: Deep-dive promises citations to web and company sources. Sources: dust:dust:deep. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:web, dust:dust:deep #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents support schedules and webhook automation with admin-created event sources. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - workflow_builder — Is there a workflow or chain builder? [partial]: Agents orchestrate tools and sub-agents; external n8n and trigger workflows are documented. A separate visual multi-step chain canvas was not established. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Agents can run on recurring schedules. Sources: dust:dust:schedules. - event_triggers — Can external events start a workflow? [supported]: Built-in webhook sources include GitHub, Jira, Linear, Zendesk and Fathom; signed custom webhooks are supported. Sources: dust:dust:webhooks. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Admins connect event sources; builders/members attach filtered triggers in Agent Builder and can use natural-language trigger creation through Dust Default. Sources: dust:dust:webhooks, dust:dust:changelog. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog, dust:dust:schedules, dust:dust:webhooks #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Multi-step agent work and visible Deep-dive progress are documented; safety controls depend on tool and trigger. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No shared gather/documents/email fixture or side-effect audit was run. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Deep-dive plans, delegates and synthesizes, and Computer can execute deterministic file/code work. Sources: dust:dust:deep, dust:dust:computer. - visible_steps — Are steps and tool calls shown? [supported]: Deep-dive documentation shows reasoning and sub-agent progress in real time. Sources: dust:dust:deep. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Computer domains may require user approval and selected connector write actions ask for approval. Pods agents can also act without a human, so universal write confirmation is not claimed. Sources: dust:dust:computer, dust:dust:changelog, dust:dust:pods. - stop_control — Can the user stop a running task? [partial]: The 600-AWU root-task checkpoint offers Stop or Continue. A complete general stop/rollback behavior was not tested. Sources: dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:computer, dust:dust:changelog, dust:dust:pods, dust:dust:credits #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: supported Dust offers conversation/knowledge APIs, enforceable API-key caps and OAuth MCP access. Availability: generally-available Delivery: native Scope: surfaces=Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business conversation API; Enterprise adds Data Source API per pricing; MCP subject to workspace enablement; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. - chat_api — Is there an API for chat and assistants? [supported]: Documented APIs retrieve/create conversations and messages with scoped API keys. Sources: dust:dust:get-conversation, dust:dust:api-keys. - knowledge_api — Can documents be loaded through an API? [supported]: The data-source API upserts documents into scoped data sources. Sources: dust:dust:upsert. - api_governance — Do audit, budgets and model rules apply to API use? [supported]: Per-key caps reject further API usage at the limit. Model overrides obey workspace/tier rules; programmatic usage uses the workspace pool and does not count toward beta pooled group budgets. Sources: dust:dust:api-keys, dust:dust:models, dust:dust:credit-management. - mcp_server — Does the product expose itself to other agents over MCP? [supported]: Global and EU MCP URLs expose authorized Dust knowledge, conversations, agents, files and Pods via OAuth; admins can disable access and control redirects. Sources: dust:dust:mcp-server. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:api-keys, dust:dust:upsert, dust:dust:models, dust:dust:credit-management, dust:dust:mcp-server #### 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 ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web, browser extension and Teams access are documented; native desktop/mobile availability remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust browser extension; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web — Is a full web client available? [supported]: Dust provides the hosted web workspace, including the EU region. Sources: dust:dust:pricing, dust:dust:models. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. - mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. - browser_extension — Is there a browser extension or sidebar? [supported]: The extension guide covers Chrome, Firefox and Chromium browsers. Sources: dust:dust:browser. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:models, dust:dust:browser #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial An official Teams integration runs agents in Teams; document connectors do not imply Office add-ins. Availability: generally-available Delivery: official-integration Scope: surfaces=Dust in Microsoft Teams; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; 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? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately. - outlook — Does it work inside Outlook? [unknown]: Does it work inside Outlook? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately. - teams — Is there a Teams app or bot? [supported]: Dust in Teams has an official integration guide and admin setup. Sources: dust:dust:teams. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately. - licence_prerequisites — Which licences or consents are needed? [partial]: The Teams guide requires integration/admin authorization in a Dust workspace. Extra Microsoft/Dust licence charges were not established. Sources: dust:dust:teams. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:teams #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents can perform language work, but document-translation fidelity and controlled terminology are untested. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; 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? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - translation_engine — Which engine translates? [unknown]: Which engine translates? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Configurable agent instructions and Computer document editing support writing workflows; a separate dedicated proofreading product was not established. Sources: dust:dust:builder, dust:dust:computer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:computer #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Image tools use reference images and parallel generation; exact model and output-right terms need further evidence. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - image_generation — Can users generate images, with which models? [partial]: Image Generation is a configurable agent capability with SynthID-marked output. The exact current model identifier is not named in the checked guide. Sources: dust:dust:images. - image_editing — Can users edit uploaded images? [partial]: Uploaded and prior generated images can be used as references, with up to 14 references. Precise inpainting/masking controls were not established. Sources: dust:dust:images. - admin_control — Can admins restrict image generation? [partial]: Builders enable image tools in an agent, while group governance controls who creates/publishes agents. A separate organization/group image-off switch was not established. Sources: dust:dust:images, dust:dust:governance. - usage_terms — What usage rights apply to output? [unknown]: What usage rights apply to output? The image guide and legal entry points were checked. Current model identifier, per-image tariff and contractual output usage rights were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:images, dust:dust:governance #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Speech generation and meeting-transcript integrations are documented; live voice and Swiss German recognition remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dictation — Can users dictate prompts? [unknown]: Can users dictate prompts? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established. - read_aloud — Can answers be read aloud? [partial]: Speech Generator converts written text to MP3 audio with selectable voices/languages; a one-click read-aloud mode for all responses was not established. Sources: dust:dust:speech. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established. - meeting_summaries — Are meetings transcribed and summarised? [supported]: Connected Granola/Fathom/Gong/Praiz transcripts can feed summaries; private Gong transcripts are excluded. This is not a native meeting recorder claim. Sources: dust:dust:meetings. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:speech, dust:dust:meetings #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: supported Computer executes analysis and creates real Office files; Frames provide editable interactive output. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No Excel/PowerPoint fixture or artifact fidelity test. File Generation is deprecated in favor of Computer as of October 14, 2026. - data_analysis — Can it analyse spreadsheets with executed code? [supported]: Computer executes code to inspect and transform Excel/CSV, compute every-row results and return edited workbooks. Sources: dust:dust:computer. - charts — Can it produce charts? [supported]: Computer documents chart generation from spreadsheet data and inclusion in reports/decks. Sources: dust:dust:computer. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Computer creates/edits Word, Excel and PowerPoint files and returns downloadable artifacts, with fidelity caveats. Sources: dust:dust:computer. - canvas_editing — Is there a document or canvas editor for iterating on output? [supported]: Frames are persistent interactive content that can be revised through agents and shared. Sources: dust:dust:frames. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:computer, dust:dust:frames #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pods provide shared team conversations, files and tasks; source-sharing effects still need testing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No cross-group sharing fixture. Do not infer source-ACL propagation from Pod membership. - share_chats — Can chats be shared inside the organisation? [supported]: Pod conversations are visible to all members, who can contribute. Sources: dust:dust:pod-chats. - team_spaces — Are shared projects or workspaces available? [supported]: Open/Restricted Pods group conversations, files and tasks; restricted access is invite-only. Sources: dust:dust:pods. - group_chat — Can several people chat together with the AI? [supported]: Teammates and agents participate in the same Pod thread and can be mentioned. Sources: dust:dust:pod-chats. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: All Pod members read conversation contents. Spaces restrict source/agent use and personal tools act under their user; recipient-safe redaction of previously generated text was not established. Sources: dust:dust:pod-chats, dust:dust:permissions, dust:dust:credentials. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pod-chats, dust:dust:pods, dust:dust:permissions, dust:dust:credentials #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial German and French UI releases are documented alongside English, with remaining English areas. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - ui_languages — Which UI languages are offered? [supported]: October 21, 2026 release adds German; October 16 adds French alongside English US/UK, across product, Frames, extension, Sidekick and Slack/Teams. Sources: dust:dust:changelog. - dach_language_quality — Are German, French and Italian UIs complete and natural? [partial]: Release notes explicitly leave agent/skill names and instructions in English. German/French naturalness and completeness were not observed; Italian UI was not established. Sources: dust:dust:changelog. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? The dated locale announcements were checked; Italian UI and a WCAG conformance statement/report were not established. - admin_ui_languages — Is the admin interface available in German? [partial]: Admins can set a workspace default language. A complete German admin-screen walkthrough was not observed. Sources: dust:dust:changelog. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog #### 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 ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial SAML SSO can be enforced; Business offers it from five seats on demand. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No self-serve SSO login test. - sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML SSO is documented, with Okta, Entra ID and JumpCloud named on pricing. Enterprise marketing also names OIDC; a full provider/protocol matrix was not verified. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise. - sso_plan — Which plan includes SSO? [supported]: Business pricing lists SSO for 5+ seats on demand; Enterprise includes it. Sources: dust:dust:pricing. - mfa — Can MFA be enforced? [partial]: Enforced SAML routes sign-in through the IdP. Specific MFA enforcement behavior was not tested or established in the checked setup guide. Sources: dust:dust:sso. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise SCIM and group roles are documented, with specific annual-seat reclaim behavior. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise for SCIM; seat-management differences stated; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - scim — Is SCIM provisioning supported? [supported]: SCIM 2.0 creates, updates and deactivates users from an IdP as an Enterprise feature. Sources: dust:dust:provision. - group_sync — Are identity-provider groups synced? [supported]: Provisioned IdP groups govern Space access and can map to Admin/Manager roles. Sources: dust:dust:provision, dust:dust:spaces. - jit_provisioning — Are users created at first login? [unknown]: Are users created at first login? Provisioning and seat docs were checked. First-login JIT creation and complete leaver-data transfer were not established. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: SCIM deactivates users; removal/reassignment affects seats but exact chat/agent/knowledge ownership transfer was not tested. Sources: dust:dust:provision, dust:dust:seats. - seat_assignment — Can admins assign and reclaim seats? [supported]: Admins assign seat types independent of roles. Unassigned members cannot interact with agents; annual seats return to stock, and already-granted credits can persist to period end. Sources: dust:dust:seats. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:provision, dust:dust:spaces, dust:dust:seats #### 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. ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust separates Admin, Manager, Member and group-manager permissions and supports restricted knowledge spaces. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Admins control all governance; Managers delegate member/group/usage administration; group managers administer selected groups. Sources: dust:dust:governance. - groups — Can permissions be set per group? [supported]: Permissions go to manual or provisioned groups using Everyone, Groups or Admin-only modes. Multiple grants combine additively. Sources: dust:dust:governance. - feature_toggles — Which features can be switched on or off per group? [partial]: Group controls cover agent/skill creation and publishing, automation charging, billing/security and model ceilings. An exhaustive per-feature toggle matrix for uploads/web/images was not established. Sources: dust:dust:governance, dust:dust:tiers. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Restricted Spaces and Pods separate audiences inside a workspace; separate legal/subsidiary tenant boundaries within one contract were not established. Sources: dust:dust:spaces, dust:dust:pods. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:governance, dust:dust:tiers, dust:dust:spaces, dust:dust:pods #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Consumption analytics has detailed attribution and exports without message content. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - adoption_dashboard — Is there an adoption dashboard? [partial]: Pricing lists usage/adoption reporting; the Analytics guide focuses on credit consumption and attribution rather than a complete active-user adoption scorecard. Sources: dust:dust:pricing, dust:dust:analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [supported]: Analytics filters/ranks agents, members, groups, models, tools, sources, API keys, skills and Pods. Group attribution may count a member in several groups. Sources: dust:dust:analytics. - export — Can usage data be exported? [supported]: Raw CSV consumption export and API analytics export are documented, with workspace enablement and key-scope restrictions. Sources: dust:dust:analytics. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: Analytics exports omit message content, but contain member/message/conversation identifiers. Pseudonymous or works-council privacy modes were not established. Sources: dust:dust:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:analytics #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Credit plans offer consumption visibility, member limits and plan-specific pooled budgets, with programmatic exceptions. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Group budgets are beta and exclude programmatic usage. No budget fixture test. - cost_visibility — Can admins see cost or consumption per user and group? [supported]: Analytics and Credits show consumed credits by member, group, model, tool and agent. Credits are not assumed to be invoice currency. Sources: dust:dust:analytics, dust:dust:credit-management. - budgets — Can budgets be set per user or group? [supported]: Members have shared-pool spend limits; beta group budgets require Enterprise Pooled. Programmatic monthly and API-key caps are separate. Sources: dust:dust:credit-management, dust:dust:api-keys. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Pool limits/group budgets block further requests; an in-progress message can finish above its starting cap. API calls reject at per-key caps. Optional automatic seat upgrades may increase billed subscriptions. Sources: dust:dust:credit-management, dust:dust:api-keys. - chargeback — Can costs be exported per cost centre? [partial]: Consumption CSV includes groups and identifiers, but group attribution can duplicate usage and is not a guaranteed invoice-ready cost-center chargeback. Sources: dust:dust:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:analytics, dust:dust:credit-management, dust:dust:api-keys #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise has documented event logs and SIEM delivery; content logging and legal hold remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - admin_events — Are admin and security events logged? [supported]: Enterprise Audit Logs record significant admin/security, user, API-key, system and tool events with timestamps, targets and actor metadata. Sources: dust:dust:audit. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [unknown]: Can prompts and answers be retained for compliance, and is it configurable? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established. - siem_export — Can logs stream to a SIEM or be exported? [supported]: CSV export and continuous destinations include Datadog, Splunk, S3, GCS and custom HTTPS. Sources: dust:dust:audit. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established. - log_retention — How long are logs kept? [partial]: Enterprise marketing states 365-day audit retention; no underlying report/contract or configurable retention details were retrieved. Sources: dust:dust:enterprise. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:audit, dust:dust:enterprise #### 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 ### 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. #### Dust 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. #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents have persistent instructions and workspace governance; broad enforced content-policy administration is unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - org_instructions — Can admins set organisation-wide instructions? [partial]: Admins/builders configure agent instructions; an enforced single organization-wide instruction applied to every agent/message was not established. Sources: dust:dust:builder, dust:dust:governance. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established. - content_filters — Are content filters configurable? [partial]: Image Generation documents NSFW/celebrity safety filtering. Custom organization-wide topic/content rules were not established. Sources: dust:dust:images. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:images #### 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 ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial EU workspace and EU model controls are distinct from general hosting and global subprocessing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - storage_region — Where are chats, files and indexes stored? [partial]: Pricing/security advertise EU or US workspace hosting. Exact cloud provider, storage country and index location were not established. Sources: dust:dust:pricing, dust:dust:security. - inference_region — Where do model calls run, per provider? [supported]: EU credit-priced workspaces using Dust-hosted models can enable EU-hosted models only after all active agents comply. BYOK is outside this setting; not every model is eligible. Sources: dust:dust:eu-models. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established. - support_access_region — From where can vendor staff access data? [partial]: The controller privacy policy permits non-EEA access/processing including the US; it does not establish customer-content support access by staff country. Sources: dust:dust:privacy. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established. - residency_plan — Which plan or option provides residency? [supported]: Business and Enterprise list EU/US residency; EU-only model restrictions additionally require EU region and credit pricing with Dust model hosting. Sources: dust:dust:pricing, dust:dust:eu-models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:eu-models, dust:dust:privacy #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosted Business and Enterprise single-tenant offers are public; supported customer-operated whole-platform modes are unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust Enterprise single-tenant deployment; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=not specified; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - multi_tenant_saas — Is a shared SaaS offered? [partial]: Business is a self-serve hosted workspace; exact shared-infrastructure isolation architecture is not documented in the checked pages. Sources: dust:dust:pricing, dust:dust:privacy. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: Enterprise pricing advertises single-tenant deployment. Numerical seat/spend minimum, supported countries and operating terms were not established. Sources: dust:dust:pricing. - customer_cloud — Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment. - 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? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: Business/Enterprise packaging differs in connectors, MCP, Spaces, APIs and governance. No customer-operated hosting feature-parity contract was established. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:privacy #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust publishes no-training and provider-retention claims; the customer DPA was not retrieved. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Controller privacy-policy scope is distinct from processor DPA coverage. - vendor_training — Does the vendor train on customer content? [partial]: The security page claims customer data is never used for model training. This remains vendor-claimed because no customer DPA/contract clause was retrieved. Sources: dust:dust:security. - provider_training — Do model providers train on it under this product's contracts? [partial]: The privacy policy names OpenAI, Anthropic, Mistral, Google and Fireworks as prohibited from training on customer/personal content; BYOK arrangements need separate confirmation. Sources: dust:dust:training-policy. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: The policy states providers do not log Customer Content for human review or save it to disk. Exception/abuse-retention periods were not established from customer contracts. Sources: dust:dust:training-policy. - zero_retention — Is zero data retention available, and on which plan? [partial]: Security and privacy pages assert provider zero retention, but applicable plan/model exceptions were not contract-verified. Sources: dust:dust:security, dust:dust:training-policy. - human_review — Can provider staff review content? [partial]: The published policy says listed providers do not log Customer Content for human review. This is a vendor assertion, not an independently reviewed model-provider contract. Sources: dust:dust:training-policy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:training-policy #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Some user deletion and memory retention behavior is documented; tenant-wide retention schedules remain open. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - default_retention — What is retained and for how long by default? [partial]: Agent memories persist until manually deleted. This does not define default retention for all conversations, files, indexes or logs. Sources: dust:dust:memory. - admin_retention — Can admins set retention periods? [partial]: Enterprise pricing offers custom data retention; periods, deletion mechanics and exceptions were not retrieved. Sources: dust:dust:pricing. - user_deletion — Can users delete their chats and files permanently? [partial]: Users can delete conversations and agent memories. Backup erasure timing and all attached-file deletion behavior were not established. Sources: dust:dust:delete-chat, dust:dust:memory. - contract_end_deletion — What is deleted at contract end, and when? [unknown]: What is deleted at contract end, and when? Conversation/memory docs, Enterprise pricing and unreadable legal entry points were checked. Contract-end erasure timing and complete storage/index/log retention defaults remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:memory, dust:dust:pricing, dust:dust:delete-chat #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust identifies a French operating entity; customer subprocessor inventory and notice rules remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - subprocessor_list — Is a dated sub-processor list published? [unknown]: Is a dated sub-processor list published? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established. - change_notification — Are customers notified of sub-processor changes? [unknown]: Are customers notified of sub-processor changes? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The public policy identifies Permutation Labs at a Paris, France address. A separate parent company or controlling entity was not established. Sources: dust:dust:privacy. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [partial]: For its controller processing, the privacy policy describes adequacy or EU SCC safeguards for non-EU transfers, including the US. Customer processor transfer terms were not retrieved. Sources: dust:dust:privacy. - government_access_policy — Is there a published government-access or transparency policy? [partial]: The controller policy allows legally required disclosure to authorities; a dedicated government-request transparency policy for customer content was not established. Sources: dust:dust:privacy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise offers custom MSA/DPA terms, while the underlying legal materials were inaccessible. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dpa — Is a DPA available, and is it negotiable? [partial]: Enterprise pricing explicitly offers custom MSA/DPA terms. The form, sign-up incorporation and negotiability boundaries were not inspected. Sources: dust:dust:pricing. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: Marketing and privacy materials reference GDPR; explicit Swiss revDSG coverage in the customer DPA was not established. Sources: dust:dust:security, dust:dust:privacy. - governing_law — Which law and court govern the contract? [unknown]: Which law and court govern the contract? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established. - sector_materials — Are FINMA or other sector materials provided? [partial]: Security marketing says the service enables HIPAA compliance. A BAA, FINMA or banking-secrecy outsourcing pack was not retrieved. Sources: dust:dust:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:privacy #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial SOC 2 Type II is claimed publicly, without a verified report or certificate. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - iso_27001 — ISO 27001 with scope and validity? [unknown]: ISO 27001 with scope and validity? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. - soc2 — SOC 2 type, period and covered service? [partial]: Dust security/pricing claim SOC 2 Type II. Auditor, reporting period and exact service scope were not verified. Sources: dust:dust:security, dust:dust:pricing. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. - report_access — How can customers obtain reports? [partial]: The security page directs customers to trust.dust.com; underlying reports were not accessible in this public source pass. Sources: dust:dust:security. - pentest — Are independent penetration test summaries available? [unknown]: Are independent penetration test summaries available? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:pricing #### 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 ### 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). #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust claims AES-256/TLS and advertises Enterprise single tenancy; customer key custody is unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - encryption_at_rest — Is data encrypted at rest? [supported]: The security page states AES-256 at rest and TLS in transit; this is a vendor claim. Sources: dust:dust:security. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Security, pricing and network/MCP docs were checked. Customer-managed/held data-encryption keys and key-location guarantees were not established. Provider API BYOK is not encryption-key custody. - private_networking — Is private connectivity or IP restriction available? [partial]: Custom MCP servers can restrict access and use documented static egress on verified domains. This is tool connectivity, not proof of private connectivity to the whole service. Sources: dust:dust:tools. - tenant_isolation — How are customers separated in shared SaaS? [partial]: Enterprise offers single tenancy; shared Business tenancy and lower-level isolation mechanics were not established. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:tools, dust:dust:pricing #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public personnel/model handling statements exist; an explicit professional-secrecy contract and subprocessor flow-down remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Dust Business/Enterprise public policy; Enterprise and BYOK routes differ; add_ons=none stated; deployment_mode=multi-tenant-saas; region=EU/US storage and provider routes; no DE/CH-specific secrecy contract verified; os=not specified. Limitations: - No-training, ZDR marketing/policy assertions, EU hosting and a general privacy policy 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]: The public security and platform privacy pages do not establish a signed §203 StGB/Art321 StGB professional-secrecy undertaking covering Dust staff. The Terms/Policies link did not expose readable contractual text in this pass. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy describes service-provider data-protection agreements and model no-training/retention conditions, but no dedicated professional-secrecy undertaking or its binding subprocessor flow-down was retrieved. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No publicly documented German/Swiss professional-secrecy-specific plan or paid add-on was established. Enterprise single-tenancy/EU model options are not treated as such a contractual undertaking. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The platform privacy policy limits personnel access to authorized staff and says customer context is processed by selected foundation-model providers; it asserts no provider disk retention/human-review logging. This vendor statement does not establish the complete customer-content plaintext access matrix, support countries, private contracts or every BYOK/MCP/tool route. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Reviewed public security, privacy, EU-hosted model documentation and Enterprise plan scope plus targeted first-party secrecy search. Trust Center content was not available and Terms/Policies routed to unreadable external content. No public §203/Art321 template or professional-body guidance was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models #### 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 ## 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business seat prices are public; only the documented prepaid route is described here, while conflicting Business overage eligibility remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Free/Pro/Max seat list pricing; Enterprise quoted pool and programmatic contracts are separate; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - Do not present Business PAYG as established; retain list seat prices separately from the unresolved overage route. - pricing_unit — What is the pricing unit? [partial]: Business publishes per-seat subscriptions and included credits. Detailed Credit management describes prepaid Business top-ups and Enterprise PAYG; pricing FAQ separately describes enabled Business workspace overage, so Business post-allocation billing eligibility is unverified. Sources: dust:dust:pricing, dust:dust:credit-management. - list_prices — What are list prices per plan, with date and currency? [supported]: As retrieved 2026-10-21, ex-VAT Business Free is EUR 0; Pro EUR 30/month or EUR 24/month annually; Max EUR 150/month or EUR 120/month annually. Enterprise is quote-only. Sources: dust:dust:pricing. - included_usage — What usage is included? [supported]: Free has 500 lifetime credits, Pro 8,000/month and Max 40,000/month. Monthly credits do not roll over; Workspace seats draw from a contracted pool. Sources: dust:dust:credits, dust:dust:seats. - add_ons — Which features cost extra? [partial]: Business limits include three connectors, five remote MCP servers and five Spaces. Enterprise adds unlimited connector/MCP packaging, SCIM, audit, retention and support. Individual add-on tariffs are not published. Sources: dust:dust:pricing. - overage — What do usage beyond limits and premium models cost? [unknown]: Effective Business post-allocation billing is unknown: current pricing FAQ allows Pro/Max workspace overage, while Credit management reserves PAYG for Enterprise and describes prepaid Business top-ups. The USD0.01/credit Business programmatic rate does not resolve whether interactive overage is PAYG or prepaid. No account/contract test resolved this. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:credit-management, dust:dust:credits, dust:dust:seats #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21 apply; all three target seat counts require unpriced Enterprise terms. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - cost_200 — Year-one cost at 200 users? [unknown]: Year-one cost at 200 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope. - cost_1000 — Year-one cost at 1,000 users? [unknown]: Year-one cost at 1,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope. - cost_5000 — Year-one cost at 5,000 users? [unknown]: Year-one cost at 5,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope. - variable_share — Which part depends on usage? [supported]: Consumption adds token and action credits, including sub-agent work. Programmatic use and Enterprise PAYG draw from workspace pools separately from personal seat allocations. Sources: dust:dust:credits, dust:dust:credit-management. - unknown_parts — Which costs could not be priced? [supported]: Business is scoped to 100 people, so 200/1,000/5,000 seat Enterprise fees, committed pool and PAYG tariffs are unknown. The default Standard auto list is published, but a complete token-to-credit tariff is not, so no proxy replaces vendor-billed usage. Sources: dust:dust:pricing, dust:dust:models, dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:credit-management, dust:dust:pricing, dust:dust:models, dust:dust:fx-ecb #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial A limited Business free option enables self-serve evaluation; Enterprise features remain contract-scoped. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - free_tier — Is there a free tier for business use? [supported]: Business free supports up to five members with 500 lifetime credits per Free seat. Credits do not reset and a user cannot return to Free after upgrading. Sources: dust:dust:seats. - self_serve_trial — Is a self-serve business trial available? [partial]: The public site offers self-serve free workspace access, not a documented time-limited fully featured Enterprise trial. No card requirement was established. Sources: dust:dust:pricing, dust:dust:seats. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Business lists up to three connectors/five Spaces/five remote MCP servers and SSO at 5+ seats on demand. SCIM, audit and custom retention are Enterprise. Sources: dust:dust:pricing. - sales_gate — Does meaningful evaluation require sales contact? [supported]: Enterprise terms, pooled credits, advanced governance and support are sales-led; a small-team free evaluation is self-serve. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:seats, dust:dust:pricing #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business monthly and annual subscriptions are public; Enterprise seats are annual and prices contractual. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - minimum_commitment — What seat or spend minimum applies? [partial]: The free option has up to five members and Business targets up to 100 people; Enterprise numerical seat/spend minimum was not established. Sources: dust:dust:pricing, dust:dust:seats. - contract_length — What contract lengths are offered? [supported]: Business offers monthly and annual seats together; Enterprise seats are annual only. Sources: dust:dust:seats. - cancellation — How can the contract be cancelled or reduced? [supported]: Monthly seats unassign immediately with a prorated credit; annual seats return to stock for reassignment and are not refunded when someone leaves. Sources: dust:dust:seats. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Prices are displayed in EUR and the privacy policy identifies a French entity; CHF invoicing and the actual invoicing entity/currency were not contract-verified. Sources: dust:dust:pricing, dust:dust:privacy. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified: Business seat prices/credit allowances are public, while Enterprise pricing, complete usage conversion and negotiated terms require a quote. Sources: dust:dust:pricing, dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:seats, dust:dust:privacy, dust:dust:credits #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial The pinned public repository has an MIT root licence; hosted licensing and complete component coverage are separate. Availability: generally-available Delivery: native Scope: surfaces=Public dust-tt/dust repository root licence; version=dust-tt/dust commit2b1a4973af824f8ff970d585c5eb1f40ae76186c; root LICENSE only; plan=Public source component, not Business/Enterprise hosted-service rights; add_ons=none stated; deployment_mode=not specified; region=Repository licence has no deployment-region entitlement; os=not specified. Limitations: - MIT applies to the pinned repository root grant only; dependencies, supported self-host deployment, hosted terms and any closed Enterprise boundary remain unverified. - licence_type — Which licence applies to each component? [partial]: dust-tt/dust root LICENSE is MIT at commit 2b1a4973af824f8ff970d585c5eb1f40ae76186c. This does not classify every dependency or the contracted hosted service. Sources: dust:dust:licence. - branding_restrictions — Do licence terms restrict branding or user counts? [supported]: The MIT root grant requires preserving copyright and permission notices and does not itself impose branding or user-count caps. Sources: dust:dust:licence. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? The pinned root LICENSE and README were retrieved; a complete nested-component licence inventory and separate closed Enterprise edition boundary were not established. Hosted terms were inaccessible. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:licence #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business Conversation API and Enterprise Data Source API provide scoped data retrieval; agent export entitlement and complete tenant exit remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust APIs and MCP server, Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Conversation API and web analytics; Enterprise adds Data Source API. Agent-YAML endpoint entitlement is unverified.; add_ons=API keys with appropriate workspace/resource permissions; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Conversation and document retrieval require the corresponding plan and resource permissions. Complete organization coverage, agent-export entitlement and the post-termination retrieval window remain unknown. - chat_export — Can admins export all chats? [partial]: Business pricing includes Conversation API; authorized API users retrieve accessible conversation messages with pagination. This does not establish one-click all-tenant admin export. Sources: dust:dust:get-conversation, dust:dust:pricing. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: The agent-YAML endpoint and public pricing were checked on 2026-10-21. Neither establishes its Business or Enterprise entitlement. Reusable assistant/prompt export for a named plan remains unknown. - knowledge_export — Can knowledge bases and their sources be exported? [partial]: Enterprise pricing adds Data Source API; the documented endpoint retrieves accessible data-source documents as JSON. Complete source/credential/permission portability and an all-tenant export are unverified. Sources: dust:dust:get-document, dust:dust:pricing. - export_format — Are formats documented and machine-readable? [partial]: Business Conversation API and Enterprise Data Source API return JSON for accessible resources. Web analytics separately exports CSV. These formats do not establish complete tenant export; no plan-scoped agent-YAML export is claimed. Sources: dust:dust:get-conversation, dust:dust:get-document, dust:dust:analytics, dust:dust:pricing. - post_termination_window — How long can data be retrieved after termination? [unknown]: How long can data be retrieved after termination? No trial admin exit/export was run; complete tenant coverage and the post-termination retrieval window were not established from the accessible API docs or unreadable contract route. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:pricing, dust:dust:get-document, dust:dust:analytics #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business email support and Enterprise priority/SLA service are advertised; credit terms and local-language support remain open. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - support_channels — Which support channels are available on each plan? [supported]: Pricing lists Business email and Enterprise priority support with dedicated CSM; public support/community resources are available. Sources: dust:dust:pricing, dust:dust:support. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Support/pricing/Enterprise pages and the official status URL were checked. German/French/Italian staffed support and detailed credited SLA terms were not established. - regional_presence — Is there a DACH or Swiss entity, team or partner? [partial]: The public policy identifies a Paris, France entity. A DACH/Swiss support team or named regional partner was not established. Sources: dust:dust:privacy. - uptime_sla — Is there an uptime SLA with credits? [partial]: Enterprise marketing claims 99.9% uptime and pricing includes an SLA; service-credit amounts, exclusions and claim rules were not retrieved. Sources: dust:dust:enterprise, dust:dust:pricing. - status_page — Is there a public status page with history? [partial]: Model-selection docs link https://dust.statuspage.io for incidents. Direct retrieval timed out, so incident history was not verified. Sources: dust:dust:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:support, dust:dust:privacy, dust:dust:enterprise, dust:dust:models #### 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 ### 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. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust has rollout and training material, with hands-on support packaged for Enterprise. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Public learning material (no paid entitlement required to read); contracted CSM/onboarding is Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - onboarding_service — Is guided onboarding included? [supported]: Enterprise pricing includes dedicated CSM and onboarding; exact hours and scope are contractual. Sources: dust:dust:pricing. - user_training — Is end-user training offered, in which languages? [partial]: Public team onboarding and education resources are available. Course/live-session language coverage was not established. Sources: dust:dust:training, dust:dust:rollout. - use_case_library — Are role-based use cases and templates provided? [supported]: The public Use Cases and Guides index lists departmental guides for Sales, Support, Marketing, Engineering, Data Analytics, Knowledge, People, Product and Collaboration; the Sales guide supplies concrete agent examples and build links. This establishes public role-based guidance, not a separately verified in-product template entitlement. Sources: dust:dust:r2-department-guides, dust:dust:r2-sales-guide. - adoption_programme — Is there a champion or adoption programme? [partial]: The rollout guide covers launch, builder community, education and expansion; a contracted champion programme entitlement was not established. Sources: dust:dust:rollout. - service_cost — Which services cost extra? [partial]: Hands-on CSM/onboarding is Enterprise packaging; a numerical professional-services tariff was not established. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:training, dust:dust:rollout, dust:dust:r2-department-guides, dust:dust:r2-sales-guide #### 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 ## Sources ### dust:dust:models Auto models and the model picker. Users select a model per message or agent; auto choices use maintained ordered lists rather than task-based routing. - URL: https://docs.dust.tt/docs/user-documentation/agents/model-selection - Locator: Auto model lists; availability; API overrides - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:eu-models EU-hosted models. EU credit-plan workspaces using Dust model hosting can restrict agents and auto choices to EU-hosted models; BYOK is excluded from this setting. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/eu-hosted-models - Locator: Availability; supported/excluded model table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:changelog Dust changelog. Recent dated changes include German/French UI, Gemini 4 Argon and migration from File Generation to Computer. - URL: https://docs.dust.tt/docs/changelog - Locator: October 21, 16 and 14, 2026 entries - Evidence kind: documented - Source date: 2026-10-21 - Retrieved: 2026-10-21 ### dust:dust:files Conversation Files. Conversation uploads are scoped to one conversation and support documents, tabular data, images and audio. - URL: https://docs.dust.tt/docs/user-documentation/data-sources/conversation-files/conversation-files - Locator: Formats; size table; generating files - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:pricing Dust Pricing. Business supports up to 100 people with Free/Pro/Max seats; Enterprise pricing is sales-led and adds pooled credits, SCIM, audit, single tenancy and support. - URL: https://dust.tt/home/pricing - Locator: Business/Enterprise table and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### 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 ### 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 ### 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 ### dust:dust:tiers Model access tiers. Admins restrict models and reasoning efforts at workspace, group or member level, with a separate published-agent bypass setting. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/model-access-tiers - Locator: Workspace, group and individual ceilings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:spaces Spaces management. Spaces control knowledge and agent access; Business allows five and Enterprise 100 spaces. - URL: https://docs.dust.tt/docs/user-documentation/admins/spaces-management - Locator: Open/restricted spaces; limits; visibility - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:credits Credits. Consumption adds token and tool credits; a 600-AWU checkpoint can pause user-started root tasks, with exceptions. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credits - Locator: Token/action credits; checkpoints - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:credit-management Credit management. Credit sources and block behavior vary by plan; beta Enterprise Pooled group budgets exclude programmatic consumption. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credit-management - Locator: Personal caps; group budgets; programmatic use - 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 ### dust:dust:file-limits File size limits. The dedicated limits FAQ gives different image, audio and tabular caps than Conversation Files and excludes direct video uploads. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/faq/file-size-limits - Locator: Upload caps; audio-only restriction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:computer Computer. Computer executes code in temporary workspaces, handles Office/PDF files, performs documented OCR and restricts network access by allowlist. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/computer - Locator: File work; OCR; network control; secrets - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:drive Google Drive. Drive sync follows a dedicated connection account and selected content; scanned documents need conversation upload for OCR and Excel table queries need conversion to Sheets. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/google-drive - Locator: Connection identity; refresh; OCR; spreadsheet limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:search Search data sources. Agents search selected knowledge sources and retrieve relevant document context. - URL: https://docs.dust.tt/docs/user-documentation/agents/knowledge/search-data-sources - Locator: Document selection; retrieval - 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 ### 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 ### dust:dust:permissions Access Controls and Permissions. Knowledge access is organized through admin-selected connection content and membership of open/restricted Spaces. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/access-controls-and-permissions - Locator: Access policy; connection account; Spaces - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:microsoft Microsoft. Microsoft data is scoped to the connecting account and selected SharePoint sources; changes synchronize on a five-minute cycle. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/microsoft - Locator: Connection account; delegated and service-principal setup; sync - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:confluence Confluence. Confluence sync covers selected global spaces, excluding private spaces and pages with view restrictions. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/confluence - Locator: Scope; restricted pages; refresh - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:jira Beta: Import Jira issues. A separately documented beta route imports Jira issues as a custom connection. - URL: https://docs.dust.tt/docs/user-documentation/data-sources/custom-connections/beta-import-jira-issues - Locator: Import path - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:sources What data sources can be connected to Dust?. Official guides identify managed connections and custom API/import routes. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/faq/general-questions/what-data-sources-can-be-connected-to-dust - Locator: Named sources - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:tools Adding an MCP Server. Admins add remote MCP servers with OAuth or bearer credentials and can restrict tools to skills. - URL: https://docs.dust.tt/docs/user-documentation/admins/tools-management/adding-an-mcp-server - Locator: Remote/custom servers; auth; tool restriction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-bigquery Dust BigQuery connection. Dust stores BigQuery metadata and runs table queries through a dedicated service account; dataset content is not synchronized into the index. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/bigquery.md - Locator: No content sync; service-account setup, one location and Space table selection - 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 ### dust:dust:credentials Personal vs Shared Credentials for Tools & MCP Servers. Tools can use a shared account or each user OAuth identity; even personal auth needs initial admin setup. - URL: https://docs.dust.tt/docs/user-documentation/admins/tools-management/personal-vs-shared-credentials - Locator: Shared versus personal authentication - 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 ### dust:dust:security Dust Security. Dust claims EU/US hosting, AES-256/TLS, no model training, provider zero retention and SOC 2 Type II. - URL: https://dust.tt/home/security - Locator: Hosting, training, encryption and certification statements - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:deep Deep-dive Agent. Deep-dive plans, delegates and writes cited reports, using Company Data knowledge and selected tools; Table Query is excluded. - URL: https://docs.dust.tt/docs/user-documentation/agents/default-agents/deep-dive-agent - Locator: Research flow; citations; limitations - 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 ### dust:dust:memory Agent Memory. Enabled agents retain user-private memory across conversations; users can view and delete it and it persists until deletion. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/agent-memory - Locator: Adding the tool; viewing/deleting; privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:builder Create your first agent. Agents combine instructions, models, knowledge and tools with controlled sharing. - URL: https://docs.dust.tt/docs/user-documentation/agents/create-your-first-agent - Locator: Instructions; tools; sharing - 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 ### dust:dust:governance Workspace Governance: Roles, Groups & Permissions. Admins delegate manager/group permissions for agents, skills, models, billing and security; grants are additive. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/workspace-governance-roles-groups-and-permissions - Locator: Roles; permission matrix; additive access - 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 ### 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 ### dust:dust:web Web Search & Browse. The tool runs Google queries and browses results, with agent-level configuration and format options. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/web-search-and-browse - Locator: Search and browsing flow - 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 ### dust:dust:triggers Triggers. Agents can run automatically from schedule or event triggers. - URL: https://docs.dust.tt/docs/user-documentation/agents/triggers/index - Locator: Schedules and events - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:schedules Schedules. Agents can run on recurring schedules. - URL: https://docs.dust.tt/docs/user-documentation/agents/triggers/schedules - Locator: Schedule setup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:webhooks Webhooks. Admins configure webhook sources; members attach filtered triggers to agents, with optional signature verification for custom sources. - URL: https://docs.dust.tt/docs/user-documentation/agents/triggers/webhooks/index - Locator: Built-in and custom event sources - 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 ### dust:dust:pods Pods overview. Pods combine shared conversations, tasks and files; open Pods are workspace-browsable and restricted Pods require invitation. - URL: https://docs.dust.tt/docs/user-documentation/pods/overview - Locator: Shared workspace and visibility - 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 ### dust:dust:api-keys API keys. Dust API keys have read/admin scopes, data access and enforceable per-key monthly caps. - URL: https://docs.dust.tt/docs/user-documentation/admins/api-keys - Locator: Scopes; Space access; caps - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:mcp-server Dust MCP Server. Dust exposes workspace knowledge, agents, conversations, files and Pods to OAuth MCP clients under the authenticated user permissions. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/dust-mcp-server - Locator: Region URLs; OAuth; user permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:upsert Upsert a document in a data source. The API loads or updates documents in a scoped data source. - URL: https://docs.dust.tt/api-reference/datasources/upsert-a-document-in-a-data-source - Locator: Endpoint and authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:get-conversation Get a conversation. The API retrieves accessible conversation messages with pagination. - URL: https://docs.dust.tt/api-reference/conversations/get-a-conversation - Locator: Response schema - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:mcp About Glean MCP server. Glean exposes enterprise search, chat, documents and agents to external hosts through MCP. - URL: https://docs.glean.com/administration/platform/mcp/about - Locator: Server capabilities; authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:core-price Glean Core Suite. Core Suite combines per-user monthly licensing with committed Model Hub consumption; the seat amount is not given. - URL: https://docs.glean.com/glean-core-suite-pricing - Locator: Seat fee; Model Hub Usage; provider rate table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:browser Browser Extension. An official extension supports Chrome, Firefox and Chromium-based browsers. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/browser-extension - Locator: Browsers and capabilities - 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 ### dust:dust:teams Dust in Teams. An official Teams integration runs Dust agents within Microsoft Teams after admin setup. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/dust-in-teams - Locator: Setup and usage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:teams-app Glean in Microsoft Teams: Admin guide. The Microsoft Teams app requires tenant admin setup and consent. - URL: https://docs.glean.com/administration/platform/embedded-integrations/glean-in-teams/glean-in-microsoft-teams--admin-guide - Locator: Installation prerequisites and deployment - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:images Image Generation. Agents generate images from text or references, up to 14 reference images, with SynthID and content restrictions. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/image-generation - Locator: Reference images; parallel generation; safety - 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 ### dust:dust:speech Voice and sound generation. The speech tool generates MP3 narration or multi-speaker dialogue with selectable languages and styles. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/voice-and-sound-generation - Locator: Speech Generator - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:meetings Meeting transcripts. Dust consumes transcripts from connected notetaker and sales tools; Gong private transcripts are excluded. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/meeting-transcripts - Locator: Providers and scope - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:frames Frames overview. Frames provide persistent interactive agent output that can be refined and shared. - URL: https://docs.dust.tt/docs/user-documentation/agents/frames/overview - Locator: Creating and editing interactive content - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:pod-chats Pod conversations. All Pod members can read and contribute to Pod conversations, which are automatically indexed. - URL: https://docs.dust.tt/docs/user-documentation/pods/conversations - Locator: Visibility; indexing; participation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:team-chat Team chat. Beta shared Editor chats run each request as its author but expose already-generated answers to all participants. - URL: https://docs.glean.com/user-guide/assistant/team-chat - Locator: How permissions work; behavior and limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:accessibility Accessibility Statement. Glean says a VPAT 2.5 ACR covering WCAG 2.0, 2.1 and 2.2 A/AA is available through its trust center. - URL: https://docs.glean.com/user-guide/about/accessibility - Locator: Conformance status - Evidence kind: documented - Source date: 2026-09-25 - Retrieved: 2026-10-21 ### dust:dust:sso Single Sign-On. Admins configure and enforce SAML SSO, which disables other social sign-in paths for the workspace. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/single-sign-on-sso/single-sign-on-sso - Locator: Setup; enforcement - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:enterprise Dust for Enterprise. The Enterprise marketing page claims 365-day audit retention, 99.9% uptime and support for 10,000+ users. - URL: https://dust.tt/home/enterprise - Locator: Security and scale - Evidence kind: vendor-claimed - Source date: Not stated - 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 ### dust:dust:provision Users and groups provisioning. Enterprise SCIM creates, updates and deactivates users and syncs groups; groups can grant Admin/Manager roles. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/users-and-groups-provisioning - Locator: SCIM 2.0; group role mapping - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:seats Seat management. Admins assign independent roles and Free/Pro/Max seats; annual stock and already-allocated credits have specific reclaim rules. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/seat-management - Locator: Seat assignments; billing cycles; leaving - 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 ### dust:dust:analytics Analytics. Consumption reports break down users, groups, models, tools, agents and Pods; exports omit message content and can double-attribute group usage. - URL: https://docs.dust.tt/analytics - Locator: Attribution; CSV; content exclusion - 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 ### dust:dust:audit Audit Logs. Enterprise logs distinguish users, API keys and system actors with CSV and continuous SIEM delivery. - URL: https://docs.dust.tt/docs/user-documentation/admins/audit-logs/audit-logs - Locator: Enterprise scope; actor types; SIEM - 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 ### 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 ### dust:dust:privacy Dust Platform Privacy Policy. The policy identifies Permutation Labs in Paris and distinguishes its controller processing from customer processor processing, with non-EEA transfer safeguards. - URL: https://dust.tt/home/platform-privacy - Locator: About Us; sections 2, 6 and 7 - 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 ### dust:dust:training-policy Dust Platform Privacy Policy. The policy asserts listed providers do not train, retain or log Customer Content for human review; this source pass did not retrieve the customer DPA. - URL: https://dust.tt/home/platform-privacy - Locator: Section 6, Foundational Model Providers - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:delete-chat Can I delete or rename a conversation?. Users can delete or rename their conversations. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/faq/managing-agents/can-i-delete-or-rename-a-conversation - Locator: Conversation actions - 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 ### glean:glean:r3-legal-index Glean legal. The index links both Business Associate Agreement forms, the Technical Services Addendum and named Outcomes Packages; inclusion and pricing depend on the applicable contract. - URL: https://www.glean.com/legal - Locator: Glean Customer Agreements and Policies - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:security-page Glean Protect security page. Glean claims SOC 2 Type II, ISO 27001 and ISO 42001; no issuer-scoped certificate was retrieved. - URL: https://www.glean.com/platform/security - Locator: Enterprise security and compliance badges - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:r4-aws-cmk-faq Glean customer-hosted AWS FAQ. Customer-managed CMKs are supported for AWS, although the FAQ recommends default AWS-managed KMS keys and documents SCP-based emergency controls. - URL: https://docs.glean.com/security/cloud-prem/aws/faq - Locator: Are customer managed keys supported? - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### glean:glean:r4-aws-key-control Glean AWS account access and deployment model. The customer-hosted AWS deployment guide says customers own and control KMS customer-managed keys used for data at rest. This does not establish key control for Glean Hosted or GCP. - URL: https://docs.glean.com/security/cloud-prem/aws/account-access-and-deployment-model - Locator: Customer controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### glean:glean:dpa-confidentiality Glean DPA. General DPA confidentiality binds authorized personnel and no-less-protective subprocessor agreements; no specific §203/Art321 undertaking was retrieved. - URL: https://www.glean.com/legal/dpa - Locator: Section4 authorized personnel confidentiality; section9 subprocessor written agreement and necessary access - Evidence kind: documented - Source date: 2026-03-06 - Retrieved: 2026-10-21 ### 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 ### dust:dust:fx-ecb ECB historical euro reference rates. EUR 1 = USD 1.1215 = CHF 0.9237 on October 20, 2026. - 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: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 ### dust:dust:licence Dust repository LICENSE at pinned commit. The pinned public repository root licence is MIT; hosted service terms and third-party components are separate. - URL: https://github.com/dust-tt/dust/blob/2b1a4973af824f8ff970d585c5eb1f40ae76186c/LICENSE - Locator: Root LICENSE, MIT permission grant - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:get-document Retrieve a document from a data source. The API retrieves a source document; this does not establish a complete one-click tenant export. - URL: https://docs.dust.tt/api-reference/datasources/retrieve-a-document-from-a-data-source - Locator: Endpoint and response - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:support Dust Support. The vendor provides public support entry points and community/documentation resources. - URL: https://dust.tt/home/support - Locator: Support channels - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:rollout Dust Rollout Guide. Public rollout guidance covers setup, launch, team education and measurement. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/dust-rollout-guide/index - Locator: Rollout phases - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:training Team onboarding material. Dust provides reusable team-onboarding material. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/dust-rollout-guide/team-onboarding-material - Locator: Training resources - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-department-guides Dust Use Cases and Guides. Public guides are organized by Sales, Support, Marketing, Engineering, Data, Knowledge, People, Product and Collaboration. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/use-cases-and-guides/index.md - Locator: Use Cases by Department - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-sales-guide Dust Sales use-case guide. The Sales guide provides concrete role-based agent examples; this is public learning material, not a contracted training entitlement. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/use-cases-and-guides/sales.md - Locator: Sales agent examples and build links - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21