--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/omnifact-vs-typingmind/" data_url: "https://onaihq.com/compare/agents/omnifact-vs-typingmind/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # Omnifact vs TypingMind / TypingMind Teams > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 47 criteria with sourced findings for both products, including 47 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - Omnifact source checks: 2026-10-21. - TypingMind / TypingMind Teams source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/omnifact-vs-typingmind/ - Machine-readable JSON: https://onaihq.com/compare/agents/omnifact-vs-typingmind/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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Teams is a customer-key multi-provider chat interface, with dated additions and explicit model selection. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - providers — Which model providers are available? [supported]: Teams admin key setup lists OpenAI, Anthropic, Google, OpenRouter, DeepInfra, DeepSeek, Groq, Mistral, Moonshot, Perplexity, xAI and Z.ai, plus custom providers. Sources: typingmind:typingmind:set-up-api-keys. - current_models — Which current models are selectable on this plan? [partial]: The dated October changelog records Gemini 4 Argon and Muse Wonder on October 14 and Claude Haiku 5.5, Mistral Large 4 and Nano Banana 2.1 on October 9. Actual availability depends on enabled endpoint and customer account; a complete Teams tenant model catalogue was not observed. Sources: typingmind:typingmind:release, typingmind:typingmind:set-up-api-keys. - user_choice — Can users pick the model per chat? [supported]: Users select an available model for a chat; Teams administrators choose which models are exposed. Sources: typingmind:typingmind:manage-ai-models, typingmind:typingmind:restrict-model-access. - 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? The first-party Teams documentation, pricing, legal pages and dated changelog retrieved on 2026-10-21 do not establish this detail; no account or bounded fixture was used. - multimodal_input — Which models accept images, audio or files? [partial]: Document upload, vision-capable model image input and transcription are documented as separate routes; the docs do not provide a complete per-model Teams image/audio/file matrix. Sources: typingmind:typingmind:chat-with-documents, typingmind:typingmind:voice. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:set-up-api-keys, typingmind:typingmind:release, typingmind:typingmind:manage-ai-models, typingmind:typingmind:restrict-model-access, typingmind:typingmind:chat-with-documents, typingmind:typingmind:voice ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated model additions are public; release lag and removal guarantees remain unestablished. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; 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? No matched first-party provider release dates for the last three releases, fixed deprecation-notice period or version-retention guarantee was retrieved. - changelog — Is there a dated public model changelog? [supported]: The public changelog dates model and Teams feature releases through October 14, 2026 in the retrieved page. Sources: typingmind:typingmind:release. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? No matched first-party provider release dates for the last three releases, fixed deprecation-notice period or version-retention guarantee was retrieved. - version_pinning — Can an admin keep an older model version? [partial]: Customer custom-model endpoint configuration can name a provider model or deployment, but a contractual right to retain discontinued SaaS wrappers or provider versions is not established. Sources: typingmind:typingmind:manage-ai-models, typingmind:typingmind:azure-openai. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:release, typingmind:typingmind:manage-ai-models, typingmind:typingmind:azure-openai ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Teams uses customer provider keys; its Custom Admin documentation also describes Claude via the customer AWS Bedrock account. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Starter/Growth/Professional custom-model setup; Bedrock Custom Admin route has no verified exact tier mapping. Separate Teams self-host licence for private endpoint configuration.; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Bedrock is documented for Custom Admin; no all-tier, all-Claude-model or self-host Bedrock entitlement is inferred. Provider-route feature parity was not tested. - own_api_keys — Can the customer use its own provider API keys? [supported]: Admins preset the organization’s provider keys. End users cannot supply separate personal keys in the Teams chat UI. Sources: typingmind:typingmind:set-up-api-keys. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Teams documents Azure OpenAI custom-model setup. Its AWS Bedrock guide explicitly applies to TypingMind Custom Admin at custom.typingmind.com/manage and configures Claude via Bedrock using the customer AWS keys, region and approved model access. Exact Bedrock tier/current-model coverage and Vertex support remain unknown. Sources: typingmind:typingmind:r2-teams-custom-models, typingmind:typingmind:r3-custom-admin-bedrock, typingmind:typingmind:r2-plan-matrix. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [partial]: Teams Admin Panel supports Add Custom Model, naming Azure OpenAI, Hugging Face and Ollama. This does not establish an arbitrary-endpoint compatibility guarantee. Separately, commercial Teams self-host operators can enable otherwise-blocked private/localhost custom endpoints; connectivity and model feature parity were not tested. Sources: typingmind:typingmind:r2-teams-custom-models, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:get-started-with-self-host-installation-instruct. - byo_pricing — Does BYO change the licence price? [supported]: Teams subscription excludes API usage and requires customer keys; BYO is the standard paid model route, not an evidenced licence discount. Sources: typingmind:typingmind:pricing, typingmind:typingmind:set-up-api-keys. - byo_restrictions — Which features stop working with BYO? [partial]: Capabilities depend on the selected model and provider API supporting files, tool use and related features; there is no complete feature-by-provider parity matrix. Sources: typingmind:typingmind:manage-ai-models, typingmind:typingmind:toolbox. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:set-up-api-keys, typingmind:typingmind:r2-teams-custom-models, typingmind:typingmind:r3-custom-admin-bedrock, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:pricing, typingmind:typingmind:manage-ai-models, typingmind:typingmind:toolbox ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Customer model endpoints are supported; optional self-host knowledge uses documented OpenAI embeddings. Availability: generally-available Delivery: native Scope: surfaces=TypingMind personal browser app and PWA, TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Personal app local-model guides; Teams SaaS custom-model setup on Starter/Growth/Professional; separate annual commercial Teams self-host package; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=Personal browser/local network; US/EU Teams SaaS; customer-selected self-host placement and external API routes; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - self_hosted_chat — Can chat use a customer-hosted model? [partial]: Personal typingmind.com has Ollama and LM Studio guides. Teams-specific Admin Panel instructions independently name Ollama custom models, but do not establish the personal local-connection procedure for Teams SaaS. Commercial Teams self-host can explicitly enable private endpoints; no hosted-to-local connectivity fixture was run. Sources: typingmind:typingmind:r2-teams-custom-models, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:ollama, typingmind:typingmind:lmstudio, typingmind:typingmind:get-started-with-self-host-installation-instruct. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [partial]: The optional KB module in the separately quoted annual Teams self-host package requires an OpenAI embeddings key and PostgreSQL pgvector. A customer-hosted embedding substitution is unverified. This is separate from personal local chat models. Sources: typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:cloud-host-vs-self-host. - feature_parity — Which features fail with self-hosted models? [partial]: Toolbox needs a model capable of calling tools; other multimodal capabilities depend on the custom model. Complete parity and failure behaviour are undocumented. Sources: typingmind:typingmind:toolbox, typingmind:typingmind:manage-ai-models. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [unknown]: Does the vendor host open-weight models in EU/CH? No vendor-hosted open-weight EU/CH model service, supported embedding substitution or full self-host-model parity matrix was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:r2-teams-custom-models, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:ollama, typingmind:typingmind:lmstudio, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:toolbox, typingmind:typingmind:manage-ai-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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Professional administrators govern model access and configurable consumption limits. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional for governance; customer-configured limits; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - model_allowlist_by_group — Can admins limit models per group? [supported]: Admins restrict model availability by user group; the limits guide still points availability controls to the legacy model-limits section. Sources: typingmind:typingmind:restrict-model-access, typingmind:typingmind:usage-limits. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: Admins configure the models available to agents and their knowledge access. No content-classification or connector-label-based model egress rule was established. Sources: typingmind:typingmind:roles-and-permissions, typingmind:typingmind:connect-knowledge-base-to-your-ai-agents. - default_model — Can admins set the default model? [unknown]: No Teams administrator control setting the default model for new chats was established. The October multi-model finalization default is a different feature; the plan matrix and model-management documents do not resolve this atom. - user_limits — What per-user message or token limits apply, and are they published? [supported]: Reusable limit groups configure message, character and token limits per time period, across users/groups, models, agents and plugins. Published examples are admin settings, not plan-wide quotas. Sources: typingmind:typingmind:usage-limits. - limit_behaviour — What happens when a limit is reached? [partial]: Users see a configurable limitation notice and can inspect details. Exact block, downgrade, overshoot and reset semantics at exhaustion were not established. Sources: typingmind:typingmind:usage-limits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:restrict-model-access, typingmind:typingmind:usage-limits, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:connect-knowledge-base-to-your-ai-agents ## 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Document text can be attached to chat; full-context training files and RAG are distinct. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - formats — Which formats are accepted? [supported]: The chat guide lists PDF, Markdown, CSV, XLSX, TXT, DOCX, JSON and HTML. Images require a suitable vision model. Sources: typingmind:typingmind:chat-with-documents. - limits — What size and count limits apply per file and chat? [partial]: Chat uploads are bounded by the selected model’s context, but a numeric per-chat file-count/size limit was not established. The separate KB documents 50MB uploads. Sources: typingmind:typingmind:chat-with-documents, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? No scanned-PDF OCR accuracy, spreadsheet-preservation fixture or numerical ordinary-chat upload matrix was established. - spreadsheets — Are Excel tables read with structure intact? [partial]: XLSX and CSV are accepted; Toolbox executes local Python/JavaScript analysis. Preservation of merged cells, formula results and workbook structure was not tested. Sources: typingmind:typingmind:chat-with-documents, typingmind:typingmind:toolbox. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: Ordinary chat document text enters chat context and can later leave the model window; agent training files are injected into system context, while KB access retrieves relevant chunks. These are separate modes. Sources: typingmind:typingmind:chat-with-documents, typingmind:typingmind:training-files-vs-knowledge-base. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:chat-with-documents, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team, typingmind:typingmind:toolbox, typingmind:typingmind:training-files-vs-knowledge-base ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Growth and above provide a tagged organization KB bound to agents; the technical guide still labels it Early Access. Availability: beta Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional: RAG and tagged agent KB; Professional additionally supplies group/resource visibility restrictions; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification. - No source-user permission fixture was run. - persistent_collections — Can users keep document collections across chats? [supported]: The organization KB persists documents and connected data across conversations; this differs from temporary chat uploads and full-context agent training files. Sources: typingmind:typingmind:get-started-with-knowledge-base, typingmind:typingmind:training-files-vs-knowledge-base. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [partial]: Growth/Professional support tagged KB data bound to agents. Per-user/group agent restrictions require Professional governance; these restrictions do not establish per-document source ACL mirroring. Sources: typingmind:typingmind:connect-knowledge-base-to-your-ai-agents, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:r2-plan-matrix. - size_limits — What are the collection limits? [supported]: The KB guide states 50MB per upload and one million included training characters with extra capacity purchasable; indexed chunks are about 3,000 words and retrieval is up to five chunks. Sources: typingmind:typingmind:how-knowledge-base-works-in-typingmind-team. - assistant_binding — Can collections be bound to an assistant? [supported]: Knowledge Base Access in an agent selects tags identifying the accessible data. Sources: typingmind:typingmind:connect-knowledge-base-to-your-ai-agents. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:get-started-with-knowledge-base, typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:connect-knowledge-base-to-your-ai-agents, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team ### 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). #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Named knowledge integrations and extensible tools exist; broad source mentions lack enterprise permission detail. Availability: beta Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional SaaS RAG; separate annual commercial Teams self-host licence with optional KB and customer-managed connector credentials; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification. - A reachable self-host plugin endpoint is not a native file-share crawler. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: The training-files comparison mentions OneDrive as a possible KB source; no retrieved setup guide establishes SharePoint, Outlook or Teams ingestion, permissions or maintenance. Sources: typingmind:typingmind:training-files-vs-knowledge-base. - google_workspace — Which Google sources are connected? [partial]: Growth/Professional SaaS RAG names Google Drive. In the separate commercial Teams self-host package, external KB connectors require the operator’s OAuth configuration. Gmail and the full Workspace source set remain unverified. Sources: typingmind:typingmind:get-started-with-knowledge-base, typingmind:typingmind:setup-external-connectors-for-knowledge-base, typingmind:typingmind:r2-plan-matrix. - atlassian — Confluence and Jira? [unknown]: Confluence and Jira? No first-party Confluence/Jira connector setup, complete M365 connector matrix or maintained on-prem file-share connector was established. - other_systems — Which other business systems? [supported]: KB documentation names Notion and GitHub; admins select Notion pages/databases. Separate MCP/HTTP plugins can query other systems without proving a maintained KB connector. Sources: typingmind:typingmind:get-started-with-knowledge-base, typingmind:typingmind:connect-with-your-notion-pages, typingmind:typingmind:mcp. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Self-host operators can explicitly permit private custom-model/plugin/agent endpoints; custom database actions are described. A supported file-share crawler is not established. Sources: typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:overview. - connector_provider — Who builds and maintains each connector? [partial]: TypingMind documents built-in KB setup; external self-host sources need operator-managed OAuth credentials and Firecrawl for web scraping. MCP servers and custom plugins have separate maintainers. Sources: typingmind:typingmind:setup-external-connectors-for-knowledge-base, typingmind:typingmind:mcp. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:get-started-with-knowledge-base, typingmind:typingmind:setup-external-connectors-for-knowledge-base, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:connect-with-your-notion-pages, typingmind:typingmind:mcp, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:overview ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Documented access control is by tagged knowledge and agent/group visibility; per-user source ACL enforcement is unproven. Availability: beta Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional RAG data/tag selection; Professional adds group-based resource restrictions; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification. - No two-user source-permission or revocation fixture. - source_permissions_respected — Are source permissions enforced per user? [unknown]: Are source permissions enforced per user? No two-user permission/revocation fixture, source ACL mirror, revocation SLA or Microsoft Purview-label enforcement documentation was retrieved. Do not equate agent access with source-user permissions. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [partial]: Growth/Professional bind data tags to agents; Professional adds agent availability by user/group. This application-side mechanism does not establish synchronized source-user ACLs. Sources: typingmind:typingmind:connect-knowledge-base-to-your-ai-agents, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:r2-plan-matrix. - revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? No two-user permission/revocation fixture, source ACL mirror, revocation SLA or Microsoft Purview-label enforcement documentation was retrieved. Do not equate agent access with source-user permissions. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins choose the Notion pages/databases to ingest and select knowledge tags for each agent. Sources: typingmind:typingmind:connect-with-your-notion-pages, typingmind:typingmind:connect-knowledge-base-to-your-ai-agents. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? No two-user permission/revocation fixture, source ACL mirror, revocation SLA or Microsoft Purview-label enforcement documentation was retrieved. Do not equate agent access with source-user permissions. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:connect-knowledge-base-to-your-ai-agents, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:connect-with-your-notion-pages ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial The KB indexes copies, refreshes connected content daily and uses selected SaaS or customer-hosted storage. Availability: beta Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional SaaS RAG; separately quoted annual Teams self-host licence and optional PostgreSQL KB; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification. - No synchronization/deletion latency fixture. - live_or_indexed — Is content searched live or copied into an index? [supported]: RAG splits and embeds copied source text in a knowledge index; full-context training files and live custom tools are separate. Sources: typingmind:typingmind:training-files-vs-knowledge-base. - sync_interval — How often does an index refresh? [supported]: The KB guide describes daily connected-source refresh; Notion initial sync takes a few minutes. Neither is a permission-revocation guarantee. Sources: typingmind:typingmind:how-knowledge-base-works-in-typingmind-team, typingmind:typingmind:connect-with-your-notion-pages. - deletion_propagation — How quickly does a deleted document disappear? [unknown]: How quickly does a deleted document disappear? Deleted-document propagation and exact SaaS index/backup location were not established. - index_location — Where is indexed content stored? [partial]: Opt-in EU SaaS uses Vercel/AWS EU resources; optional self-host KB uses the operator’s PostgreSQL pgvector database and blob configuration. Exact SaaS index, backup and telemetry placement is not itemized. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:get-started-with-self-host-installation-instruct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team, typingmind:typingmind:connect-with-your-notion-pages, typingmind:typingmind:eu-data-center, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:cloud-host-vs-self-host ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Clickable source references are documented, but retrieval quality has no observed multilingual fixture. Availability: beta Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Growth/Professional SaaS RAG and reference display; model-followed instructions separate from retrieval guarantees; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Current plan matrix sells RAG in Growth/Professional, while the technical KB guide (updated2025-11-10) still labels it Early Access. No dated GA transition or tenant rollout was verified; findings retain beta/Early Access qualification. - No shared multilingual/citation-accuracy fixture. - citations — Are answers linked to specific sources? [supported]: Admins may enable reference display for knowledge responses so users can follow source links. Sources: typingmind:typingmind:get-started-with-knowledge-base. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? No shared German/French/English question set, source-support check, cross-language retrieval test or measured answer count 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? No shared German/French/English question set, source-support check, cross-language retrieval test or measured answer count was run. - no_answer_behaviour — Does it say when the corpus has no answer? [partial]: Admins can instruct the model to refrain from answering when knowledge is insufficient; the system-prompt guide gives an example. This is prompt configuration, not a tested no-answer guarantee. Sources: typingmind:typingmind:system-prompts-on-admin-panel. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? No shared German/French/English question set, source-support check, cross-language retrieval test or measured answer count was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:get-started-with-knowledge-base, typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:r2-plan-matrix ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Persistent agent and global admin instructions are documented; named-tier cross-chat memory and its controls remain unknown. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Starter/Growth/Professional instructions and shared agents; exact commercial entitlement for non-project memory and its controls unverified; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Persistent instructions are distinct from learned cross-chat memory. The Memory guide and release do not establish its named-tier entitlement. - custom_instructions — Can users set persistent instructions? [supported]: Persistent agent instructions and global admin instructions are documented; agents can include full-context training files. Sources: typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:training-files-vs-knowledge-base. - cross_chat_memory — Does the product remember facts across chats? [unknown]: The October 14 Teams release and Memory guide describe cross-chat memory, but no named Starter/Growth/Professional entitlement for that capability was established. The Growth/Professional Projects gate does not establish non-project memory availability. - user_memory_controls — Can users view, edit and delete memories? [unknown]: The Memory guide describes saved-memory settings, but their named Teams tier entitlement and complete edit/delete behavior remain unverified. No personal-app control is inferred to be a Teams entitlement. - admin_memory_controls — Can admins turn memory off? [unknown]: The October 14 Teams release describes an admin Memory switch, but the current plan matrix does not map it to a named tier. Organization-wide memory-control entitlement remains unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:release, typingmind:typingmind:memory, typingmind:typingmind:r2-plan-matrix ## 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: supported Teams admins publish agents and prompts, with delegated creation permissions and group access. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Starter/Growth/Professional shared agents and prompts; Growth/Professional RAG; Professional delegated roles and resource visibility; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: All SaaS tiers include shared agents and configured models/plugins; tagged RAG knowledge requires Growth/Professional. Sources: typingmind:typingmind:build-a-shared-ai-agent-collection, typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:r2-plan-matrix. - creator_permissions — Can admins limit who creates them? [supported]: Professional custom roles delegate AI Agent management separately from other Admin Panel permissions. Sources: typingmind:typingmind:roles-and-permissions, typingmind:typingmind:r2-plan-matrix. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: All tiers publish shared agent collections; Professional adds per-user/group resource restrictions. Sources: typingmind:typingmind:build-a-shared-ai-agent-collection, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:r2-plan-matrix. - catalogue — Is there an internal assistant directory? [supported]: The shared agent collection is displayed in the team chat UI. Sources: typingmind:typingmind:build-a-shared-ai-agent-collection. - prompt_library — Are shared prompt templates available? [supported]: All SaaS tiers provide a shared prompt library; Professional adds per-user prompt visibility controls. Sources: typingmind:typingmind:build-a-shared-prompt-library, typingmind:typingmind:r2-plan-matrix. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:build-a-shared-ai-agent-collection, typingmind:typingmind:training-files-vs-knowledge-base, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:build-a-shared-prompt-library ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Built-in plugins and custom HTTP/JavaScript/MCP tools are available; authentication varies by connector. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Starter/Growth/Professional plugins and remote MCP; Professional group restrictions; personal Private MCP Connector route separate; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=Remote server/provider regions depend on configuration; personal local MCP is not a verified Teams local route; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - builtin_tools — Which tools are built in? [supported]: Documented tools include Toolbox, web/deep research, image generation and voice services; optional third-party API keys may be required. Sources: typingmind:typingmind:toolbox, typingmind:typingmind:deep-research, typingmind:typingmind:image, typingmind:typingmind:voice. - custom_actions — Can admins add API actions? [supported]: Custom actions can be implemented as JavaScript, HTTP actions or MCP integrations. Sources: typingmind:typingmind:overview. - mcp_client — Can it use remote MCP servers, and with what admin control? [partial]: Teams pricing lists MCP integration and the MCP guide explicitly gives Team OAuth callbacks and per-user/per-chat sessions for remote HTTP MCP. The Private MCP Connector and local terminal-command procedure are explicitly personal-app routes; Teams local MCP support is unverified. Sources: typingmind:typingmind:mcp, typingmind:typingmind:pricing, typingmind:typingmind:r2-plan-matrix. - tool_auth — Do tools act as the user or as a shared account? [partial]: Teams remote MCP supports user OAuth and per-user sessions; separately configured plugins may use shared keys. The personal Private MCP Connector is not claimed for Teams. Sources: typingmind:typingmind:mcp, typingmind:typingmind:deep-research, typingmind:typingmind:r2-plan-matrix. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Professional admins restrict plugin visibility/usage by group. The MCP guide allows tools to be disabled individually; a mandatory per-action side-effect confirmation policy and Teams local connector are unverified. Sources: typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:mcp, typingmind:typingmind:r2-plan-matrix. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:toolbox, typingmind:typingmind:deep-research, typingmind:typingmind:image, typingmind:typingmind:voice, typingmind:typingmind:overview, typingmind:typingmind:mcp, typingmind:typingmind:pricing, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:restrict-plugin-access ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Deep Research is a configurable search/read/report plugin with separate provider accounts. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams plugin access on Starter/Growth/Professional; Professional for group availability/limits; add_ons=Customer SerpAPI and Firecrawl keys; model API charges; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web_search — Is web search available? [supported]: The Deep Research plugin performs iterative web search and page reading. Sources: typingmind:typingmind:deep-research. - admin_toggle — Can admins disable it per organisation or group? [supported]: Professional admins restrict the research/search plugin to selected user groups through Plugin Access and Limits. Sources: typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix. - search_provider — Which search provider handles queries, and where? [partial]: This plugin requires SerpAPI for search and Firecrawl for page retrieval; processing countries for queries/content were not established. Sources: typingmind:typingmind:deep-research. - deep_research — Is multi-step research with a report available? [supported]: The plugin plans and iterates search/reading into a report, within its documented two-minute execution bound. Sources: typingmind:typingmind:deep-research. - web_citations — Are web sources cited? [partial]: The research plugin produces a sourced report, but link completeness and citation accuracy were not independently checked. Sources: typingmind:typingmind:deep-research. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:deep-research, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial The documented automation layer uses agents and plugins rather than an established visual scheduling system. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, TypingMind Teams REST API; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams plugins/agents on Starter/Growth/Professional; Professional external REST API integration; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - workflow_builder — Is there a workflow or chain builder? [partial]: Docs describe composing AI interactions with JavaScript/HTTP/MCP plugins and business automation examples. A visual DAG/chain builder was not established. Sources: typingmind:typingmind:overview. - scheduled_tasks — Can prompts or assistants run on a schedule? [unknown]: Can prompts or assistants run on a schedule? No native recurring scheduler, durable workflow engine or supported event trigger setup was established. - event_triggers — Can external events start a workflow? [partial]: Professional external REST integration lets an external application call a Teams chat/agent API. This is a developer invocation route, not an established native managed trigger engine. Sources: typingmind:typingmind:api-integration-overview, typingmind:typingmind:r2-plan-matrix. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Team users use shared agents; technical builders configure JavaScript/HTTP plugins and credentials. Professional custom roles delegate administration, and its API supports developer integrations. Sources: typingmind:typingmind:overview, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:r2-plan-matrix. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:overview, typingmind:typingmind:api-integration-overview, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:roles-and-permissions ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Multi-step tool workflows exist; universal side-effect confirmation and run controls remain unproven. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: The Deep Research plugin repeatedly searches/reads, and automation docs describe tool-driven multistep business actions. Sources: typingmind:typingmind:deep-research, typingmind:typingmind:overview. - visible_steps — Are steps and tool calls shown? [partial]: The research workflow is described as iterative search and page reading, but a complete visible execution trace for all agents/tools was not established. Sources: typingmind:typingmind:deep-research. - side_effect_confirmation — Must the user confirm actions with side effects? [unknown]: Must the user confirm actions with side effects? No bounded run verified visible traces, stop behaviour, rollback or mandatory side-effect confirmation for all custom tools. - stop_control — Can the user stop a running task? [unknown]: Can the user stop a running task? No bounded run verified visible traces, stop behaviour, rollback or mandatory side-effect confirmation for all custom tools. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:deep-research, typingmind:typingmind:overview ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial The Teams REST API creates chat/agent responses with governed api-users. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams REST API; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional API integration; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - chat_api — Is there an API for chat and assistants? [supported]: Teams REST endpoints produce model or agent responses, including configured plugins, KB and MCP capabilities. Sources: typingmind:typingmind:api-integration-overview. - knowledge_api — Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? The retrieved API overview did not establish a supported knowledge-upload API or an MCP server exposing TypingMind itself. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: An API key creates an api-user subject to the same user restrictions and usage limits. Complete audit coverage, currency budgets and all API routes were not established. Sources: typingmind:typingmind:api-integration-overview. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? The retrieved API overview did not establish a supported knowledge-upload API or an MCP server exposing TypingMind itself. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:api-integration-overview ## 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial The primary client is a browser app; installable PWAs are documented separately from native apps. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Starter/Growth/Professional browser chat; PWA installation findings only for personal typingmind.com (licence feature gates separate); add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web — Is a full web client available? [supported]: Teams supplies a branded browser chat interface and separate Admin Panel. Sources: typingmind:typingmind:typingmind-vs-typingmind-team. - desktop_apps — Windows and macOS apps? [partial]: The personal typingmind.com app has browser-PWA installation instructions for Windows/macOS; this is not evidence of a Teams native desktop app or Teams PWA deployment entitlement. Sources: typingmind:typingmind:install, typingmind:typingmind:r2-personal-bulk-licence. - mobile_apps — iOS and Android apps with SSO? [partial]: Personal typingmind.com can be added to iOS/Android home screens as a browser PWA. Teams Professional SSO is a separate entitlement; no Teams installable mobile client or mobile SSO fixture was verified. Sources: typingmind:typingmind:install, typingmind:typingmind:r2-personal-bulk-licence, typingmind:typingmind:r2-plan-matrix. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? No MDM packaging/configuration, supported browser sidebar/extension or mobile feature-parity matrix was established. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? No MDM packaging/configuration, supported browser sidebar/extension or mobile feature-parity matrix was established. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? No MDM packaging/configuration, supported browser sidebar/extension or mobile feature-parity matrix was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:typingmind-vs-typingmind-team, typingmind:typingmind:install, typingmind:typingmind:r2-personal-bulk-licence, typingmind:typingmind:r2-plan-matrix ### 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. #### 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 #### TypingMind / TypingMind Teams 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-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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Configurable model instructions support writing workflows; dedicated translation fidelity is unestablished. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; 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? No whole-document formatting-preserving translation fixture, company glossary engine or Swiss language-quality test was retrieved. - translation_engine — Which engine translates? [partial]: Writing/translation prompts are handled by the customer-selected LLM; no separate translation engine or formatting-preserving document pipeline was established. Sources: typingmind:typingmind:manage-ai-models, typingmind:typingmind:system-prompts-on-admin-panel. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? No whole-document formatting-preserving translation fixture, company glossary engine or Swiss language-quality test was retrieved. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Global and agent instructions can specify tone and language, but no dedicated de-CH/formality switch or quality guarantee was established. Sources: typingmind:typingmind:system-prompts-on-admin-panel. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Shared prompts and marketing-writing workflows support rewriting tasks; a dedicated proofreading interface and correction-quality fixture were not established. Sources: typingmind:typingmind:build-a-shared-prompt-library, typingmind:typingmind:ad-creative-generator. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:manage-ai-models, typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:build-a-shared-prompt-library, typingmind:typingmind:ad-creative-generator ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial GPT Image generation and editing use customer API credentials and controllable plugins. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams plugin access on Starter/Growth/Professional; Professional for group-based image-plugin governance; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - image_generation — Can users generate images, with which models? [supported]: The GPT Image 2.5 plugin documents image generation through the customer’s OpenAI API. Sources: typingmind:typingmind:image. - image_editing — Can users edit uploaded images? [supported]: The October 2 changelog says GPT Image editing accepts any image in a chat, including attachments and artifact images. Sources: typingmind:typingmind:release, typingmind:typingmind:image. - admin_control — Can admins restrict image generation? [partial]: Professional admins restrict the image plugin by user group. Coverage of every provider-native image route remains unverified. Sources: typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix. - usage_terms — What usage rights apply to output? [partial]: The Terms say users own their content, subject to provider terms. No independent clearance of third-party rights or all model-provider output licences was performed. Sources: typingmind:typingmind:terms-of-service. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:image, typingmind:typingmind:release, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:terms-of-service ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dictation, read-aloud and audio-summary workflows are documented; live meetings and Swiss German quality are unknown. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dictation — Can users dictate prompts? [supported]: Dictation uses browser speech recognition or customer OpenAI Whisper, Groq or Azure transcription credentials; Teams admins configure keys. Sources: typingmind:typingmind:voice. - read_aloud — Can answers be read aloud? [supported]: Browser speech, ElevenLabs or OpenAI TTS reads answers aloud with playback/autoplay controls. Sources: typingmind:typingmind:tts. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? No full-duplex live voice mode, Swiss German audio fixture or native meeting-attendance integration was established. - meeting_summaries — Are meetings transcribed and summarised? [partial]: The meeting-summarizer workflow uses recorded audio transcription and LLM summaries; Whisper upload is capped at 25MB. No live meeting bot or diarization quality test was established. Sources: typingmind:typingmind:meeting-summarizer, typingmind:typingmind:voice. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? No full-duplex live voice mode, Swiss German audio fixture or native meeting-attendance integration was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:voice, typingmind:typingmind:tts, typingmind:typingmind:meeting-summarizer ### 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. #### 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. #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: supported Toolbox executes code locally and produces charts and Office documents; Growth includes Canvas. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Growth/Professional for Canvas; Toolbox on tool-capable models with separate API usage; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. - data_analysis — Can it analyse spreadsheets with executed code? [supported]: Toolbox runs Python/JavaScript in the browser, including tabular analysis libraries. Network is disabled by default; analysis is not a vendor EU code-execution guarantee. Sources: typingmind:typingmind:toolbox. - charts — Can it produce charts? [supported]: Toolbox supports chart generation with Plotly and Bokeh. Sources: typingmind:typingmind:toolbox. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Toolbox creates/edits documents, spreadsheets, presentations and PDFs, including Office formats. Sources: typingmind:typingmind:toolbox. - canvas_editing — Is there a document or canvas editor for iterating on output? [supported]: The Teams plan comparison lists Canvas and Artifacts for Growth and Professional. Sources: typingmind:typingmind:compare-typingmind-team-plans. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:toolbox, typingmind:typingmind:compare-typingmind-team-plans ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared agents and prompt libraries are documented, but collaborative project/chat boundaries are not established. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - share_chats — Can chats be shared inside the organisation? [unknown]: Can chats be shared inside the organisation? No Teams-specific shared-chat recipient ACL/redaction guarantee, simultaneous multi-person AI conversation or source-permission sharing fixture was established. - team_spaces — Are shared projects or workspaces available? [partial]: Teams share an agent catalogue and prompt library; project-scoped memory is documented. Shared project membership and cross-user workspace semantics were not established. Sources: typingmind:typingmind:build-a-shared-ai-agent-collection, typingmind:typingmind:build-a-shared-prompt-library, typingmind:typingmind:release. - group_chat — Can several people chat together with the AI? [unknown]: Can several people chat together with the AI? No Teams-specific shared-chat recipient ACL/redaction guarantee, simultaneous multi-person AI conversation or source-permission sharing fixture was established. - share_permission_boundary — Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? No Teams-specific shared-chat recipient ACL/redaction guarantee, simultaneous multi-person AI conversation or source-permission sharing fixture was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:build-a-shared-ai-agent-collection, typingmind:typingmind:build-a-shared-prompt-library, typingmind:typingmind:release ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Multilingual capability is advertised without a verified DACH UI or accessibility matrix. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - ui_languages — Which UI languages are offered? [partial]: Teams plan documentation advertises a multilingual chat interface and a public translation collaboration project exists. A complete current language list was not established. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:translations. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? No complete German/French/Italian UI review, German Admin Panel guarantee, WCAG conformance statement or assistive-technology fixture was retrieved. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? No complete German/French/Italian UI review, German Admin Panel guarantee, WCAG conformance statement or assistive-technology fixture was retrieved. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? No complete German/French/Italian UI review, German Admin Panel guarantee, WCAG conformance statement or assistive-technology fixture was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:translations ## 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Teams Professional provides SAML SSO and OAuth/OIDC options. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional identity features; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML SSO accepts IdP metadata and multiple connections; OAuth/OIDC includes Microsoft, Google and custom provider configuration. Sources: typingmind:typingmind:sso, typingmind:typingmind:o-auth-2-0. - sso_plan — Which plan includes SSO? [supported]: The plan comparison places SSO/OAuth and Directory Sync in Professional. Sources: typingmind:typingmind:compare-typingmind-team-plans. - mfa — Can MFA be enforced? [partial]: The DPA security measures mention MFA and SSO; documented tenant-level enforcement settings and IdP MFA propagation were not verified. Sources: typingmind:typingmind:data-processing-agreement. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? No Entra conditional-access test or verified-domain capture/mandatory login policy was established. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? No Entra conditional-access test or verified-domain capture/mandatory login policy was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:sso, typingmind:typingmind:o-auth-2-0, typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:data-processing-agreement ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Professional supports SCIM, group sync and JIT; OAuth revocation alone does not remove a seat. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional Directory Sync; distinguish SCIM suspension from OAuth revocation; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - scim — Is SCIM provisioning supported? [supported]: SCIM v2 creates, updates and suspends users from a compatible IdP. Sources: typingmind:typingmind:scim. - group_sync — Are identity-provider groups synced? [supported]: Directory Sync assigns users to corresponding groups received from the identity provider. Sources: typingmind:typingmind:scim. - jit_provisioning — Are users created at first login? [supported]: OAuth login can create a user on first sign-in and consumes an available seat; creation fails without a free seat. Sources: typingmind:typingmind:o-auth-2-0. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: SCIM suspends users; separate OAuth docs warn that revoking IdP authorization alone does not remove an existing user, requiring admin removal. Shared asset ownership, deletion and session-revocation timing are not established. Sources: typingmind:typingmind:scim, typingmind:typingmind:o-auth-2-0. - seat_assignment — Can admins assign and reclaim seats? [partial]: Admins invite/manage users and JIT consumes purchased seats. Exact seat reclamation timing, licence proration and asset transfer were not established. Sources: typingmind:typingmind:invite-team-members, typingmind:typingmind:o-auth-2-0. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:scim, typingmind:typingmind:o-auth-2-0, typingmind:typingmind:invite-team-members ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Custom admin roles and user groups provide delegated management and feature availability controls. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional custom roles, resource groups and usage limits; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; 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]: Default Admin has highest permissions. Owners create custom roles for models, plugins, agents, reporting, billing, users, keys, KB and portal settings. Users may hold multiple roles; the former Content Moderator preset was removed. Sources: typingmind:typingmind:roles-and-permissions. - groups — Can permissions be set per group? [supported]: User groups govern resource visibility and limits. Admin roles are assigned to individual members; assigning roles to groups is still described as coming soon. Sources: typingmind:typingmind:roles-and-permissions, typingmind:typingmind:create-and-manage-user-groups. - feature_toggles — Which features can be switched on or off per group? [supported]: Professional provides model, agent and plugin group availability/usage controls through resource Access/Limit settings; the plan matrix separately lists per-user prompt visibility. CSS/themes are excluded from this permission finding. Sources: typingmind:typingmind:restrict-model-access, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix. - multi_entity — Can subsidiaries or departments be separated within one contract? [unknown]: Can subsidiaries or departments be separated within one contract? No multi-subsidiary legal/entity separation, independent subtenant keys or consolidated contract administration was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:roles-and-permissions, typingmind:typingmind:create-and-manage-user-groups, typingmind:typingmind:restrict-model-access, typingmind:typingmind:restrict-ai-agents-access, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Teams analytics reports adoption and consumption, including identifiable user breakdowns. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional analytics; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - adoption_dashboard — Is there an adoption dashboard? [supported]: Dashboard counts active users, messages, conversations, characters and estimated tokens over a selected period. Sources: typingmind:typingmind:chatbot-analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [supported]: Reporting filters by user, group, model and agent; a complete per-feature cost map was not established. Sources: typingmind:typingmind:chatbot-analytics. - export — Can usage data be exported? [partial]: Charts can be downloaded; a complete raw usage ledger export format was not established. Sources: typingmind:typingmind:chatbot-analytics. - privacy_modes — Can per-person reporting be limited or pseudonymised? [unknown]: Can per-person reporting be limited or pseudonymised? No pseudonymised reporting mode or enforceable per-person aggregation threshold was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:chatbot-analytics ### ADM-05: Spend controls and cost allocation Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins can inspect estimated consumption and set token/message limits; monetary budgets are unestablished. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional; API charges billed directly by customer providers; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Analytics shows estimated token and character usage per user/group/model/agent. Customer model bills remain external; reconciled currency cost is not established. Sources: typingmind:typingmind:chatbot-analytics. - budgets — Can budgets be set per user or group? [partial]: Admins configure reusable token/message/character limits for users/groups and resources, rather than an evidenced currency-denominated budget. Sources: typingmind:typingmind:usage-limits. - budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: Users are shown applicable limits, but hard monetary blocking, alerts, downgrade and in-flight overshoot semantics were not established. Sources: typingmind:typingmind:usage-limits. - chargeback — Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? No cost-centre chargeback ledger or exact monetary budget-enforcement documentation was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:chatbot-analytics, typingmind:typingmind:usage-limits ### ADM-06: Audit logs and compliance export Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Optional chat recording exposes prompts and answers to authorized admins with retention and JSON export. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional chat logs; logging must be enabled; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - admin_events — Are admin and security events logged? [unknown]: Are admin and security events logged? No first-party security/admin event catalogue, legal hold or eDiscovery workflow was established. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [supported]: Record all chats is opt-in and off by default; authorized Admin Panel roles can view saved user prompts and model responses. Sources: typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:export-chat-logs, typingmind:typingmind:roles-and-permissions. - siem_export — Can logs stream to a SIEM or be exported? [partial]: An API exports recorded chats as JSON, last 100 matching conversations per request with date filtering. Native SIEM streaming and complete audit-event export were not established. Sources: typingmind:typingmind:export-chat-logs. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? No first-party security/admin event catalogue, legal hold or eDiscovery workflow was established. - log_retention — How long are logs kept? [partial]: Admins set chat retention and old records are permanently deleted. A default duration and separate admin/security log retention were not established. Sources: typingmind:typingmind:view-and-export-user-chat-logs. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:export-chat-logs, typingmind:typingmind:roles-and-permissions ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### ADM-08: AI policy and guardrails Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Global instructions can govern chat behaviour, but policy acceptance and violation reporting remain unknown. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS global instructions; Professional for group/resource plugin restrictions; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - org_instructions — Can admins set organisation-wide instructions? [supported]: Admins set hidden global system instructions, few-shot examples and post-message reminders across chats and agents. Sources: typingmind:typingmind:system-prompts-on-admin-panel. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? No mandatory policy-acceptance record, enforcement-grade content filter or admin policy-hit report was established. - content_filters — Are content filters configurable? [partial]: Admins configure model-followed instructions; Professional separately restricts plugin availability by group. Neither establishes deterministic PII/content filtering or a policy-enforcement engine. Sources: typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? No mandatory policy-acceptance record, enforcement-grade content filter or admin policy-hit report was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:system-prompts-on-admin-panel, typingmind:typingmind:restrict-plugin-access, typingmind:typingmind:r2-plan-matrix ## 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial EU SaaS storage is optional; inference, tools and support are separate residency questions. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - storage_region — Where are chats, files and indexes stored? [partial]: Teams offers US and opt-in EU instances. The EU guide names Vercel web hosting and AWS database resources; exact file/index/backup components are not fully enumerated. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:privacy-policy. - inference_region — Where do model calls run, per provider? [supported]: The EU guide explicitly warns model calls may go outside the EU. Customers can choose an EU Azure endpoint or private/local model; this is not an all-provider EU inference promise. Sources: typingmind:typingmind:eu-data-center. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? Backup, telemetry, support-access country matrix and contractual Swiss-only end-to-end processing were not established. - support_access_region — From where can vendor staff access data? [partial]: The DPA identifies the processor at a Da Nang, Vietnam address and requires need-to-know confidentiality; actual operational staff access countries and restrictions were not established. Sources: typingmind:typingmind:data-processing-agreement. - swiss_hosting — Is Swiss hosting available? [partial]: Customer self-host can run on operator-selected infrastructure, but no vendor-operated Swiss SaaS region or complete CH-only processing undertaking was established. Sources: typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct. - residency_plan — Which plan or option provides residency? [supported]: The EU instance is an account/instance choice for Teams SaaS. Self-host is a separate quoted annual commercial licence, not the personal licence. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:selfhost. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:privacy-policy, typingmind:typingmind:data-processing-agreement, typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Teams offers multitenant SaaS and a separate commercial self-host package; offline operation is not established. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Marketing language about data staying on customer infrastructure must be read with model, embedding, licence and update egress requirements. - multi_tenant_saas — Is a shared SaaS offered? [supported]: The privacy policy explicitly describes Teams as server-stored multitenant SaaS, unlike the default local-storage personal app. Sources: typingmind:typingmind:privacy-policy. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [partial]: Self-host permits one customer-operated instance with five included users. A separate vendor-operated dedicated SaaS service and its minimum were not established. Sources: typingmind:typingmind:selfhost. - customer_cloud — Can it run in the customer's own cloud account, from what size? [supported]: A quoted self-host licence runs the NodeJS service, MySQL, optional PostgreSQL KB and blob store in the customer’s cloud account. Sources: typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct. - on_premise — Can the whole platform run on customer infrastructure, from what size? [supported]: The self-host package can run on customer infrastructure with Docker/NodeJS and required databases; five users and one instance are included under the annual quote. Sources: typingmind:typingmind:selfhost. - air_gapped — Can it run without internet access? [partial]: The self-host FAQ lists external model requests plus update and licence checks. Private models reduce model egress, while the optional KB guide still requires OpenAI embeddings. A supported air-gapped licence was not established. Sources: typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct. - mode_feature_gaps — Which features are missing outside SaaS? [supported]: Self-host releases lag cloud by approximately one to three weeks; optional KB needs additional infrastructure, external OAuth setup and OpenAI embeddings. SLA/dedicated support is a separate paid option. Sources: typingmind:typingmind:selfhost, typingmind:typingmind:setup-external-connectors-for-knowledge-base, typingmind:typingmind:get-started-with-self-host-installation-instruct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:privacy-policy, typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:setup-external-connectors-for-knowledge-base ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial TypingMind asserts no vendor training; customer provider contracts control training and retention. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - vendor_training — Does the vendor train on customer content? [supported]: The published policy says TypingMind does not use conversations for AI training. This is a vendor policy assertion, not an independently verified contract-wide audit. Sources: typingmind:typingmind:data-usage-and-model-training-policy. - provider_training — Do model providers train on it under this product's contracts? [partial]: Teams uses customer provider keys and direct customer provider contracts. The policy summarizes provider-specific training defaults; this pass did not verify every provider contract or free/paid API variant. Sources: typingmind:typingmind:set-up-api-keys, typingmind:typingmind:data-usage-and-model-training-policy. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: The policy discusses provider-dependent abuse monitoring, retention and paid/unpaid distinctions; no uniform current retention duration applies to every customer-selected route. Sources: typingmind:typingmind:data-usage-and-model-training-policy. - zero_retention — Is zero data retention available, and on which plan? [partial]: A customer may select a provider/endpoint with suitable terms, but no TypingMind-wide ZDR entitlement, plan or complete exception matrix was established. Sources: typingmind:typingmind:data-usage-and-model-training-policy, typingmind:typingmind:eu-data-center. - human_review — Can provider staff review content? [partial]: TypingMind’s provider summary says OpenAI authorized employees may review API data for abuse/legal compliance. Its Gemini section distinguishes paid no-training from unpaid improvement use and says human reviewers may read/annotate/process inputs and outputs for quality improvement. These are qualified vendor summaries, not verified terms for every customer paid/unpaid endpoint, ZDR approval or actual account. Sources: typingmind:typingmind:data-usage-and-model-training-policy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:data-usage-and-model-training-policy, typingmind:typingmind:set-up-api-keys, typingmind:typingmind:eu-data-center ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins control recorded chat retention; termination deletion/return is contractual without a fixed public completion window. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional for admin chat recording/retention; general service privacy/DPA rights separate from personal/local history; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; 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]: Professional admin chat recording is off by default; that is separate from user-visible history and personal browser storage. The privacy policy separately mentions90-day unpaid-account inactivity deletion with warning; a paid Teams history lifetime is not specified. Sources: typingmind:typingmind:export-chat-logs, typingmind:typingmind:privacy-policy, typingmind:typingmind:r2-plan-matrix. - admin_retention — Can admins set retention periods? [supported]: Professional chat-log settings set recorded-chat retention, with permanent deletion of older records. No personal/local or backup deletion interval is inferred. Sources: typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:r2-plan-matrix. - user_deletion — Can users delete their chats and files permanently? [partial]: The privacy policy provides data-erasure rights; immediate permanent deletion across Teams files, backups and logs by the user UI was not established. Sources: typingmind:typingmind:privacy-policy. - contract_end_deletion — What is deleted at contract end, and when? [partial]: The DPA permits customer-choice deletion or return and certification on request, subject to legal retention; a fixed completion deadline and self-serve export window are not specified. Sources: typingmind:typingmind:data-processing-agreement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:export-chat-logs, typingmind:typingmind:privacy-policy, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:data-processing-agreement ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial A public DPA lists processors and transfer measures; vendor legal jurisdiction differs from hosting region. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - subprocessor_list — Is a dated sub-processor list published? [partial]: DPA Appendix II publishes a subprocessor list; no standalone dated list revision was visible in the retrieved document. Sources: typingmind:typingmind:data-processing-agreement. - subprocessor_countries — Which countries do sub-processors operate in? [supported]: The list includes AWS US/Germany, Render US, Vercel US/EU, US services including Sentry/Axiom/Customer.io/Stripe/HelpScout/Mailgun and Paddle US/UK. EU storage does not remove these separate vendor paths. Sources: typingmind:typingmind:data-processing-agreement. - change_notification — Are customers notified of sub-processor changes? [supported]: DPA 7.8 says the processor will endeavor to give 30 days’ notice of additions/replacements, with 15 days for objections; preserve the qualified notice wording. Sources: typingmind:typingmind:data-processing-agreement. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: Terms identify Typing Technology Co Ltd with Singapore governing law; the DPA gives a Vietnam processor address. Parent ownership/jurisdiction and actual staff locations were not independently established. Sources: typingmind:typingmind:terms-of-service, typingmind:typingmind:data-processing-agreement. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA 7.9 and its SCC appendix provide EU transfer safeguards, subject to actual processing configuration; a Swiss-specific addendum was not established. Sources: typingmind:typingmind:data-processing-agreement. - government_access_policy — Is there a published government-access or transparency policy? [partial]: The privacy policy allows disclosures for authorized legal requests; no separate transparency report or detailed government-request policy was retrieved. Sources: typingmind:typingmind:privacy-policy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:data-processing-agreement, typingmind:typingmind:terms-of-service, typingmind:typingmind:privacy-policy ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial A public GDPR DPA and Singapore-law business terms are available; Swiss and sector-specific undertakings remain gaps. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dpa — Is a DPA available, and is it negotiable? [partial]: A public fillable GDPR Article 28 DPA names the processor, security measures and SCCs. Whether bespoke negotiation is available was not established. Sources: typingmind:typingmind:data-processing-agreement. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: The DPA expressly addresses GDPR and SCCs; explicit revised Swiss FADP/revDSG coverage was not established. Sources: typingmind:typingmind:data-processing-agreement. - governing_law — Which law and court govern the contract? [supported]: The September 17, 2026 Terms use Singapore law, with SIAC English-language business arbitration; the DPA SCC appendix separately uses EU exporter-state law/forum where applicable. Sources: typingmind:typingmind:terms-of-service, typingmind:typingmind:data-processing-agreement. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? No EU AI Act compliance package, FINMA outsourcing materials or dedicated professional-secrecy agreement was retrieved. - sector_materials — Are FINMA or other sector materials provided? [unknown]: Are FINMA or other sector materials provided? No EU AI Act compliance package, FINMA outsourcing materials or dedicated professional-secrecy agreement was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:data-processing-agreement, typingmind:typingmind:terms-of-service ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial The self-host page claims SOC 2 Type II. A report with auditor, period and covered-service scope was not retrieved, and other attestations remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Commercial self-hosted TypingMind Teams server; version=Public self-host page retrieved 2026-10-26; no certificate verified; plan=Commercial Teams self-host marketing assurance claim; no customer report or SaaS certificate scope inferred; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Vendor assertion only. No independently verified report, certificate scope or validity was accessed; trust.typingmind.com returned HTTP 403. - iso_27001 — ISO 27001 with scope and validity? [unknown]: ISO 27001 with scope and validity? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved. - soc2 — SOC 2 type, period and covered service? [partial]: The vendor advertises SOC 2 Type II on the Teams self-host page. Auditor, report period, covered entity/service and applicability to a customer-operated deployment are unverified. Sources: typingmind:typingmind:r4-soc2-selfhost-claim. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved. - report_access — How can customers obtain reports? [unknown]: How can customers obtain reports? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved. - pentest — Are independent penetration test summaries available? [unknown]: Are independent penetration test summaries available? Trust Center access returned HTTP 403. The retrieved DPA security appendix is not an ISO/SOC/C5 certificate. Issuer, service scope, validity/report period, report-access process and independent penetration-test summary were not retrieved. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: typingmind:typingmind:r4-soc2-selfhost-claim ### 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). #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Encryption and private self-host infrastructure are documented without a SaaS customer-key guarantee. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS US/EU storage; separately quoted annual Teams self-host network controls; personal local-key claims explicitly separate; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Teams OpenAI route: server requests using centrally configured admin keys. Personal direct-browser/local-key assertions are not inherited by Teams. - The generic policy versus Teams FAQ scope discrepancy remains visible pending policy clarification. - encryption_at_rest — Is data encrypted at rest? [partial]: The EU guide says stored information is encrypted; exact cipher, key ownership and component coverage were not established. Personal optional cloud encryption is a different surface. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:privacy-policy. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? No Teams SaaS customer-managed/held encryption-key option or complete private-connectivity configuration was established. - private_networking — Is private connectivity or IP restriction available? [partial]: Self-host permits customer network placement; localhost/private custom endpoints require ALLOW_UNSAFE_USER_ENDPOINTS. SaaS private links, IP allowlisting and private model routing were not established. Sources: typingmind:typingmind:get-started-with-self-host-installation-instruct. - tenant_isolation — How are customers separated in shared SaaS? [partial]: The privacy policy calls Teams multitenant; logical isolation implementation and independent tenant-boundary testing were not established. Sources: typingmind:typingmind:privacy-policy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:eu-data-center, typingmind:typingmind:privacy-policy, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:r2-teams-server-route ### 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. #### 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. #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial General GDPR confidentiality and configurable admin/model access are documented; a specific §203 or Art321 undertaking is unverified. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Professional chat governance and separately quoted self-host licence; ordinary public DPA; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US/EU SaaS or customer self-host placement; customer provider contracts separate; os=not specified. Limitations: - DPA confidentiality, direct provider contracts and self-host placement alone do not establish professional-secrecy suitability. - 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]: DPA7.4(c) limits personnel access and requires confidentiality/statutory duties. No signed/signon §203 StGB or Art321 StGB professional-secrecy undertaking was retrieved; ordinary GDPR confidentiality is not treated as that agreement. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: DPA7.8(d)-(e) requires substantially equivalent data-protection obligations and allows a redacted subprocessor agreement on request. A dedicated professional-secrecy undertaking flowing to subprocessors was not established. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No specific professional-secrecy package/add-on or SaaS/self-host plan entitlement was established. Customer-operated infrastructure and the commercial self-host licence do not by themselves prove that undertaking. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: SaaS authorized personnel may access data only as needed under the DPA; customer admins with chat-log permission may inspect recorded prompts/answers when logging is enabled. Selected customer API providers process content; self-host placement changes operator access but model/embedding/blob routes remain relevant. A complete plaintext support/subprocessor/provider human-access matrix was not retrieved. Sources: typingmind:typingmind:dpa-confidentiality, typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:set-up-api-keys, typingmind:typingmind:get-started-with-self-host-installation-instruct. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public DPA, security appendix, processor list and self-host data-flow guides were retrieved. Targeted first-party search did not establish a professional-secrecy contract template, DE/CH-specific data-flow addendum or professional-body guidance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:dpa-confidentiality, typingmind:typingmind:view-and-export-user-chat-logs, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:set-up-api-keys, typingmind:typingmind:get-started-with-self-host-installation-instruct ## 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Teams subscriptions, personal one-time licences and self-host annual quotes are separate cost structures. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams SaaS Starter/Growth/Professional/quoted Business; separate annual Teams self-host quote; personal Standard/Extended/Premium one-time licences and separate bulk pack; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - pricing_unit — What is the pricing unit? [supported]: Teams SaaS uses recurring instance/seats billing; commercial Teams self-host is an annual quoted licence per instance. Personal one-time licences, including the separate shareable bulk pack, do not establish a Teams administration entitlement. Sources: typingmind:typingmind:pricing, typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:r2-personal-bulk-licence. - list_prices — What are list prices per plan, with date and currency? [supported]: As retrieved October 21, annual-selected landing cards display USD83/166/249 per month Starter/Growth/Professional (Professional crossed-out USD499). The documentation’s monthly table lists USD99/199/299 plus USD8/additional user/month. Business starts USD18,700/year by quote; conditional “as low as USD4/user/month” is not a universal rate. Sources: typingmind:typingmind:pricing, typingmind:typingmind:compare-typingmind-team-plans. - included_usage — What usage is included? [supported]: All SaaS tiers include five users and unlimited configured models/agents/plugins/prompts, excluding provider API usage. One million KB training characters belongs to the Growth/Professional RAG guide, still labeled Early Access; no Starter KB allowance is inferred. Sources: typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team. - add_ons — Which features cost extra? [supported]: Additional seats, KB character capacity, model APIs and third-party plugin services are separate; self-host SLA/dedicated support is an add-on. Sources: typingmind:typingmind:pricing, typingmind:typingmind:selfhost, typingmind:typingmind:deep-research. - overage — What do usage beyond limits and premium models cost? [partial]: Model usage is billed by the customer’s chosen provider. No unified TypingMind premium-model tariff applies; extra KB capacity and Business/self-host scope require current checkout or quote. Sources: typingmind:typingmind:pricing, typingmind:typingmind:set-up-api-keys. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:pricing, typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:r2-personal-bulk-licence, typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:how-knowledge-base-works-in-typingmind-team, typingmind:typingmind:selfhost, typingmind:typingmind:deep-research, typingmind:typingmind:set-up-api-keys ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial A conditional Professional monthly licence-plus-BYOK floor is calculable; Business and self-host totals remain unknown. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Conditional documented Professional monthly list route; not a large-scale quote; add_ons=Model usage proxy; other add-ons unknown; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Known price floor plus explicitly unpriced parts; no complete year-one TCO or negotiated price claim. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: 12 months ex VAT, 60% light100/30% regular400/10% power1500 messages per user/month, hence330; 3000 input+600 output tokens/message. Conditional undiscounted Teams Professional monthly route USD299 + USD8*(N−5) monthly, not the annual promotion or a Business quote. Direct-provider BYOK proxy gpt-6-luna, reasoning effort none, Standard short context USD0.10 input/USD0.50 output per million; no cache => USD2.376/user/year. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD/EUR divide1.1215, EUR/CHF multiply0.9237. For200 users: licence USD22,308 + model proxy USD475.20 = from USD22,783.20 / EUR20,314.94 / CHF18,764.91 + unknown components. Not a 200-seat quote. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:pricing, typingmind:typingmind:openai-price, typingmind:typingmind:openai-model, typingmind:typingmind:fx. - cost_1000 — Year-one cost at 1,000 users? [partial]: Same assumptions:1000 users licence USD99,108 + model USD2,376 = from USD101,484 / EUR90,489.52 / CHF83,585.17 + unknown components. Scale entitlement and negotiated Business alternative unverified. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:pricing, typingmind:typingmind:openai-price, typingmind:typingmind:openai-model, typingmind:typingmind:fx. - cost_5000 — Year-one cost at 5,000 users? [partial]: Same assumptions:5000 users licence USD483,108 + model USD11,880 = from USD494,988 / EUR441,362.46 / CHF407,686.51 + unknown components. Scale entitlement and Business alternative unverified. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:pricing, typingmind:typingmind:openai-price, typingmind:typingmind:openai-model, typingmind:typingmind:fx. - variable_share — Which part depends on usage? [supported]: The disclosed model proxy contributes USD2.376/user/year. Actual provider model mix, tools, images, audio, embeddings, cached/context tokens and regional API uplifts change usage. This proxy is a comparison assumption, not a vendor default or invoice. Sources: typingmind:typingmind:set-up-api-keys, typingmind:typingmind:openai-price, typingmind:typingmind:openai-model. - unknown_parts — Which costs could not be priced? [supported]: Unknown: large-scale SaaS entitlement/Business quote, current checkout promotion terms, extra KB capacity, connectors/search/plugin bills, embeddings, support/implementation and optional regional processing uplift. Self-host annual commercial licence/support quote plus MySQL, optional PostgreSQL/blob/network infrastructure and operator effort are unpriced; no zero-licence OSS assumption applies. Sources: typingmind:typingmind:pricing, typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:deep-research. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:pricing, typingmind:typingmind:openai-price, typingmind:typingmind:openai-model, typingmind:typingmind:fx, typingmind:typingmind:set-up-api-keys, typingmind:typingmind:selfhost, typingmind:typingmind:get-started-with-self-host-installation-instruct, typingmind:typingmind:deep-research ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Teams SaaS has a self-serve trial; self-host evaluation is a separate sales-gated route. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=TypingMind Teams SaaS; Starter, Growth and Professional prerequisites stated per answer; Business quote not obtained; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=multi-tenant-saas; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - free_tier — Is there a free tier for business use? [partial]: The cloud offer advertises a time-limited trial rather than a documented permanent free business tier. Personal free-use rights do not supply Teams governance. Sources: typingmind:typingmind:pricing, typingmind:typingmind:typingmind-vs-typingmind-team. - self_serve_trial — Is a self-serve business trial available? [supported]: The cloud-vs-self-host comparison offers a 14-day self-serve cloud trial with no upfront payment. Sources: typingmind:typingmind:cloud-host-vs-self-host. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: The trial provides cloud evaluation; exact trial entitlements for SSO, SCIM, connectors and API quotas were not independently established. Sources: typingmind:typingmind:cloud-host-vs-self-host. - sales_gate — Does meaningful evaluation require sales contact? [supported]: Cloud starts self-serve; Business and annual self-host require a quote, and self-host has no free trial. Sources: typingmind:typingmind:pricing, typingmind:typingmind:selfhost, typingmind:typingmind:cloud-host-vs-self-host. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:pricing, typingmind:typingmind:typingmind-vs-typingmind-team, typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:selfhost ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Cloud supports monthly/annual subscriptions; self-host is annual and commercial. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Starter/Growth/Professional monthly or annual SaaS; quoted Business and separate annual commercial Teams self-host; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - minimum_commitment — What seat or spend minimum applies? [supported]: Cloud plan cards and self-host licence include five users. Business advertises a USD18,700/year starting quote; no all-scenario minimum was established. Sources: typingmind:typingmind:pricing, typingmind:typingmind:selfhost. - contract_length — What contract lengths are offered? [supported]: Cloud-host vs Self-host explicitly describes monthly SaaS and annual quoted self-host subscriptions; the current SaaS landing also offers annual billing. Teams Terms specify renewal of the agreed term. Sources: typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:pricing, typingmind:typingmind:terms-of-service. - cancellation — How can the contract be cancelled or reduced? [partial]: Cloud billing settings manage subscriptions; Terms make fixed-term Teams/self-host fees generally nonrefundable. Exact mid-term seat-reduction proration and notice deadline were not established. Sources: typingmind:typingmind:manage-your-subscription, typingmind:typingmind:terms-of-service. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: Can it be invoiced in CHF or EUR from a European entity? CHF/EUR invoicing from a European entity, tax handling and bespoke contract negotiation were not established. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partial: public small-plan SaaS seat pricing with separate API bills, quote-only Business and self-host, and unpriced optional support/knowledge services. Sources: typingmind:typingmind:pricing, typingmind:typingmind:selfhost. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:pricing, typingmind:typingmind:selfhost, typingmind:typingmind:cloud-host-vs-self-host, typingmind:typingmind:terms-of-service, typingmind:typingmind:manage-your-subscription ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial TypingMind is commercial proprietary software; self-host access is not an open-source licence. Availability: generally-available Delivery: native Scope: surfaces=TypingMind personal browser app and PWA, TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Commercial personal licence, separate bulk pack, Teams SaaS Starter/Growth/Professional and separate commercial Teams self-host licence; personal user/device allowance unverified; add_ons=Customer-paid model APIs; optional knowledge-base capacity and third-party plugin services; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - The personal user/device allowance is unknown. No five-user or one-user allowance is published as a reconciled finding; Teams and annual self-host seat rights remain separate. - licence_type — Which licence applies to each component? [supported]: The personal app and Teams operate under commercial Terms/EULA. Self-host provides compiled/minified code in a private repository with no analysis, modification, resale, sharing or redistribution rights; white-box review is by arrangement. Sources: typingmind:typingmind:end-user-license-agreement, typingmind:typingmind:terms-of-service, typingmind:typingmind:selfhost. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Teams SaaS provides custom branding; the separate commercial Teams self-host licence includes one instance with five seats. Personal user/device allowance remains unknown because the generic five-device-or-user comparison conflicts with the one-user Terms. The separate bulk pack does not establish the default personal allowance. Sources: typingmind:typingmind:custom-branding, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:selfhost, typingmind:typingmind:terms-of-service, typingmind:typingmind:r2-personal-bulk-licence. - enterprise_features_closed — Are enterprise features in a separate closed edition? [supported]: Teams administration is part of the commercial service; SSO/SCIM, analytics, roles, logs and API are in Professional rather than an open-source core edition. Sources: typingmind:typingmind:compare-typingmind-team-plans. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:end-user-license-agreement, typingmind:typingmind:terms-of-service, typingmind:typingmind:selfhost, typingmind:typingmind:custom-branding, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:r2-personal-bulk-licence, typingmind:typingmind:compare-typingmind-team-plans ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Recorded Teams chats have a JSON API export; generic app exports do not prove full organizational portability. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams REST API, TypingMind Teams SaaS chat and Admin Panel, TypingMind personal browser app and PWA; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Professional recorded-chat API/export; separate personal app JSON backups (feature licence gate not mapped); add_ons=Professional chat recording enabled before export; authorized API key; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - chat_export — Can admins export all chats? [partial]: Professional includes chat logs/data export and API integration. Authorized admins export recorded conversation JSON via the API, last100 matching conversations/request plus date filters; complete tenant history and pagination were not tested. Sources: typingmind:typingmind:export-chat-logs, typingmind:typingmind:r2-plan-matrix. - assistant_export — Can assistants and prompts be exported in a reusable format? [partial]: The personal-app backup guide exports user agents, prompts/plugins/model settings as JSON. That is not evidence of bulk centrally managed Teams asset export; its personal feature gate is not mapped here. Sources: typingmind:typingmind:export-import-data. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? A bulk reusable organization KB/source export and complete centrally managed agent/prompt export were not established. - export_format — Are formats documented and machine-readable? [supported]: Professional recorded-chat API responses are JSON; the separate personal backup/import also uses JSON. Formats do not establish complete organization portability. Sources: typingmind:typingmind:export-chat-logs, typingmind:typingmind:export-import-data, typingmind:typingmind:r2-plan-matrix. - post_termination_window — How long can data be retrieved after termination? [partial]: The DPA allows deletion/return at termination but does not publish a fixed retrieval grace period. Terms allow content deletion after termination. Sources: typingmind:typingmind:data-processing-agreement, typingmind:typingmind:terms-of-service. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:export-chat-logs, typingmind:typingmind:r2-plan-matrix, typingmind:typingmind:export-import-data, typingmind:typingmind:data-processing-agreement, typingmind:typingmind:terms-of-service ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Email support is documented; self-host SLA is optional and public incident data was inaccessible. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Starter/Growth/Professional public email support/material; separate quoted annual Teams self-host Enterprise Support add-on; add_ons=Commercial Teams self-host Enterprise Support (SLA/SLO/dedicated queue), separately quoted; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Self-host support package is distinct from SaaS support/onboarding; no public numerical uptime/credit or adoption-service tariff established. - support_channels — Which support channels are available on each plan? [supported]: Cloud plan comparison lists email support. Self-host dedicated support/SLA is a separate option; exact Business response targets were not established. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:selfhost. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? No German/French/Italian support commitment, DACH/Swiss support entity or public credit-bearing SLA terms were retrieved. - regional_presence — Is there a DACH or Swiss entity, team or partner? [unknown]: Is there a DACH or Swiss entity, team or partner? No German/French/Italian support commitment, DACH/Swiss support entity or public credit-bearing SLA terms were retrieved. - uptime_sla — Is there an uptime SLA with credits? [partial]: Self-host marketing offers a paid SLA/SLO/dedicated-support add-on; a public uptime percentage, credit schedule or standard SaaS SLA was not retrieved. Sources: typingmind:typingmind:selfhost. - status_page — Is there a public status page with history? [partial]: A public status site loads but returned an error fetching status data in this pass, so history and measured availability are unknown. Sources: typingmind:typingmind:status. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:compare-typingmind-team-plans, typingmind:typingmind:selfhost, typingmind:typingmind:status, typingmind:typingmind:pricing, typingmind:typingmind:cloud-host-vs-self-host ### 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. #### 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 #### TypingMind / TypingMind Teams Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public setup guides and role examples exist; managed adoption services are not fully specified. Availability: generally-available Delivery: native Scope: surfaces=TypingMind Teams SaaS chat and Admin Panel, Commercial self-hosted TypingMind Teams server; version=Public documentation and changelog retrieved 2026-10-21; no deployed tenant observed; plan=Teams Starter/Growth/Professional public email support/material; separate quoted annual Teams self-host Enterprise Support add-on; add_ons=Commercial Teams self-host Enterprise Support (SLA/SLO/dedicated queue), separately quoted; deployment_mode=not specified; region=US or opt-in EU SaaS storage; inference and tools depend on customer-selected providers; os=not specified. Limitations: - Self-host support package is distinct from SaaS support/onboarding; no public numerical uptime/credit or adoption-service tariff established. - onboarding_service — Is guided onboarding included? [unknown]: Is guided onboarding included? No included guided-onboarding scope, multilingual training commitment or champion/adoption programme was established. - user_training — Is end-user training offered, in which languages? [partial]: Public documentation teaches setup, use, agents and workflows. A contracted live user-training service and languages were not established. Sources: typingmind:typingmind:typingmind-vs-typingmind-team, typingmind:typingmind:overview. - use_case_library — Are role-based use cases and templates provided? [supported]: The documentation provides marketing ad creation, meeting-summary and business automation examples and role/permission examples. Sources: typingmind:typingmind:ad-creative-generator, typingmind:typingmind:meeting-summarizer, typingmind:typingmind:overview, typingmind:typingmind:roles-and-permissions. - adoption_programme — Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? No included guided-onboarding scope, multilingual training commitment or champion/adoption programme was established. - service_cost — Which services cost extra? [partial]: Self-host dedicated support/SLA is an optional extra; onboarding/training/adoption-program prices were not established. Sources: typingmind:typingmind:selfhost. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: typingmind:typingmind:typingmind-vs-typingmind-team, typingmind:typingmind:overview, typingmind:typingmind:ad-creative-generator, typingmind:typingmind:meeting-summarizer, typingmind:typingmind:roles-and-permissions, typingmind:typingmind:selfhost, typingmind:typingmind:pricing, typingmind:typingmind:cloud-host-vs-self-host ## Sources ### 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 ### typingmind:typingmind:set-up-api-keys Set up API Keys. Teams admins preset customer provider keys; end users cannot enter their own key in the chat interface. - URL: https://docs.typingmind.com/typingmind-team/getting-started/set-up-api-keys.md - Locator: Set up API Keys - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:manage-ai-models Manage AI Models. The app has a per-chat model selector and configurable model endpoints; provider examples are not a complete current catalogue. - URL: https://docs.typingmind.com/manage-and-connect-ai-models/manage-ai-models.md - Locator: Manage AI Models - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:release TypingMind changelog. Dated releases include Teams memory administration, new models, browser-local code and office outputs, and GPT Image editing. - URL: https://feedback.typingmind.com/changelog/ - Locator: 2026-10-14 Memory for Teams and new models; 2026-10-13 Toolbox; 2026-10-02 image editing - Evidence kind: documented - Source date: 2026-10-14 - Retrieved: 2026-10-21 ### typingmind:typingmind:restrict-model-access Restrict Model access. Teams admins restrict available models by user group. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/restrict-model-access.md - Locator: Restrict Model access - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:chat-with-documents Chat with documents. Uploads accept PDF, Markdown, CSV, XLSX, TXT, DOCX, JSON and HTML, with document text added as chat context. - URL: https://docs.typingmind.com/upload-and-chat-with-files/chat-with-documents.md - Locator: Chat with documents - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:voice Voice input. Browser speech recognition or customer OpenAI, Groq and Azure transcription keys enable dictation; uploaded Whisper recordings have a 25MB limit. - URL: https://docs.typingmind.com/voice-input - Locator: Transcription models and Teams configuration - Evidence kind: documented - Source date: Not stated - 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 ### typingmind:typingmind:azure-openai Azure OpenAI. A customer Azure OpenAI endpoint and deployment can be configured. - URL: https://docs.typingmind.com/manage-and-connect-ai-models/azure-openai.md - Locator: Azure OpenAI - 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 ### typingmind:typingmind:pricing TypingMind Teams pricing. Annual selected prices display USD83/166/249 per month for Starter/Growth/Professional, five users, USD8 extra seats; Business starts USD18,700/year. - URL: https://custom.typingmind.com/pricing - Locator: Annual selector, plan cards, Add-ons and Business card - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:get-started-with-self-host-installation-instruct Self-host installation instructions. A NodeJS service needs MySQL 8, optional PostgreSQL 16 pgvector KB, OpenAI embeddings and S3-compatible blobs; private endpoints are blocked by default. - URL: https://docs.typingmind.com/typingmind-team/self-host-guides/get-started-with-self-host-installation-instruct.md - Locator: Self-host installation instructions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:toolbox Toolbox. A free built-in plugin executes Python and JavaScript locally in the browser with network disabled by default and creates Office/PDF files and charts. - URL: https://docs.typingmind.com/plugins/toolbox - Locator: Local execution, network control and file capabilities - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:r2-teams-custom-models Teams API Keys Setup. Teams-specific instructions name Azure OpenAI, Hugging Face and Ollama custom-model setup in the Admin Panel; this is distinct from personal local-server guides. - URL: https://docs.typingmind.com/typingmind-team/getting-started/set-up-api-keys.md - Locator: Use with other models; Add Custom Model in Admin Panel - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:r2-plan-matrix Compare Teams Plans. All SaaS tiers list custom models and shared resources; Growth adds RAG/projects; Professional adds roles, restrictions, logs and external API integration. - URL: https://docs.typingmind.com/typingmind-team/getting-started/compare-typingmind-team-plans.md - Locator: Full Feature Comparison - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:r3-custom-admin-bedrock AWS Bedrock Anthropic. The Custom Admin route configures Claude via Bedrock with customer AWS access/secret keys, region and approved model access; current model and commercial tier coverage are not enumerated. - URL: https://docs.typingmind.com/manage-and-connect-ai-models/aws-bedrock-anthropic - Locator: Custom Admin restriction and steps 2-4, including custom.typingmind.com/manage - 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 ### typingmind:typingmind:ollama Ollama. A customer Ollama model endpoint can be added; network accessibility must be configured. - URL: https://docs.typingmind.com/manage-and-connect-ai-models/ollama.md - Locator: Ollama - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:lmstudio LM Studio. Customer local LM Studio can supply an OpenAI-compatible model endpoint. - URL: https://docs.typingmind.com/manage-and-connect-ai-models/lmstudio.md - Locator: LM Studio - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:cloud-host-vs-self-host Cloud host vs self host. SaaS has a self-serve 14-day trial; self-host has no free trial and carries a quoted annual licence and update/support conditions. - URL: https://docs.typingmind.com/typingmind-team/getting-started/cloud-host-vs-self-host.md - Locator: Cloud host vs self host - 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 ### typingmind:typingmind:usage-limits Usage limits. Reusable limit groups cover messages, characters and tokens by period, applicable globally or to users, groups, models, agents and plugins. - URL: https://docs.typingmind.com/typingmind-team/user-management/usage-limits.md - Locator: Usage limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:connect-knowledge-base-to-your-ai-agents Connect Knowledge Base to your AI Agents. Tagged knowledge is assigned to agents through Knowledge Base Access. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/connect-knowledge-base-to-your-ai-agents.md - Locator: Connect Knowledge Base to your AI Agents - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:roles-and-permissions Roles and Permissions. Owners delegate granular Admin Panel permissions through custom roles; group-role assignment is described as coming soon. - URL: https://docs.typingmind.com/typingmind-team/user-management/roles-and-permissions.md - Locator: Roles and Permissions - 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 ### typingmind:typingmind:how-knowledge-base-works-in-typingmind-team How Knowledge Base works in TypingMind Team. The early-access KB uses RAG, about 3,000-word chunks and up to five retrieved chunks, 50MB uploads and daily source refresh. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/how-knowledge-base-works-in-typingmind-team.md - Locator: Early Access; indexing; limits and refresh - Evidence kind: documented - Source date: 2025-11-10 - Retrieved: 2026-10-21 ### typingmind:typingmind:training-files-vs-knowledge-base Training Files vs Knowledge Base. Agent training-file text is injected into system context; the separate KB retrieves chunks and advertises multiple source integrations. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/training-files-vs-knowledge-base.md - Locator: Training Files vs Knowledge Base - 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 ### typingmind:typingmind:get-started-with-knowledge-base Get started with Knowledge Base. Admins add documents or connected sources, tag data, bind tags to agents and optionally show clickable references. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/get-started-with-knowledge-base.md - Locator: Get started with Knowledge Base - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:restrict-ai-agents-access Restrict AI Agents access. Agent access and usage can be limited for groups. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/restrict-ai-agents-access.md - Locator: Restrict AI Agents access - 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 ### typingmind:typingmind:connect-with-your-notion-pages Connect with Notion pages. Admins select Notion pages/databases for an instance, with initial sync taking a few minutes. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/connect-with-your-notion-pages.md - Locator: Connect with Notion pages - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:setup-external-connectors-for-knowledge-base Self-host external knowledge connectors. Optional self-host KB external connectors need separate OAuth configuration and Firecrawl for web scraping. - URL: https://docs.typingmind.com/typingmind-team/self-host-guides/setup-external-connectors-for-knowledge-base.md - Locator: Self-host external knowledge connectors - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:overview LLM Automated Workflows overview. JavaScript, HTTP and MCP plugins can perform multi-step business actions; example flows are not evidence of a scheduler. - URL: https://docs.typingmind.com/llm-automated-workflows/overview.md - Locator: LLM Automated Workflows overview - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:mcp MCP in TypingMind. The client connects remote HTTP or local-command MCP servers, supports OAuth and individual tool controls, and separates Teams sessions per user/chat. - URL: https://docs.typingmind.com/model-context-protocol-(mcp)-in-typingmind - Locator: Remote and local connectors; Teams sessions; tool control - 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 ### typingmind:typingmind:eu-data-center EU data center. EU instances use Vercel and AWS EU storage but model API calls may leave the EU. - URL: https://docs.typingmind.com/typingmind-team/account-management/eu-data-center.md - Locator: EU data center - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:system-prompts-on-admin-panel System Prompts on Admin Panel. Global system instructions, few-shot examples and post-message reminders apply across chats and agents. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/system-prompts-on-admin-panel.md - Locator: System Prompts on Admin Panel - 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 ### typingmind:typingmind:memory Memory. Users can enable memory globally or for an agent/project and inspect saved memories. - URL: https://docs.typingmind.com/memory.md - Locator: Memory - 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 ### typingmind:typingmind:build-a-shared-ai-agent-collection Build a Shared AI Agent collection. Admins create an agent collection exposed in the team chat interface and control group access. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/build-a-shared-ai-agent-collection.md - Locator: Build a Shared AI Agent collection - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:build-a-shared-prompt-library Build a Shared Prompt Library. Admins can publish reusable prompts to the team interface. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/build-a-shared-prompt-library.md - Locator: Build a Shared Prompt Library - 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 ### typingmind:typingmind:restrict-plugin-access Restrict Plugin access. Plugins can be made available or unavailable to specified user groups. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/restrict-plugin-access.md - Locator: Restrict Plugin access - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:deep-research Deep Research plugin. A multi-step search/read/report plugin requires customer SerpAPI and Firecrawl keys and has a two-minute execution limit. - URL: https://docs.typingmind.com/plugins/deep-research - Locator: Requirements and operation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:image GPT Image 2.5 plugin. The plugin generates and edits images using the customer OpenAI API route. - URL: https://docs.typingmind.com/plugins/gpt-image-2-5 - Locator: Image generation, editing and API key - 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 ### typingmind:typingmind:api-integration-overview API integration overview. REST chat/agent API uses API-key-associated api-users subject to user restrictions and usage limits. - URL: https://docs.typingmind.com/typingmind-team/integrations/api-integration-overview.md - Locator: API integration overview - 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 ### 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 ### 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 ### typingmind:typingmind:typingmind-vs-typingmind-team TypingMind vs TypingMind Team. The personal app and Teams with an Admin Panel, managed users and centrally preset keys are separate offerings. - URL: https://docs.typingmind.com/quickstart/typingmind-vs-typingmind-team.md - Locator: TypingMind vs TypingMind Team - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:install Install TypingMind app. Installation uses browser PWA technology; browser storage remains separate and this does not establish native app-store clients. - URL: https://docs.typingmind.com/install-typingmind-app - Locator: PWA installation on Windows, Mac, iOS and Android - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:r2-personal-bulk-licence TypingMind personal licence checkout. Personal licences normally cover five devices for one user; a separate shareable Bulk License is offered, without establishing a Teams Admin Panel entitlement. - URL: https://checkout.typingmind.com/buy - Locator: How many devices/users? and Team/Bulk License FAQ; self-host FAQ - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:ad-creative-generator Ad creative generator workflow. Public examples include marketing automation built with AI and plugins. - URL: https://docs.typingmind.com/llm-automated-workflows/ad-creative-generator.md - Locator: Ad creative generator workflow - 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 ### typingmind:typingmind:terms-of-service Terms of Service. Typing Technology Co Ltd contracts under Singapore law and business SIAC arbitration; Teams renews and self-host code has restricted licence rights. - URL: https://docs.typingmind.com/security-and-compliance/terms-of-service.md - Locator: Sections 1, 4-6, 13 and 16 - Evidence kind: documented - Source date: 2026-09-17 - Retrieved: 2026-10-21 ### typingmind:typingmind:tts Text to speech. Answers can be read aloud using browser speech, ElevenLabs or OpenAI TTS. - URL: https://docs.typingmind.com/use-text-to-speech - Locator: Browser, ElevenLabs and OpenAI options - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:meeting-summarizer Meeting summarizer workflow. The guide offers an audio-transcription and summarisation workflow, not a demonstrated meeting bot. - URL: https://docs.typingmind.com/llm-automated-workflows/meeting-summarizer.md - Locator: Meeting summarizer workflow - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:compare-typingmind-team-plans Compare TypingMind Team plans. The comparison lists monthly USD99/199/299, five users plus USD8 additional users, Growth knowledge and Professional identity/governance. - URL: https://docs.typingmind.com/typingmind-team/getting-started/compare-typingmind-team-plans.md - Locator: Compare TypingMind Team plans - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:translations Translation collaboration. A translation project exists, but the retrieved page does not establish completeness of German, French, Italian or Admin Panel translations. - URL: https://docs.typingmind.com/app-translation/translation-collaboration - Locator: Multilingual app translation project - Evidence kind: documented - 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 ### typingmind:typingmind:sso Single Sign-On (SSO). SAML identity-provider metadata, entity ID and reply URL are configured in Teams. - URL: https://docs.typingmind.com/typingmind-team/user-management/single-sign-on-(sso) - Locator: SAML configuration and multiple connections - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:o-auth-2-0 OAuth 2.0. OAuth/OIDC supports built-in Microsoft and Google logins and JIT seats; revoking IdP authorization alone does not remove the user. - URL: https://docs.typingmind.com/typingmind-team/user-management/o-auth-2-0.md - Locator: OAuth 2.0 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:data-processing-agreement Data Processing Agreement. The public GDPR processor form includes confidentiality, subprocessor flow-down, SCC transfers and customer-choice deletion or return. - URL: https://docs.typingmind.com/security-and-compliance/data-processing-agreement.md - Locator: Clauses 7.4, 7.8-7.10 and Appendices I-IV - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:scim Directory Sync (SCIM v2). SCIM sync creates and suspends users, updates profiles and assigns corresponding groups from the IdP. - URL: https://docs.typingmind.com/typingmind-team/user-management/directory-sync-(scim-v2) - Locator: Create, update, suspend users and groups - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:invite-team-members Invite team members. Teams admins invite members to the instance and manage seats. - URL: https://docs.typingmind.com/typingmind-team/user-management/invite-team-members.md - Locator: Invite team members - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:create-and-manage-user-groups Create and manage user groups. Groups control access and are usable for limits and analytics. - URL: https://docs.typingmind.com/typingmind-team/user-management/create-and-manage-user-groups.md - Locator: Create and manage user groups - 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 ### typingmind:typingmind:chatbot-analytics Chatbot analytics. Reporting covers active users, messages, conversations, estimated tokens and characters, with model/agent/group/user breakdowns and chart downloads. - URL: https://docs.typingmind.com/typingmind-team/analytics/chatbot-analytics.md - Locator: Chatbot analytics - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:view-and-export-user-chat-logs View and export user chat logs. Opt-in Record all chats exposes user prompts and responses to authorized admins and configurable retention permanently deletes old records. - URL: https://docs.typingmind.com/typingmind-team/analytics/view-and-export-user-chat-logs.md - Locator: View and export user chat logs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:export-chat-logs Export chat logs. Chat logging is off by default; the API exports JSON conversation content and dates, limited to the last 100 matching conversations per request. - URL: https://docs.typingmind.com/typingmind-team/integrations/export-chat-logs.md - Locator: Export chat logs - 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 ### 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 ### typingmind:typingmind:selfhost TypingMind Teams Self Host. Commercial self-host requires an annual quote, includes five users, uses compiled/minified code, checks licence/updates externally and can use customer model endpoints. - URL: https://custom.typingmind.com/self-host - Locator: Technical requirements, licensing, network, updates and pricing FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:privacy-policy Privacy policy. The policy distinguishes personal local storage from Teams multitenant server storage, and lists inactive unpaid account deletion. - URL: https://docs.typingmind.com/security-and-compliance/privacy-policy.md - Locator: Storage scope, API keys and section on account deletion - Evidence kind: documented - Source date: 2026-09-19 - 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 ### typingmind:typingmind:data-usage-and-model-training-policy Data Usage and Model Training Policy. The vendor says it does not train on conversations; customers contract directly with model providers and their retention/training terms vary. - URL: https://docs.typingmind.com/security-and-compliance/data-usage-and-model-training-policy.md - Locator: TypingMind role and provider API comparison - Evidence kind: vendor-claimed - 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/ ### typingmind:typingmind:r4-soc2-selfhost-claim TypingMind Teams self-host. The self-host marketing page claims SOC 2 Type II; no auditor, reporting period, covered legal entity or report was retrieved. This is a vendor claim rather than verified attestation. - URL: https://custom.typingmind.com/self-host - Locator: Maximum security, SOC 2 Type II badge; updates and licence checks - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-26 ### typingmind:typingmind:r2-teams-server-route TypingMind Teams pricing FAQ. The Teams-specific FAQ says users do not see the key and OpenAI requests are sent from the Teams server. - URL: https://custom.typingmind.com/pricing - Locator: Do my users see my OpenAI API key? - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:dpa-confidentiality TypingMind DPA confidentiality. Staff have need-to-know confidentiality duties and subprocessor contracts carry substantially the same data-protection obligations; a specific professional-secrecy agreement is not established. - URL: https://docs.typingmind.com/security-and-compliance/data-processing-agreement.md - Locator: 7.4(c),7.8(d)-(e); AppendixII andIII - Evidence kind: documented - Source date: Not stated - 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 ### typingmind:typingmind:openai-price OpenAI API pricing. gpt-6-luna Standard input is USD0.10 and output USD0.50 per million tokens, excluding cache and optional regional uplifts. - URL: https://developers.openai.com/api/docs/pricing - Locator: Standard short-context gpt-6-luna row - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:openai-model GPT-6 Luna model documentation. Reasoning effort none is the lowest option; the shared cost proxy does not use reasoning tokens. - URL: https://developers.openai.com/api/docs/models/gpt-6-luna - Locator: Reasoning effort and API support - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:fx ECB reference exchange rates. EUR1 equals USD1.1215 and CHF0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20 - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### typingmind:typingmind:manage-your-subscription Manage your subscription. Cloud customers manage the recurring subscription through billing settings. - URL: https://docs.typingmind.com/typingmind-team/account-management/manage-your-subscription.md - Locator: Manage your subscription - 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 ### typingmind:typingmind:end-user-license-agreement End User License Agreement. The software is commercially licensed with restrictions on redistribution and modification. - URL: https://docs.typingmind.com/security-and-compliance/end-user-license-agreement.md - Locator: End User License Agreement - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:custom-branding Custom branding. Teams supports instance logo, theme and branded presentation within its commercial licence. - URL: https://docs.typingmind.com/typingmind-team/branding-and-customizations/custom-branding.md - Locator: Custom branding - 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 ### typingmind:typingmind:export-import-data Export and import data. User app settings export/import chats, prompts, plugins, folders, agents and model settings as JSON. - URL: https://docs.typingmind.com/cloud-sync-and-backup/export-import-data.md - Locator: Export and import data - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### typingmind:typingmind:status TypingMind status. The status site loaded a status shell but reported an error fetching data; incident history and measured uptime were not retrieved. - URL: https://status.typingmind.ai - Locator: Public status shell - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21