--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/dust-vs-omnifact/" data_url: "https://onaihq.com/compare/agents/dust-vs-omnifact/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-21 last_cross_checked_at: 2026-10-21 next_check_at: 2026-12-20 publisher: "onAI" --- # Dust vs Omnifact > 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 46 criteria with sourced findings for both products, including 46 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. - Omnifact source checks: 2026-10-21. - Canonical HTML: https://onaihq.com/compare/agents/dust-vs-omnifact/ - Machine-readable JSON: https://onaihq.com/compare/agents/dust-vs-omnifact/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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Manual selection spans OpenAI, Anthropic, Google and Mistral with EU/direct routes and tier controls. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed model catalogue; customer API keys and custom/self-hosted endpoints require Enterprise BYOK; add_ons=Enterprise BYOK for custom provider endpoints; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - current_models: Public text catalogue: GPT6Sol/Luna,5.6Sol/Terra/Luna,5.5,5.4/mini,5.2,5.1,5/mini/nano,4.1/mini/nano,4o/mini,4,3.5; Claude Opus5.5/5/4.8/4.7/4.6/4.5/4.1/4, Sonnet5.5/5/4.6/4.5/4, Haiku5.5/4.5; Gemini4Argon,3.8/3.7/3.6/3.5Flash,3.5Flash Lite,3.1Pro/Flash Lite,3Pro,2.5Pro/Flash,2.0Flash/Flash Lite; Mistral Medium3.5/3, Large3, Small4, Nemo, Ministral8B, Pixtral Large, Codestral, Devstral Small. Each is subject to admin enablement, tier, route and provider availability; not independently tested in picker. - multimodal_input: Image input only for capable selected models; experimental audio uploads need audio-capable models. Extracted document text and code tools are separate paths; no complete model-by-model native audio matrix was established. - Unverified auto_routing: No documented automatic cross-model routing strategy or chosen-model display after automatic routing was established; autonomous tool selection is separate from model routing. - providers — Which model providers are available? [partial]: Pro/Enterprise managed provider options include OpenAI/AzureOpenAI, Anthropic, Google/Vertex and Mistral subject to workspace configuration. Customer API keys, custom OpenAI-compatible endpoints and self-hosted model connections require Enterprise BYOK. Optional DPA-listed Groq is not treated as a currently selectable managed model. Sources: omnifact:omnifact:providers-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:models. - current_models — Which current models are selectable on this plan? [partial]: Public text catalogue: GPT6Sol/Luna,5.6Sol/Terra/Luna,5.5,5.4/mini,5.2,5.1,5/mini/nano,4.1/mini/nano,4o/mini,4,3.5; Claude Opus5.5/5/4.8/4.7/4.6/4.5/4.1/4, Sonnet5.5/5/4.6/4.5/4, Haiku5.5/4.5; Gemini4Argon,3.8/3.7/3.6/3.5Flash,3.5Flash Lite,3.1Pro/Flash Lite,3Pro,2.5Pro/Flash,2.0Flash/Flash Lite; Mistral Medium3.5/3, Large3, Small4, Nemo, Ministral8B, Pixtral Large, Codestral, Devstral Small. Each is subject to admin enablement, tier, route and provider availability; not independently tested in picker. Sources: omnifact:omnifact:models. - user_choice — Can users pick the model per chat? [supported]: Picker changes before/within a conversation and shows provider logo, model name and region flag. Reasoning effort has Low/Medium/High/Extra High depending on model. Sources: omnifact:omnifact:select. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? Unknown. No documented automatic cross-model routing strategy or chosen-model display after automatic routing was established; autonomous tool selection is separate from model routing. - multimodal_input — Which models accept images, audio or files? [partial]: Image input only for capable selected models; experimental audio uploads need audio-capable models. Extracted document text and code tools are separate paths; no complete model-by-model native audio matrix was established. Sources: omnifact:omnifact:files, omnifact:omnifact:groups-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:providers-rev2, omnifact:omnifact:dpa-rev2, omnifact:omnifact:models, omnifact:omnifact:select, omnifact:omnifact:files, omnifact:omnifact:groups-rev2, omnifact:omnifact:pricing-rev2 ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated model/feature changelog exists; exact release lag and fixed deprecation policy are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Unverified release_lag_days, deprecation_notice, version_pinning: Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee 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. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. - changelog — Is there a dated public model changelog? [supported]: Monthly release notes updated2026-10-20; individual feature posts date Gemini4Argon October 13, Haiku5.5 October 8, Sonnet5.5 September 28 and GPT6/Opus5.5 September 22. Sources: omnifact:omnifact:changes, omnifact:omnifact:blog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. - version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:changes, omnifact:omnifact:blog ### 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. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise BYOK supports own provider accounts and custom OpenAI-compatible connections. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise BYOK, customer provider contracts; add_ons=Customer provider charges separate; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - own_cloud_contract: Supported environments include Azure OpenAI, Vertex Anthropic/Vertex Google; model settings mention AWSBedrock via custom endpoints. Customer deployment/contract setup details not fully specified. - byo_pricing: BYOK moves model costs to customer account/negotiated rates; Enterprise licence adjustment is quote-only. - Unverified byo_restrictions: No complete BYOK-specific feature failure/parity matrix or public licence discount was established. - own_api_keys — Can the customer use its own provider API keys? [supported]: Enterprise only; connects own provider API keys, charges provider account and bypasses standard Omnifact rate limits. Sources: omnifact:omnifact:providers. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Supported environments include Azure OpenAI, Vertex Anthropic/Vertex Google; model settings mention AWSBedrock via custom endpoints. Customer deployment/contract setup details not fully specified. Sources: omnifact:omnifact:providers, omnifact:omnifact:model-settings. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Custom provider supports OpenAI-compatible endpoints; self-hosted connection enabled with support. Sources: omnifact:omnifact:providers, omnifact:omnifact:terms. - byo_pricing — Does BYO change the licence price? [partial]: BYOK moves model costs to customer account/negotiated rates; Enterprise licence adjustment is quote-only. Sources: omnifact:omnifact:providers. - byo_restrictions — Which features stop working with BYO? [unknown]: Which features stop working with BYO? Unknown. No complete BYOK-specific feature failure/parity matrix or public licence discount was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:providers, omnifact:omnifact:model-settings, omnifact:omnifact:terms ### 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. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise can integrate customer-hosted models; embedding and tool parity remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise self-hosted model connection; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - vendor_hosted_open_models: Mistral family appears with EU flags; the operating party and infrastructure for every open-weight route are not fully mapped. It is not proof of Swiss hosting. - Unverified self_hosted_embeddings, feature_parity: No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Enterprise lists self-hosted LLMs; terms6.4 requires coordination with support and custom provider endpoints are documented. Sources: omnifact:omnifact:pricing, omnifact:omnifact:providers, omnifact:omnifact:terms. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either. - feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: Mistral family appears with EU flags; the operating party and infrastructure for every open-weight route are not fully mapped. It is not proof of Swiss hosting. Sources: omnifact:omnifact:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:providers, omnifact:omnifact:terms, omnifact:omnifact:models ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Groups add model-tier/capability permissions while organization settings control concrete models/routes. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - model_allowlist_by_group: Groups add Base/Standard/Premium-tier and US-hosted-model access. Everyone and overlapping groups union grants; no deny overrides. Concrete model enablement is organization-wide, not an arbitrary per-group model list. - data_bound_models: Admins disable providers/models globally; DPA annexes also describe per-Space provider approval. No tested classifier routes knowledge content to distinct allowed models automatically. - default_model: October notes set Haiku5.5 as fast default for new organizations. Image default and Published Space model are configurable; universal organization text-default setting not established. - user_limits: Plan-determined per-user24-hour rolling message quotas show remaining count/reset. Numeric plan quotas are not public; pooled credit and page limits are separate. - model_allowlist_by_group — Can admins limit models per group? [partial]: Groups add Base/Standard/Premium-tier and US-hosted-model access. Everyone and overlapping groups union grants; no deny overrides. Concrete model enablement is organization-wide, not an arbitrary per-group model list. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: Admins disable providers/models globally; DPA annexes also describe per-Space provider approval. No tested classifier routes knowledge content to distinct allowed models automatically. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:dpa. - default_model — Can admins set the default model? [partial]: October notes set Haiku5.5 as fast default for new organizations. Image default and Published Space model are configurable; universal organization text-default setting not established. Sources: omnifact:omnifact:changes, omnifact:omnifact:model-settings, omnifact:omnifact:published. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Plan-determined per-user24-hour rolling message quotas show remaining count/reset. Numeric plan quotas are not public; pooled credit and page limits are separate. Sources: omnifact:omnifact:chat. - limit_behaviour — What happens when a limit is reached? [supported]: Daily message exhaustion disables new sends until reset. Monthly credit exhaustion greys premium models and chat falls back; Gateway returns credit error for all models without fallback. Sources: omnifact:omnifact:chat, omnifact:omnifact:limits, omnifact:omnifact:gateway. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings, omnifact:omnifact:dpa, omnifact:omnifact:changes, omnifact:omnifact:published, omnifact:omnifact:chat, omnifact:omnifact:limits, omnifact:omnifact:gateway ## 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Broad attachment formats and published limits exist; indexing uses OCR/chunks while workbook fidelity is untested. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - limits: 10 attachments/message;8000 text characters/message;20MB/image;25MB/audio. Space Uploaded Files FAQ says no individual/aggregate file-size limit; ordinary document/chat count ceilings not fully specified. - ocr: Space upload pipeline documents Apache Tika OCR for scanned PDFs/images; no accuracy fixture. - spreadsheets: Spreadsheet inputs can be processed with executed Python and native XLSX formulas; structure/merged cells/formula preservation not tested. - full_vs_chunked: Space documents are extracted/chunked/embedded and relevant sections retrieved with progress/citation displays. Exact direct-attachment full-text thresholds were not established. - formats — Which formats are accepted? [supported]: PDF, Word, Excel, Power Point, Open Document text/presentation, TXT, JSON, Markdown, CSV, SVG; images PNG/JPEG/Web P/HEIC/HEIF/AVIF/BMP/GIF/ICO/TIFF/SVG; audio examples MP3/WAV/AAC/FLAC with group/model restriction. Sources: omnifact:omnifact:files. - limits — What size and count limits apply per file and chat? [partial]: 10 attachments/message;8000 text characters/message;20MB/image;25MB/audio. Space Uploaded Files FAQ says no individual/aggregate file-size limit; ordinary document/chat count ceilings not fully specified. Sources: omnifact:omnifact:files, omnifact:omnifact:uploads. - ocr — Are scanned PDFs read? [partial]: Space upload pipeline documents Apache Tika OCR for scanned PDFs/images; no accuracy fixture. Sources: omnifact:omnifact:uploads. - spreadsheets — Are Excel tables read with structure intact? [partial]: Spreadsheet inputs can be processed with executed Python and native XLSX formulas; structure/merged cells/formula preservation not tested. Sources: omnifact:omnifact:documents. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Space documents are extracted/chunked/embedded and relevant sections retrieved with progress/citation displays. Exact direct-attachment full-text thresholds were not established. Sources: omnifact:omnifact:uploads, omnifact:omnifact:retrieval. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:files, omnifact:omnifact:uploads, omnifact:omnifact:documents, omnifact:omnifact: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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Spaces persist and share uploaded/connected knowledge. The applicable Pro page quota remains unknown; Enterprise advertises unlimited pages. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro up to50users and Enterprise Spaces; actual Pro page quota unverified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Pro page quota is excluded from verified limits until the applicable offer is identified. Connected-source and manual-upload accounting are separate. - persistent_collections — Can users keep document collections across chats? [supported]: Uploaded Files and connected folders persist in a Space for multiple conversations; message attachments remain specific to their conversation. Sources: omnifact:omnifact:spaces. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Organization users/groups including Everyone; Admin/Editor manage, Member queries. Groups receive view-only membership; edit grants are individual. Sources: omnifact:omnifact:share. - size_limits — What are the collection limits? [partial]: Enterprise pricing advertises unlimited knowledge pages. Actual Pro page quota is unknown because pricing says25000 while Billing says5000; neither is asserted as an independently applicable limit. The Connected Sources documentation says synced files currently do not count against the manual-upload page quota. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:sync. - assistant_binding — Can collections be bound to an assistant? [supported]: Space agent uses its own instructions and isolated Uploaded Files/Connected Sources knowledge. Sources: omnifact:omnifact:spaces. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share, omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:sync ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Cloud document sync and live first-party MCP integrations cover different system/action scopes. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise cloud document connectors; separately run API-enabled XWiki importer documented at pinned revision; add_ons=Customer-run XWiki sync tool; API access and source credentials required; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - XWiki behavior is documented in a pinned README, with no support/guarantee. It was not implementation-inspected or executed in this pass. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint, OneDrive Business and personal OneDrive document access/sync. No verified native Outlook/Teams connector in current catalogue. Sources: omnifact:omnifact:integrations. - google_workspace — Which Google sources are connected? [supported]: Drive document sync plus MCP Drive, Docs, Sheets, Slides, Gmail, Calendar, Chat tools. Sources: omnifact:omnifact:integrations. - atlassian — Confluence and Jira? [supported]: Atlassian official MCP for Jira/Confluence search and updates. Sources: omnifact:omnifact:directory. - other_systems — Which other business systems? [partial]: Slack, Zoom, Notion, Hub Spot, Zendesk, Box, Egnyte, Asana, Click Up, Linear, Airtable, Canva, Miro, Lucid, Stripe, Pay Pal, Git Hub/Git Lab, Sentry, PostHog, Supabase, Neon, Webflow, Todoist; official XWiki importer is separate unsupported CLI. Sources: omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Custom MCP can expose internal systems but cloud deployment blocks private IP/loopback/subnets by default. XWiki REST importer runs where customer executes it; native file-share/database network support is not established. Sources: omnifact:omnifact:mcp-rev2, omnifact:omnifact:xwiki-sync-rev2. - connector_provider — Who builds and maintains each connector? [partial]: Catalogue MCP servers are supplied by listed software vendors; Omnifact manages installation/governance. Document connectors and XWiki tool are Omnifact; support scope varies. Sources: omnifact:omnifact:directory, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:integrations, omnifact:omnifact:directory, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:mcp-rev2 ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Personal OAuth tools honor source-account rights; synced content is scoped to Space membership, without a verified per-user ACL mirror. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - source_permissions_respected: OAuth MCP executes only within each user account rights. Space indexed knowledge is available under shared Space membership; per-recipient source ACL enforcement was not established. - enforcement_point: Live OAuth uses source account access. Space retrieval is indexed and checks Space membership; this is not documented as a source-ACL recheck on every query. - revocation_delay: Removing Space/group membership immediately revokes those grants; source document/ACL revocation timing beyond deletion sync was not tested. - admin_scope_controls: Space admins select connected folders; organization enables/removes connectors and tools. No sensitivity-label classifier was established. - Unverified sensitivity_labels: No cross-group source-ACL/revocation fixture or Microsoft Purview sensitivity-label implementation was established. - source_permissions_respected — Are source permissions enforced per user? [partial]: OAuth MCP executes only within each user account rights. Space indexed knowledge is available under shared Space membership; per-recipient source ACL enforcement was not established. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [partial]: Live OAuth uses source account access. Space retrieval is indexed and checks Space membership; this is not documented as a source-ACL recheck on every query. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync. - revocation_delay — How quickly does a removed permission take effect? [partial]: Removing Space/group membership immediately revokes those grants; source document/ACL revocation timing beyond deletion sync was not tested. Sources: omnifact:omnifact:share, omnifact:omnifact:groups. - admin_scope_controls — Can admins exclude sites, folders or labels? [partial]: Space admins select connected folders; organization enables/removes connectors and tools. No sensitivity-label classifier was established. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? Unknown. No cross-group source-ACL/revocation fixture or Microsoft Purview sensitivity-label implementation was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync, omnifact:omnifact:share, omnifact:omnifact:groups, omnifact:omnifact:integrations ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Connected documents are indexed on a five-minute cycle; live MCP queries remain separate. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise cloud document connectors; separately run API-enabled XWiki importer documented at pinned revision; add_ons=Customer-run XWiki sync tool; API access and source credentials required; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - XWiki behavior is documented in a pinned README, with no support/guarantee. It was not implementation-inspected or executed in this pass. - live_or_indexed — Is content searched live or copied into an index? [supported]: Connected Sources index selected cloud files; MCP tools query source systems live. XWiki CLI uploads converted Markdown on customer-run sync. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2. - sync_interval — How often does an index refresh? [supported]: Connected Sources checks every five minutes; initial indexing may take minutes. XWiki tool is one-shot and requires external cron/systemd/Kubernetes scheduling. Sources: omnifact:omnifact:sync, omnifact:omnifact:xwiki-sync-rev2. - deletion_propagation — How quickly does a deleted document disappear? [supported]: Cloud deletions removed on next five-minute cycle; disconnect permanently removes that source index from Space. XWiki importer tracks deleted/excluded pages on next run. Sources: omnifact:omnifact:sync, omnifact:omnifact:xwiki-sync-rev2. - index_location — Where is indexed content stored? [partial]: DPA maps prefilter files/indexing to Azure Saa S Germany/Frankfurt storage; model embeddings/summaries have provider-dependent paths not fully mapped. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:dpa-rev2 ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Passage citations and controllable strict grounding are documented; retrieval quality remains unmeasured. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - no_answer_behaviour: Space instructions can require answers only from uploaded documents and explicit missing-information statements; default guaranteed abstention is not established. - Unverified citation_accuracy, cross_language, observed_accuracy: No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. - citations — Are answers linked to specific sources? [supported]: Source references identify uploaded document or cloud filename/provider and direct original link; progress shows retrieved document count. Sources: omnifact:omnifact:retrieval, omnifact:omnifact:sync. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. - 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 DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. - no_answer_behaviour — Does it say when the corpus has no answer? [partial]: Space instructions can require answers only from uploaded documents and explicit missing-information statements; default guaranteed abstention is not established. Sources: omnifact:omnifact:retrieval. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:retrieval, omnifact:omnifact:sync ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Persistent personal instructions exist; automatic cross-chat memory was not established. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - user_memory_controls: Users edit/remove their supplied personalization fields. This is not documentation of viewing/deleting automatically learned memories. - Unverified cross_chat_memory, admin_memory_controls: No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory. - custom_instructions — Can users set persistent instructions? [supported]: Personalization stores role/context and response tone/style/format and sends them in every conversation. These fields bypass the Privacy Filter. Sources: omnifact:omnifact:account. - cross_chat_memory — Does the product remember facts across chats? [unknown]: Does the product remember facts across chats? Unknown. No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users edit/remove their supplied personalization fields. This is not documentation of viewing/deleting automatically learned memories. Sources: omnifact:omnifact:account. - admin_memory_controls — Can admins turn memory off? [unknown]: Can admins turn memory off? Unknown. No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:account ## 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Space agents combine custom instructions, knowledge and shared access with starter prompts. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - creator_permissions: Member role includes Space creation; group permissions control file/code/features. An explicit deny-Space-creation privilege was not established. - prompt_library: Space Starters/template previews and example prompts provide shared starting points; a separate centrally managed standalone prompt-library product was not established. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Members create Spaces, become Space Admin and set instructions/examples/knowledge. Workspace-level tool availability is governed separately. Sources: omnifact:omnifact:create, omnifact:omnifact:users. - creator_permissions — Can admins limit who creates them? [partial]: Member role includes Space creation; group permissions control file/code/features. An explicit deny-Space-creation privilege was not established. Sources: omnifact:omnifact:users, omnifact:omnifact:groups. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Users or organization groups including Everyone; group membership grants Member only. Sources: omnifact:omnifact:share. - catalogue — Is there an internal assistant directory? [supported]: All/Favorite Spaces directory shows accessible agents with pin/favorite navigation. Sources: omnifact:omnifact:spaces. - prompt_library — Are shared prompt templates available? [partial]: Space Starters/template previews and example prompts provide shared starting points; a separate centrally managed standalone prompt-library product was not established. Sources: omnifact:omnifact:create, omnifact:omnifact:changes. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:create, omnifact:omnifact:users, omnifact:omnifact:groups, omnifact:omnifact:share, omnifact:omnifact:spaces, omnifact:omnifact:changes ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Remote MCP has explicit tool policies, personal OAuth and teamwide static-credential access. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed remote MCP; workspace-admin setup and chosen tool policy required; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Configured policies are documented; initial-discovery defaults remain unknown. Static credentials are shared teamwide as documented and do not provide personal source authorization. - Experimental code/output entitlement is unknown; generic Enterprise early-access wording does not identify an eligible Execute code tier. - builtin_tools — Which tools are built in? [partial]: Web search/browse, Space retrieval, image tools and curated MCP business actions are documented for the scoped workspace. Eligibility for the separate Experimental Execute code and its Python/Office outputs is unknown because the documentation does not map it to Pro or Enterprise. Sources: omnifact:omnifact:web, omnifact:omnifact:retrieval, omnifact:omnifact:images, omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:groups-rev2. - custom_actions — Can admins add API actions? [partial]: Admins add custom remote MCP URL and discovered tools. Arbitrary non-MCP REST wrappers require an external server. Sources: omnifact:omnifact:mcp-rev2. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Remote HTTP MCP supports OAuth, APIkey, Bearer, customheader ornone. Destination validation blocks private/subnet/metadata endpoints by default. Sources: omnifact:omnifact:mcp-rev2. - tool_auth — Do tools act as the user or as a shared account? [partial]: OAuth requires personal sign-in; static APIkey/Bearer/header/none is central and immediately available teamwide, with no current per-user/group permission for those types. Sources: omnifact:omnifact:mcp-rev2. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins explicitly configure each tool as Always, Approval or Disable. Approval displays the exact request payload with Allow/Deny; later refresh adds new tools disabled. Initial-discovery default is unknown because setup and security sections disagree, so no safe or permissive initial default is asserted. Sources: omnifact:omnifact:mcp-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:web, omnifact:omnifact:retrieval, omnifact:omnifact:images, omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:mcp-rev2, omnifact:omnifact:groups-rev2 ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web research is cited and group-controlled; Brave handles public search. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - search_provider: DPA names Brave Software US as web-search processor; exact request-processing datacentre is not specified. Masked-sensitive queries are blocked before search. - deep_research: Agents can perform multi-step browsing/research; no separately bounded Deep Research report product or benchmark was established. - web_search — Is web search available? [supported]: Automatically triggered when needed or explicitly requested; URL reader caps2MB and excludes login/paywall/captcha pages. Sources: omnifact:omnifact:web. - admin_toggle — Can admins disable it per organisation or group? [supported]: Groups grant web search/browsing additively; remove grant from Everyone/allgroups to disable for targeted users. Sources: omnifact:omnifact:groups. - search_provider — Which search provider handles queries, and where? [partial]: DPA names Brave Software US as web-search processor; exact request-processing datacentre is not specified. Masked-sensitive queries are blocked before search. Sources: omnifact:omnifact:dpa, omnifact:omnifact:web. - deep_research — Is multi-step research with a report available? [partial]: Agents can perform multi-step browsing/research; no separately bounded Deep Research report product or benchmark was established. Sources: omnifact:omnifact:changes, omnifact:omnifact:web. - web_citations — Are web sources cited? [supported]: Numbered citations and original source links accompany search/browse results. Sources: omnifact:omnifact:web. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:dpa, omnifact:omnifact:changes ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial External n8n nodes support automation; a native scheduled workflow builder is not established. Availability: generally-available Delivery: official-integration Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise Published Spaces/Documents API when enabled; AI Gateway nodes require Enterprise; external n8n runs separately; add_ons=External n8n community-node installation; customer-run scheduler/XWiki importer; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - These integrations are pinned README documentation, not executed or source-inspected implementation. A native Omnifact workflow builder/scheduler is not established. - workflow_builder — Is there a workflow or chain builder? [partial]: Vendor-owned repository publishes n8n community nodes for Gateway completions/model list, Published Space chat and document CRUD. The visual builder is external n8n, not an established native Omnifact builder. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2. - scheduled_tasks — Can prompts or assistants run on a schedule? [partial]: XWiki importer explicitly uses external cron/systemd/Kubernetes Cron Job. Native scheduled prompts/agents were not established. Sources: omnifact:omnifact:xwiki-sync-rev2. - event_triggers — Can external events start a workflow? [unknown]: Can external events start a workflow? Unknown. Native schedule/webhook/event-trigger support was not established from docs, index, changelog and automation integrations. - builder_audience — Is building aimed at business users, IT or developers? [partial]: n8n community-node/API integrations and CLI sync target technical integrators; Space instructions target business users. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2, omnifact:omnifact:create. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:create ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agentic chat plans tools and streams progress with configurable approvals and Stop. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - visible_steps: Tool/search/retrieval progress and expandable reasoning show activity; exact full execution trace was not independently inspected. - side_effect_confirmation: Curated actions wait for confirmation by default; admins choose Always/Approval/Disable. It is not unconditional confirmation for every write under all configurations. - stop_control: Send becomes Stop while response generates; clicking halts generation. Cancellation of already committed external side effects is not established. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: August release rebuilt chat around multi-step agents with automatic tool selection; API optionally enables agentic workflow. Sources: omnifact:omnifact:changes, omnifact:omnifact:api-chat. - visible_steps — Are steps and tool calls shown? [partial]: Tool/search/retrieval progress and expandable reasoning show activity; exact full execution trace was not independently inspected. Sources: omnifact:omnifact:select, omnifact:omnifact:retrieval, omnifact:omnifact:web. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Curated actions wait for confirmation by default; admins choose Always/Approval/Disable. It is not unconditional confirmation for every write under all configurations. Sources: omnifact:omnifact:directory, omnifact:omnifact:mcp. - stop_control — Can the user stop a running task? [partial]: Send becomes Stop while response generates; clicking halts generation. Cancellation of already committed external side effects is not established. Sources: omnifact:omnifact:stop. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:changes, omnifact:omnifact:api-chat, omnifact:omnifact:select, omnifact:omnifact:retrieval, omnifact:omnifact:web, omnifact:omnifact:directory, omnifact:omnifact:mcp, omnifact:omnifact:stop ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Spaces/document API and Enterprise Gateway use organization keys with different filtering/credit behavior. Availability: generally-available Delivery: native Scope: surfaces=Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro published Spaces advertised but support enablement needed; Gateway Enterprise opt-in; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - chat_api: Published Spaces chat JSON/SSE with source/agentic headers; Enterprise Gateway OpenAI-compatible completions. Gateway V1 explicitly lacks tool calls and structured outputs. - knowledge_api: Document upload, list, inspect, rename/delete with Space scope and async ingestion; no agent-configuration CRUD endpoint established. - api_governance: Org-level revocable key, enabled-modelcontrols and shared credit budget apply. Gateway hard-stops on exhaustion; Published Space API disables Privacy Filter. Fine-grained API-key scopes/end-user identities/audit parity were not established. - Unverified mcp_server: No first-party Omnifact MCP server exposing platform agents was established; inbound MCP client integrations are distinct. - chat_api — Is there an API for chat and assistants? [partial]: Published Spaces chat JSON/SSE with source/agentic headers; Enterprise Gateway OpenAI-compatible completions. Gateway V1 explicitly lacks tool calls and structured outputs. Sources: omnifact:omnifact:api-chat, omnifact:omnifact:gateway. - knowledge_api — Can documents be loaded through an API? [partial]: Document upload, list, inspect, rename/delete with Space scope and async ingestion; no agent-configuration CRUD endpoint established. Sources: omnifact:omnifact:api-docs. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Org-level revocable key, enabled-modelcontrols and shared credit budget apply. Gateway hard-stops on exhaustion; Published Space API disables Privacy Filter. Fine-grained API-key scopes/end-user identities/audit parity were not established. Sources: omnifact:omnifact:developer, omnifact:omnifact:gateway, omnifact:omnifact:published, omnifact:omnifact:model-settings. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unknown. No first-party Omnifact MCP server exposing platform agents was established; inbound MCP client integrations are distinct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:api-chat, omnifact:omnifact:gateway, omnifact:omnifact:api-docs, omnifact:omnifact:developer, omnifact:omnifact:published, omnifact:omnifact:model-settings ## 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Browser and mobile web access are advertised; native and managed clients remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - mobile_apps: Pricing lists Mobile Web App and model picker adapts to small screens; no native i OS/Android app with SSO was established. - client_feature_gaps: Mobile effort picker is inline rather than flyout; broader mobile feature parity is not specified. - Unverified desktop_apps, browser_extension, managed_deployment: No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - web — Is a full web client available? [supported]: Full Saa S browser client provides chat and Spaces. Sources: omnifact:omnifact:home. - desktop_apps — Windows and macOS apps? [unknown]: Windows and mac OS apps? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - mobile_apps — iOS and Android apps with SSO? [partial]: Pricing lists Mobile Web App and model picker adapts to small screens; no native i OS/Android app with SSO was established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:select. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - client_feature_gaps — Which features are missing on mobile? [partial]: Mobile effort picker is inline rather than flyout; broader mobile feature parity is not specified. Sources: omnifact:omnifact:select. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:home, omnifact:omnifact:pricing, omnifact:omnifact:select ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Office files and live Google connectors exist; embedded office/Teams apps are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - word_excel_powerpoint: Generates DOCX/XLSX/PPTX and modifies uploaded files, but this does not establish in-Word/Excel/Power Point add-ins. - google_workspace_apps: Google Docs/Sheets/Slides/Gmail/Calendar/Chat MCP actions run from Omnifact after personal OAuth; embedded add-ons were not established. - licence_prerequisites: Microsoft document access may require tenantwide admin consent; all OAuth integrations need individual authorized source accounts and third-party entitlements. Exact office-suite licence matrix not established. - Unverified outlook, teams: No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [partial]: Generates DOCX/XLSX/PPTX and modifies uploaded files, but this does not establish in-Word/Excel/Power Point add-ins. Sources: omnifact:omnifact:documents. - outlook — Does it work inside Outlook? [unknown]: Does it work inside Outlook? Unknown. No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue. - teams — Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [partial]: Google Docs/Sheets/Slides/Gmail/Calendar/Chat MCP actions run from Omnifact after personal OAuth; embedded add-ons were not established. Sources: omnifact:omnifact:integrations. - licence_prerequisites — Which licences or consents are needed? [partial]: Microsoft document access may require tenantwide admin consent; all OAuth integrations need individual authorized source accounts and third-party entitlements. Exact office-suite licence matrix not established. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:sync ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Persistent style instructions support writing; specialized document translation is unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - formality_and_variants: Personal response instructions can request formal/casual tone and style. Specific de-CH controls or terminology enforcement were not documented. - writing_tools: Chat supports drafting and rewriting via instructions and document generation; a dedicated proofreading/translation toolbar was not established. - Unverified document_translation, translation_engine, glossaries: Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - translation_engine — Which engine translates? [unknown]: Which engine translates? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Personal response instructions can request formal/casual tone and style. Specific de-CH controls or terminology enforcement were not documented. Sources: omnifact:omnifact:account. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Chat supports drafting and rewriting via instructions and document generation; a dedicated proofreading/translation toolbar was not established. Sources: omnifact:omnifact:account, omnifact:omnifact:documents. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:account, omnifact:omnifact:documents ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Image generation and edits use configured OpenAI/Google models under group permission. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - image_generation: Model Settings lists GPTImage2/1.5/1/1Mini, Nano Banana/Pro/2; September notes add GPTImage2.5Flare/Sunburst and October Nano Banana2.1 direct Google. EU generation remains Nano Banana2 because2.1 is not on Google Cloud EU. - admin_control: Generate Images is group-granted; model enablement/default is organization-wide. Image/audio contents bypass PII masking and retain route constraints. - Unverified usage_terms: Model-specific output licence/commercial rights were not established; general software rights do not define image-output ownership. - image_generation — Can users generate images, with which models? [partial]: Model Settings lists GPTImage2/1.5/1/1Mini, Nano Banana/Pro/2; September notes add GPTImage2.5Flare/Sunburst and October Nano Banana2.1 direct Google. EU generation remains Nano Banana2 because2.1 is not on Google Cloud EU. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:changes. - image_editing — Can users edit uploaded images? [supported]: Uploaded reference images can be transformed with text instructions; results appear in gallery and download. Sources: omnifact:omnifact:images. - admin_control — Can admins restrict image generation? [partial]: Generate Images is group-granted; model enablement/default is organization-wide. Image/audio contents bypass PII masking and retain route constraints. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings, omnifact:omnifact:privacy. - usage_terms — What usage rights apply to output? [unknown]: What usage rights apply to output? Unknown. Model-specific output licence/commercial rights were not established; general software rights do not define image-output ownership. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:changes, omnifact:omnifact:images, omnifact:omnifact:groups, omnifact:omnifact:privacy ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Experimental dictation/audio input exists; meeting bot/live voice coverage is unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - dictation: Experimental Dictate Messages requires enabled Azure OpenAI; audio bypasses filtering and speech is converted to text. - meeting_summaries: Uploaded meeting transcripts can be summarized and Zoom integration searches/recaps recordings; no native automatic meeting-joining/transcription bot was established. - Unverified read_aloud, voice_conversation, swiss_german_speech: No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. - dictation — Can users dictate prompts? [partial]: Experimental Dictate Messages requires enabled Azure OpenAI; audio bypasses filtering and speech is converted to text. Sources: omnifact:omnifact:groups. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. - meeting_summaries — Are meetings transcribed and summarised? [partial]: Uploaded meeting transcripts can be summarized and Zoom integration searches/recaps recordings; no native automatic meeting-joining/transcription bot was established. Sources: omnifact:omnifact:directory, omnifact:omnifact:documents. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:groups, omnifact:omnifact:directory, omnifact:omnifact:documents ### 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 #### Omnifact 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. ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared Spaces organize agents/knowledge; multi-user conversations and complete source-safe redistribution are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - share_permission_boundary: Space members can see referenced uploaded knowledge. Personal OAuth MCP follows each source account, but Space source-ACL rechecking and generated-answer resharing boundaries were not tested. - Unverified share_chats, group_chat: Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence. - share_chats — Can chats be shared inside the organisation? [unknown]: Can chats be shared inside the organisation? Unknown. Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence. - team_spaces — Are shared projects or workspaces available? [supported]: Space instructions, knowledge and membership are shared with users/groups; conversations remain organized under the Space. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share. - group_chat — Can several people chat together with the AI? [unknown]: Can several people chat together with the AI? Unknown. Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: Space members can see referenced uploaded knowledge. Personal OAuth MCP follows each source account, but Space source-ACL rechecking and generated-answer resharing boundaries were not tested. Sources: omnifact:omnifact:share, omnifact:omnifact:mcp, omnifact:omnifact:sync. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share, omnifact:omnifact:mcp, omnifact:omnifact:sync ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial English and German UI are documented; language quality and accessibility are untested. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - admin_ui_languages: A separate German admin documentation tree is published; this does not verify complete German in-app admin translation. - Unverified dach_language_quality, accessibility_statement: No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector. - ui_languages — Which UI languages are offered? [supported]: Account language selector offers English/German, otherwise browser-language default. Sources: omnifact:omnifact: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 DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector. - admin_ui_languages — Is the admin interface available in German? [partial]: A separate German admin documentation tree is published; this does not verify complete German in-app admin translation. Sources: omnifact:omnifact:account. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact: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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise SAML2.0 uses identity-provider MFA and conditional-access policies; nativeTOTP entitlement is outside this finding. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise SAML/SSO only; nativeTOTP entitlement excluded; add_ons=Enterprise SSO enablement; identity-provider MFA/conditional access; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - The supported MFA path here is the Enterprise identity provider. Native password/TOTP accounts require separate plan verification. - sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML2.0 via SSO Ready; Entra ID, Okta, Keycloak and SAML-compatible Id Ps. OIDC was not established. Sources: omnifact:omnifact:users, omnifact:omnifact:sso-blog, omnifact:omnifact:public-sector. - sso_plan — Which plan includes SSO? [supported]: SSO/SCIM exclusive to Enterprise and support-enabled configuration. Sources: omnifact:omnifact:users. - mfa — Can MFA be enforced? [partial]: For Enterprise SAML/SSO users, authentication and MFA are controlled by the identity provider; Omnifact native2FA setup is hidden. No nativeTOTP entitlement for Pro or Enterprise is asserted. Sources: omnifact:omnifact:security-rev2, omnifact:omnifact:sso-blog. - conditional_access — Do Entra conditional-access policies apply? [partial]: SSO announcement says existing Id P conditional access/MFA/password rules apply; Entra device/location combinations were not tested. Sources: omnifact:omnifact:sso-blog. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. No verified company-domain capture/ownership process was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:sso-blog, omnifact:omnifact:public-sector, omnifact:omnifact:security-rev2, omnifact:omnifact:auth ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise SCIM synchronizes users/groups; deactivation blocks login while detailed asset disposition remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - jit_provisioning: Provisioned status includes SSO/SCIM-created accounts before first login; invitations are skipped for SSO. Exact just-in-time account trigger not specified. - deprovisioning: Deactivated users cannot log in; only unaccepted invitees can be permanently deleted from user list. Space removal keeps prior contributions; full leaver private data/agent ownership effects unspecified. - seat_assignment: Active and invited users count as seats; adding prorates cost, removal credits next invoice. Deactivated-seat billing treatment not fully specified. - scim — Is SCIM provisioning supported? [supported]: Dedicated sso-sync creates, updates anddeactivates users automatically; manual creation/profile/role/CSV changes are locked under SCIM. Sources: omnifact:omnifact:users. - group_sync — Are identity-provider groups synced? [supported]: Entra, Okta or Google Workspace groups mirror into immutable-membership Synced Groups with Omnifact-managed permissions. Sources: omnifact:omnifact:groups. - jit_provisioning — Are users created at first login? [partial]: Provisioned status includes SSO/SCIM-created accounts before first login; invitations are skipped for SSO. Exact just-in-time account trigger not specified. Sources: omnifact:omnifact:users. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: Deactivated users cannot log in; only unaccepted invitees can be permanently deleted from user list. Space removal keeps prior contributions; full leaver private data/agent ownership effects unspecified. Sources: omnifact:omnifact:users, omnifact:omnifact:share. - seat_assignment — Can admins assign and reclaim seats? [partial]: Active and invited users count as seats; adding prorates cost, removal credits next invoice. Deactivated-seat billing treatment not fully specified. Sources: omnifact:omnifact:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:groups, omnifact:omnifact:share, omnifact:omnifact:billing ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Owner/Admin/Member and Space roles combine with additive groups. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - multi_entity: Organization tenant separation and department Space/group boundaries are described; terms prohibit multiple accounts for one company and usage beyond own personnel without agreement. Multi-subsidiary contract rights were not established. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Owner includes Admin/Member, Admin includes Member; Admin manages team users/settings except Owner. Space Admin/Editor is separate, with optional Knowledge Base Manager in DPA. Sources: omnifact:omnifact:users, omnifact:omnifact:share, omnifact:omnifact:dpa. - groups — Can permissions be set per group? [supported]: Everyone, SCIM-synced andmanual groups; permissions union rather than deny. Sources: omnifact:omnifact:groups. - feature_toggles — Which features can be switched on or off per group? [supported]: Group grants file/image uploads, audio, web, imagegeneration, code, dictation, modeltiers, USmodels, filterexemption; organization models/features must also be enabled. Sources: omnifact:omnifact:groups. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Organization tenant separation and department Space/group boundaries are described; terms prohibit multiple accounts for one company and usage beyond own personnel without agreement. Multi-subsidiary contract rights were not established. Sources: omnifact:omnifact:dpa, omnifact:omnifact:terms, omnifact:omnifact:share. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:share, omnifact:omnifact:dpa, omnifact:omnifact:groups, omnifact:omnifact:terms ### ADM-04: Usage and adoption analytics Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Consumption analytics has detailed attribution and exports without message content. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - adoption_dashboard — Is there an adoption dashboard? [partial]: Pricing lists usage/adoption reporting; the Analytics guide focuses on credit consumption and attribution rather than a complete active-user adoption scorecard. Sources: dust:dust:pricing, dust:dust:analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [supported]: Analytics filters/ranks agents, members, groups, models, tools, sources, API keys, skills and Pods. Group attribution may count a member in several groups. Sources: dust:dust:analytics. - export — Can usage data be exported? [supported]: Raw CSV consumption export and API analytics export are documented, with workspace enablement and key-scope restrictions. Sources: dust:dust:analytics. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: Analytics exports omit message content, but contain member/message/conversation identifiers. Pseudonymous or works-council privacy modes were not established. Sources: dust:dust:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:analytics #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise adoption analytics show active users and message counts; deeper breakdown/export controls are unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise Usage Analytics & Insights; Pro excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Dashboard scope is organization/day level; additional model/group/assistant breakdowns and export remain unverified. - adoption_dashboard — Is there an adoption dashboard? [supported]: Analytics provides date-range totals and daily active-user/message charts with interactive metric toggles; Enterprise-only in pricing. Sources: omnifact:omnifact:analytics-rev2, omnifact:omnifact:pricing-rev2. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Documented dashboard is organization/day level. Model, group, feature andassistant breakdown matrix was not established. Sources: omnifact:omnifact:analytics-rev2. - export — Can usage data be exported? [unknown]: Can usage data be exported? Unknown. No documented analytics export/API or configurable individual-reporting controls were established. Direct HTML retrieval returned403; public cached official page was retrieved through the web tool. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: DPA describes anonymized PostHog feature-use analytics without individual attribution; separate customer-visible reporting privacy toggles were not established. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:analytics-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:dpa-rev2 ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared pooled credits and model permissions constrain spend; individual financial allocation is unspecified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - cost_visibility: Billing shows pooled real-time consumption andforecast; Enterprise detailed real-time dashboard is described as forthcoming, while total used is available. - budgets: Organization pooled allowance and manual additional-credit recharge. Model-tier and USroute access can be group-controlled, but per-user/group monetary hard caps were not established. - Unverified chargeback: No cost-centre chargeback export or complete cost-per-user/group allocation interface was established. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Billing shows pooled real-time consumption andforecast; Enterprise detailed real-time dashboard is described as forthcoming, while total used is available. Sources: omnifact:omnifact:billing. - budgets — Can budgets be set per user or group? [partial]: Organization pooled allowance and manual additional-credit recharge. Model-tier and USroute access can be group-controlled, but per-user/group monetary hard caps were not established. Sources: omnifact:omnifact:billing, omnifact:omnifact:groups. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Monthly budget: chat downgrades to enabled fallbacks; Gateway hard-blocks all calls on exhausted credits. Daily message quota disables send until reset. Sources: omnifact:omnifact:limits, omnifact:omnifact:gateway, omnifact:omnifact:chat. - chargeback — Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? Unknown. No cost-centre chargeback export or complete cost-per-user/group allocation interface was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:billing, omnifact:omnifact:groups, omnifact:omnifact:limits, omnifact:omnifact:gateway, omnifact:omnifact:chat ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA documents append-only admin logs for at least 90 days; content compliance export is unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - log_retention: Administrative logs retained at least 90 days; content retention is customer-configured but not a published compliance archive. - Unverified content_logging, siem_export, ediscovery: No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - admin_events — Are admin and security events logged? [supported]: TOM2.5 records user-status changes/resource deletions with user attribution, UTC timestamps, encrypted transport/storage and append-only protection; event coverage can expand. Sources: omnifact:omnifact:dpa. - 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? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - siem_export — Can logs stream to a SIEM or be exported? [unknown]: Can logs stream to a SIEM or be exported? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are e Discovery and legal hold supported? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - log_retention — How long are logs kept? [partial]: Administrative logs retained at least 90 days; content retention is customer-configured but not a published compliance archive. Sources: omnifact:omnifact:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa ### 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. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Default Privacy Filter combines local NER/regex masking with several explicit bypass paths. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise, filter defaults enabled; user exemptions/advanced feature flags qualified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - pii_detection: Names, addresses, email, phone, IPv4, US/German IDs/passports, tax/pensionnumbers, IBAN/BIC/card/routing/account numbers, companies anddocument filenames. Media bytes are not scanned; AHV recognition untested. - pii_action: Detected strings replaced with placeholders then restored in output; web queries containing masked values are blocked. Click-to-Reveal confirms sending individual terms; optional%%exemption defaults off andrequires Support. Group exemptions may disable filtering per agent/Space. - custom_patterns: Vendor detector uses custom-trained SLMNER andregex, but customer-defined pattern/dictionary UI/API was not established. Optional%%syntax bypasses rather than adds detection. - filter_location: DPA places filter within Azure Germany West Central, Frankfurt before external model. MCP arguments/results, code, sandbox, images/audio bytes, personalization and Published Space API bypass filtering by design. - Unverified dlp_integration: No existing third-party DLP/Purview integration or synthetic AHV/IBAN accuracy fixture was established. - pii_detection — Is personal data detected in prompts and files? [partial]: Names, addresses, email, phone, IPv4, US/German IDs/passports, tax/pensionnumbers, IBAN/BIC/card/routing/account numbers, companies anddocument filenames. Media bytes are not scanned; AHV recognition untested. Sources: omnifact:omnifact:dpa, omnifact:omnifact:files, omnifact:omnifact:privacy. - pii_action — Is it redacted, masked, blocked or only warned? [partial]: Detected strings replaced with placeholders then restored in output; web queries containing masked values are blocked. Click-to-Reveal confirms sending individual terms; optional%%exemption defaults off andrequires Support. Group exemptions may disable filtering per agent/Space. Sources: omnifact:omnifact:privacy, omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:dpa. - custom_patterns — Can admins add custom patterns or terms? [partial]: Vendor detector uses custom-trained SLMNER andregex, but customer-defined pattern/dictionary UI/API was not established. Optional%%syntax bypasses rather than adds detection. Sources: omnifact:omnifact:dpa. - dlp_integration — Does it integrate with an existing DLP product? [unknown]: Does it integrate with an existing DLP product? Unknown. No existing third-party DLP/Purview integration or synthetic AHV/IBAN accuracy fixture was established. - filter_location — Where does filtering run? [partial]: DPA places filter within Azure Germany West Central, Frankfurt before external model. MCP arguments/results, code, sandbox, images/audio bytes, personalization and Published Space API bypass filtering by design. Sources: omnifact:omnifact:dpa, omnifact:omnifact:privacy, omnifact:omnifact:published, omnifact:omnifact:account. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa, omnifact:omnifact:files, omnifact:omnifact:privacy, omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:published, omnifact:omnifact:account ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Company/Space instructions and privacy/tool governance exist; mandatory policy workflows are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - org_instructions: Teamdescription supplies businesscontext; Spaceinstructions set response behavior and strict grounding. No guaranteed immutable organization safety instruction hierarchy was established. - content_filters: Organization PIImasking, group capabilities/modelroutes andper-tool approval/block settings are documented. General topic/abusefilter customization was not established. - Unverified usage_notice, violation_reporting: No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established. - org_instructions — Can admins set organisation-wide instructions? [partial]: Teamdescription supplies businesscontext; Spaceinstructions set response behavior and strict grounding. No guaranteed immutable organization safety instruction hierarchy was established. Sources: omnifact:omnifact:company, omnifact:omnifact:create, omnifact:omnifact:retrieval. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Unknown. No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established. - content_filters — Are content filters configurable? [partial]: Organization PIImasking, group capabilities/modelroutes andper-tool approval/block settings are documented. General topic/abusefilter customization was not established. Sources: omnifact:omnifact:privacy, omnifact:omnifact:groups, omnifact:omnifact:mcp. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:company, omnifact:omnifact:create, omnifact:omnifact:retrieval, omnifact:omnifact:privacy, omnifact:omnifact:groups, omnifact:omnifact:mcp ## 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosted primary workspace storage is in Azure EU. Germany-only processing and complete backup/log/support residency are not established; model and metadata routes differ. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted Azure platform storage; model and edge-metadata routes separately scoped; add_ons=Enterprise AI Gateway where named; provider/model route and eu/ prefix selected explicitly; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - The storage finding covers primary workspace content, not every model/edge/support processing path. No Germany-only or whole-service EU-only guarantee is made. - storage_region — Where are chats, files and indexes stored? [partial]: Hosted raw chats/files/indexed workspace content uses Azure infrastructure in the EU. DPA identifies GermanyWestCentral/Frankfurt; the live infrastructure register also names NL/SE/IE. Only EU primary-platform storage is claimed here; a Germany-only deployment footprint is not established. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2. - inference_region — Where do model calls run, per provider? [supported]: EU routes include Azure OpenAI, Google Cloud EU for Gemini/Anthropic, and Mistral EU. Direct OpenAI/Anthropic US and Google API global routes also exist. Gateway needs eu/ prefix; unprefixed IDs never use EU backends. Sources: omnifact:omnifact:models, omnifact:omnifact:vertex, omnifact:omnifact:gateway, omnifact:omnifact:trust-rev2. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Unknown per-service backup/log geography for a particular contract. DPA Frankfurt/EU wording and the broader Azure DE/NL/SE/IE register do not map each backup stream. Cloudflare EU/US edge metadata/security logs are separate from platform document storage. - support_access_region — From where can vendor staff access data? [partial]: Pricing names German and US service teams; DPA permits justified, time-limited production access. Staff physical access locations by task are not specified. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:dpa-rev2. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unknown. No full Swiss platform/backup/support hosting option was established. - residency_plan — Which plan or option provides residency? [partial]: Pro/Enterprise pricing offers EU cloud storage and EU model routes. This does not establish all-service EU residency. Enterprise Gateway requests require eu/ model IDs for EU backends; direct/global model routes and edge metadata have different geography. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:gateway, omnifact:omnifact:providers-rev2, omnifact:omnifact:trust-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:models, omnifact:omnifact:vertex, omnifact:omnifact:gateway, omnifact:omnifact:trust-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:groups-rev2, omnifact:omnifact:providers-rev2 ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Saa S, customer-cloud and on-premise are offered without published private-deployment minimums. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Enterprise customer-cloud/on-premise; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise Saa S; Enterprise quoted private deployment; add_ons=Deployment/infrastructure/operator costs quoted; deployment_mode=not specified; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - dedicated_instance: Managed, own-cloud and on-premise are advertised; a distinct dedicated Saa S specification and seat threshold were not established. - customer_cloud: Own/private cloud is available on request; minimum seats/spend, operating roles and supported infrastructure are not public. - on_premise: Enterprise on-premise option includes municipal datacenters; numeric minimum and architecture requirements are unpublished. - Unverified air_gapped, mode_feature_gaps: Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification. - multi_tenant_saas — Is a shared SaaS offered? [supported]: Cloud Saa S uses logical organization/client separation. Sources: omnifact:omnifact:terms, omnifact:omnifact:dpa. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [partial]: Managed, own-cloud and on-premise are advertised; a distinct dedicated Saa S specification and seat threshold were not established. Sources: omnifact:omnifact:home. - customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: Own/private cloud is available on request; minimum seats/spend, operating roles and supported infrastructure are not public. Sources: omnifact:omnifact:home, omnifact:omnifact:public-sector. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Enterprise on-premise option includes municipal datacenters; numeric minimum and architecture requirements are unpublished. Sources: omnifact:omnifact:pricing, omnifact:omnifact:public-sector. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification. - mode_feature_gaps — Which features are missing outside SaaS? [unknown]: Which features are missing outside Saa S? Unknown. Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:terms, omnifact:omnifact:dpa, omnifact:omnifact:home, omnifact:omnifact:public-sector, omnifact:omnifact:pricing ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Managed-route documentation promises no model training. Applicable upstream retention, ZDR eligibility and human-review exceptions remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed chat routes; AI Gateway statements apply only to the Enterprise API module; actual upstream retention unverified; add_ons=Enterprise AI Gateway enablement where explicitly named; BYOK under customer-provider agreement; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - No universal provider ZDR finding is made. The advertised ZDR option is not treated as unsupported; its applicable terms remain a gap. - vendor_training — Does the vendor train on customer content? [supported]: Vendor says it never uses customer data to train its own models. Sources: omnifact:omnifact:privacy-intro. - provider_training — Do model providers train on it under this product's contracts? [partial]: The vendor promises no underlying-provider training for the Enterprise AI Gateway. BYOK processing is under the customer-provider agreement; no managed-route promise is extended to arbitrary customer keys. Sources: omnifact:omnifact:gateway-web, omnifact:omnifact:dpa-rev2. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [unknown]: Unknown applicable duration per enabled model/provider/project. The Trust register describes typical directOpenAI30-day retention and configuration-dependent Google logging, while EU-route pages advertise ZDR. These are not mapped to an actual customer route/contract, so no model-specific retention guarantee is asserted. - zero_retention — Is zero data retention available, and on which plan? [unknown]: Unknown verified ZDR eligibility and scope per Pro/Enterprise model route. Gateway payload handling and EU-route marketing do not establish the upstream provider agreement or every safety/logging exception. Workspace database storage is separate. - human_review — Can provider staff review content? [partial]: Provider processing summaries are request-only in Trust Center; human abuse-review exceptions by provider/model were not established. Sources: omnifact:omnifact:trust-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:privacy-intro, omnifact:omnifact:gateway-web, omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2, omnifact:omnifact:vertex ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA contract-end return/approved-destruction duties are separate from support-request deletion and backup retention. A guaranteed runtime exit window remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise published DPA return/deletion obligations; actual runtime exit and account-deletion timing unverified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - The finding states separate contractual and documented operational procedures. It does not turn a support-request clock into an exit grace period. - default_retention — What is retained and for how long by default? [partial]: DPA: database PITR30 days with daily snapshots/continuous WAL; weekly pg_dump fallback; blob soft-delete14 days. Universal default chat/file retention is unspecified. Sources: omnifact:omnifact:dpa-rev2. - admin_retention — Can admins set retention periods? [partial]: DPA permits organization administrators to set customer-data retention; UI range and per-object options are not published. Sources: omnifact:omnifact:dpa-rev2. - user_deletion — Can users delete their chats and files permanently? [partial]: The Space uploaded-file guide describes permanent deletion of a selected file. Registered-user/profile and whole-organization runtime deletion semantics are not established here; the user-list Delete operation applies to unaccepted invitations. Sources: omnifact:omnifact:uploads, omnifact:omnifact:users. - contract_end_deletion — What is deleted at contract end, and when? [partial]: DPA9.2 requires return or controller-approved destruction no later than contract end, except legal retention;9.3 permits proof-of-processing documentation retention. The TOM separately describes support-request organization deletion within30days and backups aging out. No guaranteed post-termination self-service access window or tested runtime completion time is inferred. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:users, omnifact:omnifact:uploads ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA defines processor-change notice and transfer safeguards; a complete current contract-specific supplier/entity/country register remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise standard hosted DPA; optional model-provider routes only under the applicable contract/instruction; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Neither public list is silently treated as complete. Ordinary notification/transfer contract terms remain distinct from a verified current processing inventory. - subprocessor_list — Is a dated sub-processor list published? [unknown]: Unknown complete current plan-specific processor inventory. DPAAnnex4 and the live Trust register publish different sets; no source establishes a consolidated applicable list or the role of every listed provider for a given contract. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: Unknown complete country/legal-entity matrix for the scoped contract. Azure infrastructure and Cloudflare metadata have different roles, and optional model-provider routes depend on selection. The differing DPA/Trust entries are not combined into one asserted authoritative list. - change_notification — Are customers notified of sub-processor changes? [supported]: DPA6.3 requires written/text notice at least 30 days before new/replaced subprocessor and objection opportunity before start. Sources: omnifact:omnifact:dpa-rev2. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: Omnifact Gmb H, Frankfurt, Germany, HRB131357. Ultimate parent/shareholding was not established. Sources: omnifact:omnifact:imprint. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [partial]: DPA1.4 permits nonEEA processing after prior information and safeguards under Articles44-49. Optional BYOK/provider routes depend on their applicable agreements. A specific current SCC/DPF basis for every Trust entry was not verified. Sources: omnifact:omnifact:dpa-rev2. - government_access_policy — Is there a published government-access or transparency policy? [partial]: DPA11.2 requires seizure/confiscation notice unless prohibited by court/authority; Terms15.3 require advance compelled-disclosure notice where legal. Separate request statistics were not verified. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2, omnifact:omnifact:imprint, omnifact:omnifact: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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public GDPR DPA is binding in German; Swiss and sector-specific contract coverage remains incomplete. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - dpa: Article28 DPA accepted at registration. German text prevails; English is a translation. Written amendments are possible but negotiability is not promised. - revdsg_gdpr: GDPR is explicit; revised Swiss DSG coverage/addendum and Swiss SCC modifications were not established. - ai_act_materials: Public AI Act whitepaper and Academy literacy/certification training are advertised; these are not product conformity attestations. - sector_materials: Public-administration, banking and healthcare positioning/private hosting are advertised; actual FINMA/DORA/§203 contract pack was not verified. - dpa — Is a DPA available, and is it negotiable? [partial]: Article28 DPA accepted at registration. German text prevails; English is a translation. Written amendments are possible but negotiability is not promised. Sources: omnifact:omnifact:dpa, omnifact:omnifact:dpa-de. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: GDPR is explicit; revised Swiss DSG coverage/addendum and Swiss SCC modifications were not established. Sources: omnifact:omnifact:dpa. - governing_law — Which law and court govern the contract? [supported]: German law and Frankfurt exclusive jurisdiction under Terms18; German legal version prevails. Sources: omnifact:omnifact:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Public AI Act whitepaper and Academy literacy/certification training are advertised; these are not product conformity attestations. Sources: omnifact:omnifact:whitepapers, omnifact:omnifact:pricing. - sector_materials — Are FINMA or other sector materials provided? [partial]: Public-administration, banking and healthcare positioning/private hosting are advertised; actual FINMA/DORA/§203 contract pack was not verified. Sources: omnifact:omnifact:home, omnifact:omnifact:public-sector. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa, omnifact:omnifact:dpa-de, omnifact:omnifact:terms, omnifact:omnifact:whitepapers, omnifact:omnifact:pricing, omnifact:omnifact:home, omnifact:omnifact:public-sector ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public ISO27001 certificate verifies platform/Spaces ISMS through 2029-04-06. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - pentest: DPA states annual external pentests with remediation; actual report/period/summary was not verified. - Unverified soc2, c5, other_certifications: No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - iso_27001 — ISO 27001 with scope and validity? [supported]: Prescient Security LLC certificate123228 issue1, ISO/IEC27001:2022, issued/certified 2026-04-07, valid until 2029-04-06 subject to surveillance. Covers ISMS supporting Platform/Spaces, data, Azure infrastructure, software, people and procedures; So A1.4 dated 2026-03-30. All in-scope activities conducted remotely. Sources: omnifact:omnifact:iso. - soc2 — SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - report_access — How can customers obtain reports? [supported]: ISO PDF is public and downloadable through Trust Center. Eight AI-provider processing summaries are request-only and were not requested. Sources: omnifact:omnifact:trust. - pentest — Are independent penetration test summaries available? [partial]: DPA states annual external pentests with remediation; actual report/period/summary was not verified. Sources: omnifact:omnifact:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:iso, omnifact:omnifact:trust, omnifact:omnifact:dpa ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial AES256/TLS and logical tenant separation are documented; customer-held keys remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - private_networking: Vendor internal services use NSGs/Private Endpoints and NetBird JIT VPN for privileged production access; public app is Cloudflare-fronted. A customer private-link/IP-allowlist option was not established. - Unverified customer_managed_keys: No customer-managed/held encryption-key configuration was established; sovereignty discussion does not establish key-management functionality. - encryption_at_rest — Is data encrypted at rest? [supported]: DPA requires AES256 at rest for Postgre SQL, Blob Storage and other persistent Azure services; HTTPS/TLS in transit. Sources: omnifact:omnifact:dpa. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. No customer-managed/held encryption-key configuration was established; sovereignty discussion does not establish key-management functionality. - private_networking — Is private connectivity or IP restriction available? [partial]: Vendor internal services use NSGs/Private Endpoints and NetBird JIT VPN for privileged production access; public app is Cloudflare-fronted. A customer private-link/IP-allowlist option was not established. Sources: omnifact:omnifact:dpa. - tenant_isolation — How are customers separated in shared SaaS? [supported]: Organization-scoped data/roles, separate production/development/test Azure environments, no customer data in tests. This is logical tenant separation. Sources: omnifact:omnifact:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa ### DATA-09: Professional secrecy Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment. #### 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 #### Omnifact 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro costs EUR25/user/month annually up to50users. Its binding credit currency/value and recharge tariff remain unknown; Enterprise Gateway costs are outside this offer. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro hosted workspace up to50users; Enterprise/API Gateway quote and markup excluded; add_ons=Optional Academy separately quoted; Enterprise terms require separate offer; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Pro Chat/Spaces pricing is not mixed with Enterprise Gateway billing. The conflicting credit examples remain a named allowance gap. - pricing_unit — What is the pricing unit? [supported]: Pro uses named seats with monthly or annual billing and pooled premium-model credit; this finding covers the hosted Chat/Spaces subscription. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing. - list_prices — What are list prices per plan, with date and currency? [partial]: Checked2026-10-21: Pro EUR25/user/month billed annually, advertised16% discount versus monthly. Exact monthly rate was not verified. Pro up to50 users; Enterprise custom with unlimited team size. VAT excluded under terms. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms. - included_usage — What usage is included? [partial]: Unknown applicable monetary allowance currency/value for the contract: pricing statesEUR5/user/month while Billing usesUSD5 examples. Pooling, monthly expiry and continued base-tier access subject to fair-use limits are documented, but no definitive currency-denominated allowance is asserted. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing. - add_ons — Which features cost extra? [partial]: Academy training is separately quoted. Enterprise is a separate custom offer adding SSO/SCIM, BYOK/self-hosted models, analytics and custom deployment/SLA. No Enterprise Gateway markup is applied to Pro Chat/Spaces pricing. Sources: omnifact:omnifact:pricing-rev2. - overage — What do usage beyond limits and premium models cost? [partial]: The Pro billing guide directs admins to discuss additional credits; a public recharge tariff was not established. Base-tier chat remains available after included premium credit is used subject to usage limits. Enterprise Gateway billing/markup is outside this Pro finding. Sources: omnifact:omnifact:billing, omnifact:omnifact:pricing-rev2, omnifact:omnifact:limits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:terms, omnifact:omnifact:limits, omnifact:omnifact:users, omnifact:omnifact:gateway, omnifact:omnifact:developer ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared v1.4 costs remain unknown for200/1000/5000 users because all exceed the50-seat Pro cap. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. - ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 200 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 1000 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 5000 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx. - variable_share — Which part depends on usage? [partial]: Enterprise base,pooled credit allowance,model/route rates,additional credits and Gateway markup are unknown. Quote base plus usage beyond included credit plus deployment/services; convert known EUR components at0.9237 CHF/EUR. No substitute vendor tariff/model assumed. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway, omnifact:omnifact:billing, omnifact:omnifact:ecb-fx. - unknown_parts — Which costs could not be priced? [supported]: Enterprise seat/volume rate,minimum spend,credit allowance,recharge tariff,model/route rates,Gateway markup percentage,private hosting and Academy service fees are unknown. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway, omnifact:omnifact:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx, omnifact:omnifact:gateway, omnifact:omnifact:billing ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Ten-day no-card Pro trial is self-serve; enterprise setup is gated. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - free_tier: Time-limited free trial; billing requires a paid subscription afterward. No permanent business free tier established. - trial_scope: Pro chat, Spaces, Privacy Filter and platform access advertised; terms call trial scope limited. Enterprise SSO/SCIM/BYOK/private deployment and support-enabled APIs are not established trial entitlements. - sales_gate: Base Pro trial is self-serve; Enterprise quotes, SSO and advanced API activation require vendor interaction. No vendor contact was made. - free_tier — Is there a free tier for business use? [partial]: Time-limited free trial; billing requires a paid subscription afterward. No permanent business free tier established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:billing. - self_serve_trial — Is a self-serve business trial available? [supported]: Ten-day trial, no credit card, teams up to50 users via account signup. Sources: omnifact:omnifact:pricing. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Pro chat, Spaces, Privacy Filter and platform access advertised; terms call trial scope limited. Enterprise SSO/SCIM/BYOK/private deployment and support-enabled APIs are not established trial entitlements. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:developer. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Base Pro trial is self-serve; Enterprise quotes, SSO and advanced API activation require vendor interaction. No vendor contact was made. Sources: omnifact:omnifact:pricing, omnifact:omnifact:users, omnifact:omnifact:developer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:billing, omnifact:omnifact:terms, omnifact:omnifact:developer, omnifact:omnifact:users ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro monthly/annual terms are public; Enterprise minimum and CHF invoicing are unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - minimum_commitment: Pro maximum 50 users, Enterprise no team-size cap; public Enterprise minimum seat/spend and private-deployment minimum not established. - local_invoicing: Omnifact Gmb H Frankfurt invoices EUR public prices, supports invoice/SEPA and payment within 14 days. CHF billing not established. - transparency_class: Partial: public Pro price/credits/team cap but Enterprise, deployment, additional credits and services quote-only; Gateway markup not quantified. - minimum_commitment — What seat or spend minimum applies? [partial]: Pro maximum 50 users, Enterprise no team-size cap; public Enterprise minimum seat/spend and private-deployment minimum not established. Sources: omnifact:omnifact:pricing. - contract_length — What contract lengths are offered? [supported]: Monthly/annual terms; Enterprise flexible agreement. Annual renews yearly, monthly renews monthly. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms. - cancellation — How can the contract be cancelled or reduced? [supported]: Annual notice three months before term end; monthly cancel for following month; text/email accepted. Seat removal gives prorated credit on next invoice per billing doc. Sources: omnifact:omnifact:terms, omnifact:omnifact:billing. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Omnifact Gmb H Frankfurt invoices EUR public prices, supports invoice/SEPA and payment within 14 days. CHF billing not established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:imprint. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partial: public Pro price/credits/team cap but Enterprise, deployment, additional credits and services quote-only; Gateway markup not quantified. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:billing, omnifact:omnifact:imprint, omnifact:omnifact:gateway ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Platform is proprietary; four inspected public integration/client components have MIT licences. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync, Omnifact example embeddable widget; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted licence; separately MIT-licensed client/integration tools at pinned revisions; API enablement required; add_ons=Customer-run CLI/widget tools; Published Spaces/API access and resource permissions as needed; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Client/integration capabilities are documented in pinned README/licence files, not implementation-inspected or tested; they do not license the hosted platform. - licence_type — Which licence applies to each component? [supported]: Terms grant contract-term nontransferable/non-sublicensable software use; platform source excluded unless expressly agreed. CLI, widget, n8n nodes and XWiki sync carry MIT licences at pinned commits; these do not license the hosted platform. Sources: omnifact:omnifact:terms, omnifact:omnifact:cli-licence-rev2, omnifact:omnifact:widget-licence-rev2, omnifact:omnifact:n8n-nodes-omnifact-licence-rev2, omnifact:omnifact:xwiki-sync-licence-rev2. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Platform use limited to agreed user count/own business personnel. Widget can theme colors/title under MIT notice obligations; MIT integrations do not impose seat limits. Platform branding-removal rules were not fully established. Sources: omnifact:omnifact:terms, omnifact:omnifact:widget-rev2, omnifact:omnifact:widget-licence-rev2. - enterprise_features_closed — Are enterprise features in a separate closed edition? [partial]: Enterprise is a commercial feature/deployment tier; no open-core platform edition was established. Source may be included by separate agreement under terms3.3. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:terms, omnifact:omnifact:cli-licence-rev2, omnifact:omnifact:widget-licence-rev2, omnifact:omnifact:n8n-nodes-omnifact-licence-rev2, omnifact:omnifact:xwiki-sync-licence-rev2, omnifact:omnifact:widget-rev2, omnifact:omnifact:pricing-rev2 ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA promises data handover; documented APIs do not establish a complete workspace export. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync, Omnifact example embeddable widget; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted licence; separately MIT-licensed client/integration tools at pinned revisions; API enablement required; add_ons=Customer-run CLI/widget tools; Published Spaces/API access and resource permissions as needed; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Client/integration capabilities are documented in pinned README/licence files, not implementation-inspected or tested; they do not license the hosted platform. - chat_export — Can admins export all chats? [unknown]: Can admins export all chats? Unknown. No admin export-all-chats or reusable complete Space/agent/prompt export was established. No exit fixture was run. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. No admin export-all-chats or reusable complete Space/agent/prompt export was established. No exit fixture was run. - knowledge_export — Can knowledge bases and their sources be exported? [partial]: Documents API/CLI list metadata and manage Space files, while native generated files download. Full original-source, index and ACL export bundle was not established. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:cli-rev2, omnifact:omnifact:documents. - export_format — Are formats documented and machine-readable? [partial]: Document metadata via JSON; native outputs DOCX/XLSX/PPTX and chart images. Widget stores only its own conversation in browser local Storage; this is not an admin export of platform chats. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:documents, omnifact:omnifact:widget-rev2. - post_termination_window — How long can data be retrieved after termination? [partial]: DPA9.2 requires handover or approved destruction at completion/end; no guaranteed post-termination self-service download window specified. TOM gives30-day support organization deletion. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:cli-rev2, omnifact:omnifact:documents, omnifact:omnifact:widget-rev2, omnifact:omnifact:dpa-rev2 ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro email support and Enterprise custom support are documented; a single applicable platform uptime SLA remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro published support terms; Enterprise support and negotiated SLA only under its contract; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Network and system availability percentages are not interchangeable. Enterprise SLA terms require the actual contract. - support_channels — Which support channels are available on each plan? [partial]: Pro pricing promises email within 24 hours; terms process M–F usually09–17 and answer within one working day. Enterprise dedicated support/account manager/custom SLA; timezone not specified in terms. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. No verified public incident-history status page or contracted DE/FR/IT support-language matrix was located; status.omnifact.ai did not resolve. - regional_presence — Is there a DACH or Swiss entity, team or partner? [partial]: Omnifact Gmb H Frankfurt, Germany; pricing also mentions German and US service teams. No Swiss entity established. Sources: omnifact:omnifact:imprint, omnifact:omnifact:pricing-rev2. - uptime_sla — Is there an uptime SLA with credits? [unknown]: Unknown applicable end-to-end service guarantee. Terms7.3 specify99.5% annual pure-network availability while DPA TOM states99.9% system availability, and Enterprise offers a custom SLA. No order-form/service mapping or fixed credit schedule was retrieved, so no single platform SLA is asserted. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? Unknown. No verified public incident-history status page or contracted DE/FR/IT support-language matrix was located; status.omnifact.ai did not resolve. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms, omnifact:omnifact:imprint, omnifact:omnifact:dpa-rev2 ### 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 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro has learning material/webinar; Enterprise workshops and Academy are tailored. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - user_training: Academy offers foundational/advanced courses, individual training and certificate options supporting AI literacy; complete delivery-language/volume entitlement not published. - adoption_programme: Enterprise rollout/admin enablement/use-case workshops and Academy strategy/governance workshops advertised; a formal champion programme was not established. - service_cost: Academy/additional training separately quoted; terms3.6 generally make installations, instruction/training chargeable under separate agreement. - onboarding_service — Is guided onboarding included? [supported]: Pro onboarding documentation/e-learning and webinar; Enterprise custom onboarding/use-case workshops and account manager. Sources: omnifact:omnifact:pricing. - user_training — Is end-user training offered, in which languages? [partial]: Academy offers foundational/advanced courses, individual training and certificate options supporting AI literacy; complete delivery-language/volume entitlement not published. Sources: omnifact:omnifact:pricing. - use_case_library — Are role-based use cases and templates provided? [supported]: Space Starter templates include content creation, knowledge queries, professional development; release notes add meeting-minutes/mail-triage/helpdesk template previews. Sources: omnifact:omnifact:create, omnifact:omnifact:changes. - adoption_programme — Is there a champion or adoption programme? [partial]: Enterprise rollout/admin enablement/use-case workshops and Academy strategy/governance workshops advertised; a formal champion programme was not established. Sources: omnifact:omnifact:home, omnifact:omnifact:pricing. - service_cost — Which services cost extra? [partial]: Academy/additional training separately quoted; terms3.6 generally make installations, instruction/training chargeable under separate agreement. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:create, omnifact:omnifact:changes, omnifact:omnifact:home, omnifact:omnifact:terms ## 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 ### omnifact:omnifact:models Models: All Leading AI Models on One Platform – Omnifact. Current catalogue lists model families, tiers and EU/global region flags. - URL: https://omnifact.ai/models - Locator: OpenAI, Anthropic, Google and Mistral tables - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:select Selecting an AI Model - Omnifact. Manual model picker shows provider/model/region and reasoning effort; browser stores per-model effort. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/model-selection - Locator: Model selector, effort and reasoning trace - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:files Attaching Documents & Images - Omnifact. Attachments have type-specific limits and media bypasses text filtering. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/attaching-documents - Locator: Formats, input limits and privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:pricing-rev2 Pricing Plans – Omnifact. Pro is EUR25/user/month annually up to50users. Enterprise adds BYOK/self-hosted models, analytics, SSO and custom SLA. The page is not used to establish an eligible Gateway markup or reconcile conflicting credit examples. - URL: https://omnifact.ai/pricing - Locator: Pro/Enterprise tier table, annual price and credit footnote - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:providers-rev2 Providers - Omnifact. Customer keys, custom OpenAI-compatible endpoints and self-hosted model connections require Enterprise BYOK; managed model access is separate. - URL: https://docs.omnifact.ai/en/platform/team-administration/providers - Locator: Supported Providers and Enterprise-only Bring Your Own Key - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:groups-rev2 Group Management - Omnifact. The Python/code execution tool is explicitly Experimental, has internet access and bypasses the Privacy Filter for sandbox inputs. - URL: https://docs.omnifact.ai/en/platform/team-administration/groups - Locator: Execute code (Experimental), tool controls and security note - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:dpa-rev2 Data Processing Agreement – Omnifact. DPA states return/approved destruction at contract end, distinct support-request deletion within30days, backup schedules and30-day subprocessor-change notice. This does not resolve runtime/plan-specific implementation or a complete current supplier mapping. - URL: https://omnifact.ai/dpa - Locator: Sections6.3,9.2/9.3; Annex3 deletion and backups; Annex4 subprocessor terms - Evidence kind: documented - Source date: 2026-04-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:changes Release Notes – Omnifact. Dated release notes through October 20 add models, agents, code, MCP, groups and 2FA. - URL: https://omnifact.ai/release-notes - Locator: October–May2026 and earlier entries - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### omnifact:omnifact:blog Blog – Omnifact. Feature announcements include Gemini4Argon October 13 and integrations October 6. - URL: https://omnifact.ai/blog - Locator: Current dated feature drops - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:terms Terms of Service – Omnifact. Terms define proprietary rights,99.5% annual network availability, support and cancellation. - URL: https://omnifact.ai/terms - Locator: Sections3/6–8/10–11/14–18 - Evidence kind: documented - Source date: 2024-08-01 - Retrieved: 2026-10-21 ### omnifact:omnifact:providers Providers - Omnifact. Enterprise BYOK supports direct providers, Azure/Vertex and custom OpenAI-compatible endpoints. - URL: https://docs.omnifact.ai/en/platform/team-administration/providers - Locator: Supported Providers, BYOK and connection management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:model-settings Model Management - Omnifact. Model enablement applies to chat, Published Spaces and Gateway; image defaults and tiers are configurable. - URL: https://docs.omnifact.ai/en/platform/team-administration/models - Locator: Availability, Image Models and Model Providers - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:pricing Pricing Plans – Omnifact. Pro annual EUR25 includes pooled EUR5 monthly AI credits per seat up to50 users; Enterprise and Academy are quoted. - URL: https://omnifact.ai/pricing - Locator: Pro, Enterprise, comparison and footnote1 - Evidence kind: vendor-claimed - 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 ### omnifact:omnifact:dpa Data Processing Agreement – Omnifact. DPA includes Frankfurt infrastructure/TOMs, retention, audit requirements and approved subprocessors. - URL: https://omnifact.ai/dpa - Locator: Sections1/6/9/11, Annex1, TOMs2.1–2.10 and Annex4 - Evidence kind: documented - Source date: 2026-04-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:groups Group Management - Omnifact. Additive groups govern capabilities, model tiers, US routes and filter exemptions; Enterprise SCIM mirrors groups. - URL: https://docs.omnifact.ai/en/platform/team-administration/groups - Locator: Group types, SCIM, permissions and sharing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:gateway AI Gateway - Omnifact. Enterprise opt-in OpenAI-compatible gateway uses eu/ routing and hard credit enforcement; V1 lacks tools/structured output. - URL: https://docs.omnifact.ai/en/platform/team-administration/ai-gateway - Locator: Prerequisites, EU routes, constraints, billing and errors - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:published Published Spaces - Omnifact. Support-enabled Published Space APIs disable the Privacy Filter and use secret endpoint URLs. - URL: https://docs.omnifact.ai/en/platform/team-administration/published-spaces - Locator: Activation, model management and security - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:chat Introduction to Chats - Omnifact. Chat retains conversations and supports document output, sources and daily message quotas. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/introduction - Locator: Features, quotas and message limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:limits AI Credits and Usage Limits - Omnifact. Exhausted monthly credits fall back in chat; Gateway blocks all calls without base fallback. - URL: https://docs.omnifact.ai/en/guides/troubleshooting/usage-and-credits - Locator: Credit exhaustion and fallback models - 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 ### omnifact:omnifact:documents Document Creation - Omnifact. Isolated Python code creates XLSX/DOCX/PPTX/charts with internet egress and group controls. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/document-creation - Locator: Document types, editing, formulas and sandbox - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:uploads Managing Uploaded Files - Omnifact. Space file pipeline uses Tika OCR, chunking, embeddings and summaries; documents can be deleted permanently. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/managing-uploaded-files - Locator: Processing, deletion and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:retrieval Uploaded Files Retrieval - Omnifact. Agents retrieve source passages under Space membership and show citations/progress; strict no-answer grounding is instructed. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/uploaded-files-retrieval - Locator: Retrieval and source behavior - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:billing Billing & Usage - Omnifact. Billing describes proration, pooled credit and plan changes but uses USD5 examples and5000-page Pro quota. - URL: https://docs.omnifact.ai/en/platform/team-administration/billing - Locator: Seat Management, Monthly Usage Credit and Plan Management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:spaces What are Spaces? - Omnifact. Spaces persist instructions/knowledge and conversations with shared member access. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/introduction - Locator: Concepts, benefits and examples - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:share Sharing Spaces with Colleagues - Omnifact. Organization users/groups share Spaces; group access is view-only and removal is immediate. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/sharing-spaces - Locator: Roles, group sharing and removal - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:sync Connected Sources - Omnifact. Connected sources index selected Drive/OneDrive/SharePoint folders every five minutes and remove deleted content next cycle. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/connected-sources - Locator: Setup, privacy and FAQ - 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 ### omnifact:omnifact:integrations Integrations - Omnifact. Curated first-party MCP and document connectors use separate live-versus-indexed access patterns. - URL: https://docs.omnifact.ai/en/platform/team-administration/integrations - Locator: Catalog, integration types and privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:directory Integrations: Connect the Tools Your Team Uses – Omnifact. Current catalogue names cloud storage, Google, Atlassian, CRM, design, communications and developer systems. - URL: https://omnifact.ai/integrations/catalog - Locator: Integration cards and custom MCP - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:xwiki-sync-rev2 omnifact-xwiki-sync pinned README. omnifact-xwiki-sync documents incremental XWiki page/attachment ingestion with delete propagation. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-xwiki-sync/blob/599db2ec0c7f28ddb2a22c4a09a9242e5781316b/README.md - Locator: Pinned README.md documentation at commit 599db2ec0c7f28ddb2a22c4a09a9242e5781316b; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-08-25 - Retrieved: 2026-10-21 ### omnifact:omnifact:mcp-rev2 MCP Servers - Omnifact. Tools have Always/Approval/Disable policies; Approval shows the request payload. Documentation conflicts on initial discovery defaults, which remain unknown. - URL: https://docs.omnifact.ai/en/platform/team-administration/mcp-servers - Locator: Per-tool policies, authentication and later tool refresh; initial discovery defaults excluded - 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 ### omnifact:omnifact:mcp MCP Servers - Omnifact. Remote MCP has personal OAuth/shared static credentials, per-tool Always/Approval/Disable policies and private-network restrictions. - URL: https://docs.omnifact.ai/en/platform/team-administration/mcp-servers - Locator: Setup, policies, OAuth, approvals and privacy boundaries - 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 ### omnifact:omnifact:account Account Settings - Omnifact. English/German UI and persistent personal context/instructions are documented; personalization is unfiltered. - URL: https://docs.omnifact.ai/en/platform/core-features/account-settings/user-profile-and-personalization - Locator: Language Preferences and Personalization - 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 ### omnifact:omnifact:users User Management - Omnifact. User roles and Enterprise SSO/SCIM automate lifecycle while locking manual changes. - URL: https://docs.omnifact.ai/en/platform/team-administration/users - Locator: Roles, statuses, lifecycle and SSO/SCIM - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:create Creating New Spaces - Omnifact. Users create custom Space agents with instructions and starter examples. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/creating-spaces - Locator: Space Starters and configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:images Image Generation - Omnifact. Images are generated/edited from references and retained in an Assets gallery. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/image-generation - Locator: Generation, reference images and gallery - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:web Web Search and Browsing - Omnifact. Web search displays citations and blocks queries with masked sensitive values. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/web-search-browsing - Locator: Search, privacy and limitations - 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 ### 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 ### omnifact:omnifact:n8n-nodes-omnifact-rev2 n8n-nodes-omnifact pinned README. n8n-nodes-omnifact documents n8n community nodes for Gateway/chat/documents. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/n8n-nodes-omnifact/blob/7a3947c620206d4e195064421db525aaa4dfb50a/README.md - Locator: Pinned README.md documentation at commit 7a3947c620206d4e195064421db525aaa4dfb50a; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-09-10 - 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 ### omnifact:omnifact:api-chat Published Spaces Chat API - Omnifact. Published chat provides JSON/SSE and optional inline sources/agentic workflow headers. - URL: https://docs.omnifact.ai/en/api-reference/published-space-chat - Locator: Headers, responses and SSE events - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:stop Stopping and Regenerating Responses - Omnifact. Send changes to a Stop button during response generation. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/stopping-regenerating-responses - Locator: How to Stop - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### 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 ### omnifact:omnifact:developer Developer Tools - Omnifact. API enablement is gated and organization key regeneration/revocation is centralized. - URL: https://docs.omnifact.ai/en/platform/team-administration/developer-tools - Locator: Activation and API key management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:api-docs Documents API - Omnifact. Document APIs upload/list/inspect/update/delete Space files asynchronously. - URL: https://docs.omnifact.ai/en/api-reference/documents - Locator: Endpoints and schema examples - 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 ### omnifact:omnifact:home AI for the Public Sector & Regulated Industries – Omnifact. Platform offers governed multi-model chat, Spaces, Privacy Filter and private deployment. - URL: https://omnifact.ai/ - Locator: Product, governance and deployment overview - 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 ### 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 ### omnifact:omnifact:privacy Data Privacy - Omnifact. Filter defaults on but MCP, code, image/audio paths bypass it; code sandbox has internet egress. - URL: https://docs.omnifact.ai/en/platform/team-administration/data-privacy - Locator: Privacy Filter Control and boundaries - 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 ### 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 ### 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 ### omnifact:omnifact:sso-blog Single Sign-On (SSO) for Enterprise Authentication – Omnifact. Enterprise SAML2.0 supports optional SCIM, Id P policies and disabled email sign-in. - URL: https://omnifact.ai/blog/feature-drop-introducing-sso - Locator: Setup, benefits and changes - Evidence kind: documented - Source date: 2024-11-25 - Retrieved: 2026-10-21 ### omnifact:omnifact:public-sector GDPR-Compliant AI for Public Administration – Omnifact. Public-sector page names Entra/Okta/Keycloak and Germany/municipal on-premise options. - URL: https://omnifact.ai/solutions/public-administration - Locator: SSO, deployment and onboarding - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:auth Authentication - Omnifact. TOTP, recovery codes and account/IP-specific throttling are described. - URL: https://docs.omnifact.ai/en/platform/core-features/account-settings/authentication - Locator: 2FA setup and failure handling - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:security-rev2 Security and Access - Omnifact. SSO/SAML users rely on identity-provider authentication and MFA and do not see native2FA setup. This does not establish nativeTOTP inclusion in a plan. - URL: https://docs.omnifact.ai/en/platform/team-administration/security-and-access - Locator: SSO/SAML identity-provider authentication; native2FA tier not established - 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 ### 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 ### omnifact:omnifact:analytics-rev2 Analytics - Omnifact. Enterprise dashboard presents daily active users and messages with date ranges and toggles; export and additional breakdowns are not established. - URL: https://docs.omnifact.ai/en/platform/team-administration/team-analytics - Locator: Analytics heading, date-range selector, summary cards, activity chart; HTTP200 re-read2026-10-21 - 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 ### omnifact:omnifact:company Company Profile - Omnifact. Company description and business context shape AI responses. - URL: https://docs.omnifact.ai/en/platform/team-administration/company-profile - Locator: Team Description and company identity - 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 ### omnifact:omnifact:vertex EU Data Residency for Claude and Gemini via Google Cloud – Omnifact. Google/Anthropic EU via Google Cloud are advertised with zero retention and EU-only configuration. - URL: https://omnifact.ai/blog/feature-drop-eu-data-residency-vertex-ai - Locator: What is new, compliance and EU model configuration - Evidence kind: vendor-claimed - Source date: 2026-04-01 - Retrieved: 2026-10-21 ### omnifact:omnifact:trust-rev2 https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust. Public register lists Azure DE/NL/SE/IE infrastructure and Cloudflare EU/US edge metadata, plus model-provider routes; it is not a plan-specific processor/data-flow inventory. - URL: https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust - Locator: Public JSON subprocessors, lastUpdatedAt; infrastructure/metadata roles distinguished - Evidence kind: documented - Source date: 2026-10-21 - 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 ### omnifact:omnifact:gateway-web AI Gateway: One API for Every Model – Omnifact. Gateway consumes organization budget, does not store payloads and requires ZDR-capable models for strict retention. - URL: https://omnifact.ai/ai-gateway - Locator: Regional routing, budget and governance - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:privacy-intro Why Data Privacy Matters - Omnifact. Vendor explicitly excludes training its own models on customer data and distinguishes EU/self-hosted routes. - URL: https://docs.omnifact.ai/en/platform/core-features/privacy-security/introduction - Locator: Privacy Commitment and FAQ - 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 ### omnifact:omnifact:imprint Legal Notice – Omnifact. Omnifact Gmb H is registered in Frankfurt, Germany, HRB131357. - URL: https://omnifact.ai/legal-notice - Locator: Company address and register - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:dpa-de Auftragsverarbeitungsvertrag – Omnifact. Binding German DPA confirms region, transfer, retention and processor terms. - URL: https://omnifact.ai/de/dpa - Locator: Anlagen and main agreement - Evidence kind: documented - Source date: 2026-04-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:whitepapers Get Instant Access to our Full Enterprise Whitepaper – Omnifact. Public library includes AI Act, workplace enablement, self-hosting and RAG guides. - URL: https://omnifact.ai/whitepapers - Locator: Whitepaper catalogue - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:trust https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust. Public Trust Center JSON exposes certificate access and named processor locations, including US direct model routes and Cloudflare telemetry. - URL: https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust - Locator: documents, subprocessors and lastUpdatedAt - Evidence kind: documented - Source date: 2026-10-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:iso Omnifact GmbH ISO/IEC27001:2022 official certificate. Certificate123228 issue1 from Prescient Security LLC covers Omnifact Platform/Spaces and Azure ISMS; valid2026-04-07 through 2029-04-06 subject to surveillance. - URL: https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust/documents/bb9dd08f-c61a-48f3-be41-9fbcdf24e9c3/download-url - Locator: Public Trust Center certificate PDF, one page: scope, issuer, issue date and validity - Evidence kind: certificate-verified - Source date: 2026-04-07 - Retrieved: 2026-10-21 - Issuer: Prescient Security LLC - Certificate scope: ISMS supporting Omnifact GmbH, Omnifact Platform and Spaces, associated data, infrastructure, software, personnel and procedures, including Microsoft Azure; SoA1.4 dated2026-03-30. - Valid: 2026-04-07 to 2029-04-06 - Registry: https://trust.omnifact.ai/ ### 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 ### omnifact:omnifact: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 ### omnifact:omnifact:widget-rev2 omnifact-widget pinned README. omnifact-widget documents an unsupported demonstration web component with local Storage conversations. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-widget/blob/9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2/README.md - Locator: Pinned README.md documentation at commit 9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-02-06 - Retrieved: 2026-10-21 ### omnifact:omnifact:cli-licence-rev2 omnifact-cli MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-cli/blob/576aea6a6c0ce195de08a1d2b9b385d18efe3d06/LICENSE - Locator: Pinned LICENSE documentation at commit 576aea6a6c0ce195de08a1d2b9b385d18efe3d06; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-05-12 - Retrieved: 2026-10-21 ### omnifact:omnifact:widget-licence-rev2 omnifact-widget MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-widget/blob/9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2/LICENSE - Locator: Pinned LICENSE documentation at commit 9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-02-06 - Retrieved: 2026-10-21 ### omnifact:omnifact:n8n-nodes-omnifact-licence-rev2 n8n-nodes-omnifact MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/n8n-nodes-omnifact/blob/7a3947c620206d4e195064421db525aaa4dfb50a/LICENSE - Locator: Pinned LICENSE documentation at commit 7a3947c620206d4e195064421db525aaa4dfb50a; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-09-10 - Retrieved: 2026-10-21 ### omnifact:omnifact:xwiki-sync-licence-rev2 omnifact-xwiki-sync MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-xwiki-sync/blob/599db2ec0c7f28ddb2a22c4a09a9242e5781316b/LICENSE - Locator: Pinned LICENSE documentation at commit 599db2ec0c7f28ddb2a22c4a09a9242e5781316b; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-08-25 - 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 ### omnifact:omnifact:cli-rev2 omnifact-cli pinned README. omnifact-cli documents document management and conversational CLI commands. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-cli/blob/576aea6a6c0ce195de08a1d2b9b385d18efe3d06/README.md - Locator: Pinned README.md documentation at commit 576aea6a6c0ce195de08a1d2b9b385d18efe3d06; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-05-12 - Retrieved: 2026-10-21 ### dust:dust:support Dust Support. The vendor provides public support entry points and community/documentation resources. - URL: https://dust.tt/home/support - Locator: Support channels - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:rollout Dust Rollout Guide. Public rollout guidance covers setup, launch, team education and measurement. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/dust-rollout-guide/index - Locator: Rollout phases - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:training Team onboarding material. Dust provides reusable team-onboarding material. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/dust-rollout-guide/team-onboarding-material - Locator: Training resources - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-department-guides Dust Use Cases and Guides. Public guides are organized by Sales, Support, Marketing, Engineering, Data, Knowledge, People, Product and Collaboration. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/use-cases-and-guides/index.md - Locator: Use Cases by Department - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-sales-guide Dust Sales use-case guide. The Sales guide provides concrete role-based agent examples; this is public learning material, not a contracted training entitlement. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/use-cases-and-guides/sales.md - Locator: Sales agent examples and build links - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21