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