--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/dust-vs-langdock/" data_url: "https://onaihq.com/compare/agents/dust-vs-langdock/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # Dust vs Langdock > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 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. - Langdock source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/dust-vs-langdock/ - Machine-readable JSON: https://onaihq.com/compare/agents/dust-vs-langdock/data.json - Methodology: https://onaihq.com/compare/agents/methodology/ ## Models ### MOD-01: Model catalogue and providers Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Curated multi-provider models and a task-complexity Auto mode are documented; catalogue publication is not a tested picker. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - current_models: Published text catalogue: Gemini 3.1 Pro Preview, 3 Flash Preview, 3.5/3.6/3.7/3.8 Flash, 4 Argon; GPT-5/5.1/5.1 Thinking Fast/5.2/5.2 Pro/5.4/5.4 Mini/5.5/5.6 Luna/Sol/Terra/5 Mini/5 Pro, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol, GPT oss 120b; Fable 5/5.1, Haiku 4.5/5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.5/4.6/5/5.5; Llama 3.3 70B/4 Maverick; Mistral Large 3/4; DeepSeek v3.1. Plan/admin/region settings can narrow this list; API availability is listed alongside chat, not independently observed. - auto_routing: Auto analyzes the first message and estimates complexity to select a conversation model; exact final model disclosure was not verified. - Unverified multimodal_input: A model-by-model image/audio input matrix and authenticated model picker were not inspected. - providers — Which model providers are available? [supported]: OpenAI, Anthropic, Google, Meta, Mistral and DeepSeek have named current catalogue entries. Sources: langdock:langdock:models. - current_models — Which current models are selectable on this plan? [partial]: Published text catalogue: Gemini 3.1 Pro Preview, 3 Flash Preview, 3.5/3.6/3.7/3.8 Flash, 4 Argon; GPT-5/5.1/5.1 Thinking Fast/5.2/5.2 Pro/5.4/5.4 Mini/5.5/5.6 Luna/Sol/Terra/5 Mini/5 Pro, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol, GPT oss 120b; Fable 5/5.1, Haiku 4.5/5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.5/4.6/5/5.5; Llama 3.3 70B/4 Maverick; Mistral Large 3/4; DeepSeek v3.1. Plan/admin/region settings can narrow this list; API availability is listed alongside chat, not independently observed. Sources: langdock:langdock:models. - user_choice — Can users pick the model per chat? [supported]: Per-chat selection and mid-chat switching are documented. Sources: langdock:langdock:model-guide. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Auto analyzes the first message and estimates complexity to select a conversation model; exact final model disclosure was not verified. Sources: langdock:langdock:model-guide. - multimodal_input — Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. A model-by-model image/audio input matrix and authenticated model picker were not inspected. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:models, langdock:langdock:model-guide ### MOD-02: Model freshness Judgment rule: Measure the days from a provider's general release to availability in the product for the last three major releases from OpenAI, Anthropic and Google (and Mistral where offered). Use dated changelogs or observation. Record deprecation notice for retired models. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public dated model additions exist, but release-lag medians and guaranteed retirement notice remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Unverified release_lag_days, deprecation_notice, version_pinning: No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established. - changelog — Is there a dated public model changelog? [supported]: Changelog includes Gemini 4 Argon on 13 October, Haiku 5.5 on 8 October and GPT-6.1 Sol on 30 September 2026. Sources: langdock:langdock:changes. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established. - version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. No complete last-three-major-release reconciliation against provider GA dates, contractual model retirement notice, or stable version-pinning promise was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:changes ### MOD-03: Bring-your-own keys and provider contracts Judgment rule: Record customer-held API keys, customer cloud accounts (Azure OpenAI, Bedrock, Vertex), and aggregator routes (OpenRouter, LiteLLM) as separate routes. Record what still works without a vendor-provided model, whether prices change with BYO, and documented restrictions. API-key support does not imply support for the customer's own Azure contract. #### 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. #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial BYOK supports customer credentials, named cloud providers and custom compatible HTTPS endpoints. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business BYOK and individually contracted Enterprise BYOK; customer provider charges separate; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Cloud BYOK requires separately configured completion, embedding and image routes; local/private endpoints are not implied by a cloud key. - own_api_keys — Can the customer use its own provider API keys? [supported]: Customer keys can replace managed completion, embedding and image keys; BYOK can be selected at upgrade or enabled later by support. Sources: langdock:langdock:byok. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [supported]: Guides cover customer Azure deployment settings, Google cloud and AWS Bedrock, separately from simple direct provider keys. Sources: langdock:langdock:byok-routes. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Manual OpenAI-compatible endpoints include vLLM, LiteLLM, Ollama, TGI and LocalAI. Cloud requires public HTTPS; private/local hostnames are blocked by default. Sources: langdock:langdock:byok-routes. - byo_pricing — Does BYO change the licence price? [partial]: Customer model usage is billed by the customer provider under BYOK. The applicable Business/Enterprise BYOK licence rate is unknown: the public Standard headline and calculator do not reconcile, and the prior hashed asset is not a stable tariff source. No BYOK seat-rate arithmetic is retained. Sources: langdock:langdock:byok, langdock:langdock:billing. - byo_restrictions — Which features stop working with BYO? [supported]: Completion, embeddings and image models must all be configured. Deep Research needs reasoning/fast-reasoning/backbone routes; absent categories leave features non-functional. Sources: langdock:langdock:byok, langdock:langdock:research. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:byok, langdock:langdock:byok-routes, langdock:langdock:billing, langdock:langdock:research ### MOD-04: Local and self-hosted models Judgment rule: Record support for models running in the customer's environment (vLLM, Ollama, TGI or similar) and which features work with them: chat, RAG, tools, embeddings. Distinguish a documented, supported route from a generic endpoint that happens to work. #### 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. #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-hosted compatible inference is a documented BYOK route with network and capability requirements. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - self_hosted_embeddings: BYOK requires a configured embedding model for search; custom model setup includes embeddings. A private customer-hosted embedding network path was not independently verified. - feature_parity: Manual setup needs correct image, tool and editor capability flags. Missing embeddings/images or research routes disables their corresponding features; there is no universal parity guarantee. - vendor_hosted_open_models: Catalogue includes Llama, GPT oss, Mistral and DeepSeek; terms identify Azure/Mistral EU routes, with global opt-ins separately described. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: vLLM/Ollama/TGI/LocalAI routes work through OpenAI-compatible HTTPS endpoints, not localhost/private addresses on default SaaS. Sources: langdock:langdock:byok-routes. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [partial]: BYOK requires a configured embedding model for search; custom model setup includes embeddings. A private customer-hosted embedding network path was not independently verified. Sources: langdock:langdock:byok, langdock:langdock:byok-models. - feature_parity — Which features fail with self-hosted models? [partial]: Manual setup needs correct image, tool and editor capability flags. Missing embeddings/images or research routes disables their corresponding features; there is no universal parity guarantee. Sources: langdock:langdock:byok-models, langdock:langdock:research. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: Catalogue includes Llama, GPT oss, Mistral and DeepSeek; terms identify Azure/Mistral EU routes, with global opt-ins separately described. Sources: langdock:langdock:models, langdock:langdock:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:byok-routes, langdock:langdock:byok, langdock:langdock:byok-models, langdock:langdock:research, langdock:langdock:models, langdock:langdock:terms ### MOD-05: Model control and usage limits Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace model defaults and usage/fallback behavior are documented; per-group model/data boundaries remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - user_limits: Five-hour session and Monday-reset weekly limits depend on model-priced token consumption; numeric included budget is shown per account, not fully published. Spam protection is 250 messages/3h. Max is five times Standard. - Unverified model_allowlist_by_group, data_bound_models: Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run. - model_allowlist_by_group — Can admins limit models per group? [unknown]: Can admins limit models per group? Unknown. Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? Unknown. Group-specific model allowlists and rules binding connectors/knowledge to certain models were not established in model and role documentation; no two-user test was run. - default_model — Can admins set the default model? [supported]: Admins set a default across new chats and agents; users can have their own default. Sources: langdock:langdock:workspace. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Five-hour session and Monday-reset weekly limits depend on model-priced token consumption; numeric included budget is shown per account, not fully published. Spam protection is 250 messages/3h. Max is five times Standard. Sources: langdock:langdock:limits, langdock:langdock:pricing. - limit_behaviour — What happens when a limit is reached? [supported]: With no usable extra usage, Cloud falls back to GPT-6 Luna; BYOK/dedicated use configured fallback. Current responses finish, so spend can slightly overshoot. Personal API calls error rather than fall back. Sources: langdock:langdock:extra. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:limits, langdock:langdock:pricing, langdock:langdock:extra ## Company knowledge ### KNOW-01: Files in chat Judgment rule: Record supported formats, size and count limits, scanned-PDF OCR, tables and spreadsheets, images inside documents, and whether a file is read in full or retrieved in chunks. Upload the shared fixture set (long German PDF, scanned contract, Excel with formulas, PowerPoint) and record failures. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Format/count limits and direct previews differ from semantic search paths. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - spreadsheets: Spreadsheets use direct reading and file tools, not chunk embeddings; source formula/structure accuracy was not fixture-tested. - Unverified ocr: No shared scanned-PDF OCR or multilingual file fixture was uploaded. - formats — Which formats are accepted? [supported]: PDF/Word/PowerPoint and text, Excel/CSV/TSV/Parquet, listed image, audio and video types are documented; Knowledge bases exclude tabular/media. Sources: langdock:langdock:files. - limits — What size and count limits apply per file and chat? [supported]: Web 50 files/message, mobile five; agent 50 files. PDF/Office 256 MB, text 10 MB, tabular 100 MB, images 20 MB; text 8M characters and PDF 5000 pages. Sources: langdock:langdock:files, langdock:langdock:file-count. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. No shared scanned-PDF OCR or multilingual file fixture was uploaded. - spreadsheets — Are Excel tables read with structure intact? [partial]: Spreadsheets use direct reading and file tools, not chunk embeddings; source formula/structure accuracy was not fixture-tested. Sources: langdock:langdock:files, langdock:langdock:retrieval. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: Small direct files are previewed in full where possible; agent knowledge above 20 documents uses lists/tools. Knowledge-base/synced text uses up to 50 chunks of up to 2000 characters. Sources: langdock:langdock:retrieval. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:files, langdock:langdock:file-count, langdock:langdock:retrieval ### KNOW-02: Knowledge bases and shared collections Judgment rule: Record curated document collections that persist across chats, who can create and share them, size limits, and how they attach to assistants. Distinguish personal, group and organisation-wide scope. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: supported Persistent knowledge bases and library folders have separate limits and access roles. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. - persistent_collections — Can users keep document collections across chats? [supported]: Knowledge bases persist for chat, agents, workflows and API use. Sources: langdock:langdock:knowledge. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Owner/Editor/Viewer roles; share with persons, groups or workspace, subject to workspace-sharing permission. Sources: langdock:langdock:knowledge. - size_limits — What are the collection limits? [supported]: Cloud Knowledge bases support 1000 files, 8M characters/file. Normal folders have 100 files and 250 MB total; dedicated limits are configurable. Sources: langdock:langdock:knowledge, langdock:langdock:file-count. - assistant_binding — Can collections be bound to an assistant? [supported]: Agent Folders attach knowledge bases/library folders/synced folders. Sources: langdock:langdock:agents. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:knowledge, langdock:langdock:file-count, langdock:langdock:agents ### KNOW-03: Enterprise connectors Judgment rule: List each connector separately with plan, availability and setup owner: SharePoint, OneDrive, Outlook, Teams, Google Drive, Gmail, Confluence, Jira, Notion, Box, Salesforce, ServiceNow, file shares. Record whether the vendor or a third party (or the customer via MCP) provides it, and whether it needs admin consent. A connector listed on a roadmap or partner page is `announced`. An on-prem connector or gateway proves access to local data, not a self-hosted platform (DATA-02). #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Native tools, daily folder sync and customer MCP/API integrations are distinct routes. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - on_prem_sources: Confluence Data Center and customer API/MCP endpoints can connect; private network access is restricted by default in Cloud, so generic local shares are not established. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [supported]: Directory includes SharePoint, OneDrive, Outlook Email/Calendar and Teams. SharePoint/OneDrive also support indexed folder sync. Sources: langdock:langdock:integrations, langdock:langdock:sync. - google_workspace — Which Google sources are connected? [supported]: Drive, Gmail, Calendar, Docs, Sheets, Slides and Meet are listed; Drive supports folder sync. Sources: langdock:langdock:integrations. - atlassian — Confluence and Jira? [supported]: Confluence Cloud, self-hosted Confluence Data Center and Jira are in the native directory. Sources: langdock:langdock:integrations. - other_systems — Which other business systems? [supported]: Named routes include Salesforce, ServiceNow, HubSpot, Slack, Notion, Airtable, Asana, GitHub, Azure AI Search, Kendra and Databricks; see directory for authentication and actions. Sources: langdock:langdock:integrations. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Confluence Data Center and customer API/MCP endpoints can connect; private network access is restricted by default in Cloud, so generic local shares are not established. Sources: langdock:langdock:integrations, langdock:langdock:mcp. - connector_provider — Who builds and maintains each connector? [supported]: Langdock provides native integrations; customers build custom actions or connect official third-party MCP servers. Sources: langdock:langdock:integrations, langdock:langdock:mcp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations, langdock:langdock:sync, langdock:langdock:mcp ### KNOW-04: Permission-aware retrieval Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Folder Sync checks each user source access; Purview labels add a separate, qualified control. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - source_permissions_respected: Synced folder retrieval checks the user source rights in real time and requires the user connection. Static shared knowledge follows Langdock sharing instead. No fixture test was run. - sensitivity_labels: Request-enabled policy covers five Microsoft integrations, with exceptions for certain Outlook actions/copy attachments, unlabeled/new labels, custom MCP and uploaded files; saved-policy enforcement is conditional on integration rollout. - Unverified revocation_delay: A two-user restricted-file/revocation test was not run; no measured source-permission revocation latency is asserted. - source_permissions_respected — Are source permissions enforced per user? [partial]: Synced folder retrieval checks the user source rights in real time and requires the user connection. Static shared knowledge follows Langdock sharing instead. No fixture test was run. Sources: langdock:langdock:sync, langdock:langdock:knowledge. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: A copied content index is searched while access is checked live against the source system for synced files. Sources: langdock:langdock:sync. - revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unknown. A two-user restricted-file/revocation test was not run; no measured source-permission revocation latency is asserted. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins choose integrations/actions; synced folders scope imported content and labels can exclude documents. Sources: langdock:langdock:actions, langdock:langdock:labels, langdock:langdock:sync. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [partial]: Request-enabled policy covers five Microsoft integrations, with exceptions for certain Outlook actions/copy attachments, unlabeled/new labels, custom MCP and uploaded files; saved-policy enforcement is conditional on integration rollout. Sources: langdock:langdock:labels. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:sync, langdock:langdock:knowledge, langdock:langdock:labels, langdock:langdock:actions ### KNOW-05: Freshness and sync model Judgment rule: Record live (federated) search versus a copied index, sync interval, deletion propagation, and where the index is stored. Edit and delete one fixture document and record when answers change. A copied index adds storage location to DATA-01. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Folder Sync copies indexed text and refreshes daily, with live access checks and manual refresh. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - deletion_propagation: Daily sync removes source-deleted files; no measured end-to-end deletion delay is available. - index_location: Terms place customer files/embeddings in EU Azure storage, with default Frankfurt hosting. Per-index backup copies are not separately mapped. - live_or_indexed — Is content searched live or copied into an index? [supported]: Folder Sync downloads supported text into an index; spreadsheets remain direct-read files. Other integration actions query source APIs. Sources: langdock:langdock:sync, langdock:langdock:integrations. - sync_interval — How often does an index refresh? [supported]: Daily updates, manual refresh and up to one hour initial sync. Sources: langdock:langdock:sync. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Daily sync removes source-deleted files; no measured end-to-end deletion delay is available. Sources: langdock:langdock:sync. - index_location — Where is indexed content stored? [partial]: Terms place customer files/embeddings in EU Azure storage, with default Frankfurt hosting. Per-index backup copies are not separately mapped. Sources: langdock:langdock:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:sync, langdock:langdock:integrations, langdock:langdock:terms ### KNOW-06: Grounding and retrieval quality Judgment rule: Run the shared question set over the fixture corpus: factual lookups, cross-document questions, German document with an English question, a question with no answer in the corpus. Record citation presence, link accuracy, correct answers and refusals to invent. Disclose model, settings, attempt count and failures. Single runs support a case study, not a ranking. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Citations are documented; retrieval outcomes remain untested. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - citations: Agent responses cite sources by default; source-access restriction can hide click-through while still using content. - Unverified citation_accuracy, cross_language, no_answer_behaviour, observed_accuracy: No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. - citations — Are answers linked to specific sources? [partial]: Agent responses cite sources by default; source-access restriction can hide click-through while still using content. Sources: langdock:langdock:agents. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared corpus or question set was run. Citation accuracy, cross-language retrieval, no-answer behavior and numeric accuracy remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:agents ### KNOW-07: Memory and personal context Judgment rule: Record personal custom instructions, cross-chat memory, project or workspace context, and user controls to view, edit, delete or disable memory. Record whether admins can disable memory organisation-wide. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: supported Regular-chat instructions and memory have user and workspace controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. - custom_instructions — Can users set persistent instructions? [supported]: Personal instructions apply in regular chat; agent/project instructions replace them. Sources: langdock:langdock:account. - cross_chat_memory — Does the product remember facts across chats? [supported]: Regular chats use a personal store of up to 50 memories; projects/agents do not use this memory. Sources: langdock:langdock:memory. - user_memory_controls — Can users view, edit and delete memories? [supported]: Users inspect, edit, delete or disable memories in account settings and can update/forget through chat. Sources: langdock:langdock:memory, langdock:langdock:account. - admin_memory_controls — Can admins turn memory off? [supported]: Memory availability requires workspace and personal enablement. Sources: langdock:langdock:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account, langdock:langdock:memory, langdock:langdock:chat ## Assistants and agents ### AGT-01: Custom assistants Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents combine reusable knowledge and tools with creation/sharing controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - sharing_scope: Workspace/group resources and permissioned agent configuration are documented; no fixture was shared. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Agents configure model, instructions, files, folders, integrations, subagents, skills and workflows. Sources: langdock:langdock:agents. - creator_permissions — Can admins limit who creates them? [supported]: System/custom roles and extra permissions control agent creation/sharing. Sources: langdock:langdock:roles. - sharing_scope — Can assistants be shared with users, groups or everyone? [partial]: Workspace/group resources and permissioned agent configuration are documented; no fixture was shared. Sources: langdock:langdock:workspace, langdock:langdock:agents. - catalogue — Is there an internal assistant directory? [supported]: Workspace agent management has All/Unassigned/Verified views. Sources: langdock:langdock:workspace. - prompt_library — Are shared prompt templates available? [supported]: The workspace guide documents group/workspace prompt-library sharing. Sources: langdock:langdock:workspace. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:agents, langdock:langdock:roles, langdock:langdock:workspace ### AGT-02: Tools, actions and MCP Judgment rule: Record built-in tools, custom actions (OpenAPI), MCP client support (local and remote servers), authentication model per tool (shared service account or per-user OAuth), and admin approval of tools. Verify one external-tool call and its access boundary. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Remote MCP and custom actions have admin access controls and optional confirmations. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - tool_approval: Admins share integrations/actions by user/group/key, but native core actions cannot be disabled. New MCP tools default to no confirmation; per-tool/agent confirmations can be configured. - builtin_tools — Which tools are built in? [supported]: Search, images, file work, document editor, memory, research and company knowledge are governed tools. Sources: langdock:langdock:chat. - custom_actions — Can admins add API actions? [supported]: Custom API integrations and shareable individual actions are documented. Sources: langdock:langdock:actions. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Streamable HTTP/SSE with OAuth CIMD/DCR/manual PKCE, API key or none; private network URLs blocked by default. Sources: langdock:langdock:mcp. - tool_auth — Do tools act as the user or as a shared account? [supported]: Native integrations use personal OAuth or service credentials per provider; MCP supports user OAuth or API headers. Sources: langdock:langdock:integrations, langdock:langdock:mcp. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins share integrations/actions by user/group/key, but native core actions cannot be disabled. New MCP tools default to no confirmation; per-tool/agent confirmations can be configured. Sources: langdock:langdock:actions, langdock:langdock:mcp, langdock:langdock:changes. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:chat, langdock:langdock:actions, langdock:langdock:mcp, langdock:langdock:integrations, langdock:langdock:changes ### AGT-03: Web search and deep research Judgment rule: Record web search on/off control per organisation and group, search provider, citation of web sources, deep or multi-step research, and whether queries leave the residency boundary. Admins of regulated companies often need web search off. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Cited search and public-web Deep Research are available; provider/region details remain incomplete. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - admin_toggle: Workspace admins disable web search and separate agent capabilities. Per-group search-toggle coverage was not established. - Unverified search_provider: Search/crawl provider contracts and query-processing region were not established in the public tool documentation. - web_search — Is web search available? [supported]: Chat tool generates a query and can open URLs; sources are inspectable. Sources: langdock:langdock:web. - admin_toggle — Can admins disable it per organisation or group? [partial]: Workspace admins disable web search and separate agent capabilities. Per-group search-toggle coverage was not established. Sources: langdock:langdock:workspace. - search_provider — Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? Unknown. Search/crawl provider contracts and query-processing region were not established in the public tool documentation. - deep_research — Is multi-step research with a report available? [supported]: Regular chat only, public web only, cited PDF reports; standard keys allow 15 researches per rolling 30 days. BYOK needs research models. Sources: langdock:langdock:research. - web_citations — Are web sources cited? [supported]: Search sources link to corresponding paragraphs and Deep Research has activity/source lists. Sources: langdock:langdock:web, langdock:langdock:research. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:web, langdock:langdock:workspace, langdock:langdock:research ### AGT-04: Workflows and automation Judgment rule: Record no-code or low-code workflows, scheduled prompts, triggers from email, forms or business systems, and multi-step chains. Name where they run and who can build them. A shared prompt template is not a workflow. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Multi-step workflows support automatic triggers and human review. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=Workflow run package; model usage separately metered; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - builder_audience: Quickstart and conversational Workflow Builder guide non-developers, with code/HTTP nodes for technical users. - workflow_builder — Is there a workflow or chain builder? [supported]: Workflows chain agents, integrations, logic, loops and custom code after workspace activation. Sources: langdock:langdock:workflows. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Schedule triggers are documented for workflows; the public API index also exposes recurring saved tasks. Sources: langdock:langdock:workflows. - event_triggers — Can external events start a workflow? [supported]: Connected-app events, forms and webhooks start runs; dated composable-workflow release supports multiple triggers. Sources: langdock:langdock:workflows, langdock:langdock:changes. - builder_audience — Is building aimed at business users, IT or developers? [partial]: Quickstart and conversational Workflow Builder guide non-developers, with code/HTTP nodes for technical users. Sources: langdock:langdock:workflows. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workflows, langdock:langdock:changes ### AGT-05: Agentic task execution Judgment rule: Record an agent mode that plans and carries out multi-step tasks with tools (browser, files, connectors), with visible steps, user confirmation of side effects and stop control. Run one fixture task (gather three documents, draft a summary, propose an email). Record interventions and what ran. A final claim of success is not proof. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents execute actions/subagents; workflow and add-in confirmation behavior is explicit. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock Excel and Outlook add-ins; version=Public documentation checked 2026-10-26; plan=Business Chat & Agents/Workflows; Outlook add-in for paid plans and trials, enabled by workspace admin; add_ons=Workflow package as needed; compatible Microsoft Outlook/Exchange Online subscription; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - visible_steps: Deep Research shows search/page-read activity; workflows expose run history and nested run links. General agent step-display completeness was not independently observed. - side_effect_confirmation: Configurable per-agent confirmations and workflow action review exist. Newly saved MCP actions default to no confirmation; Office add-ins ask before edits by default. - stop_control: Deep Research has a stop button; general external side effects already committed cannot be inferred reversible. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Agents can call integrations, subagents and workflows to carry out multiple steps. Sources: langdock:langdock:agents. - visible_steps — Are steps and tool calls shown? [partial]: Deep Research shows search/page-read activity; workflows expose run history and nested run links. General agent step-display completeness was not independently observed. Sources: langdock:langdock:research, langdock:langdock:changes. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Web agents can require configured action confirmation; workflow action review is separate. Newly saved MCP actions default to no confirmation. In the Outlook add-in, edits ask by default, users can allow subsequent edits for the chat, and sending requires a requested action plus confirmation. Sources: langdock:langdock:changes, langdock:langdock:hitl, langdock:langdock:mcp, langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace. - stop_control — Can the user stop a running task? [partial]: Deep Research has a stop button; general external side effects already committed cannot be inferred reversible. Sources: langdock:langdock:research. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:agents, langdock:langdock:research, langdock:langdock:changes, langdock:langdock:hitl, langdock:langdock:mcp, langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:agents-20261026, langdock:langdock:research-20261026, langdock:langdock:changes-20261026, langdock:langdock:hitl-20261026, langdock:langdock:mcp-20261026, langdock:langdock:excel-20261026 ### AGT-06: Programmable access Judgment rule: Record a public API for chat, assistants and knowledge, SDKs, API authentication, rate limits and whether API use counts against the same governance (audit, budgets, model restrictions). Being an MCP client is different from exposing the product over MCP. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public APIs include knowledge and agent MCP, with distinct personal/workspace governance boundaries. Availability: generally-available Delivery: native Scope: surfaces=Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-21; plan=API/Agent/Knowledge scopes; workspace activation may apply; add_ons=Metered API usage; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - api_governance: Personal API keys share member/workspace spend limits and error on exhaustion; workspace API keys and workflow costs use separate limits. - chat_api — Is there an API for chat and assistants? [supported]: Public Completion and Agent APIs use scoped bearer keys. Workspace/personal key access is controlled by admins. Sources: langdock:langdock:workspace. - knowledge_api — Can documents be loaded through an API? [supported]: Knowledge Folder API supports upload/update/delete/retrieve/search with API-key sharing roles. Sources: langdock:langdock:knowledge. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Personal API keys share member/workspace spend limits and error on exhaustion; workspace API keys and workflow costs use separate limits. Sources: langdock:langdock:billing, langdock:langdock:extra. - mcp_server — Does the product expose itself to other agents over MCP? [supported]: https://api.langdock.com/mcp exposes find_agent/ask_agent/ask_custom_agent under Agent API key scope; dedicated URL differs. Sources: langdock:langdock:mcp-server. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:knowledge, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock:mcp-server ## Daily work ### WORK-01: Clients and access points Judgment rule: List web, desktop (Windows, macOS), iOS, Android, mobile browser and browser extension separately. For each, record login with company SSO, feature gaps against web, and MDM/Intune deployability. An installable app is different from a mobile website. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web, desktop and mobile clients are documented, with IT deployment guidance. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock Windows/macOS desktop, Langdock iOS/Android; version=Public documentation checked 2026-10-21; plan=Business or contracted Enterprise workspace clients; the same subscription/approved models apply; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=Windows, macOS, iOS, Android. Limitations: - Native-client and SSO parity beyond the documented file limit was not tested. The source is installation guidance, not proof of a paid Enterprise-only client entitlement. - web — Is a full web client available? [supported]: The core platform is a browser workspace. Sources: langdock:langdock:terms. - desktop_apps — Windows and macOS apps? [supported]: Official Windows/macOS downloads use the same workspace and approved models as web. This is documented availability, not a hands-on parity test. Sources: langdock:langdock:desktop-product. - mobile_apps — iOS and Android apps with SSO? [partial]: The vendor publishes iOS/Android clients and official store links. Mobile-specific SSO and managed-access compatibility were not independently tested. Sources: langdock:langdock:mobile-rev2, langdock:langdock:mobile-product. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. A general browser extension and exhaustive mobile/SSO/Intune parity matrix were not established. - managed_deployment — Can IT deploy and configure clients through MDM? [partial]: Windows machine-wide MSIX/Intune and deployment kits are documented. macOS PKG/DMG works with Jamf, Kandji and Intune. These are client installation methods; separate mobile MAM/dedicated entitlements are not established by this finding. Sources: langdock:langdock:desktop-rev2. - client_feature_gaps — Which features are missing on mobile? [partial]: Mobile permits five files per message versus 50 on web; other parity gaps were not tested. Sources: langdock:langdock:file-count. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:desktop-product, langdock:langdock:mobile-rev2, langdock:langdock:mobile-product, langdock:langdock:desktop-rev2, langdock:langdock:file-count ### WORK-02: Office suite and Teams integration Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Excel and Outlook add-ins and a Teams bot are documented; broad Office-suite coverage is not inferred. Availability: generally-available Delivery: native Scope: surfaces=Langdock Excel and Outlook add-ins, Langdock Teams bot; version=Public documentation checked 2026-10-26; plan=Business or Enterprise workspace; Outlook available on paid plans/trials, Excel/Teams require workspace-admin enablement; add_ons=Compatible Microsoft licences not priced; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - word_excel_powerpoint: Excel add-in reads/writes workbooks with formulas/charts; no Word or PowerPoint add-in was established. - licence_prerequisites: Excel web/Windows/Mac version matrix and Outlook Exchange Online requirement are explicit; workspace admin access controls apply and extra M365 seat costs were not priced. - Unverified google_workspace_apps: Google in-editor apps were not established; Google content integrations are recorded separately. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [partial]: Excel add-in reads/writes workbooks with formulas/charts; no Word or PowerPoint add-in was established. Sources: langdock:langdock:excel. - outlook — Does it work inside Outlook? [supported]: Outlook reads connected mailbox/calendar and edits drafts; sending requires a requested action and confirmation. Exchange Online is required. Sources: langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace. - teams — Is there a Teams app or bot? [supported]: Admin-installed Teams bot supports private chat and collaborative channel mentions. Sources: langdock:langdock:teams, langdock:langdock:teams-20261026. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Google in-editor apps were not established; Google content integrations are recorded separately. Rechecked 2026-10-26 in Outlook Add-in, Excel Add-in, How to use the Teams Bot. The Teams Markdown guide was retrieved with HTTP 200; Google in-editor app coverage remains undocumented in these sources. - licence_prerequisites — Which licences or consents are needed? [partial]: Excel web/Windows/Mac version matrix and Outlook Exchange Online requirement are explicit; workspace admin access controls apply and extra M365 seat costs were not priced. Sources: langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:teams, langdock:langdock:outlook-marketplace, langdock:langdock:teams-20261026. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:excel, langdock:langdock:outlook-rev2, langdock:langdock:outlook-marketplace, langdock:langdock:teams, langdock:langdock:outlook-rev2-20261026, langdock:langdock:outlook-admin-20261026, langdock:langdock:pricing-20261026, langdock:langdock:excel-20261026, langdock:langdock:teams-20261026 ### WORK-03: Translation and writing Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial DeepL integration offers document translation and glossaries; end-to-end layout quality is untested. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - document_translation: Native DeepL integration lists document translation; its supported layout guarantees were not verified in a trial. - glossaries: DeepL integration lists glossary management; full enterprise glossary rollout was not tested. - Unverified formality_and_variants: Formality/de-CH configuration and DE-to-FR/IT layout-preservation fixtures remain unverified. - document_translation — Can whole documents be translated with formatting kept? [partial]: Native DeepL integration lists document translation; its supported layout guarantees were not verified in a trial. Sources: langdock:langdock:integrations. - translation_engine — Which engine translates? [supported]: The dedicated DeepL integration uses the customer DeepL API key; ordinary chat rewriting uses the chosen model. Sources: langdock:langdock:integrations. - glossaries — Are company glossaries supported? [partial]: DeepL integration lists glossary management; full enterprise glossary rollout was not tested. Sources: langdock:langdock:integrations. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Formality/de-CH configuration and DE-to-FR/IT layout-preservation fixtures remain unverified. - writing_tools — Are dedicated rewrite and proofreading tools available? [supported]: DeepL integration includes writing polish; Document Editor supports selected-text and whole-document AI edits. Sources: langdock:langdock:integrations, langdock:langdock:editor. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations, langdock:langdock:editor ### WORK-04: Image generation and editing Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Image generation and model-specific editing are documented with workspace controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - image_generation: Image-generation tool invokes a chosen available image model; dated September release names EU GPT-Image 2.5 Flare and Sunburst. - image_editing: The release describes image editing and BYOK model setup has an image-editing capability flag; exhaustive per-model editing limits were not verified. - usage_terms: As between customer/vendor, customer content rights belong to the customer; third-party model terms and rights restrictions remain applicable. - image_generation — Can users generate images, with which models? [partial]: Image-generation tool invokes a chosen available image model; dated September release names EU GPT-Image 2.5 Flare and Sunburst. Sources: langdock:langdock:images, langdock:langdock:changes. - image_editing — Can users edit uploaded images? [partial]: The release describes image editing and BYOK model setup has an image-editing capability flag; exhaustive per-model editing limits were not verified. Sources: langdock:langdock:changes, langdock:langdock:byok-models. - admin_control — Can admins restrict image generation? [supported]: Workspace admins can disable image generation and manage available models. Sources: langdock:langdock:workspace. - usage_terms — What usage rights apply to output? [partial]: As between customer/vendor, customer content rights belong to the customer; third-party model terms and rights restrictions remain applicable. Sources: langdock:langdock:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:images, langdock:langdock:changes, langdock:langdock:byok-models, langdock:langdock:workspace, langdock:langdock:terms ### WORK-05: Voice and meetings Judgment rule: Record dictation, read-aloud, live voice conversation, meeting transcription and summarisation, supported languages including Swiss German speech, and where audio is processed. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Audio/meeting-source integrations are documented; live voice and Swiss German remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - read_aloud: ElevenLabs integration offers text-to-speech using a customer API key; this is not a guaranteed native read-aloud control. - meeting_summaries: Google Meet/Zoom and ElevenLabs integrations can retrieve transcripts; source recordings and processing depend on the connected service. No native meeting-bot transcription fixture was run. - Unverified dictation, voice_conversation, swiss_german_speech: Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages. - dictation — Can users dictate prompts? [unknown]: Can users dictate prompts? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages. - read_aloud — Can answers be read aloud? [partial]: ElevenLabs integration offers text-to-speech using a customer API key; this is not a guaranteed native read-aloud control. Sources: langdock:langdock:integrations. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages. - meeting_summaries — Are meetings transcribed and summarised? [partial]: Google Meet/Zoom and ElevenLabs integrations can retrieve transcripts; source recordings and processing depend on the connected service. No native meeting-bot transcription fixture was run. Sources: langdock:langdock:integrations. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Dictation, native live voice, audio processing-region mapping and Swiss German recognition were not established in the user guide or client pages. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:integrations ### WORK-06: Data analysis and document output Judgment rule: Record code execution for data analysis, charts, and generation of downloadable Word, Excel, PowerPoint and PDF files. Analyse the fixture Excel and request a PowerPoint summary. Record where code runs and whether files are editable. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial File analysis, charts and editable document generation are documented; execution-location detail is incomplete. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - data_analysis: The data-analysis guide documents spreadsheet metrics/calculations; exact executed-code sandbox/model configuration was not verified. - canvas_editing: Document Editor replaces Canvas; it exports Markdown/Word/PDF but cannot directly edit imported Word/PDF files. - data_analysis — Can it analyse spreadsheets with executed code? [partial]: The data-analysis guide documents spreadsheet metrics/calculations; exact executed-code sandbox/model configuration was not verified. Sources: langdock:langdock:analysis. - charts — Can it produce charts? [supported]: Charts and downloadable chart images are supported in the guide. Sources: langdock:langdock:analysis. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Analysis lists Excel/CSV/Word/PDF/JSON; changelog and agent file templates also describe PowerPoint. Sources: langdock:langdock:analysis, langdock:langdock:changes. - canvas_editing — Is there a document or canvas editor for iterating on output? [partial]: Document Editor replaces Canvas; it exports Markdown/Word/PDF but cannot directly edit imported Word/PDF files. Sources: langdock:langdock:editor. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:analysis, langdock:langdock:changes, langdock:langdock:editor ### WORK-07: Sharing and team spaces Judgment rule: Record chat sharing (link, user, group), shared projects or team spaces, channels or group chat with AI, and commenting. Test sharing a chat with a colleague in another group and record what the recipient sees, including knowledge they lack access to. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared projects expose chats/files, and Teams channels support group interaction. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock Teams bot; version=Public documentation checked 2026-10-21; plan=Business/Enterprise workspace sharing; Teams bot requires workspace-admin setup and Microsoft tenant installation; add_ons=Microsoft Teams access; bot installed and permitted by tenant admin; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Unverified share_permission_boundary: No cross-group source-boundary sharing fixture was run; project sharing does not by itself prove permission-safe redistribution of generated answers. - share_chats — Can chats be shared inside the organisation? [supported]: Workspace chat-link sharing is managed under account shared chats. Sources: langdock:langdock:account. - team_spaces — Are shared projects or workspaces available? [supported]: Projects shared with users/groups include all current and future project chats, files and instructions; cannot share a project to the whole workspace. Sources: langdock:langdock:projects. - group_chat — Can several people chat together with the AI? [supported]: Teams channel threads allow several people to participate with @Langdock. Sources: langdock:langdock:teams. - share_permission_boundary — Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? Unknown. No cross-group source-boundary sharing fixture was run; project sharing does not by itself prove permission-safe redistribution of generated answers. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account, langdock:langdock:projects, langdock:langdock:teams ### WORK-08: Interface languages and accessibility Judgment rule: Record UI languages, focusing on German, French, Italian and English, with translation quality observed (complete, partial, machine-translated). Record response language handling and WCAG conformance statements. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Five interface languages are documented; quality and accessibility have not been audited. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Unverified dach_language_quality, accessibility_statement, admin_ui_languages: No authenticated language-quality/admin-translation inspection or WCAG conformance report was established. - ui_languages — Which UI languages are offered? [supported]: English, German, Spanish, French and Italian are listed in Account Preferences. Sources: langdock:langdock:account. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated language-quality/admin-translation inspection or WCAG conformance report was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:account ## Administration and governance ### ADM-01: Single sign-on and authentication Judgment rule: Record SAML, OIDC, Microsoft Entra ID, Google, LDAP, MFA enforcement, conditional-access compatibility, domain verification and plan restrictions. Test one SSO login on a trial where possible. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business includes SAML SSO and verified domains; MFA relies on the identity provider. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - mfa: No standalone Langdock MFA; SAML identity provider enforces MFA. - Unverified conditional_access: OIDC/LDAP enterprise options and a tested Entra Conditional Access compatibility matrix were not established. - sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML 2.0 with Entra ID, Google Workspace and Okta; account docs also name Google/Microsoft SSO. Sources: langdock:langdock:saml, langdock:langdock:account. - sso_plan — Which plan includes SSO? [supported]: Business up to 1000 users includes SSO, SCIM and SAML. Sources: langdock:langdock:billing. - mfa — Can MFA be enforced? [partial]: No standalone Langdock MFA; SAML identity provider enforces MFA. Sources: langdock:langdock:saml. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. OIDC/LDAP enterprise options and a tested Entra Conditional Access compatibility matrix were not established. - domain_capture — Can the company claim its email domain? [supported]: Join by domain and verified email domains are prerequisites for SAML; SAML remains required on those verified domains. Sources: langdock:langdock:saml. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:saml, langdock:langdock:account, langdock:langdock:billing ### ADM-02: User provisioning and lifecycle Judgment rule: Record SCIM, just-in-time provisioning, group sync from the identity provider, deprovisioning effects (chats, assistants, knowledge ownership transfer) and licence assignment. Deprovision a test user and record what happens to their content. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial SCIM synchronizes users/groups and preserves functioning ownerless agents. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - deprovisioning: Entra Update removes unassigned/blocked/soft-deleted memberships when enabled. Agents become unassigned, continue to work and need a new owner before editing; sync-folder owner removal can interrupt refresh. - seat_assignment: Admins assign roles/plans in member management; exact reclaimed-seat billing rules depend on subscription. - Unverified jit_provisioning: Just-in-time first-login provisioning and complete user-chat/knowledge ownership effects were not tested or fully specified. - scim — Is SCIM provisioning supported? [supported]: SCIM 2.0 via Entra, with prior SAML and verified domains. Sources: langdock:langdock:scim. - group_sync — Are identity-provider groups synced? [supported]: Entra SCIM group sync is documented and can be disabled; default group roles are separately configurable. Sources: langdock:langdock:scim-entra, langdock:langdock:workspace. - jit_provisioning — Are users created at first login? [unknown]: Are users created at first login? Unknown. Just-in-time first-login provisioning and complete user-chat/knowledge ownership effects were not tested or fully specified. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: Entra Update removes unassigned/blocked/soft-deleted memberships when enabled. Agents become unassigned, continue to work and need a new owner before editing; sync-folder owner removal can interrupt refresh. Sources: langdock:langdock:scim-entra, langdock:langdock:leaver, langdock:langdock:sync. - seat_assignment — Can admins assign and reclaim seats? [partial]: Admins assign roles/plans in member management; exact reclaimed-seat billing rules depend on subscription. Sources: langdock:langdock:workspace. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:scim, langdock:langdock:scim-entra, langdock:langdock:workspace, langdock:langdock:leaver, langdock:langdock:sync ### ADM-03: Roles, groups and feature permissions Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial System/custom roles and delegated groups govern product and action permissions. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - feature_toggles: Role permissions plus integration/action sharing can target people/groups. Global chat/agent capabilities include search, images and file work; universal per-group toggle parity was not established. - Unverified multi_entity: Subsidiary/contract-level isolation beyond group and workspace boundaries was not established. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Member, Editor, Admin, up to five custom roles and extra permissions; group admins are separate from workspace admins. Sources: langdock:langdock:roles. - groups — Can permissions be set per group? [supported]: Groups can be SCIM-synced, admin-created or user-created if allowed; group rights and resources are distinct from system roles. Sources: langdock:langdock:workspace. - feature_toggles — Which features can be switched on or off per group? [partial]: Role permissions plus integration/action sharing can target people/groups. Global chat/agent capabilities include search, images and file work; universal per-group toggle parity was not established. Sources: langdock:langdock:roles, langdock:langdock:actions, langdock:langdock:workspace. - multi_entity — Can subsidiaries or departments be separated within one contract? [unknown]: Can subsidiaries or departments be separated within one contract? Unknown. Subsidiary/contract-level isolation beyond group and workspace boundaries was not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:roles, langdock:langdock:workspace, langdock:langdock:actions ### ADM-04: Usage and adoption analytics Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: supported Analytics and exports cover adoption and consumption with user-detail controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. - adoption_dashboard — Is there an adoption dashboard? [supported]: Active users, message trends, agent/group counts and leaderboards are documented. Sources: langdock:langdock:workspace. - breakdowns — Can usage be broken down by group, model, feature and assistant? [supported]: Products, models, users, groups, API keys, agents, workflows, projects and add-ins have dashboard/export breakdowns. Sources: langdock:langdock:workspace, langdock:langdock:exports. - export — Can usage data be exported? [supported]: CSV and Usage Export API, up to 12 months, one million rows per export and 15-minute generation limit. Sources: langdock:langdock:exports. - privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: User-level data toggle omits listed identifying fields from CSV; whole analytics can be disabled via support. Sources: langdock:langdock:exports, langdock:langdock:workspace. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:exports ### ADM-05: Spend controls and cost allocation Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat/BYOK, workspace API and workflows have separate spend controls. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - budget_enforcement: Chat/agents fall back; personal API errors; workflow AI runs stop. Current response overshoot, unpriced models and excluded backbone/workspace API/workflow costs limit a single-budget interpretation. - chargeback: Usage CSV/API include cost and department/company grouping fields; a full accounting chargeback integration was not established. - cost_visibility — Can admins see cost or consumption per user and group? [supported]: BYOK analytics show estimated USD from configured custom-model rates; API/extra usage has billed costs. These can differ from provider invoices. Sources: langdock:langdock:workspace, langdock:langdock:byok. - budgets — Can budgets be set per user or group? [supported]: Workspace, plan, group, user and agent BYOK limits; personal extra limits; workflow workspace and individual limits. Sources: langdock:langdock:byok-limits, langdock:langdock:extra, langdock:langdock:workflow-limits. - budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: Chat/agents fall back; personal API errors; workflow AI runs stop. Current response overshoot, unpriced models and excluded backbone/workspace API/workflow costs limit a single-budget interpretation. Sources: langdock:langdock:extra, langdock:langdock:byok-limits, langdock:langdock:workflow-limits. - chargeback — Can costs be exported per cost centre? [partial]: Usage CSV/API include cost and department/company grouping fields; a full accounting chargeback integration was not established. Sources: langdock:langdock:exports. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:byok, langdock:langdock:byok-limits, langdock:langdock:extra, langdock:langdock:workflow-limits, langdock:langdock:exports ### ADM-06: Audit logs and compliance export Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise dedicated deployment documents separate administrative-event and conversation-content export APIs. Cloud content export requires workspace enablement and is outside this dedicated finding. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-26; plan=Enterprise dedicated deployment: administrative and resource APIs plus separately enabled Compliance API; Business Cloud outside this finding; add_ons=Dedicated Enterprise deployment and relevant API scopes; Compliance API deployment enablement; deployment_mode=dedicated-instance; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Audit events, usage rows and conversation-content exports are distinct API functions. The dedicated-deployment behavior is not universal Business Cloud availability. - admin_events — Are admin and security events logged? [partial]: API logs workspace/model/role/skill/action/workflow changes and failed logins with actor/IP/diff; immutable storage guarantees were not verified. Sources: langdock:langdock:audit. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: Dedicated deployments serve the Compliance API unless disabled for that deployment. A key with the Compliance API scope is required. Conversation message content and tool inputs/outputs are included only when include_message_content=true and include_action_results=true are both set. On Cloud the scope is hidden and requests return 404 until workspace enablement; Business Cloud entitlement is not inferred. Sources: langdock:langdock:compliance-rev2-20261026. - siem_export — Can logs stream to a SIEM or be exported? [supported]: Cursor-paginated event API is documented for SIEM ingestion, under AUDIT_LOG_API scope. Sources: langdock:langdock:audit. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Unknown. Native legal hold/eDiscovery and audit integrity guarantees were not established. Rechecked 2026-10-26 in Audit Logs API Overview, Export tool parameters and outputs. - log_retention — How long are logs kept? [supported]: Administrative audit events have documented90-day retention. Conversation data follows the deployment workspace retention settings. A separate SaaS workflow pricing retention period is not asserted for this dedicated deployment. Sources: langdock:langdock:audit, langdock:langdock:workspace, langdock:langdock:pricing. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:audit, langdock:langdock:compliance-rev2, langdock:langdock:workspace, langdock:langdock:pricing, langdock:langdock:compliance-rev2-20261026, langdock:langdock:audit-20261026, langdock:langdock:workspace-20261026, langdock:langdock:pricing-20261026 ### ADM-07: Data loss prevention and personal data Judgment rule: Record detection and handling of personal and confidential data before it reaches a model: redaction, masking, blocking, warning. Record integration with Purview, Netskope or similar, and whether filtering runs locally or at a third party. Send a fixture prompt with a Swiss AHV number and IBAN and record the outcome. #### 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. #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Purview source filtering is documented; generic prompt/file PII redaction remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - dlp_integration: Request-enabled Purview label policy can withhold content before AI access for supported Microsoft integrations, with substantial documented exclusions. - filter_location: The label check runs in Langdock integration code before permitted content reaches the AI; it is not a generic AHV/IBAN detector. - Unverified pii_detection, pii_action, custom_patterns: The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run. - pii_detection — Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run. - pii_action — Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run. - custom_patterns — Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. The full documentation indexes and official PII/redaction search did not establish generic detection, redaction behavior or configurable sensitive-number patterns; no AHV/IBAN fixture was run. - dlp_integration — Does it integrate with an existing DLP product? [partial]: Request-enabled Purview label policy can withhold content before AI access for supported Microsoft integrations, with substantial documented exclusions. Sources: langdock:langdock:labels. - filter_location — Where does filtering run? [partial]: The label check runs in Langdock integration code before permitted content reaches the AI; it is not a generic AHV/IBAN detector. Sources: langdock:langdock:labels. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:labels ### ADM-08: AI policy and guardrails Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Instructions, disclaimers and agent compliance checks exist; prompt-level topic enforcement remains incomplete. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - org_instructions: Company description supplies up to 10000 characters in regular chats; agent/project instructions replace that field. - usage_notice: Admins can set chat/folder disclaimers and custom guidance links; required acceptance is not established. - content_filters: Governance rules evaluate agent configurations when created/published, not every prompt; failure can lead to manual flag/disable. - violation_reporting: Rule severity/results and per-rule failure analytics are visible in Governance; runtime prompt-policy reporting was not established. - org_instructions — Can admins set organisation-wide instructions? [partial]: Company description supplies up to 10000 characters in regular chats; agent/project instructions replace that field. Sources: langdock:langdock:workspace. - usage_notice — Can users be required to accept a usage policy? [partial]: Admins can set chat/folder disclaimers and custom guidance links; required acceptance is not established. Sources: langdock:langdock:workspace. - content_filters — Are content filters configurable? [partial]: Governance rules evaluate agent configurations when created/published, not every prompt; failure can lead to manual flag/disable. Sources: langdock:langdock:gov. - violation_reporting — Are policy hits visible to admins? [partial]: Rule severity/results and per-rule failure analytics are visible in Governance; runtime prompt-policy reporting was not established. Sources: langdock:langdock:gov. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:workspace, langdock:langdock:gov ## Data protection and sovereignty ### DATA-01: Hosting location and data residency Judgment rule: Record country or region separately for chat storage, files and indexes, model inference, backups, logs and telemetry, and support access. Name the cloud provider. Record whether residency is default, a paid option or plan-dependent. "EU data boundary" programmes are recorded with their documented exceptions. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Default Azure Frankfurt/EU storage and provider-specific inference are contractually distinguished. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - backups_logs_region: DPA Appendix 2 places Sentry diagnostic data in EU; full backup/telemetry physical region matrix was not disclosed. - swiss_hosting: Custom model setup allows CH region on some dedicated deployments, which does not prove end-to-end Swiss platform/support residency. - support_access_region: User-granted Support sharing expires after 72 hours and is unavailable on dedicated deployments; staff access geography is not specified. - storage_region — Where are chats, files and indexes stored? [supported]: Terms Appendix 1 places files, prompts, outputs and embeddings in selected EU Azure data centres; Frankfurt named. Sources: langdock:langdock:terms. - inference_region — Where do model calls run, per provider? [supported]: Azure, OpenAI, Google, AWS Bedrock and Mistral have described EU routes. Opt-in Global Azure/Google/AWS/OpenAI routes can infer worldwide, including US; default model enablement is EU only. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:workspace. - backups_logs_region — Where are backups, logs and telemetry? [partial]: DPA Appendix 2 places Sentry diagnostic data in EU; full backup/telemetry physical region matrix was not disclosed. Sources: langdock:langdock:dpa. - support_access_region — From where can vendor staff access data? [partial]: User-granted Support sharing expires after 72 hours and is unavailable on dedicated deployments; staff access geography is not specified. Sources: langdock:langdock:account. - swiss_hosting — Is Swiss hosting available? [partial]: Custom model setup allows CH region on some dedicated deployments, which does not prove end-to-end Swiss platform/support residency. Sources: langdock:langdock:byok-models. - residency_plan — Which plan or option provides residency? [supported]: Standard multi-tenant uses EU Azure; global model activation is a controller instruction under DPA section 8. Sources: langdock:langdock:security, langdock:langdock:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:workspace, langdock:langdock:byok-models, langdock:langdock:account, langdock:langdock:security ### DATA-02: Deployment options Judgment rule: Record multi-tenant SaaS, dedicated single-tenant instance, deployment in the customer's cloud account, on-premise and air-gapped as separate options with plan and availability. Record which features are missing in each mode, who operates it, and the documented seat or contract threshold for each mode, which can differ from the enterprise plan threshold (e.g. dedicated SaaS from 2,000 seats, own cloud from 5,000). A local-network connector or gateway that reaches on-prem data from a vendor-hosted platform is KNOW-03, not on-premise deployment. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Deployment minimums differ from Enterprise subscription entry. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Standard SaaS; Enterprise 1000+; managed dedicated 2000+; own cloud/on-premise 5000+; add_ons=Deployment and operations quoted; deployment_mode=not specified; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - customer_cloud: Customer-cloud dedicated deployment from 5000+ seats; detailed operator and feature allocation are contract-specific. - on_premise: Custom Kubernetes via Helm from 5000+ seats; operator split and infrastructure requirements are not public here. - mode_feature_gaps: Dedicated lacks Support chat-sharing and password/profile editing in Langdock; other feature controls depend on deployment configuration. No exhaustive parity list was found. - Unverified air_gapped: Air-gapped operation was not established. Thresholds are not universal feature or pricing entitlements. - multi_tenant_saas — Is a shared SaaS offered? [supported]: Standard multi-tenant SaaS is hosted on Microsoft Azure within EU. Sources: langdock:langdock:security. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: Langdock-managed single-tenant SaaS from 2000+ seats. Sources: langdock:langdock:security. - customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: Customer-cloud dedicated deployment from 5000+ seats; detailed operator and feature allocation are contract-specific. Sources: langdock:langdock:security. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Custom Kubernetes via Helm from 5000+ seats; operator split and infrastructure requirements are not public here. Sources: langdock:langdock:security. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Air-gapped operation was not established. Thresholds are not universal feature or pricing entitlements. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: Dedicated lacks Support chat-sharing and password/profile editing in Langdock; other feature controls depend on deployment configuration. No exhaustive parity list was found. Sources: langdock:langdock:account, langdock:langdock:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:account, langdock:langdock:chat ### DATA-03: Training use and provider retention Judgment rule: Record whether customer content trains vendor or provider models, by plan and default; zero-data-retention arrangements with model providers; abuse-monitoring retention and human review; and the model provider's terms that apply. A "no training" claim on a marketing page is `vendor-claimed` until the contract or DPA says so. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: supported Microsoft Azure model routes use the contract-described no-training and Modified Abuse Monitoring configuration. Other providers are outside this finding. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business/Enterprise managed Microsoft Azure model routes only; BYOK and Fable/other-provider routes excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default; explicitly selected global Azure models may infer outside EU; os=not specified. Limitations: - Fable5/5.1 and direct/OpenAI image/file exceptions are outside this Azure-only scope; no platform-wide ZDR claim is made. - vendor_training — Does the vendor train on customer content? [supported]: Terms section9 prohibits Langdock use of customer data for model development, training or improvement. Sources: langdock:langdock:terms-rev2. - provider_training — Do model providers train on it under this product's contracts? [supported]: Appendix1 Microsoft Azure obligations exclude sharing customer prompts/files/embeddings with model developers and using them to train or improve models. Sources: langdock:langdock:terms-rev2. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [supported]: For the scoped Microsoft Azure model route, Langdock states Modified Abuse Monitoring disables provider storage of prompts/outputs for abuse monitoring. Platform conversation storage is separate. Sources: langdock:langdock:terms-rev2. - zero_retention — Is zero data retention available, and on which plan? [supported]: The Azure route has the Modified Abuse Monitoring zero-retention configuration described in Appendix1. This does not establish ZDR for arbitrary customer keys or other providers. Sources: langdock:langdock:terms-rev2. - human_review — Can provider staff review content? [supported]: Appendix1 states Azure human abuse review of the scoped prompts/outputs is disabled by Modified Abuse Monitoring. Sources: langdock:langdock:terms-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms-rev2 ### DATA-04: Retention and deletion Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins control chat retention; file cleanup depends on all remaining references. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - default_retention: No universal default duration is specified. File retention depends on recent files, chats, agents, folders or knowledge links; workflow pricing lists 30-day run retention. - user_deletion: Deleted chats become unavailable immediately; files belonging only to them are deleted at overnight cleanup. Files linked elsewhere remain; deleting a folder alone retains its files. - default_retention — What is retained and for how long by default? [partial]: No universal default duration is specified. File retention depends on recent files, chats, agents, folders or knowledge links; workflow pricing lists 30-day run retention. Sources: langdock:langdock:retention, langdock:langdock:pricing. - admin_retention — Can admins set retention periods? [supported]: Chat inactivity retention options are seven days, one/three/twelve months or forever, with daily irreversible deletion. Sources: langdock:langdock:workspace. - user_deletion — Can users delete their chats and files permanently? [partial]: Deleted chats become unavailable immediately; files belonging only to them are deleted at overnight cleanup. Files linked elsewhere remain; deleting a folder alone retains its files. Sources: langdock:langdock:retention. - contract_end_deletion — What is deleted at contract end, and when? [supported]: DPA section 11 requires deletion within 30 days of termination subject to legal retention, confirmation on request and export access until deletion. Sources: langdock:langdock:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:retention, langdock:langdock:pricing, langdock:langdock:workspace, langdock:langdock:dpa ### DATA-05: Sub-processors and foreign-law exposure Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA publishes seven default subprocessors and conditional Global routes with transfer mechanisms. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - parent_jurisdiction: Langdock GmbH, Berlin, Germany is contracting entity. Parent-company ownership was not fully established. - government_access_policy: Confidentiality clause requires minimizing legally compelled disclosure and notifying where legally permitted; no separate request statistics/transparency report was found. - subprocessor_list — Is a dated sub-processor list published? [supported]: DPA 2.1 Appendix 2 embeds the current named list; trust-centre subprocessor page needs client rendering and did not return text. Sources: langdock:langdock:dpa. - subprocessor_countries — Which countries do sub-processors operate in? [supported]: Default entities: Microsoft Ireland, AWS EMEA Luxembourg, Google Cloud EMEA Ireland, OpenAI Ireland, Mistral France, Sentry US and Cloudflare US; default processing column is EU. Global opt-ins include worldwide/US inference and Azure EU storage. Sources: langdock:langdock:dpa. - change_notification — Are customers notified of sub-processor changes? [supported]: At least 14 days before new/replaced subprocessor via public register and email only if subscribed; objection within 14 days of publication. Sources: langdock:langdock:dpa. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: Langdock GmbH, Berlin, Germany is contracting entity. Parent-company ownership was not fully established. Sources: langdock:langdock:terms. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA lists EU-US/Swiss-US DPF, UK extension and EU/UK SCCs with Swiss addenda per provider; Global OpenAI lists EU/UK SCCs. Sources: langdock:langdock:dpa. - government_access_policy — Is there a published government-access or transparency policy? [partial]: Confidentiality clause requires minimizing legally compelled disclosure and notifying where legally permitted; no separate request statistics/transparency report was found. Sources: langdock:langdock:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:dpa, langdock:langdock:terms ### DATA-06: Contracts and regulatory coverage Judgment rule: Record DPA availability and form (click-through, negotiable), reference to Swiss revDSG and GDPR, governing law and court, EU AI Act documentation (provider or deployer role, transparency materials), and sector-specific materials (FINMA outsourcing, banking secrecy, public sector). No compliance verdict. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA automatically forms part of German-law terms; Swiss and sector materials need qualification. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - dpa: Terms section 16 automatically incorporates public DPA 2.1; nonstandard instructions require written amendment, and negotiability is not promised. - revdsg_gdpr: GDPR Article 28 governs; provider transfer table includes Swiss safeguards but a complete revDSG scope/addendum was not established. - ai_act_materials: Governance templates include EU AI Act/GDPR/security checks of agent definitions; these do not establish a complete product provider/deployer dossier. - sector_materials: Legal-links page advertises a Professional Secrecy Addendum in Trust Center; no FINMA package was obtained. - dpa — Is a DPA available, and is it negotiable? [partial]: Terms section 16 automatically incorporates public DPA 2.1; nonstandard instructions require written amendment, and negotiability is not promised. Sources: langdock:langdock:terms, langdock:langdock:dpa. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: GDPR Article 28 governs; provider transfer table includes Swiss safeguards but a complete revDSG scope/addendum was not established. Sources: langdock:langdock:dpa. - governing_law — Which law and court govern the contract? [supported]: German law, Berlin exclusive jurisdiction; German language version binds over English translation. Sources: langdock:langdock:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Governance templates include EU AI Act/GDPR/security checks of agent definitions; these do not establish a complete product provider/deployer dossier. Sources: langdock:langdock:pricing, langdock:langdock:gov. - sector_materials — Are FINMA or other sector materials provided? [partial]: Legal-links page advertises a Professional Secrecy Addendum in Trust Center; no FINMA package was obtained. Sources: langdock:langdock:legal. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:dpa, langdock:langdock:pricing, langdock:langdock:gov, langdock:langdock:legal ### DATA-07: Certifications and attestations Judgment rule: Record each certificate or report separately: ISO 27001, 27017, 27018, 27701, 42001; SOC 2 Type I/II with period; BSI C5; TISAX; national schemes. Record issuer, scope (which product and entity), validity and access route. A cloud provider's certificate does not certify the product. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial ISO 27001 and SOC 2 Type II are vendor claims pending certificate/report verification. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - iso_27001: Security page claims Langdock ISO 27001; issuer, exact scope and validity were not retrieved. - soc2: Security page claims SOC 2 Type II; report period/auditor/service scope was not retrieved. - report_access: Public legal-links page sends certificate/report requests to the Trust Center, which rendered no text in this access method. - pentest: Vendor describes frequent independent penetration testing; no test report or bounded result was retrieved. - Unverified c5, other_certifications: No C5, other product certificate, issuer-register verification or gated report was established. - iso_27001 — ISO 27001 with scope and validity? [partial]: Security page claims Langdock ISO 27001; issuer, exact scope and validity were not retrieved. Sources: langdock:langdock:security. - soc2 — SOC 2 type, period and covered service? [partial]: Security page claims SOC 2 Type II; report period/auditor/service scope was not retrieved. Sources: langdock:langdock:security. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No C5, other product certificate, issuer-register verification or gated report was established. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. No C5, other product certificate, issuer-register verification or gated report was established. - report_access — How can customers obtain reports? [partial]: Public legal-links page sends certificate/report requests to the Trust Center, which rendered no text in this access method. Sources: langdock:langdock:legal. - pentest — Are independent penetration test summaries available? [partial]: Vendor describes frequent independent penetration testing; no test report or bounded result was retrieved. Sources: langdock:langdock:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:legal ### DATA-08: Encryption and key control Judgment rule: Record encryption at rest and in transit, customer-managed keys (BYOK/HYOK), key location, and private networking (private link, IP allow-lists, VPN). #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Encryption and network restrictions are documented; customer key custody is not established. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - private_networking: CIDR IP allowlists block workspace login/use from unapproved networks; private-link endpoint availability was not established. - Unverified customer_managed_keys, tenant_isolation: Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept. - encryption_at_rest — Is data encrypted at rest? [supported]: Vendor states AES-256 storage and TLS 1.2+ transport. Sources: langdock:langdock:security. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept. - private_networking — Is private connectivity or IP restriction available? [partial]: CIDR IP allowlists block workspace login/use from unapproved networks; private-link endpoint availability was not established. Sources: langdock:langdock:ip. - tenant_isolation — How are customers separated in shared SaaS? [unknown]: How are customers separated in shared SaaS? Unknown. Customer-managed encryption keys and exact shared-SaaS tenant isolation implementation were not established; LLM BYOK is a separate concept. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:security, langdock:langdock:ip ### DATA-09: Professional secrecy Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment. #### 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 #### Langdock Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## Commercials and vendor ### VEN-01: Pricing model and list prices Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business uses seats with included managed-chat usage; workflow/API and other add-ons are separate. An applicable Standard/BYOK licence tariff is not established. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents and optional modules; Enterprise quoted at1000+; applicable Standard/BYOK tariff unknown; add_ons=Workflows, Governance, API/Extra Usage; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Inconsistent price representations are retained as a named price gap, not combined into a synthetic tariff. - pricing_unit — What is the pricing unit? [supported]: Seat/month platform, per-workspace workflow packages, metered API/workflow AI/extra usage, optional per-seat Governance. Sources: langdock:langdock:pricing-rev2. - list_prices — What are list prices per plan, with date and currency? [unknown]: Unknown applicable Standard/BYOK seat tariff. The public Business headline is EUR25 while the annual price breakdown starts at EUR23.20; billing docs refer to the same pricing page without reconciling them. Enterprise1000+ is quote-only. Prior hashed-calculator rates are excluded. - included_usage — What usage is included? [partial]: Standard includes managed chat/agent usage under five-hour and weekly windows; Max has 5x. Precise numerical included cost budgets are not public. Starter includes 2500 workflow runs/month but no workflow model tokens. Sources: langdock:langdock:pricing-rev2, langdock:langdock:limits. - add_ons — Which features cost extra? [partial]: Workflow Starter includes2500runs/month with AI tokens billed separately. The public add-on page lists40k/100k packages and Governance free until2027-01-01, then separately priced per base-plan seat. The applicable binding package/billing-period amounts are not established here. Sources: langdock:langdock:pricing-rev2. - overage — What do usage beyond limits and premium models cost? [supported]: Extra usage is charged at API rates. Model page lists GPT-5 Mini EUR 0.22 input/1.78 output per million; workflow and API spend use separate caps. Sources: langdock:langdock:extra, langdock:langdock:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing-rev2, langdock:langdock:limits, langdock:langdock:extra, langdock:langdock:models ### VEN-02: Scenario cost Judgment rule: Price three workloads for 12 months: 200, 1,000 and 5,000 users with a disclosed light/regular/power usage mix, in CHF and EUR excluding VAT. Include licences, platform fees, add-ons, model usage and, for self-hosted options, a stated operating assumption. Separate fixed, variable, included and unknown costs. No invented discounts. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial All requested200/1000/5000-user totals are unknown because an applicable Business Standard tariff or Enterprise quote is not verified. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Standard up to1000 users; Enterprise1000+; all applicable scenario licence totals unknown; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21:12months, list prices, excluding VAT;60/30/10 users at100/400/1500messages monthly,3000input+600output tokens/message. Only separately billed usage uses this token mix. - ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Unknown base/variable components prevent totals; no silent conversion. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for200users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for1000users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown total for5000users over12months excluding VAT. No applicable Business Standard tariff is established from the conflicting headline/breakdown; Enterprise at1000+ is quote-only. No calculator-derived base floor or inferred discount is retained. Included managed-chat use is not separately billed by the token mix. - variable_share — Which part depends on usage? [partial]: Managed Business chat includes model usage subject to usage limits. ExtraUsage,workflow/API,Governance and customer-provider BYOK bills are separate. Missing applicable tariff/allowance components remain unknown; no proxy substitutes for vendor-billed usage. Sources: langdock:langdock:billing, langdock:langdock:extra. - unknown_parts — Which costs could not be priced? [partial]: Business Standard/BYOK applicable seat rate, Enterprise licence/deployment quote, workload-preserving overage and required modules/services are unknown. This prevents a verifiable EUR/CHF total. Sources: langdock:langdock:pricing-rev2, langdock:langdock:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing-rev2, langdock:langdock:billing, langdock:langdock:extra, langdock:langdock:ecb-fx ### VEN-03: Evaluation access Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial A seven-day self-serve business trial is advertised without a card. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - free_tier: Terms describe a time-limited trial that ends automatically; permanent business free access is not established. - trial_scope: Pricing says test all platform features, but enterprise deployments and optional enablement cannot be inferred; SAML/SCIM trial configuration was not run. - sales_gate: Base trial is self-serve; enterprise deployment and custom terms require an offer. - free_tier — Is there a free tier for business use? [partial]: Terms describe a time-limited trial that ends automatically; permanent business free access is not established. Sources: langdock:langdock:terms. - self_serve_trial — Is a self-serve business trial available? [supported]: Seven days, no card, EUR 5 model credit and team invitations. Sources: langdock:langdock:pricing. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Pricing says test all platform features, but enterprise deployments and optional enablement cannot be inferred; SAML/SCIM trial configuration was not run. Sources: langdock:langdock:pricing. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Base trial is self-serve; enterprise deployment and custom terms require an offer. Sources: langdock:langdock:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms, langdock:langdock:pricing, langdock:langdock:billing ### VEN-04: Contract terms and pricing transparency Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Monthly/annual contract defaults and EUR invoices are public; some pricing representations conflict. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - minimum_commitment: Calculator starts at one user and Business supports up to1000; Enterprise/deployment minimums differ. - local_invoicing: Langdock GmbH invoices EUR excl tax; contract specifies market-rate conversion of provider foreign-currency charges. CHF invoices were not established. - transparency_class: Partially specified public rates and usage rules; Enterprise quote-only and headline/calculator rates differ. - minimum_commitment — What seat or spend minimum applies? [partial]: Calculator starts at one user and Business supports up to1000; Enterprise/deployment minimums differ. Sources: langdock:langdock:pricing, langdock:langdock:security. - contract_length — What contract lengths are offered? [supported]: Monthly or annual; annual offers 20% reduction on Standard tiers. Sources: langdock:langdock:billing. - cancellation — How can the contract be cancelled or reduced? [supported]: Terms specify seven-day notice before monthly end, fourteen days before annual/multiyear end; automatic monthly/12-month renewals; notices by text/email or platform. Sources: langdock:langdock:terms. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Langdock GmbH invoices EUR excl tax; contract specifies market-rate conversion of provider foreign-currency charges. CHF invoices were not established. Sources: langdock:langdock:terms. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified public rates and usage rules; Enterprise quote-only and headline/calculator rates differ. Sources: langdock:langdock:pricing, langdock:langdock:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:pricing, langdock:langdock:security, langdock:langdock:billing, langdock:langdock:terms ### VEN-05: Source licence Judgment rule: Record licence per component (client, server, connectors, hosted extensions) and revision. Distinguish OSI open source, source-available with restrictions (branding clauses, user caps), and closed. Repository visibility is not a licence classification. Licences change between releases: record the current terms, and never carry a fork's historical licence over to the upstream product or the reverse. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Commercial platform rights are proprietary and time-limited. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - licence_type: Terms grant a nonexclusive/nontransferable contract-term right, not an OSI source licence. Component-level connector/client licences are not enumerated. - branding_restrictions: Terms prohibit removing proprietary notices and reselling platform access; admin branding options do not transfer platform IP. - Unverified enterprise_features_closed: A public component-by-component source licence/current revision and distinct open/closed enterprise edition mapping were not established. - licence_type — Which licence applies to each component? [partial]: Terms grant a nonexclusive/nontransferable contract-term right, not an OSI source licence. Component-level connector/client licences are not enumerated. Sources: langdock:langdock:terms. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Terms prohibit removing proprietary notices and reselling platform access; admin branding options do not transfer platform IP. Sources: langdock:langdock:terms. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. A public component-by-component source licence/current revision and distinct open/closed enterprise edition mapping were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:terms ### VEN-06: Data export and exit Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise dedicated resource/configuration and conversation-content APIs document exports. A complete source/index/ACL workspace exit bundle has not been established. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace, Langdock public APIs and agent MCP server; version=Public documentation checked 2026-10-26; plan=Enterprise dedicated deployment: administrative and resource APIs plus separately enabled Compliance API; Business Cloud outside this finding; add_ons=Dedicated Enterprise deployment and relevant API scopes; Compliance API deployment enablement; deployment_mode=dedicated-instance; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - Configuration/file APIs are separate from conversation export. Dedicated Compliance API availability does not establish a Business Cloud entitlement. - chat_export — Can admins export all chats? [partial]: The dedicated-deployment Compliance API documents paginated conversation/message exports. include_message_content=true adds messages; both it and include_action_results=true add tool arguments and outputs. A scoped key is required. Cloud workspaces need separate enablement and no Business Cloud entitlement is inferred. Sources: langdock:langdock:compliance-rev2-20261026. - assistant_export — Can assistants and prompts be exported in a reusable format? [partial]: Agent API Get/Create migration exports configuration; attachments/skills must be handled separately and some fields/ownership do not transfer. Sources: langdock:langdock:migration. - knowledge_export — Can knowledge bases and their sources be exported? [partial]: Knowledge Folder API can retrieve/list files; a complete original-source/index/ACL export bundle was not demonstrated. Sources: langdock:langdock:knowledge, langdock:langdock:knowledge-20261026. - export_format — Are formats documented and machine-readable? [partial]: Agent and Compliance API JSON plus usage CSV/JSON are documented; this is not a one-click complete workspace export. Sources: langdock:langdock:compliance-rev2, langdock:langdock:migration, langdock:langdock:exports, langdock:langdock:exports-20261026. - post_termination_window — How long can data be retrieved after termination? [supported]: DPA permits exports during contract and until deletion, which occurs no later than30 days after termination subject to legal retention. Sources: langdock:langdock:dpa. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:compliance-rev2, langdock:langdock:migration, langdock:langdock:knowledge, langdock:langdock:exports, langdock:langdock:dpa, langdock:langdock:compliance-rev2-20261026, langdock:langdock:migration-20261026, langdock:langdock:knowledge-20261026, langdock:langdock:exports-20261026, langdock:langdock:dpa-20261026 ### VEN-07: Support and service levels Judgment rule: Record support channels, languages (German, French, Italian), hours and time zone, local or regional presence, documented response times, uptime SLA and credits, public status page and incident history. Popularity is not a reliability score. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Berlin vendor support, public status history and a 99% monthly availability term are documented. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - support_channels: Support email is documented; Enterprise has custom account management/support, and rollout programmes have shared Teams/Slack channels. - uptime_sla: Terms promise at least99% monthly availability with defined exclusions and up to5h scheduled maintenance/month. Statutory remedy/credit procedure exists, but no fixed percentage-credit schedule is published. - Unverified support_languages: Contractual DE/FR/IT support languages, full hours/timezone and dedicated response/credit schedules were not established. - support_channels — Which support channels are available on each plan? [partial]: Support email is documented; Enterprise has custom account management/support, and rollout programmes have shared Teams/Slack channels. Sources: langdock:langdock:billing, langdock:langdock:playbook. - support_languages — Is support available in German, French or Italian? [partial]: The imprint says users and authorities can contact support@langdock.com in German and English. It does not specify contractual French or Italian support, hours or response times. Sources: langdock:langdock:imprint-20261026. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: Langdock GmbH contracts from Berlin, Germany. Sources: langdock:langdock:terms. - uptime_sla — Is there an uptime SLA with credits? [partial]: Terms promise at least99% monthly availability with defined exclusions and up to5h scheduled maintenance/month. Statutory remedy/credit procedure exists, but no fixed percentage-credit schedule is published. Sources: langdock:langdock:terms. - status_page — Is there a public status page with history? [supported]: Public status separates app/API/Workflow/Integration history. Sources: langdock:langdock:status. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: langdock:langdock:billing, langdock:langdock:playbook, langdock:langdock:terms, langdock:langdock:status, langdock:langdock:imprint-20261026, langdock:langdock:terms-20261026, langdock:langdock:status-20261026 ### VEN-08: Onboarding, training and adoption Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings. #### 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 #### Langdock Verification status: Agent cross-checked (agent-cross-checked) Support: partial Rollout support starts at 250 licences; public learning material and champion guidance are available. Availability: generally-available Delivery: native Scope: surfaces=Langdock hosted workspace; version=Public documentation checked 2026-10-21; plan=Business Chat & Agents; included models unless BYOK or Enterprise is explicitly named; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Azure EU default, with admin-enabled global model exceptions; os=not specified. Limitations: - onboarding_service: Dedicated rollout/workshops/shared channels are available from250 seats; exact included versus chargeable services depends on contract. - user_training: Public workshops have recordings/slides; the complete delivery-language and included-live-training matrix is not specified. - service_cost: Enterprise custom onboarding/support is quote-based; public per-workshop fees were not found. - onboarding_service — Is guided onboarding included? [partial]: Dedicated rollout/workshops/shared channels are available from250 seats; exact included versus chargeable services depends on contract. Sources: langdock:langdock:playbook. - user_training — Is end-user training offered, in which languages? [partial]: Public workshops have recordings/slides; the complete delivery-language and included-live-training matrix is not specified. Sources: langdock:langdock:training. - use_case_library — Are role-based use cases and templates provided? [supported]: Playbook recommends role-specific prompts/agents and gives structured use-case discovery material. Sources: langdock:langdock:playbook. - adoption_programme — Is there a champion or adoption programme? [supported]: Playbook includes department champions, follow-ups, hackathons and AI challenges. Sources: langdock:langdock:playbook. - service_cost — Which services cost extra? [partial]: Enterprise custom onboarding/support is quote-based; public per-workshop fees were not found. Sources: langdock:langdock:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: langdock:langdock:playbook, langdock:langdock:training, langdock:langdock:billing ## Sources ### 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 ### langdock:langdock:models AI Models | Langdock. Public model table lists current text models and EUR metered prices. - URL: https://langdock.com/models - Locator: Provider tables - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:model-guide Model Guide. Users select models or Auto routing; reasoning levels vary by model. - URL: https://docs.langdock.com/en/using-langdock/models-and-limits/models.md - Locator: Selecting a Model, Auto and Thinking - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:changes Product Changelog | Langdock. Dated releases document model additions, desktop apps and per-agent confirmations. - URL: https://langdock.com/changelog - Locator: 13 October 2026 model release; 15/10 September feature releases - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:billing https://docs.langdock.com/en/admin/billing/pricing.md. Business covers up to 1000 users, BYOK separates model costs, workflows/API are metered and Enterprise is quoted. - URL: https://docs.langdock.com/en/admin/billing/pricing.md - Locator: Products, volume tiers, Enterprise and API - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:byok https://docs.langdock.com/en/admin/byok/byok.md. BYOK replaces completion, embedding and image routes; missing model categories break relevant features. - URL: https://docs.langdock.com/en/admin/byok/byok.md - Locator: Options, requirements, setup and usage export - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:byok-routes Setup Guides. Named BYOK routes include cloud providers, Vercel Gateway and self-hosted OpenAI-compatible HTTPS endpoints. - URL: https://docs.langdock.com/en/admin/byok/setup-guides.md - Locator: Provider setup tabs and OpenAI-compatible endpoints - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:research Deep Research. Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/deep-research.md - Locator: Model configuration, limitations and usage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:terms Terms of Use | Langdock. Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults. - URL: https://langdock.com/terms - Locator: Sections 6/7/9/12/15/16/19 and Appendix 1 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:byok-models How to add your own models. Admins configure completion, image and embedding models, deployments, capability flags and USD accounting rates. - URL: https://docs.langdock.com/en/admin/byok/adding-models.md - Locator: Custom model setup and deployment configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:pricing Pricing Plans | Langdock. Business headline prices, annual discounts, workflow packages and Governance promotion are public. - URL: https://langdock.com/pricing - Locator: Chat & Agents, price breakdown, add-ons and API - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:workspace Workspace Settings. Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls. - URL: https://docs.langdock.com/en/admin/workspace/workspace.md - Locator: Product Settings, Models, Analytics and Customizations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:limits Usage Limits. Five-hour and weekly usage windows trigger extra usage or a fallback; spam protection caps 250 messages per three hours. - URL: https://docs.langdock.com/en/using-langdock/models-and-limits/fair-usage-policy.md - Locator: Usage windows and exhaustion - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:extra Extra Usage. Extra usage has workspace/plan/user caps and fallback behavior with possible final-response overshoot. - URL: https://docs.langdock.com/en/admin/manage-usage/extra-usage.md - Locator: Enabling extra usage, spend limits and API exceptions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:files Which file types does Langdock support?. Supported files have different type-specific size limits and processing restrictions. - URL: https://docs.langdock.com/en/using-langdock/troubleshooting/faq/supported-file-types.md - Locator: Format/size tables and processing limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:file-count What are the file limits in the chat and in agents?. Web message uploads allow 50 files, mobile five; agent knowledge and knowledge bases have separate limits. - URL: https://docs.langdock.com/en/using-langdock/troubleshooting/faq/file-limit.md - Locator: Chat and agent attachment limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:retrieval Knowledge Basics. Direct file previews differ from semantic search over 2000-character chunks, returning up to 50 passages. - URL: https://docs.langdock.com/en/using-langdock/guides/knowledge/knowledge-basics.md - Locator: Direct context and embedding search - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:knowledge Knowledge bases. Persistent shareable knowledge bases accept up to 1000 text documents, search chunks and attach to agents. - URL: https://docs.langdock.com/en/using-langdock/library/knowledge-bases.md - Locator: Creation, sharing, limits and agent use - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:agents Agent Configuration. Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions. - URL: https://docs.langdock.com/en/using-langdock/agents/configuration.md - Locator: Agent configuration, knowledge and source restriction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:sync Folder Sync. Daily folder sync supports SharePoint, OneDrive, Drive and Confluence, with real-time user access checks. - URL: https://docs.langdock.com/en/using-langdock/guides/integrations/folder-sync.md - Locator: Setup, permission checks, sync behavior and owner removal - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:integrations Integration Directory. The native directory lists Microsoft, Google, Atlassian, CRM, BI, vector search, DeepL and audio integrations. - URL: https://docs.langdock.com/en/using-langdock/integrations/integration-directory.md - Locator: Native integration directory - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:mcp Model Context Protocol (MCP). MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default. - URL: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/mcp.md - Locator: Transports, authentication and tool confirmation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:labels Sensitivity Label Policy. A request-enabled Purview label policy filters supported integrations, with documented actions and upload exceptions. - URL: https://docs.langdock.com/en/admin/manage-integrations/sensitivity-label-policy.md - Locator: Availability, enforcement, exceptions and unsupported areas - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:actions Manage Action Access. Admins share integrations and actions with users/groups/API keys; native core actions cannot be disabled. - URL: https://docs.langdock.com/en/admin/manage-integrations/manage-action-access.md - Locator: Access settings and native-action exception - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### 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 ### langdock:langdock:chat Basic Chat functionalities. Chat supports model selection and governed tools; memory, deep research and agent tool conditions differ. - URL: https://docs.langdock.com/en/using-langdock/chat/functionalities.md - Locator: Model selector and tool availability - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:account Account Settings. Account settings include five UI languages, personal controls and temporary 72-hour Support sharing. - URL: https://docs.langdock.com/en/using-langdock/account/account.md - Locator: Preferences, shared chats, custom instructions and memory - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:memory Memory. Memory works in regular chats only, with a 50-memory cap and view/edit/delete controls. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/memory.md - Locator: Availability, management and limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:roles Roles and extra permissions. System roles, up to five custom roles and delegated group permissions are configurable. - URL: https://docs.langdock.com/en/admin/workspace/roles.md - Locator: System roles, custom roles and group permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:web Web Search. Web search returns inspectable citations and has a separate open-URL tool. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/web-search.md - Locator: Search behavior and source inspection - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:workflows Introduction to Workflows. Workflows chain agents, integrations and logic with form, schedule and event triggers after admin activation. - URL: https://docs.langdock.com/en/using-langdock/workflows/introduction.md - Locator: Introduction and activation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:hitl Human in the Loop. Workflow runs can pause for editor approval or per-action confirmation. - URL: https://docs.langdock.com/en/using-langdock/workflows/fundamentals/human-in-the-loop.md - Locator: Approval and action confirmation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:excel Excel Add-in. The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites. - URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/excel.md - Locator: Install, workbook operations and edit permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:outlook-rev2 Outlook Add-in. The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action. - URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/outlook.md - Locator: Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:outlook-marketplace Langdock for Outlook, by Langdock GmbH. Vendor listing offers the add-in to every paid Langdock plan and trials, with draft review before sending. - URL: https://marketplace.microsoft.com/en-us/product/WA200011534?tab=Overview - Locator: Overview and eligibility sentence - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:outlook-rev2-20261026 Outlook Add-in. The Outlook add-in requires workspace-admin access and Exchange Online; edits ask by default and sending requires an explicit requested and confirmed action. - URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/outlook.md - Locator: Installation and Exchange Online prerequisites; edit permissions; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:pricing-20261026 Pricing Plans | Langdock. Business headline prices, annual discounts, workflow packages and Governance promotion are public. - URL: https://langdock.com/pricing - Locator: Chat & Agents, price breakdown, add-ons and API - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:changes-20261026 Product Changelog | Langdock. Dated releases document model additions, desktop apps and per-agent confirmations. - URL: https://langdock.com/changelog - Locator: 13 October 2026 model release; 15/10 September feature releases - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:outlook-admin-20261026 Outlook Add-in setup. Admins set Outlook add-in access to Nobody, Everyone or Specific members and groups; Outlook Email and Calendar integrations have separate access/scopes. - URL: https://docs.langdock.com/en/admin/manage-integrations/add-in-setup-guides/outlook.md - Locator: Availability and access settings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:agents-20261026 Agent Configuration. Agents combine instructions, files, folders, models, actions, skills and subagents, with optional source-access restrictions. - URL: https://docs.langdock.com/en/using-langdock/agents/configuration.md - Locator: Agent configuration, knowledge and source restriction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:research-20261026 Deep Research. Deep Research creates cited public-web reports and has a 15-per-30-days cap for standard keys. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/deep-research.md - Locator: Model configuration, limitations and usage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:hitl-20261026 Human in the Loop. Workflow runs can pause for editor approval or per-action confirmation. - URL: https://docs.langdock.com/en/using-langdock/workflows/fundamentals/human-in-the-loop.md - Locator: Approval and action confirmation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:mcp-20261026 Model Context Protocol (MCP). MCP clients support Streamable HTTP/SSE and several authentication types; new tools do not require confirmation by default. - URL: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/mcp.md - Locator: Transports, authentication and tool confirmation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:excel-20261026 Excel Add-in. The Excel add-in reads and writes workbooks with default edit confirmation and named version prerequisites. - URL: https://docs.langdock.com/en/using-langdock/microsoft-add-ins/excel.md - Locator: Install, workbook operations and edit permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### 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 ### langdock:langdock:mcp-server Langdock Agent MCP Server. A public MCP endpoint exposes workspace agents under Agent API scope. - URL: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/langdock-agent-mcp-server.md - Locator: Endpoint, authentication and tools - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:desktop-rev2 Enterprise Guide for Langdock Desktop. Managed desktop rollout supports machine-wide Windows packages and signed/notarized macOS installers; these installation instructions do not change subscription entitlements. - URL: https://docs.langdock.com/en/admin/desktop-app/deploy.md - Locator: Windows machine-wide MSIX/Intune; macOS PKG/DMG/Jamf/Kandji; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:mobile-rev2 Mobile App. HTTP200 Markdown introduction links official Apple App Store and Google Play mobile clients. - URL: https://docs.langdock.com/en/using-langdock/mobile-app/introduction.md - Locator: Download routes - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:desktop-product Langdock Desktop. Windows/macOS desktop clients use the same workspace and approved models as web. - URL: https://langdock.com/products/desktop - Locator: Downloads and Q&A - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:mobile-product Langdock Mobile. Vendor mobile page offers iOS/Android clients using the workspace-approved models. - URL: https://langdock.com/mobile - Locator: App Store/Google Play links and Q&A - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:teams How to use the Teams Bot. Teams has personal bot chats and channel threads with team participation. - URL: https://docs.langdock.com/en/using-langdock/guides/chatbots/teams-bot.md - Locator: Private chats, channels and admin install - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:teams-20261026 How to use the Teams Bot. The public Markdown guide was retrieved with HTTP 200. A workspace admin installs the Teams app, which supports private bot chat and channel threads using @Langdock; it is separate from the web chat history. - URL: https://docs.langdock.com/en/using-langdock/guides/chatbots/teams-bot.md - Locator: Installation note; Two Ways to Use the Teams Bot; Private Chat; Using Langdock in Channels; Limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:editor Document Editor. Document Editor replaces Canvas and exports Markdown, Word and PDF; imported Word/PDF cannot be edited directly there. - URL: https://docs.langdock.com/en/using-langdock/chat/document-editor.md - Locator: Editor, AI edits, export and limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:images Image Generation. Chat invokes configured image-generation models with a user model selector. - URL: https://docs.langdock.com/en/using-langdock/chat/tools/image-generation.md - Locator: Generating images and model choice - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:analysis Using Langdock for Data Analysis. Tabular analysis produces charts and downloadable spreadsheet and document formats. - URL: https://docs.langdock.com/en/using-langdock/guides/data-analysis.md - Locator: Analysis procedure and outputs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:projects Projects. Shared projects expose all project chats/files to members and can be shared with users/groups, not the whole workspace. - URL: https://docs.langdock.com/en/using-langdock/chat/projects.md - Locator: Project sharing and permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:saml https://docs.langdock.com/en/admin/security/saml/saml.md. SAML 2.0 requires a verified domain; MFA comes from the IdP rather than standalone Langdock MFA. - URL: https://docs.langdock.com/en/admin/security/saml/saml.md - Locator: Checklist, supported IdPs, external authentication and MFA - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:scim https://docs.langdock.com/en/admin/security/scim/scim.md. SCIM 2.0 supports Entra provisioning after SAML setup and domain verification. - URL: https://docs.langdock.com/en/admin/security/scim/scim.md - Locator: Overview and prerequisites - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:scim-entra https://docs.langdock.com/en/admin/security/scim/entra.md. Entra target actions control provisioning/deactivation and group synchronization. - URL: https://docs.langdock.com/en/admin/security/scim/entra.md - Locator: Target Object Actions and optional group synchronization - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:leaver Unassign Agents. Agents whose owner is deactivated keep functioning but cannot be edited until reassigned. - URL: https://docs.langdock.com/en/admin/manage-agents/unassign-agents.md - Locator: Unassigned agents and reassignment - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:exports Usage Exports. Usage CSV exports span users, agents, keys, projects, models and workflows, with user-detail privacy controls. - URL: https://docs.langdock.com/en/admin/compliance-and-governance/usage-exports.md - Locator: Export data types, limits and user-level data - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:byok-limits Usage and spend limits. BYOK cost limits depend on configured prices and exclude backbone, workflows and workspace API usage. - URL: https://docs.langdock.com/en/admin/manage-usage/byok/usage-limits.md - Locator: Scope, unpriced models and spend limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:workflow-limits Workflow limits. Workflow AI use has a separate workspace EUR limit and per-workflow USD limits that block new runs. - URL: https://docs.langdock.com/en/admin/manage-workflows/spend-limits.md - Locator: Spend limits and execution step cap - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:audit Audit Logs API Overview. Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion. - URL: https://docs.langdock.com/en/developer/audit-logs-api/intro-to-audit-logs-api.md - Locator: Event schema, retention and prerequisites - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:compliance-rev2 Export tool parameters and outputs. Cloud Compliance API is workspace-enable­ment gated; dedicated deployments serve it unless disabled. Conversation exports include messages and tool inputs/outputs only with both explicit flags. - URL: https://docs.langdock.com/en/developer/compliance-api/export-tool-results.md - Locator: Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:compliance-rev2-20261026 Export tool parameters and outputs. Cloud Compliance API is workspace-enable­ment gated; dedicated deployments serve it unless disabled. Conversation exports include messages and tool inputs/outputs only with both explicit flags. - URL: https://docs.langdock.com/en/developer/compliance-api/export-tool-results.md - Locator: Before You Start, parameters and conversation endpoints; HTTP200 Markdown re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:audit-20261026 Audit Logs API Overview. Audit events retain 90 days and are retrievable by a dedicated-scope admin API for SIEM ingestion. - URL: https://docs.langdock.com/en/developer/audit-logs-api/intro-to-audit-logs-api.md - Locator: Event schema, retention and prerequisites - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:workspace-20261026 Workspace Settings. Workspace settings define retention, model defaults, EU-only default enablement, analytics and product controls. - URL: https://docs.langdock.com/en/admin/workspace/workspace.md - Locator: Product Settings, Models, Analytics and Customizations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:gov Compliance Rules. Custom agent compliance checks produce pass/fail and severity results with per-rule analytics. - URL: https://docs.langdock.com/en/admin/governance/compliance-rules.md - Locator: Rule operation, failures and analytics - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:security security. Default Azure EU SaaS, managed dedicated from 2000 and customer-cloud/on-premise from 5000 seats are advertised. - URL: https://langdock.com/security - Locator: Deployment, security, BYOK and certifications - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:dpa Data Processing Agreement | Langdock. DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table. - URL: https://langdock.com/dpa - Locator: Sections 7-12 and Appendices 1/2 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:terms-rev2 Terms of Use | Langdock. Microsoft Azure routes use Modified Abuse Monitoring, disabling provider prompt/output retention and human abuse review. Other provider/model routes require separate assessment. - URL: https://langdock.com/terms - Locator: Section9 and Appendix1 Microsoft Azure service terms - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:retention How long are files saved in Langdock?. Deleted chats are immediately unavailable and unreferenced files are cleaned overnight; shared file references survive. - URL: https://docs.langdock.com/en/using-langdock/troubleshooting/faq/data-retention-for-files.md - Locator: Retention by object type - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:legal https://docs.langdock.com/en/admin/compliance-and-governance/legal-compliance.md. DPA applies automatically and a Professional Secrecy Addendum and certificates are linked from the Trust Center. - URL: https://docs.langdock.com/en/admin/compliance-and-governance/legal-compliance.md - Locator: Legal and compliance links - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:ip IP Restrictions. CIDR allowlists immediately block unauthorized network access when enabled. - URL: https://docs.langdock.com/en/admin/security/ip-restrictions.md - Locator: Prerequisites and enforcement - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:pricing-rev2 Pricing Plans | Langdock. The page maps Business to up to1000 users and Enterprise to1000+; the Standard headline and breakdown disagree, so no applicable Standard/BYOK tariff is established here. - URL: https://langdock.com/pricing - Locator: Business/Enterprise cards; price breakdown; product add-ons - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:ecb-fx ECB historical euro reference rates, 20 October 2026. ECB2026-10-20 reference rates:EUR1=USD1.1215=CHF0.9237, implying USD1=EUR0.89166206. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20, USD and CHF currency entries - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### 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 ### langdock:langdock:migration Agent Migration Guide. Agent API export/import preserves selected configuration; files/skills and some fields require separate migration. - URL: https://docs.langdock.com/en/developer/agents-api/agent-migration.md - Locator: Prerequisites, exported settings and field mapping - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:dpa-20261026 Data Processing Agreement | Langdock. DPA 2.1 defines third-country instructions, subprocessor notice and deletion/export rules, with an embedded provider table. - URL: https://langdock.com/dpa - Locator: Sections 7-12 and Appendices 1/2 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:migration-20261026 Agent Migration Guide. Agent API export/import preserves selected configuration; files/skills and some fields require separate migration. - URL: https://docs.langdock.com/en/developer/agents-api/agent-migration.md - Locator: Prerequisites, exported settings and field mapping - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:knowledge-20261026 Knowledge bases. The public Markdown guide was retrieved with HTTP 200. The Knowledge Folder API can upload, update, delete, retrieve and search files; Viewer supports retrieval, while writes need Editor. This does not establish a complete index/ACL workspace export bundle. - URL: https://docs.langdock.com/en/using-langdock/library/knowledge-bases.md - Locator: Create a Knowledge base and add documents, API upload; Share search access; Convert a Knowledge base to a folder - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:exports-20261026 Usage Exports. The public Markdown guide was retrieved with HTTP 200. Workspace administrators can export usage analytics as CSV or through the Usage Export API, with up to 12 months of history and JSON-valued mapping fields. Usage analytics are distinct from a complete chat/knowledge export. - URL: https://docs.langdock.com/en/admin/compliance-and-governance/usage-exports.md - Locator: Accessing Usage Exports; Export Limits; Export Data Structure; Usage Exports; Data Retention - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### 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 ### langdock:langdock:playbook Rollout Playbook. Dedicated rollout support/workshops start at 250 licences and include a champion approach. - URL: https://docs.langdock.com/en/admin/ai-adoption-and-rollout/getting-started/rollout-playbook.md - Locator: Programme qualification and rollout phases - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:status status. The public status page covers the app, APIs, Workflows and Integrations with history. - URL: https://status.langdock.com/ - Locator: Components and history - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### langdock:langdock:terms-20261026 Terms of Use | Langdock. Terms 2.1 prohibit training and describe provider-specific residency and retention agreements, proprietary use rights and contract defaults. - URL: https://langdock.com/terms - Locator: Sections 6/7/9/12/15/16/19 and Appendix 1 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:imprint-20261026 Langdock imprint and contact point. Users and authorities can contact support@langdock.com in German and English; the imprint identifies Langdock GmbH in Berlin. - URL: https://langdock.com/imprint - Locator: Contact Point for Users and Authorities - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### langdock:langdock:status-20261026 status. The public status page covers the app, APIs, Workflows and Integrations with history. - URL: https://status.langdock.com/ - Locator: Components and history - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### 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 ### langdock:langdock:training Langdock Workshops. Official workshop recordings/slides cover chat, skills, integrations, agents and workflows. - URL: https://docs.langdock.com/en/using-langdock/resources/langdock-workshops.md - Locator: Workshop catalogue - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21