Agent-readable comparison

Cohere North vs TypingMind / TypingMind Teams

Name: Cohere North vs TypingMind / TypingMind Teams: agent-readable comparison
Creator: onAI

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. 50 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. No winner is declared. A missing sourced finding is not evidence that a capability is absent.

Cohere North source checks: 2026-10-21 to 2026-10-26. Website: https://cohere.com/north
TypingMind / TypingMind Teams source checks: 2026-10-21 to 2026-10-26. Website: https://www.typingmind.com
Generated 2026-10-27; next source check due 2026-12-20.

Same facts as Markdown and JSON. 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.

Cohere North

Agent cross-checked Support: partial

North supports customer-configured Cohere and external providers; deployed models determine availability.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha model-tier aliases and direct image input; North Mini separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

current_models: The model card documents North Large 01-2026, and the October 16 release adds North Mini Beta. The Skills guide recommends additional external model identifiers, but those do not establish what any customer deployment has installed or licensed.
auto_routing: Documented resolution is group default, Default alias, then deployment default; inaccessible aliases silently fall back to provider default with a log warning. Automatic task-based routing across providers and UI disclosure of that fallback remain unknown.
multimodal_input: North Large 01-2026 accepts text/images,256K input and32K text output. Alpha image input is Cohere-only; visual parser handles PDF/DOCX/PPTX, including OCR. Dictation uses configured ASR; complete per-model matrix unknown.

providers Which model providers are available? [supported]: Provider types include customer Cohere containers, Cohere Platform/compatibility, vLLM, Azure Cohere, Bedrock, SageMaker, Azure OpenAI, OpenAI and Anthropic. Sources: cohere-north:cohere-north:n-doc-177-20261026.
current_models Which current models are selectable on this plan? [partial]: The model card documents North Large 01-2026, and the October 16 release adds North Mini Beta. The Skills guide recommends additional external model identifiers, but those do not establish what any customer deployment has installed or licensed. Sources: cohere-north:cohere-north:n-doc-32-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:n-doc-134-20261026.
user_choice Can users pick the model per chat? [supported]: Default-agent chat has a model picker; custom agents choose models in settings. Alpha tier picker aliases Default/Alternate/Legacy and can expose additional permitted models. Sources: cohere-north:cohere-north:n-doc-1-20261026, cohere-north:cohere-north:n-doc-134-20261026.
auto_routing Does the product route between models automatically, and is the chosen model shown? [partial]: Documented resolution is group default, Default alias, then deployment default; inaccessible aliases silently fall back to provider default with a log warning. Automatic task-based routing across providers and UI disclosure of that fallback remain unknown. Sources: cohere-north:cohere-north:n-doc-134-20261026.
multimodal_input Which models accept images, audio or files? [partial]: North Large 01-2026 accepts text/images,256K input and32K text output. Alpha image input is Cohere-only; visual parser handles PDF/DOCX/PPTX, including OCR. Dictation uses configured ASR; complete per-model matrix unknown. Sources: cohere-north:cohere-north:n-doc-32-20261026, cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-97-20261026.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-177-20261026, cohere-north:cohere-north:n-doc-32-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-1-20261026, cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-97-20261026.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Dated platform notes and operator-pinned model artifacts exist; provider release lag is unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: release_lag_days, deprecation_notice.

release_lag_days What was the lag for each of the last three major releases, per provider? [unknown]: Unknown for release_lag_days. No matched provider/product dates for the last three releases or contractual model-removal notice period was retrieved.
changelog Is there a dated public model changelog? [supported]: Public North release notes through October 20 v2.0.1 include model and feature changes. Sources: cohere-north:cohere-north:n-north-changelog.
deprecation_notice How much notice is given before a model is removed? [unknown]: Unknown for deprecation_notice. No matched provider/product dates for the last three releases or contractual model-removal notice period was retrieved.
version_pinning Can an admin keep an older model version? [partial]: Self-hosted serving images/model artifacts are versioned independently; operators select image tags/digests. This does not guarantee retention of external API model versions. Sources: cohere-north:cohere-north:n-doc-168.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-168.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Dated model additions are public; release lag and removal guarantees remain unestablished.

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.

Cohere North

Agent cross-checked Support: partial

North documents own keys, cloud deployments and OpenAI-compatible endpoints.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha direct image input restriction; provider registration is separately scoped; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

own_cloud_contract: Own Azure OpenAI, Bedrock Cohere/Anthropic and SageMaker endpoints documented. Foundry can bill supported inference to customer Azure subscription; Vertex integration not established.
byo_pricing: Unknown for byo_pricing. Provider configuration is documented; commercial BYO discounts and complete feature parity across every provider remain unknown. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers?format=html, https://private.docs.cohere.com/north/docs/admin/bedrock-anthropic?format=html. No additional scoped evidence established this answer.
byo_restrictions: Alpha direct image input currently requires Cohere models. Foundry lacks North Large/sparse and Compass keyless model authentication; complete per-provider feature parity remains unknown.

own_api_keys Can the customer use its own provider API keys? [supported]: Provider registration accepts customer API keys or identity tokens; declarative providers reference Kubernetes Secrets. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-177-20261026.
own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Own Azure OpenAI, Bedrock Cohere/Anthropic and SageMaker endpoints documented. Foundry can bill supported inference to customer Azure subscription; Vertex integration not established. Sources: cohere-north:cohere-north:n-doc-177-20261026, cohere-north:cohere-north:n-doc-135-20261026, cohere-north:cohere-north:n-doc-218-20261026.
custom_endpoint Can an admin add any OpenAI-compatible endpoint? [supported]: OpenAI provider base_url can point at compatible endpoints; vLLM and Cohere compatibility provider types also supported. Actual compatibility still depends on model/tool schema. Sources: cohere-north:cohere-north:n-doc-177-20261026.
byo_pricing Does BYO change the licence price? [unknown]: Unknown for byo_pricing. Provider configuration is documented; commercial BYO discounts and complete feature parity across every provider remain unknown. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers?format=html, https://private.docs.cohere.com/north/docs/admin/bedrock-anthropic?format=html. No additional scoped evidence established this answer.
byo_restrictions Which features stop working with BYO? [partial]: Alpha direct image input currently requires Cohere models. Foundry lacks North Large/sparse and Compass keyless model authentication; complete per-provider feature parity remains unknown. Sources: cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-218-20261026.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-177-20261026, cohere-north:cohere-north:n-doc-135-20261026, cohere-north:cohere-north:n-doc-218-20261026, cohere-north:cohere-north:n-doc-14-20261026.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

North chat and retrieval models can run in customer infrastructure.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: vendor_hosted_open_models.

self_hosted_chat Can chat use a customer-hosted model? [supported]: Customer Cohere serving containers and vLLM endpoints are supported; independent model chart deploys generative services in customer GPU clusters. Sources: cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-doc-168.
self_hosted_embeddings Can retrieval use customer-hosted embeddings? [partial]: Packed Compass provides local dense embeddings, sparse and rerank. Operator connects North/Compass to these services; arbitrary embedding model compatibility was not established. Sources: cohere-north:cohere-north:n-doc-168.
feature_parity Which features fail with self-hosted models? [partial]: Local visual processing needs parser/GPU deployment; hosted search/MCP needs egress. Foundry lacks sparse/North Large, so mixed inference required there. No full disconnected parity matrix retrieved. Sources: cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-218.
vendor_hosted_open_models Does the vendor host open-weight models in EU/CH? [unknown]: Unknown for vendor_hosted_open_models. Self-hosted Cohere models and Compass are documented; arbitrary embedding-model compatibility and a Cohere-operated EU/CH open-model hosting SKU were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-218.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Group model controls have additive and shared-agent exceptions; alpha limits require deployment.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha model RBAC and Flow control; Models UI separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

data_bound_models: Unknown for data_bound_models. Model RBAC and alpha rate limits are documented; content-bound model exclusion and measured enforcement were not tested. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents?format=html, https://private.docs.cohere.com/north/docs/admin/flow-control?format=html. No additional scoped evidence established this answer.
user_limits: Alpha Flow control supports requests/input/output tokens by user/group/model/source/provider and time window. Limits default unlimited; no fixed commercial message allowance was retrieved.
limit_behaviour: Configured limits block until window resets. Enforcement requires Helm proxy services; UI alone does nothing. Failure policy may allow or deny requests and token estimation is optional; actual overshoot untested.

model_allowlist_by_group Can admins limit models per group? [supported]: Beta Models UI configures provider/model user/group access; alpha model RBAC must be enabled. Provider OR model grants access, admins bypass; shared agents use owner permissions, not each recipient. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-18-20261026.
data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: Unknown for data_bound_models. Model RBAC and alpha rate limits are documented; content-bound model exclusion and measured enforcement were not tested. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/models?format=html, https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents?format=html, https://private.docs.cohere.com/north/docs/admin/flow-control?format=html. No additional scoped evidence established this answer.
default_model Can admins set the default model? [supported]: Group defaults precede Default tier and deployment default. Aliases are per deployment and initially empty. Sources: cohere-north:cohere-north:n-doc-134-20261026.
user_limits What per-user message or token limits apply, and are they published? [partial]: Alpha Flow control supports requests/input/output tokens by user/group/model/source/provider and time window. Limits default unlimited; no fixed commercial message allowance was retrieved. Sources: cohere-north:cohere-north:n-doc-137-20261026.
limit_behaviour What happens when a limit is reached? [partial]: Configured limits block until window resets. Enforcement requires Helm proxy services; UI alone does nothing. Failure policy may allow or deny requests and token estimation is optional; actual overshoot untested. Sources: cohere-north:cohere-north:n-doc-137-20261026.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-134-20261026, cohere-north:cohere-north:n-doc-18-20261026, cohere-north:cohere-north:n-doc-137-20261026.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Broad file formats and optional OCR are documented; the effective My files size limit for a deployment remains unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

limits: The effective My files default is unknown: its dedicated guide states 50 MB/file subject to configuration, while Supported files describes a 100 MB limit across all files. Neither is asserted as the verified deployment limit. Separately, chat images are limited to 20/message, 5 MB/image and 20 MB total; the supported-files guide lists 500 MB for SharePoint/OneDrive.
ocr: Vision parser can OCR scanned PDFs and extract visual tables; alpha setup requires smart parser and hosted vision parser. More than500 visual pages fall back to pure text processing. No scan test run.
spreadsheets: The supported-files guide says spreadsheet rows are not indexed for ordinary search and requires Data Interpreter for tabular prompts. Beta Skills also provide spreadsheet/CSV file operations through the code sandbox. Workbook formula/structure fidelity has not been tested.
full_vs_chunked: The SharePoint and OneDrive implementation guides remain inaccessible in Markdown, HTML and page-level index forms on 2026-10-26. Retrieved My files and multimodality guides do not establish universal full-file/chunk thresholds or prompt-context disclosure. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/get-started/supported-files?format=html, https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality?format=html, https://private.docs.cohere.com/north/docs/get-started/tools/my-files/home?format=html. No additional scoped evidence established this answer.

formats Which formats are accepted? [supported]: Office/PDF/text/HTML/email/JSON/XML/EPUB and tabular formats; common images, audio/video with parser enabled. Upload/index support differs from preview and individual vision model support. Sources: cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-14-20261026.
limits What size and count limits apply per file and chat? [partial]: The effective My files default is unknown: its dedicated guide states 50 MB/file subject to configuration, while Supported files describes a 100 MB limit across all files. Neither is asserted as the verified deployment limit. Separately, chat images are limited to 20/message, 5 MB/image and 20 MB total; the supported-files guide lists 500 MB for SharePoint/OneDrive. Sources: cohere-north:cohere-north:n-doc-66-20261026, cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-1-20261026.
ocr Are scanned PDFs read? [partial]: Vision parser can OCR scanned PDFs and extract visual tables; alpha setup requires smart parser and hosted vision parser. More than500 visual pages fall back to pure text processing. No scan test run. Sources: cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-100-20261026.
spreadsheets Are Excel tables read with structure intact? [partial]: The supported-files guide says spreadsheet rows are not indexed for ordinary search and requires Data Interpreter for tabular prompts. Beta Skills also provide spreadsheet/CSV file operations through the code sandbox. Workbook formula/structure fidelity has not been tested. Sources: cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026.
full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [unknown]: The SharePoint and OneDrive implementation guides remain inaccessible in Markdown, HTML and page-level index forms on 2026-10-26. Retrieved My files and multimodality guides do not establish universal full-file/chunk thresholds or prompt-context disclosure. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/get-started/supported-files?format=html, https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality?format=html, https://private.docs.cohere.com/north/docs/get-started/tools/my-files/home?format=html. No additional scoped evidence established this answer.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-73-20261026, cohere-north:cohere-north:n-doc-14-20261026, cohere-north:cohere-north:n-doc-66-20261026, cohere-north:cohere-north:n-doc-1-20261026, cohere-north:cohere-north:n-doc-100-20261026, cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Document text can be attached to chat; full-context training files and RAG are distinct.

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.

Cohere North

Agent cross-checked Support: partial

Beta Libraries persist shared source collections; alpha Projects are separate private workspaces.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha Projects; Libraries separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

size_limits: Alpha Projects default to a 2 GiB aggregate allowance per user across projects. Beta Libraries/uploads use administrator-configured file-size/count settings; complete effective deployment limits were not retrieved.

persistent_collections Can users keep document collections across chats? [supported]: Libraries reuse uploaded/My files/Google/Microsoft collections across agents/chats/nodes. Alpha Projects index separate private project files. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-11-20261026.
sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Libraries support user/group/company access with source-dependent roles; Outlook/Exchange remain private. Attaching library to shared agent does not grant library access. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-133-20261026.
size_limits What are the collection limits? [partial]: Alpha Projects default to a 2 GiB aggregate allowance per user across projects. Beta Libraries/uploads use administrator-configured file-size/count settings; complete effective deployment limits were not retrieved. Sources: cohere-north:cohere-north:n-doc-11-20261026, cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-66-20261026.
assistant_binding Can collections be bound to an assistant? [supported]: Agent Resources bind persistent libraries; composer attachment applies to one chat only. Shared recipients must already have library Viewer access. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-18-20261026.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-42-20261026, cohere-north:cohere-north:n-doc-11-20261026, cohere-north:cohere-north:n-doc-133-20261026, cohere-north:cohere-north:n-doc-66-20261026, cohere-north:cohere-north:n-doc-18-20261026.

TypingMind / TypingMind Teams

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).

Cohere North

Agent cross-checked Support: partial

North has first-party connectors, custom MCP and an on-prem SharePoint Server path.

Availability: unknown · Delivery: official-integration
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North 2.0.1; Notion/Linear first-party MCP Beta; SharePoint Server Alpha; other connector states per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

microsoft_365: The North 2 announcement names SharePoint, OneDrive, Outlook and Exchange. The October 16 release separately documents read-only Outlook Calendar as alpha. Teams connector entitlement was not established.
google_workspace: The retrieved sync guide distinguishes indexed Google Drive Libraries from live Full Access Drive queries. Gmail is documented, but its storage/sync behavior remains unknown because the Syncing and Sharing guides disagree. Google Calendar was not established.
atlassian: North 2 names Jira among its connectors. Versioned release notes remove the legacy Jira path in 2.0; no Confluence connector entitlement was established.
other_systems: The current North 2 announcement names Slack, Linear, Notion and GitHub. The October 16 release describes Salesforce and PitchBook as alpha features. Customer/third-party MCP connections remain separately configured and licensed.
on_prem_sources: The SharePoint Server connector setup is explicitly Alpha. Customer in-network MCP may expose other systems; a native SMB/database inventory and its source-permission guarantees remain unverified.
connector_provider: Cohere documents its North connector families and a distinct customer/third-party remote MCP setup. Exact connector-specific maintenance and service commitments require the applicable contract.

microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: The North 2 announcement names SharePoint, OneDrive, Outlook and Exchange. The October 16 release separately documents read-only Outlook Calendar as alpha. Teams connector entitlement was not established. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026.
google_workspace Which Google sources are connected? [partial]: The retrieved sync guide distinguishes indexed Google Drive Libraries from live Full Access Drive queries. Gmail is documented, but its storage/sync behavior remains unknown because the Syncing and Sharing guides disagree. Google Calendar was not established. Sources: cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:north-release-html-20261026.
atlassian Confluence and Jira? [partial]: North 2 names Jira among its connectors. Versioned release notes remove the legacy Jira path in 2.0; no Confluence connector entitlement was established. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026.
other_systems Which other business systems? [partial]: The current North 2 announcement names Slack, Linear, Notion and GitHub. The October 16 release describes Salesforce and PitchBook as alpha features. Customer/third-party MCP connections remain separately configured and licensed. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-126-20261026.
on_prem_sources Can on-prem file shares or databases be connected? [partial]: The SharePoint Server connector setup is explicitly Alpha. Customer in-network MCP may expose other systems; a native SMB/database inventory and its source-permission guarantees remain unverified. Sources: cohere-north:cohere-north:n-doc-53-20261026, cohere-north:cohere-north:n-doc-126-20261026.
connector_provider Who builds and maintains each connector? [partial]: Cohere documents its North connector families and a distinct customer/third-party remote MCP setup. Exact connector-specific maintenance and service commitments require the applicable contract. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:n-doc-126-20261026.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:north2-launch-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:n-doc-126-20261026, cohere-north:cohere-north:n-doc-53-20261026.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Indexed retrieval adds runtime source checks; shared snapshots have a separate visibility boundary.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: sensitivity_labels.

source_permissions_respected Are source permissions enforced per user? [partial]: Atlas retrieval checks agent scope and user source access; permission-check errors exclude files. This does not re-protect already generated shared chat snapshots; no ACL fixture run. Sources: cohere-north:cohere-north:n-doc-152, cohere-north:cohere-north:n-doc-4.
enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: Compass retrieves indexed candidates, then Atlas/source API checks filter permissioned documents. Google Drive Full Access queries source directly; local uploads use North sharing rules. Sources: cohere-north:cohere-north:n-doc-152, cohere-north:cohere-north:n-doc-151.
revocation_delay How quickly does a removed permission take effect? [partial]: Authorization guide claims external permission changes apply immediately; token/group membership refresh and caches are separate. No measured revocation SLA or fixture. Sources: cohere-north:cohere-north:n-doc-149, cohere-north:cohere-north:n-doc-111.
admin_scope_controls Can admins exclude sites, folders or labels? [partial]: Selected sites/folders/files scope Atlas ingestion; library and tool grants scope users/groups. Label-based exclusions not established. Sources: cohere-north:cohere-north:n-doc-64, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-126.
sensitivity_labels Are Microsoft Purview or similar labels respected? [unknown]: Unknown for sensitivity_labels. No two-user ACL revocation or sensitivity-label fixture was run; source API permission claims remain documented, not observed.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-152, cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-151, cohere-north:cohere-north:n-doc-149, cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-64, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-126.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Atlas file connectors copy selected content to Compass; Drive Full Access uses live API calls. Effective Gmail storage/sync behavior remains unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

live_or_indexed: Atlas file connectors copy selected files to Compass. Google Drive Full Access calls the live API instead. Gmail storage is unknown: the Data Syncing guide says no Compass copy by default, while Data Sharing and the tools overview describe stored/synced email. No live-only Gmail guarantee is asserted.
sync_interval: The accessible Data Syncing guide describes periodic Atlas updates and source changes appearing within minutes to hours depending on volume. Drive Full Access is request-time. The previously cited SharePoint/OneDrive 10-minute implementation detail could not be re-retrieved and is not asserted.
deletion_propagation: The source-specific SharePoint/OneDrive implementation and Data Deletion pages remain inaccessible in public Markdown/HTML/index forms. General sync documentation does not establish a bounded delete-to-answer or purge interval. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/security/data-syncing?format=html, https://private.docs.cohere.com/north/docs/security/data-sharing?format=html, https://private.docs.cohere.com/north/docs/get-started/tools-overview.md. No additional scoped evidence established this answer.
index_location: Compass runs with the customer-controlled North deployment, whose cloud/on-premise placement is selected by the operator. Foundry inference is separately routed to the customer Azure subscription. A universal vendor-hosted index country is not established.

live_or_indexed Is content searched live or copied into an index? [partial]: Atlas file connectors copy selected files to Compass. Google Drive Full Access calls the live API instead. Gmail storage is unknown: the Data Syncing guide says no Compass copy by default, while Data Sharing and the tools overview describe stored/synced email. No live-only Gmail guarantee is asserted. Sources: cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:n-doc-33.
sync_interval How often does an index refresh? [partial]: The accessible Data Syncing guide describes periodic Atlas updates and source changes appearing within minutes to hours depending on volume. Drive Full Access is request-time. The previously cited SharePoint/OneDrive 10-minute implementation detail could not be re-retrieved and is not asserted. Sources: cohere-north:cohere-north:n-doc-151-20261026.
deletion_propagation How quickly does a deleted document disappear? [unknown]: The source-specific SharePoint/OneDrive implementation and Data Deletion pages remain inaccessible in public Markdown/HTML/index forms. General sync documentation does not establish a bounded delete-to-answer or purge interval. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/security/data-syncing?format=html, https://private.docs.cohere.com/north/docs/security/data-sharing?format=html, https://private.docs.cohere.com/north/docs/get-started/tools-overview.md. No additional scoped evidence established this answer.
index_location Where is indexed content stored? [partial]: Compass runs with the customer-controlled North deployment, whose cloud/on-premise placement is selected by the operator. Foundry inference is separately routed to the customer Azure subscription. A universal vendor-hosted index country is not established. Sources: cohere-north:cohere-north:n-doc-165-20261026, cohere-north:cohere-north:n-doc-218-20261026.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-151-20261026, cohere-north:cohere-north:n-doc-152-20261026, cohere-north:cohere-north:n-doc-33, cohere-north:cohere-north:n-doc-165-20261026, cohere-north:cohere-north:n-doc-218-20261026.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Citations are documented but have model-specific limitations; quality remains unmeasured.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: citation_accuracy, cross_language, no_answer_behaviour, observed_accuracy.

citations Are answers linked to specific sources? [partial]: Chat highlights open source previews and Project citations exact passages. North Large card acknowledges missing citations in long multi-turn chats and Document Mode. Correctness not tested. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-11, cohere-north:cohere-north:n-doc-32.
citation_accuracy Do the cited passages support the answer? [unknown]: Unknown for citation_accuracy. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved.
cross_language Does a question in one language find documents in another? [unknown]: Unknown for cross_language. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved.
no_answer_behaviour Does it say when the corpus has no answer? [unknown]: Unknown for no_answer_behaviour. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved.
observed_accuracy How many of the question set were answered correctly? [unknown]: Unknown for observed_accuracy. Shared DE/FR/EN fixture was not run; citation accuracy, cross-language retrieval, abstention and measured accuracy remain unobserved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-11, cohere-north:cohere-north:n-doc-32.

TypingMind / TypingMind Teams

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.

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.

Cohere North

Agent cross-checked Support: partial

Alpha memory separates editable personal memories from inaccessible agent archival memory.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported.

custom_instructions Can users set persistent instructions? [supported]: Agents persist instructions; optional company preamble applies across models. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-86.
cross_chat_memory Does the product remember facts across chats? [supported]: Alpha personal memory learns across chats; archival memory per agent is generated in background, typically daily. Sources: cohere-north:cohere-north:n-doc-8, cohere-north:cohere-north:n-doc-96.
user_memory_controls Can users view, edit and delete memories? [partial]: Personal categories can be viewed/edited; pause retains or Delete removes memory. Archival memories cannot be viewed/edited; manual personal edits can be overwritten by later extraction. Sources: cohere-north:cohere-north:n-doc-8.
admin_memory_controls Can admins turn memory off? [supported]: Instance admin can jointly toggle core/archival/conversation memory and configure extraction frequency. Sources: cohere-north:cohere-north:n-doc-96.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-86, cohere-north:cohere-north:n-doc-8, cohere-north:cohere-north:n-doc-96.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

North offers versioned custom agents, scoped sharing and an internal catalogue.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

create_assistants Can users create assistants with instructions, knowledge and tools? [supported]: Users create agents with instructions, model, tools, libraries and output modes; drafts publish as versioned releases with restore/evaluations. Sources: cohere-north:cohere-north:n-doc-18.
creator_permissions Can admins limit who creates them? [supported]: Can create agents and separate sharing grants control creation/publication audiences. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-114.
sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Published agents share to users/groups/company subject to grants; libraries need separate recipient access and email libraries remain private. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-42.
catalogue Is there an internal assistant directory? [supported]: Agent directory has Starred/My/Shared with me/Company tabs, search and duplication. Sources: cohere-north:cohere-north:n-doc-21.
prompt_library Are shared prompt templates available? [partial]: Agents expose up to four starter prompts and reusable Skills; a separate central prompt-template catalogue not established. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-12.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-21, cohere-north:cohere-north:n-doc-12.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

MCP, code and enterprise tools have scoped authentication and configurable approvals.

Availability: unknown · Delivery: official-integration
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; always-on MCP policies are Alpha; guide recommends testing/staging initially; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.
Approval-parameter editing is an interface affordance only in this finding. No execution guarantee is credited without a corrected guide or a bounded tool-call fixture.
Always-on MCP configuration is Alpha with a testing/staging recommendation until the organization is ready for broader adoption. Criterion availability remains unknown; this subfact does not establish production readiness.

builtin_tools Which tools are built in? [supported]: Built-in search, source connectors, code sandbox, Skills and output capabilities documented with individual states. Sources: cohere-north:cohere-north:n-doc-33, cohere-north:cohere-north:n-doc-34.
custom_actions Can admins add API actions? [supported]: Custom MCP servers expose APIs/actions; admin configures tools and auth, with action hints for approval. Sources: cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-150.
mcp_client Can it use remote MCP servers, and with what admin control? [supported]: North registers custom/remote MCP; remote OAuth dynamic registration needs outbound access and is unavailable fully air-gapped. Tool access policies can target groups. Always-on MCP policies are Alpha; the guide recommends enabling them only in testing/staging until the organization is ready for broader adoption. Sources: cohere-north:cohere-north:n-doc-126.
tool_auth Do tools act as the user or as a shared account? [supported]: Static headers, per-user ID/connector tokens, OAuth client credentials or remote OAuth supported. Shared/static credentials require separate source-policy assessment. Sources: cohere-north:cohere-north:n-doc-126.
tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Destructive-hint tools can pause for approval or denial, and the modal offers parameter editing. Whether edited values execute is unknown: the guide says both that modifications replace the original request and that original keys/values are submitted. Allow Always and advance automation action permissions can bypass later prompts; universal per-action confirmation is not guaranteed. Sources: cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-30.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-33, cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-30.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

GA web search and alpha Deep Research are distinct capabilities.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Web search GA; Deep Research alpha.

web_search Is web search available? [supported]: GA web search supports live URL/search retrieval; text-only and no authenticated websites. Sources: cohere-north:cohere-north:n-doc-74.
admin_toggle Can admins disable it per organisation or group? [partial]: Admins enable provider/tool; Deep Research additionally needs user/group grants. Complete group-specific web-search matrix unverified. Sources: cohere-north:cohere-north:n-doc-74, cohere-north:cohere-north:n-doc-15.
search_provider Which search provider handles queries, and where? [partial]: Tavily defaultGA; Brave/LinkUp alpha, own API keys and one active provider. Provider processing countries not retrieved. Sources: cohere-north:cohere-north:n-doc-74.
deep_research Is multi-step research with a report available? [supported]: Alpha Deep Research delegates multi-step subqueries and creates reports; requires enabled sources, admin/user grants and may queue. Sources: cohere-north:cohere-north:n-doc-15.
web_citations Are web sources cited? [supported]: Live web and Deep Research include source citations; quality untested. Sources: cohere-north:cohere-north:n-doc-74, cohere-north:cohere-north:n-doc-15.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-74, cohere-north:cohere-north:n-doc-15.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Node workflows support schedules, API invocation and human review.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

workflow_builder Is there a workflow or chain builder? [supported]: Visual node builder combines LLM/agent/tool/conditional/loop steps, versioning and JSON import/export. Sources: cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-29.
scheduled_tasks Can prompts or assistants run on a schedule? [supported]: Users schedule hourly/daily/weekly or cron; optional natural-language suggestions require confirmation. Repeated failure can disable schedules. Sources: cohere-north:cohere-north:n-doc-30.
event_triggers Can external events start a workflow? [partial]: Authenticated execute API enables custom external event integrations. A native inbox/file-change webhook listener was not established. Sources: cohere-north:cohere-north:n-api-run.
builder_audience Is building aimed at business users, IT or developers? [supported]: Business builders use visual/natural-language tools and Human Review; IT provisions connectors/models and developers call APIs. Sources: cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-26, cohere-north:cohere-north:n-api-run.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-api-run, cohere-north:cohere-north:n-doc-26.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

North executes multi-step work with visible tasks, approval options and workflow cancellation.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

agent_mode Is there an agent mode for multi-step tasks? [supported]: Agents use tools/code; Deep Research decomposes tasks and delegates subagents; automations execute multiple nodes. Sources: cohere-north:cohere-north:n-doc-15, cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-16.
visible_steps Are steps and tool calls shown? [supported]: Sandbox activity expands executed code; automation run viewer shows node inputs/outputs; shared chat includes thinking trace. Sources: cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-doc-4.
side_effect_confirmation Must the user confirm actions with side effects? [partial]: Tool hints trigger approval; global Allow Always bypasses it and workflows accept action permissions at launch. Human Review nodes can add deliberate checkpoints. Sources: cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-doc-26.
stop_control Can the user stop a running task? [partial]: Running automations have Cancel. General chat stop behavior and rollback of already executed external actions were not tested. Sources: cohere-north:cohere-north:n-doc-30.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-15, cohere-north:cohere-north:n-doc-34, cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-30, cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-150, cohere-north:cohere-north:n-doc-26.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Multi-step tool workflows exist; universal side-effect confirmation and run controls remain unproven.

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.

Cohere North

Agent cross-checked Support: partial

North has its own authenticated REST APIs for responses, agents, files, libraries and workflows.

Availability: unknown · Delivery: native
Scope: surfaces=North instance REST API and SDK access; version=North 2.0.1 docs; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: mcp_server.

chat_api Is there an API for chat and assistants? [supported]: Instance REST API supports chat/agents/automations; response endpoint exposes models/tools and SDK access. Separate from Cohere model Platform API. Sources: cohere-north:cohere-north:n-north-api, cohere-north:cohere-north:n-api-response.
knowledge_api Can documents be loaded through an API? [supported]: Authenticated file upload stores content with IDs; library APIs create collections under library permissions. Sources: cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries, cohere-north:cohere-north:n-doc-114.
api_governance Do audit, budgets and model rules apply to API use? [partial]: APIs return permission/rate-limit errors and use North identities; sharing restrictions cover API, audit GET exists. Full guardrail/budget/content logging parity not tested. Sources: cohere-north:cohere-north:n-api-response, cohere-north:cohere-north:n-doc-89, cohere-north:cohere-north:n-doc-140.
mcp_server Does the product expose itself to other agents over MCP? [unknown]: Unknown for mcp_server. North REST APIs are public. Full API guardrail/audit/rate-limit parity and a turnkey North-as-MCP server were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-north-api, cohere-north:cohere-north:n-api-response, cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries, cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-89, cohere-north:cohere-north:n-doc-140.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

North has web and mobile access; desktop/MDM coverage is unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, North iOS and alpha Android app; version=not specified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: desktop_apps, browser_extension, managed_deployment.

web Is a full web client available? [supported]: Full browser chat, Admin and builders documented. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-18.
desktop_apps Windows and macOS apps? [unknown]: Unknown for desktop_apps. Web and alpha mobile are documented; no desktop package, browser extension, MDM deployment matrix or mobile SSO test was retrieved.
mobile_apps iOS and Android apps with SSO? [partial]: October 16 release documents Android alpha with iOS feature parity for agents/automations/record/translate. Mobile SSO/installation workflow not tested. Sources: cohere-north:cohere-north:n-north-changelog.
browser_extension Is there a browser extension or sidebar? [unknown]: Unknown for browser_extension. Web and alpha mobile are documented; no desktop package, browser extension, MDM deployment matrix or mobile SSO test was retrieved.
managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Unknown for managed_deployment. Web and alpha mobile are documented; no desktop package, browser extension, MDM deployment matrix or mobile SSO test was retrieved.
client_feature_gaps Which features are missing on mobile? [partial]: Mobile record/translate and document review are documented; complete web/admin/builders parity and managed-client matrix not retrieved. Sources: cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-97.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-north-changelog, cohere-north:cohere-north:n-doc-97.

TypingMind / TypingMind Teams

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.

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.

Cohere North

No public information found 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

No public information found 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.

Cohere North

Agent cross-checked Support: partial

Document mode supports translation and writing; controlled layout-preserving translation is unverified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: translation_engine, glossaries.

document_translation Can whole documents be translated with formatting kept? [partial]: Document mode can translate whole generated documents or selections; shortcut is alpha. Preservation of uploaded document layout, tables and glossary terms untested. Sources: cohere-north:cohere-north:n-doc-9.
translation_engine Which engine translates? [unknown]: Unknown for translation_engine. Document mode supports translation/rewriting. Layout-preserving file translation, managed glossary, dedicated engine and de-CH controls were not established.
glossaries Are company glossaries supported? [unknown]: Unknown for glossaries. Document mode supports translation/rewriting. Layout-preserving file translation, managed glossary, dedicated engine and de-CH controls were not established.
formality_and_variants Can formality and regional variants (de-CH) be set? [partial]: Tone actions include professional/friendly/concise/persuasive and prompts can request formal rewrites. Dedicated de-CH/regional controls not established. Sources: cohere-north:cohere-north:n-doc-9.
writing_tools Are dedicated rewrite and proofreading tools available? [supported]: Document editor supports rewriting, tone/length actions, manual edits and prompt-guided revision with history. Sources: cohere-north:cohere-north:n-doc-9.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-9.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Configurable model instructions support writing workflows; dedicated translation fidelity is unestablished.

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.

Cohere North

No public information found 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

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.

Cohere North

Agent cross-checked Support: partial

Alpha dictation and beta long-form mobile recording are documented.

Limitations

Dictation alpha; long-form mobile recording beta.
Remaining atomic gaps: read_aloud, voice_conversation, swiss_german_speech.

dictation Can users dictate prompts? [supported]: Off-by-default alpha dictation supports web/mobile prompts and some instruction/automation fields; configured ASR and microphone permission required. Sources: cohere-north:cohere-north:n-doc-97, cohere-north:cohere-north:n-doc-1.
read_aloud Can answers be read aloud? [unknown]: Unknown for read_aloud. Dictation and long-form mobile recording have alpha/beta states. Read-aloud, conversational speech, automatic meeting capture and Swiss German quality were not established.
voice_conversation Is a live voice mode available? [unknown]: Unknown for voice_conversation. Dictation and long-form mobile recording have alpha/beta states. Read-aloud, conversational speech, automatic meeting capture and Swiss German quality were not established.
meeting_summaries Are meetings transcribed and summarised? [partial]: North can summarise supplied meeting transcripts; beta mobile long recording exists. Automatic meeting participation/transcription and accuracy unverified. Sources: cohere-north:cohere-north:n-doc-1, cohere-north:cohere-north:n-doc-97.
swiss_german_speech Is Swiss German speech recognised? [unknown]: Unknown for swiss_german_speech. Dictation and long-form mobile recording have alpha/beta states. Read-aloud, conversational speech, automatic meeting capture and Swiss German quality were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-97, cohere-north:cohere-north:n-doc-1.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Dictation, read-aloud and audio-summary workflows are documented; live meetings and Swiss German quality are unknown.

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.

Cohere North

Agent cross-checked Support: partial

Beta sandbox/Skills create Office files. Document mode supports iteration, with alpha incremental editing distinguished from the broader document workflow.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform 2.0.1; alpha incremental document editing; sandbox/Skills separately Beta; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

data_analysis: Beta Skills run file-producing work through sandbox_run_python or sandbox_run_command and provide spreadsheet/CSV operations. The sandbox service and skills permission must be enabled. Analysis correctness and formula preservation were not benchmarked.
charts: The document-mode guide describes Data Interpreter creating a chart and embedding it in the editor. The inaccessible sandbox/interpreter guides do not establish a complete plotting-library inventory; chart correctness was not tested.

data_analysis Can it analyse spreadsheets with executed code? [partial]: Beta Skills run file-producing work through sandbox_run_python or sandbox_run_command and provide spreadsheet/CSV operations. The sandbox service and skills permission must be enabled. Analysis correctness and formula preservation were not benchmarked. Sources: cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026.
charts Can it produce charts? [partial]: The document-mode guide describes Data Interpreter creating a chart and embedding it in the editor. The inaccessible sandbox/interpreter guides do not establish a complete plotting-library inventory; chart correctness was not tested. Sources: cohere-north:cohere-north:n-doc-9-20261026.
office_file_output Can it create Word, Excel or PowerPoint files? [supported]: Beta Skills include DOCX/PPTX/XLSX/CSV creation/editing; model and sandbox prerequisites apply. Sources: cohere-north:cohere-north:n-doc-12-20261026.
canvas_editing Is there a document or canvas editor for iterating on output? [supported]: Document mode combines direct editing, prompted edits, version history and PDF/DOCX/MD/HTML export. Incremental document-editing controls are alpha; this does not make the whole criterion beta or generally available. Sources: cohere-north:cohere-north:n-doc-9-20261026, cohere-north:cohere-north:n-north-changelog-20261026.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-12-20261026, cohere-north:cohere-north:north-release-html-20261026, cohere-north:cohere-north:n-doc-9-20261026, cohere-north:cohere-north:n-north-changelog-20261026.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Shared snapshots and source collections have different access boundaries.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: group_chat.

share_chats Can chats be shared inside the organisation? [supported]: Signed-in colleagues open read-only snapshot links with messages, citations, thinking and presented sandbox files; subsequent changes need a new link. Sources: cohere-north:cohere-north:n-doc-4.
team_spaces Are shared projects or workspaces available? [partial]: Beta Libraries share collections via user/group/company roles. Alpha Projects are private per-user workspaces; not shared team Projects. Sources: cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-11.
group_chat Can several people chat together with the AI? [unknown]: Unknown for group_chat. Chat links are static read-only snapshots. Concurrent human group chat and rechecking original-source ACLs on all shared-answer content were not established.
share_permission_boundary Does sharing respect the recipient's access to sources? [partial]: Shared chat exposes existing answer text/files to signed-in recipients; no original-source ACL recheck established. Library/agent retrieval separately checks source and library access. Sources: cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-152.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-4, cohere-north:cohere-north:n-doc-42, cohere-north:cohere-north:n-doc-11, cohere-north:cohere-north:n-doc-152.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Shared agents and prompt libraries are documented, but collaborative project/chat boundaries are not established.

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.

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.

Cohere North

Agent cross-checked Support: partial

User UI offers German and French among eight languages; accessibility and admin translation remain gaps.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: accessibility_statement, admin_ui_languages.

ui_languages Which UI languages are offered? [supported]: Guide lists English default, Spanish, French, Portuguese, Arabic, Japanese, Korean and German. Italian is not in this documented selector list. Sources: cohere-north:cohere-north:n-doc-1.
dach_language_quality Are German, French and Italian UIs complete and natural? [partial]: German/French available; Italian not listed. Completeness/naturalness was not tested and model language support does not prove UI quality. Sources: cohere-north:cohere-north:n-doc-1.
accessibility_statement Is there a WCAG conformance statement? [unknown]: Unknown for accessibility_statement. Eight user UI languages are listed. No WCAG conformance statement, complete German admin UI inventory or DE/FR/IT usability assessment was retrieved.
admin_ui_languages Is the admin interface available in German? [unknown]: Unknown for admin_ui_languages. Eight user UI languages are listed. No WCAG conformance statement, complete German admin UI inventory or DE/FR/IT usability assessment was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Multilingual capability is advertised without a verified DACH UI or accessibility matrix.

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.

Cohere North

Agent cross-checked Support: partial

North supports OIDC, SAML and hybrid identity patterns in customer deployments.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: conditional_access, domain_capture.

sso_protocols Which SSO protocols and identity providers work? [supported]: Dex-based broker supports OIDC preferred/SAML legacy, LDAP shim, Entra-LDAP hybrid and authentication proxy; interactive SSO uses authorization-code PKCE. Sources: cohere-north:cohere-north:n-doc-105.
sso_plan Which plan includes SSO? [partial]: SSO is documented for deployed North; no public commercial tier restriction or included-price matrix retrieved. Sources: cohere-north:cohere-north:n-doc-105.
mfa Can MFA be enforced? [partial]: Authentication proxy supports external MFA chains; no standalone North-enforced MFA policy was retrieved. Sources: cohere-north:cohere-north:n-doc-105.
conditional_access Do Entra conditional-access policies apply? [unknown]: Unknown for conditional_access. SSO protocols and IdP integration are documented. Tenant MFA/conditional-access enforcement and domain capture were not exercised.
domain_capture Can the company claim its email domain? [unknown]: Unknown for domain_capture. SSO protocols and IdP integration are documented. Tenant MFA/conditional-access enforcement and domain capture were not exercised.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-105.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

JIT and alpha SCIM provision users/groups; deletion preserves selected shared assets.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

SCIM alpha; graceful deletion settings beta. Commercial seat assignment unverified.
Remaining atomic gaps: seat_assignment.

scim Is SCIM provisioning supported? [supported]: SCIM2 alpha provides user/group lifecycle and is bidirectional; incompatible with some connector group-filter settings. Sources: cohere-north:cohere-north:n-doc-112.
group_sync Are identity-provider groups synced? [partial]: JIT groups hydrate at login/session refresh; SCIM can sync groups including matching preregistered names. No propagation measurement. Sources: cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-112.
jit_provisioning Are users created at first login? [supported]: First successful login automatically creates user linked to external ID; no pre-invite required in this documented mode. Sources: cohere-north:cohere-north:n-doc-111.
deprovisioning What happens to a removed user's data and shared assets? [supported]: Disable removes access reversibly; delete uses grace policy, keeps shared agents/workflows/files but removes Microsoft libraries even if shared. Admin can transfer preserved assets; cleanup asynchronous. Sources: cohere-north:cohere-north:n-doc-112, cohere-north:cohere-north:n-doc-90, cohere-north:cohere-north:n-doc-153.
seat_assignment Can admins assign and reclaim seats? [unknown]: Unknown for seat_assignment. JIT and alpha bidirectional SCIM are documented. Commercial seat assignment and measured identity-propagation timing were not retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-112, cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-90, cohere-north:cohere-north:n-doc-153.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

North delegates fine-grained roles/groups; separately administered subsidiaries count as application instances.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: System roles include Agent/Automation/Tools managers, Compliance Requester/Approver and Library Access Manager; custom roles and individual temporary assignments. Some grants, including model configuration, must be assigned directly. Sources: cohere-north:cohere-north:n-doc-114.
groups Can permissions be set per group? [supported]: Permissions/roles/resources assign users, IdP groups or company. JIT group membership updates with token/session refresh; rename/delete needs configuration review. Sources: cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-111.
feature_toggles Which features can be switched on or off per group? [supported]: Group grants control agents, tools, libraries, automation and some admin capabilities; models additionally have alpha RBAC and inherited-owner exceptions. Sources: cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-134, cohere-north:cohere-north:n-doc-18.
multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Separate administered installation with its own users/config/data is a separate licensed Application Instance, including business units/subsidiaries. Single-contract multi-instance price unknown. Sources: cohere-north:cohere-north:n-doc-158.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-114, cohere-north:cohere-north:n-doc-111, cohere-north:cohere-north:n-doc-134, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-158.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Alpha analytics offers detailed adoption/usage exports with named-user visibility.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported.

adoption_dashboard Is there an adoption dashboard? [supported]: Separate Helm/ClickHouse analytics stack reports adoption, agents, automations, tools and libraries with date/group filters. Sources: cohere-north:cohere-north:n-doc-78.
breakdowns Can usage be broken down by group, model, feature and assistant? [supported]: Groups/models/sources/agents/workflows/tools and user leaderboards documented; sampled/capped cards have explicit limitations. Sources: cohere-north:cohere-north:n-doc-78.
export Can usage data be exported? [supported]: Cards export CSV data or PNG; CSV includes user names and capped tables export only loaded scope. Sources: cohere-north:cohere-north:n-doc-78.
privacy_modes Can per-person reporting be limited or pseudonymised? [partial]: Raw analytics event collection can be disabled and retention configured. This does not establish pseudonymisation or removal of named-user reporting in the dashboard. Sources: cohere-north:cohere-north:n-doc-95, cohere-north:cohere-north:n-doc-78.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-78, cohere-north:cohere-north:n-doc-95.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

North reports token use and can limit capacity; a currency budget ledger is unverified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported.
Remaining atomic gaps: chargeback.

cost_visibility Can admins see cost or consumption per user and group? [partial]: Analytics shows user/group/agent/model token activity; Prometheus/Grafana has provider/model billed/raw counters without per-user labels and can undercount. Currency cost reconciliation unknown. Sources: cohere-north:cohere-north:n-doc-78, cohere-north:cohere-north:n-doc-207.
budgets Can budgets be set per user or group? [partial]: Alpha Flow control caps requests/input/output tokens by user/group/rules, not a verified CHF/EUR spend budget. Sources: cohere-north:cohere-north:n-doc-137.
budget_enforcement Does reaching a budget alert, block or downgrade? [partial]: Limits block for the window only when Helm proxy deployed; unlimited default/failure allow option can admit use. Currency overshoot bounds and chargeback not tested. Sources: cohere-north:cohere-north:n-doc-137.
chargeback Can costs be exported per cost centre? [unknown]: Unknown for chargeback. Token metrics and alpha capacity limits are documented. Currency budgets, billing reconciliation and cost-centre allocation were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-78, cohere-north:cohere-north:n-doc-207, cohere-north:cohere-north:n-doc-137.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Alpha audits and approval-controlled compliance export coexist with operator log forwarding.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

content_logging: Alpha Compliance uses a request/approval workflow for 24-hour conversation review and CSV export, including guardrail-blocked/redacted messages. Self-approval is forbidden; view access and self-grants are restricted. Exact Organization admin approval rights remain unknown because the permission table and Reviewing requests prerequisite disagree.
siem_export: Audit records can be queried through GET /v1/admin/audits, with an actions endpoint and date/action filters. A complete supported SIEM integration, delivery/retry guarantee or content-stream schema was not established.
ediscovery: Compliance supports investigation/preservation downloads; specific eDiscovery/legal hold preventing deletion was not established.
log_retention: Retrieved Audits and Compliance pages do not state numeric audit-log retention or immutability. Analytics-event retention is a different dataset, and the general Security page could not be retrieved in public representations. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/audits?format=html, https://private.docs.cohere.com/north/docs/admin/compliance?format=html, https://private.docs.cohere.com/north/docs/admin/permissions?format=html. No additional scoped evidence established this answer.

admin_events Are admin and security events logged? [supported]: Audits records identity, permission, configuration, model/tool, sharing and compliance events; filters and GET audit API exist. Sources: cohere-north:cohere-north:n-doc-140-20261026.
content_logging Can prompts and answers be retained for compliance, and is it configurable? [partial]: Alpha Compliance uses a request/approval workflow for 24-hour conversation review and CSV export, including guardrail-blocked/redacted messages. Self-approval is forbidden; view access and self-grants are restricted. Exact Organization admin approval rights remain unknown because the permission table and Reviewing requests prerequisite disagree. Sources: cohere-north:cohere-north:n-doc-139-20261026.
siem_export Can logs stream to a SIEM or be exported? [partial]: Audit records can be queried through GET /v1/admin/audits, with an actions endpoint and date/action filters. A complete supported SIEM integration, delivery/retry guarantee or content-stream schema was not established. Sources: cohere-north:cohere-north:n-doc-140-20261026.
ediscovery Are eDiscovery and legal hold supported? [partial]: Compliance supports investigation/preservation downloads; specific eDiscovery/legal hold preventing deletion was not established. Sources: cohere-north:cohere-north:n-doc-139-20261026.
log_retention How long are logs kept? [unknown]: Retrieved Audits and Compliance pages do not state numeric audit-log retention or immutability. Analytics-event retention is a different dataset, and the general Security page could not be retrieved in public representations. Search on 2026-10-26: https://private.docs.cohere.com/north/docs/admin/audits?format=html, https://private.docs.cohere.com/north/docs/admin/compliance?format=html, https://private.docs.cohere.com/north/docs/admin/permissions?format=html. No additional scoped evidence established this answer.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-140-20261026, cohere-north:cohere-north:n-doc-139-20261026.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Selected-customer beta HiddenLayer can detect/block/redact PII, with permissive defaults and failure paths.

Availability: beta · Delivery: native
Scope: surfaces=Customer-hosted North and Compass Kubernetes deployment, North 2 web application and Admin console; version=not specified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=Selected-customer HiddenLayer beta deployment; commercial cost unverified; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: custom_patterns.

pii_detection Is personal data detected in prompts and files? [partial]: HiddenLayer scans configured prompt/response/tool content and PII entity types; beta available to selected customers after deployment. File coverage depends on what reaches scanned requests, not a verified whole-file DLP pipeline. Sources: cohere-north:cohere-north:n-doc-138.
pii_action Is it redacted, masked, blocked or only warned? [partial]: ALLOW/BLOCK/REDACT supported. Default monitor_only does not enforce; background scans and timeouts can occur after delivery, unsupported entities fail open. Effectiveness not tested. Sources: cohere-north:cohere-north:n-doc-138.
custom_patterns Can admins add custom patterns or terms? [unknown]: Unknown for custom_patterns. Selected-customer beta HiddenLayer scanning is documented. Custom regex/customer dictionaries and an external enterprise DLP integration matrix were not retrieved.
dlp_integration Does it integrate with an existing DLP product? [partial]: HiddenLayer AIDR integration documented; generic existing-DLP/Purview connector not established. Sources: cohere-north:cohere-north:n-doc-138, cohere-north:cohere-north:n-doc-193.
filter_location Where does filtering run? [supported]: Documented self-contained GPU engine runs inside customer cluster with external HiddenLayer cloud disabled; requires both HiddenLayer and cohere-guardrails releases. Sources: cohere-north:cohere-north:n-doc-193.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-138, cohere-north:cohere-north:n-doc-193.

TypingMind / TypingMind Teams

No public information found 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.

Cohere North

Agent cross-checked Support: partial

Organisation instructions/policy acceptance exist; content safety checks are advisory.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The vendor marks this control alpha. The catalogue availability field stays unknown because its enum has no alpha value; this does not mean unsupported.

org_instructions Can admins set organisation-wide instructions? [supported]: Optional company instructions append to preamble across all models; agent instructions also apply. Sources: cohere-north:cohere-north:n-doc-86.
usage_notice Can users be required to accept a usage policy? [supported]: Alpha hosted terms can require acceptance at sign-up/tool use and re-acceptance after versions. External terms URL overrides hosted terms. Sources: cohere-north:cohere-north:n-doc-145.
content_filters Are content filters configurable? [partial]: Alpha Content Compliance Auditor offers Contextual/Strict, targeted user/group rules and qualified models. Model chooses whether to check/refuse; unavailable/error verdict can be safe, so not mandatory enforcement. Sources: cohere-north:cohere-north:n-doc-138.
violation_reporting Are policy hits visible to admins? [supported]: Guardrail Events list conversation decisions/categories/actions. Safety Block means unsafe verdict to model, not proof response was prevented. Sources: cohere-north:cohere-north:n-doc-138.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-86, cohere-north:cohere-north:n-doc-145, cohere-north:cohere-north:n-doc-138.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Private North follows customer infrastructure placement; external inference and support need separate scope.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

storage_region Where are chats, files and indexes stored? [partial]: North/Compass data resides in customer VPC/on-prem storage. Customer chooses country; no fixed vendor-hosted North region matrix retrieved. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-168.
inference_region Where do model calls run, per provider? [partial]: Local model chart stays in customer environment; optional Vault/Foundry/other APIs route inference to separately configured regions. Actual contracted provider region unverified. Sources: cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-doc-218.
backups_logs_region Where are backups, logs and telemetry? [partial]: Operators configure backups, logs and telemetry collectors in their environment. Docs do not fix country or require all exports remain local. Sources: cohere-north:cohere-north:n-doc-214, cohere-north:cohere-north:n-doc-208, cohere-north:cohere-north:n-doc-146.
support_access_region From where can vendor staff access data? [partial]: Private-deployment commitment says Cohere does not receive customer prompts; optional Vault processes inference and support bundles may be shared. Support-staff countries/contract access rules unknown. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-217.
swiss_hosting Is Swiss hosting available? [partial]: Customer can place private infrastructure in its chosen country, but a Cohere-operated Swiss North hosting SKU/residency promise was not established. Sources: cohere-north:cohere-north:n-private.
residency_plan Which plan or option provides residency? [partial]: Customer-managed private deployment controls location; optional external inference/telemetry/connector routes require separate governance. No named residency add-on price retrieved. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-217.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-doc-218, cohere-north:cohere-north:n-doc-214, cohere-north:cohere-north:n-doc-208, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-commitments.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

North can run in customer cloud, on-prem or air-gapped; optional managed inference changes that boundary.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: multi_tenant_saas.

multi_tenant_saas Is a shared SaaS offered? [unknown]: Unknown for multi_tenant_saas. Private VPC/on-prem/air-gapped deployment is documented. Seat floors, full SaaS offers and every disconnected-mode feature exception were not established.
dedicated_instance Is a dedicated single-tenant instance offered, from what size? [partial]: Customer-managed North instance supported; Model Vault inference is dedicated Cohere-managed. Minimum seat/capacity size unpriced. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-vault.
customer_cloud Can it run in the customer's own cloud account, from what size? [partial]: North Helm installs on customer Kubernetes/VPC; infrastructure/network/security operated by customer. No minimum seats retrieved. Sources: cohere-north:cohere-north:n-doc-165, cohere-north:cohere-north:n-private.
on_premise Can the whole platform run on customer infrastructure, from what size? [partial]: Whole North app plus Compass/models documented for customer on-prem Kubernetes; component/GPU dependencies apply. No seat floor retrieved. Sources: cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-doc-168.
air_gapped Can it run without internet access? [partial]: Vendor explicitly offers air-gapped on-prem deployment. External API/search/remote MCP unavailable without egress; registry/image supply needs mirroring. Contracted disconnected feature matrix not retrieved. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-159.
mode_feature_gaps Which features are missing outside SaaS? [partial]: Remote MCP needs internet; external search/inference also need provider access. Local visual parsing/guardrails require extra models/GPU services. Full parity unknown. Sources: cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-193.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-vault, cohere-north:cohere-north:n-doc-165, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-doc-168, cohere-north:cohere-north:n-doc-126, cohere-north:cohere-north:n-doc-159, cohere-north:cohere-north:n-doc-14, cohere-north:cohere-north:n-doc-193.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Private North and hosted model APIs have different data-use policies.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

vendor_training Does the vendor train on customer content? [partial]: Private deployment commitments say Cohere receives no prompts/outputs. Cohere Platform API separately permits opt-out training; do not apply that SaaS default to private North. Optional Vault processes inference. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-217.
provider_training Do model providers train on it under this product's contracts? [partial]: Self-hosted inference does not call external provider. If operator configures third-party APIs, their customer contracts govern; no blanket no-training assurance retrieved. Sources: cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-commitments.
provider_retention How long do model providers keep prompts, including for abuse monitoring? [partial]: Separate Cohere SaaS model Platform logs default30 days with legal/contract/abuse exceptions; private North retention configured locally. Other configured provider retention unverified. Sources: cohere-north:cohere-north:n-commitments.
zero_retention Is zero data retention available, and on which plan? [partial]: North↔Model Vault guide documents optional ZDR for inference; North app data remains stored locally. Platform ZDR approval applies separately; not zero chat persistence. Sources: cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-commitments.
human_review Can provider staff review content? [partial]: Private prompts do not reach Cohere by default. Platform security teams may review flagged logs; local admins/investigators can review under North compliance process. Third-party staff rules unknown. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-139.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-doc-177, cohere-north:cohere-north:n-doc-139.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

TypingMind asserts no vendor training; customer provider contracts control training and retention.

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.

Cohere North

Agent cross-checked Support: partial

Retention and deletion are operator-configured with separate conversation and user policies.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Conversation retention alpha; graceful account deletion beta. Commercial exit deadline unknown.
Remaining atomic gaps: contract_end_deletion.

default_retention What is retained and for how long by default? [partial]: Automatic conversation age retention off by default; manually deleted conversations still hard-delete on hourly job with zero effective timeout. Backup/shared-resource retention differs. Sources: cohere-north:cohere-north:n-doc-88, cohere-north:cohere-north:n-doc-153.
admin_retention Can admins set retention periods? [supported]: Alpha enabled defaults90 days from creation plus30-day soft-delete timeout; configurable1+days and0–365days. Retroactive changes and batch queues can affect timing. Sources: cohere-north:cohere-north:n-doc-88.
user_deletion Can users delete their chats and files permanently? [partial]: Users delete conversations; hourly hard cleanup removes messages/metadata with best-effort external resources. Account private-data cleanup follows beta grace policy; shared assets can persist. Sources: cohere-north:cohere-north:n-doc-153, cohere-north:cohere-north:n-doc-90.
contract_end_deletion What is deleted at contract end, and when? [unknown]: Unknown for contract_end_deletion. Conversation/user deletion policies are documented. Commercial contract-end deletion and guaranteed backup purge deadlines were not retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-88, cohere-north:cohere-north:n-doc-153, cohere-north:cohere-north:n-doc-90.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Published terms name Cohere Inc. and the Trust Center lists subprocessors; ultimate post-combination ownership and the complete contracted North inventory remain unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=Published Cohere terms and Trust Center as retrieved 2026-10-21; post-combination ownership excluded as unverified; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

subprocessor_list: Trust Center exposes subprocessors but no visible revision date; complete North-specific contracted inventory not verified.
subprocessor_countries: Visible rows list Google Cloud, Fullstory, LaunchDarkly, New Relic, Retool, Sentry, Segment, Sendgrid and Vercel in USA. Scope mainly hosted services, not automatic private North content recipients.
change_notification: Unknown for change_notification. Public Trust Center lists subprocessors without a visible revision date. Full contracted North scope, change notices and post-combination legal structure remain unverified. Search on 2026-10-26: https://trustcenter.cohere.com/?format=html, https://cohere.com/terms-of-use, https://cohere.com/blog/cohere-and-aleph-alpha-sign-agreement. No additional scoped evidence established this answer.
parent_jurisdiction: The public terms name Cohere Inc. and Ontario/Toronto law. The September 16 Aleph Alpha business-combination agreement remains described as subject to final regulatory approvals in that announcement. Current October 15 AISLE copy calls Aleph Alpha a partnership, not a completed acquisition; no subsequent first-party closing notice was located. A post-combination parent/jurisdiction is not asserted.
transfer_mechanism: Trust Center says its multi-jurisdictional DPA incorporates2021 EU SCCs and describes a TIA. NDA-gated DPA and exact Swiss adaptations not inspected.
government_access_policy: Trust FAQ describes prompt customer notice of government requests unless prohibited, within DPA commitments. Actual North contract/transparency statistics unverified.

subprocessor_list Is a dated sub-processor list published? [partial]: Trust Center exposes subprocessors but no visible revision date; complete North-specific contracted inventory not verified. Sources: cohere-north:cohere-north:n-trust-20261026.
subprocessor_countries Which countries do sub-processors operate in? [partial]: Visible rows list Google Cloud, Fullstory, LaunchDarkly, New Relic, Retool, Sentry, Segment, Sendgrid and Vercel in USA. Scope mainly hosted services, not automatic private North content recipients. Sources: cohere-north:cohere-north:n-trust-20261026.
change_notification Are customers notified of sub-processor changes? [unknown]: Unknown for change_notification. Public Trust Center lists subprocessors without a visible revision date. Full contracted North scope, change notices and post-combination legal structure remain unverified. Search on 2026-10-26: https://trustcenter.cohere.com/?format=html, https://cohere.com/terms-of-use, https://cohere.com/blog/cohere-and-aleph-alpha-sign-agreement. No additional scoped evidence established this answer.
parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: The public terms name Cohere Inc. and Ontario/Toronto law. The September 16 Aleph Alpha business-combination agreement remains described as subject to final regulatory approvals in that announcement. Current October 15 AISLE copy calls Aleph Alpha a partnership, not a completed acquisition; no subsequent first-party closing notice was located. A post-combination parent/jurisdiction is not asserted. Sources: cohere-north:cohere-north:n-terms-20261026, cohere-north:cohere-north:n-combination-20261026, cohere-north:cohere-north:corporate-aisle-20261026.
transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [partial]: Trust Center says its multi-jurisdictional DPA incorporates2021 EU SCCs and describes a TIA. NDA-gated DPA and exact Swiss adaptations not inspected. Sources: cohere-north:cohere-north:n-trust-20261026.
government_access_policy Is there a published government-access or transparency policy? [partial]: Trust FAQ describes prompt customer notice of government requests unless prohibited, within DPA commitments. Actual North contract/transparency statistics unverified. Sources: cohere-north:cohere-north:n-trust-20261026.

Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust-20261026, cohere-north:cohere-north:n-terms-20261026, cohere-north:cohere-north:n-combination-20261026, cohere-north:cohere-north:corporate-aisle-20261026.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

A public DPA lists processors and transfer measures; vendor legal jurisdiction differs from hosting region.

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.

Cohere North

Agent cross-checked Support: partial

DPA and regulatory resources are listed, but North-specific contract terms remain unverified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

dpa Is a DPA available, and is it negotiable? [partial]: Trust Center says DPA available on request with NDA; Enterprise Data Commitments offers SaaS DPA but says private deployment receives no input processing. No contact/request made; North negotiated terms unknown. Sources: cohere-north:cohere-north:n-trust, cohere-north:cohere-north:n-commitments.
revdsg_gdpr Does the DPA cover revDSG and GDPR? [partial]: Vendor says multi-jurisdictional DPA/GDPR compliance. Explicit revised Swiss DSG terms not retrieved from gated DPA. Sources: cohere-north:cohere-north:n-trust.
governing_law Which law and court govern the contract? [partial]: General 2022website/service terms choose Ontario/Canadian law and Toronto courts, subject to subscription agreement. Binding North commercial agreement not retrieved. Sources: cohere-north:cohere-north:n-terms.
ai_act_materials Is EU AI Act documentation provided? [partial]: Trust Center lists EU AI Act/GPAI Code of Practice FAQs. Contents and North deployment obligations not inspected. Sources: cohere-north:cohere-north:n-trust.
sector_materials Are FINMA or other sector materials provided? [partial]: Trust FAQ says BAA only for approved custom model development and excludes Cohere-hosted SaaS/PHI. North-specific health/FINMA contract not retrieved. Sources: cohere-north:cohere-north:n-trust.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust, cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-terms.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

A public GDPR DPA and Singapore-law business terms are available; Swiss and sector-specific undertakings remain gaps.

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.

Cohere North

Agent cross-checked Support: partial

Trust Center lists attestations; certificates and reports were not verified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: c5.

iso_27001 ISO 27001 with scope and validity? [partial]: ISO 27001 certificate listed behind request; issuer, scope and validity unknown. Sources: cohere-north:cohere-north:n-trust.
soc2 SOC 2 type, period and covered service? [partial]: SOC 2 Type II annual audit/report listed, request and signed mutual NDA needed; report period/scope not inspected. Sources: cohere-north:cohere-north:n-trust.
c5 BSI C5 attestation? [unknown]: Unknown for c5. Trust Center lists certificates and reports behind requests. Issuer, scope, validity and independent report contents were not inspected.
other_certifications Which other certificates (27701, 42001, TISAX)? [partial]: ISO 42001 and UK Cyber Essentials for Cohere Inc./Cohere UK listed. Certificate validity/scope not inspected. Sources: cohere-north:cohere-north:n-trust.
report_access How can customers obtain reports? [supported]: Trust Center requests gate reports; SOC 2 requires signed mutual NDA, DPA also NDA-gated. No request made. Sources: cohere-north:cohere-north:n-trust.
pentest Are independent penetration test summaries available? [partial]: Latest API and web penetration test reports listed behind request; findings/scope/date not inspected. Sources: cohere-north:cohere-north:n-trust.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust.

TypingMind / TypingMind Teams

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).

Cohere North

Agent cross-checked Support: partial

Customer keys can encrypt chat columns; workflows and other stores need separate controls.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

encryption_at_rest Is data encrypted at rest? [partial]: Optional deployment-level AES256GCM envelope encryption covers sensitive PostgreSQL chat columns, excluding automations/workflows. Operator must secure object/index/backups and database volumes separately. Sources: cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-146.
customer_managed_keys Can the customer manage or hold the keys? [partial]: Operator supplies32-byte master key in Kubernetes Secret or chart generates it; wrapped DEKs stay in database, key rotation supported. Hardware-held external-KMS entitlement not established. Sources: cohere-north:cohere-north:n-doc-154.
private_networking Is private connectivity or IP restriction available? [partial]: Customer manages VPC, ingress/egress, TLS and Kubernetes network policies; private/on-prem operation documented. These are deployment tasks, not proof every installation enforces them. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-doc-159.
tenant_isolation How are customers separated in shared SaaS? [partial]: Each separately administered installation has own users/config/data; customer operates cluster/network isolation. Multi-tenant hosted North architecture not established. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-doc-146.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-146, cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-doc-159, cohere-north:cohere-north:n-doc-158.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Profession-specific secrecy undertaking and add-on remain unknown; general confidentiality and scoped content-access controls do not establish §203 StGB or Art.321 StGB coverage.

Availability: unknown · Delivery: unknown
Scope: surfaces=Customer-hosted North and Compass Kubernetes deployment, North 2 web application and Admin console, Optional Cohere-managed Model Vault inference with customer-hosted North; version=North 2.0.1; plan=Customer-hosted North 2.0.1 under custom commercial contract; optional Model Vault/external models separately scoped; add_ons=none stated; deployment_mode=not specified; region=No profession-specific DE/CH contractual scope verified; deployment/provider regions follow the other scoped claims.; os=not specified.

Limitations

Contract facts only; no legal suitability assessment. No profession-specific commitment or paid option inferred from generic confidentiality, hosting, encryption or no-training terms.
Public, unauthenticated source pass only; no sales contact, NDA request or authenticated access-control test.

secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: Unknown. Reviewed North security/encryption/compliance and private-deployment data flows, Trust Center and Enterprise Data Commitments, plus targeted first-party professional-secrecy searches. DPA is request/NDA-gated. No public North §203 StGB or Art.321 StGB undertaking or profession-specific add-on was retrieved; none requested. A DPA or no-training clause alone does not answer whether a profession-specific undertaking is signed.
subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: Unknown. No retrieved §203/Art.321 undertaking establishes flow-down to all relevant subcontractors/model providers. General DPA confidentiality is not equivalent.
secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: Unknown. No documented profession-specific plan, dedicated instance option or paid secrecy add-on and its entitlements/pricing were established.
content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Private-deployment commitments say Cohere does not receive customer prompts/outputs; the local North app decrypts configured chat columns for use and authorised investigators can export conversations. Optional Model Vault processes inference despite ZDR, and external model endpoints follow their contracts. No complete staff/subprocessor plaintext matrix or secrecy undertaking was inspected. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-trust.
secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Unknown. Reviewed North security/encryption/compliance and private-deployment data flows, Trust Center and Enterprise Data Commitments, plus targeted first-party professional-secrecy searches. DPA is request/NDA-gated. No public North §203 StGB or Art.321 StGB undertaking or profession-specific add-on was retrieved; none requested. General data-flow/security pages are available but do not document such a secrecy offering.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-commitments, cohere-north:cohere-north:n-doc-154, cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-doc-217, cohere-north:cohere-north:n-trust.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

North uses capacity and installation licensing with custom prices.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: overage.

pricing_unit What is the pricing unit? [supported]: Compute Units cover model GPU capacity via hardware/model factors; Application Instances count separate administered North installations. Not documented as a universal per-seat tariff. Sources: cohere-north:cohere-north:n-doc-158.
list_prices What are list prices per plan, with date and currency? [partial]: North pricing page says custom enterprise pricing; numeric North licence rates not published in retrieved sources. Separate Model Vault/API rates are not North total. Sources: cohere-north:cohere-north:n-pricing.
included_usage What usage is included? [partial]: Licensed capacity depends on GPUs/model factors, application instances and contract; no public included-message allowance retrieved. Sources: cohere-north:cohere-north:n-doc-158.
add_ons Which features cost extra? [partial]: Model Vault inference, external provider/search API contracts, extra parser/guardrail GPUs and deployment services may add cost; exact included entitlements/rates unknown. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-193, cohere-north:cohere-north:n-doc-14.
overage What do usage beyond limits and premium models cost? [unknown]: Unknown for overage. Compute units/application instances and custom pricing are documented. North rates, included usage, minimums and extras were not quoted or invented.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-193, cohere-north:cohere-north:n-doc-14.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Shared-scenario North totals remain unknown because the commercial rates and capacity sizing are not public.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

cost_200 Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: twelve months, excl VAT, no discounts, 330 messages/user/month. At 200 users, North licence/capacity, infrastructure, implementation and support are unknown in EUR/CHF. No total or nonzero floor can be calculated without North tariff and sizing. Separate Model Vault/API prices are not substitutes. FX basis: ECB 2026-10-20 EUR1=USD1.1215=CHF0.9237. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb.
cost_1000 Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: twelve months, excl VAT, no discounts, 330 messages/user/month. At 1,000 users, North licence/capacity, infrastructure, implementation and support are unknown in EUR/CHF. No total or nonzero floor can be calculated without North tariff and sizing. Separate Model Vault/API prices are not substitutes. FX basis: ECB 2026-10-20 EUR1=USD1.1215=CHF0.9237. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb.
cost_5000 Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21: twelve months, excl VAT, no discounts, 330 messages/user/month. At 5,000 users, North licence/capacity, infrastructure, implementation and support are unknown in EUR/CHF. No total or nonzero floor can be calculated without North tariff and sizing. Separate Model Vault/API prices are not substitutes. FX basis: ECB 2026-10-20 EUR1=USD1.1215=CHF0.9237. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb.
variable_share Which part depends on usage? [partial]: Capacity, replicas and external model/search usage vary;330 messages/user does not determine GPUs, parallelism or tool calls. Vendor-recommended model cannot price unknown North commercial terms; variable currency share remains unknown. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-pricing.
unknown_parts Which costs could not be priced? [partial]: North licence per CU/instance, minimum capacity, model translation factors for chosen current models, HA/GPU sizing, external usage, storage/network, support, rollout and taxes outside excl VAT basis. No quote/contact requested. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:fx-ecb.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Public demo and model API trial do not verify a full North tenant trial.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

The partial atomic answers state their documentation or verification limits.

free_tier Is there a free tier for business use? [partial]: Pricing page distinguishes free rate-limited model API trial from paid production; trial key prohibited for commercial/production use. A free North business tier not established. Sources: cohere-north:cohere-north:n-pricing.
self_serve_trial Is a self-serve business trial available? [partial]: North links instant demo/custom pricing; no self-serve North tenant with SSO/admin/connectors was provisioned or established. Sources: cohere-north:cohere-north:n-home, cohere-north:cohere-north:n-pricing.
trial_scope Do trials include SSO, connectors and admin features? [partial]: Free model API trial does not establish North SSO, connectors or administration. Full North evaluation scope unknown. Sources: cohere-north:cohere-north:n-pricing.
sales_gate Does meaningful evaluation require sales contact? [partial]: North custom pricing and private rollout route through sales; whether an independent full tenant evaluation can start without contact remains unknown. No contact made. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-private.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-pricing, cohere-north:cohere-north:n-home, cohere-north:cohere-north:n-private.

TypingMind / TypingMind Teams

Agent cross-checked Support: partial

Teams SaaS has a self-serve trial; self-host evaluation is a separate sales-gated route.

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.

Cohere North

Agent cross-checked Support: partial

North contract minimums, term and local billing are unverified; pricing is quote-only.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: contract_length, cancellation, local_invoicing.

minimum_commitment What seat or spend minimum applies? [partial]: Each separately administered installation counts as an Application Instance; compute-unit licence metric exists, but numeric minimum/spend not retrieved. Sources: cohere-north:cohere-north:n-doc-158.
contract_length What contract lengths are offered? [unknown]: Unknown for contract_length. North custom enterprise contract was not public in retrieved sources; minimums, term, reduction and invoice currencies remain unknown.
cancellation How can the contract be cancelled or reduced? [unknown]: Unknown for cancellation. North custom enterprise contract was not public in retrieved sources; minimums, term, reduction and invoice currencies remain unknown.
local_invoicing Can it be invoiced in CHF or EUR from a European entity? [unknown]: Unknown for local_invoicing. North custom enterprise contract was not public in retrieved sources; minimums, term, reduction and invoice currencies remain unknown.
transparency_class Is pricing transparent, partial, quote-only or unknown? [supported]: Quote-only for North licence/deployment. Separate Model Vault instance rates and model API tariffs do not make North pricing transparent. Sources: cohere-north:cohere-north:n-pricing.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-pricing.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

North is commercially licensed; component source rights and branding terms need contract review.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: enterprise_features_closed.

licence_type Which licence applies to each component? [partial]: Commercial CU/Application Instance licence documented; full North application/model/component licence texts not retrieved. Sources: cohere-north:cohere-north:n-doc-158.
branding_restrictions Do licence terms restrict branding or user counts? [partial]: White-label settings configure product branding; entitlement, use restrictions and licence fee terms unverified. Separate installations count for licensing, with no public per-user cap retrieved. Sources: cohere-north:cohere-north:n-doc-142, cohere-north:cohere-north:n-doc-158.
enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Unknown for enterprise_features_closed. North is commercially licensed by capacity/installations. Full application/model component licences and branding rights were not publicly retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-158, cohere-north:cohere-north:n-doc-142.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

APIs and approved exports provide some portability; full tenant exit is unverified.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: post_termination_window.

chat_export Can admins export all chats? [partial]: Alpha compliance approves targeted user/agent conversations for24 hours and downloadsCSV. API lists/retrieves conversations; a single complete admin export and preservation hold not established. Sources: cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-north-api.
assistant_export Can assistants and prompts be exported in a reusable format? [partial]: Automation definitions export reusableJSON graph/dependencies but omit credentials and schedules. Agent configurations have API access/version history; full portable agent export not established. Sources: cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-north-api.
knowledge_export Can knowledge bases and their sources be exported? [partial]: File API retrieves content and library metadata APIs exist; complete all-index/source bulk export and permission preservation not established. Sources: cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries.
export_format Are formats documented and machine-readable? [partial]: AutomationJSON, complianceCSV, original file API content and documentPDF/DOCX/HTML/TXT/MD are documented. These do not constitute complete tenant-state export. Sources: cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-doc-9.
post_termination_window How long can data be retrieved after termination? [unknown]: Unknown for post_termination_window. Automation JSON, API files and approved compliance CSV are documented. Complete bulk tenant export, agent portability and post-exit recovery window remain unverified.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-139, cohere-north:cohere-north:n-north-api, cohere-north:cohere-north:n-doc-29, cohere-north:cohere-north:n-api-upload, cohere-north:cohere-north:n-api-libraries, cohere-north:cohere-north:n-doc-9.

TypingMind / TypingMind Teams

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.

Cohere North

Agent cross-checked Support: partial

Support resources exist; North SLA, regional entity and support languages remain unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: support_languages, uptime_sla.

support_channels Which support channels are available on each plan? [partial]: Private deployments include access to solution architects, applied ML and customer success; public security/support resources exist. Contracted response times unknown. Sources: cohere-north:cohere-north:n-private.
support_languages Is support available in German, French or Italian? [unknown]: Unknown for support_languages. Public support/status resources and deployment assistance exist; response languages, North SLA credits and contracted DACH entity were not established.
regional_presence Is there a DACH or Swiss entity, team or partner? [partial]: September 16 agreement plans Berlin/Toronto headquarters and Heidelberg research subject to close. A North-contract Swiss/DACH delivery entity or completed combination was not verified. Sources: cohere-north:cohere-north:n-combination.
uptime_sla Is there an uptime SLA with credits? [unknown]: Unknown for uptime_sla. Public support/status resources and deployment assistance exist; response languages, North SLA credits and contracted DACH entity were not established.
status_page Is there a public status page with history? [partial]: Cohere has a public hosted API status page. Customer-hosted North availability is operator-managed; a North-wide hosted status/SLA not established. Sources: cohere-north:cohere-north:n-status, cohere-north:cohere-north:n-doc-165.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-combination, cohere-north:cohere-north:n-status, cohere-north:cohere-north:n-doc-165.

TypingMind / TypingMind Teams

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.

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.

Cohere North

Agent cross-checked Support: partial

Deployment assistance and public user/builder guides are offered; included service scope is unknown.

Availability: unknown · Delivery: native
Scope: surfaces=North 2 web application and Admin console, Customer-hosted North and Compass Kubernetes deployment; version=North platform2.0.1; exact docs feature state stated per atom; plan=North custom enterprise contract; current 2.0.1 release and per-feature states, entitlements unverified; add_ons=none stated; deployment_mode=not specified; region=Customer-selected private deployment; cloud inference and provider region configured separately; os=not specified.

Limitations

Remaining atomic gaps: adoption_programme, service_cost.

onboarding_service Is guided onboarding included? [partial]: Vendor describes rollout support from architects, applied ML and customer success. Included hours/fees are not published. Sources: cohere-north:cohere-north:n-private.
user_training Is end-user training offered, in which languages? [partial]: Public user/agent/workflow guides support self-learning. Live end-user training and language entitlement not established. Sources: cohere-north:cohere-north:n-guide, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-16.
use_case_library Are role-based use cases and templates provided? [supported]: Agent guide gives ticket deflection/sales/legal examples and internal agent catalogue permits sharing; document/Skills guides include task examples. Sources: cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-21, cohere-north:cohere-north:n-doc-12.
adoption_programme Is there a champion or adoption programme? [unknown]: Unknown for adoption_programme. Vendor offers rollout assistance and guides; service language, included hours, adoption programme and costs were not retrieved.
service_cost Which services cost extra? [unknown]: Unknown for service_cost. Vendor offers rollout assistance and guides; service language, included hours, adoption programme and costs were not retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-private, cohere-north:cohere-north:n-guide, cohere-north:cohere-north:n-doc-18, cohere-north:cohere-north:n-doc-16, cohere-north:cohere-north:n-doc-21, cohere-north:cohere-north:n-doc-12.

TypingMind / TypingMind Teams

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

Headless model providers cohere-north:cohere-north:n-doc-177-20261026
Operators register Cohere, vLLM, Azure, Bedrock, SageMaker, OpenAI and Anthropic endpoints with customer secrets.
Provider types, endpoint and credentials; public representation of https://private.docs.cohere.com/north/docs/advanced/headless-configuration/model-providers.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 813d19abcb01a5b84e23e8615ef38b9e94cd57097f91ae7e44a139e6b62c4cbb on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
North Large 01-2026 cohere-north:cohere-north:n-doc-32-20261026
North partnership model accepts text/images with256K input/32K output and48 languages; citation gaps acknowledged.
Model card and limitations; public representation of https://private.docs.cohere.com/north/docs/north-large-01-2026.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 46ad467b680bd511cfc5f0d3168f40dd32b61be945b039d7cf029b3527b5ece7 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Models and providers cohere-north:cohere-north:n-doc-134-20261026
Custom endpoints/providers, group access and defaults; grants additive and alias may silently fall back to provider default.
Beta UI, alpha RBAC, aliases and fallback; public representation of https://private.docs.cohere.com/north/docs/admin/models.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 3ddb8818e63c7322d79680498f711ab0dd1a15dd87f1315c3065bed5171538dd on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Chat cohere-north:cohere-north:n-doc-1-20261026
Chat model choice, source-linked responses, eight UI languages and configurable voice/image input are documented.
Model picker, UI languages, image input and dictation; public representation of https://private.docs.cohere.com/north/docs/get-started/north-chat.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 2a609c8b8dc88bce89ad912f7d8c43ee63449c23a0bac0e5fcb5954bf55e0964 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
North multimodal features cohere-north:cohere-north:n-doc-14-20261026
Vision/OCR requires configured models/parser; third-party image input planned, document visual pages limited500.
Cohere-only image input and visual parser; public representation of https://private.docs.cohere.com/north/docs/get-started/north-automations/building-automations/north-multimodality.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 c4763a8ec53fc0d63b4393939e71c9df423160564cdbc748004dcd7af256faba on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Voice settings cohere-north:cohere-north:n-doc-97-20261026
Dictation and long-form mobile recording are separately off by default and require configured transcription service.
Alpha dictation and beta mobile recording; public representation of https://private.docs.cohere.com/north/docs/admin/configuring_voice_settings.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 26565385151f6fa21890665138a7d900c61ea1cbff3bb96f46e67955e5ac54a1 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Skills cohere-north:cohere-north:n-doc-12-20261026
Built-in/custom skills create/edit DOCX/PPTX/XLSX/CSV using code sandbox and supported models.
Beta skills and Office file packages; public representation of https://private.docs.cohere.com/north/docs/get-started/skills.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 9167ea7e86e91dabe44c8cbcc8e0f3b3baa5b44badaf1d393bb4ae67e41fdb0d on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
North release notes, public HTML cohere-north:cohere-north:north-release-html-20261026
North 2 documents model aliases, beta Library sharing/Skills and sandbox, alpha controls, version-scoped legacy removals and the October 20 storage patch. Release labels are feature-specific, not a guarantee of private-deployment parity.
October 16 North 2.0.0 and October 20 2.0.1; Models, Libraries, Google Drive, Skills, Sandbox and Admin; HTTP 200, body SHA256 be38218043c7eb99d836db5d02f86ce71b5af7c2c267327410f58f81936ed720 · documented · Source date 2026-10-20 · Retrieved 2026-10-26
Set up API Keys typingmind:typingmind:set-up-api-keys
Teams admins preset customer provider keys; end users cannot enter their own key in the chat interface.
Set up API Keys · documented · Source date not stated · Retrieved 2026-10-21
Manage AI Models typingmind:typingmind:manage-ai-models
The app has a per-chat model selector and configurable model endpoints; provider examples are not a complete current catalogue.
Manage AI Models · documented · Source date not stated · Retrieved 2026-10-21
TypingMind changelog typingmind:typingmind:release
Dated releases include Teams memory administration, new models, browser-local code and office outputs, and GPT Image editing.
2026-10-14 Memory for Teams and new models; 2026-10-13 Toolbox; 2026-10-02 image editing · documented · Source date 2026-10-14 · Retrieved 2026-10-21
Restrict Model access typingmind:typingmind:restrict-model-access
Teams admins restrict available models by user group.
Restrict Model access · documented · Source date not stated · Retrieved 2026-10-21
Chat with documents typingmind:typingmind:chat-with-documents
Uploads accept PDF, Markdown, CSV, XLSX, TXT, DOCX, JSON and HTML, with document text added as chat context.
Chat with documents · documented · Source date not stated · Retrieved 2026-10-21
Voice input typingmind:typingmind:voice
Browser speech recognition or customer OpenAI, Groq and Azure transcription keys enable dictation; uploaded Whisper recordings have a 25MB limit.
Transcription models and Teams configuration · documented · Source date not stated · Retrieved 2026-10-21
North release notes cohere-north:cohere-north:n-north-changelog
Dated releases document new models, beta/alpha capabilities and removal/deprecation of legacy connectors and APIs.
October 20 v2.0.1 andOctober 16 v2.0.0; migrations · documented · Source date 2026-10-20 · Retrieved 2026-10-21
Deploy models chart cohere-north:cohere-north:n-doc-168
Customer GPU model chart supports local chat/embed/rerank; serving containers version independently.
In-cluster generative/Compass components and pinned artifacts · documented · Source date not stated · Retrieved 2026-10-21
Azure OpenAI typingmind:typingmind:azure-openai
A customer Azure OpenAI endpoint and deployment can be configured.
Azure OpenAI · documented · Source date not stated · Retrieved 2026-10-21
Bedrock Anthropic setup cohere-north:cohere-north:n-doc-135-20261026
Own AWS account/region and authorized Claude models support chat, agents and automations.
Customer AWS prerequisites and roles; public representation of https://private.docs.cohere.com/north/docs/admin/bedrock-anthropic.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 185176cbe038586b463babfc0584a55cd212cf96f554cf6eadaf1238e4105617 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Microsoft Foundry with North cohere-north:cohere-north:n-doc-218-20261026
Customer Azure billing supports chat/embed/rerank/Parse5; sparse and North Large unavailable there, mixed hosting required.
Customer Azure inference and feature gaps; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 e717dddf6149bafdb68a613b1268d366565e212be0e292d989d1c2a8d960f35e on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
TypingMind Teams pricing typingmind:typingmind:pricing
Annual selected prices display USD83/166/249 per month for Starter/Growth/Professional, five users, USD8 extra seats; Business starts USD18,700/year.
Annual selector, plan cards, Add-ons and Business card · documented · Source date not stated · Retrieved 2026-10-21
Self-host installation instructions typingmind:typingmind:get-started-with-self-host-installation-instruct
A NodeJS service needs MySQL 8, optional PostgreSQL 16 pgvector KB, OpenAI embeddings and S3-compatible blobs; private endpoints are blocked by default.
Self-host installation instructions · documented · Source date not stated · Retrieved 2026-10-21
Toolbox typingmind:typingmind: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.
Local execution, network control and file capabilities · documented · Source date not stated · Retrieved 2026-10-21
Teams API Keys Setup typingmind:typingmind:r2-teams-custom-models
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.
Use with other models; Add Custom Model in Admin Panel · documented · Source date not stated · Retrieved 2026-10-21
Compare Teams Plans typingmind:typingmind:r2-plan-matrix
All SaaS tiers list custom models and shared resources; Growth adds RAG/projects; Professional adds roles, restrictions, logs and external API integration.
Full Feature Comparison · documented · Source date not stated · Retrieved 2026-10-21
AWS Bedrock Anthropic typingmind:typingmind:r3-custom-admin-bedrock
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.
Custom Admin restriction and steps 2-4, including custom.typingmind.com/manage · documented · Source date not stated · Retrieved 2026-10-21
Headless model providers cohere-north:cohere-north:n-doc-177
Operators register Cohere, vLLM, Azure, Bedrock, SageMaker, OpenAI and Anthropic endpoints with customer secrets.
Provider types, endpoint and credentials · documented · Source date not stated · Retrieved 2026-10-21
North multimodal features cohere-north:cohere-north:n-doc-14
Vision/OCR requires configured models/parser; third-party image input planned, document visual pages limited500.
Cohere-only image input and visual parser · documented · Source date not stated · Retrieved 2026-10-21
Microsoft Foundry with North cohere-north:cohere-north:n-doc-218
Customer Azure billing supports chat/embed/rerank/Parse5; sparse and North Large unavailable there, mixed hosting required.
Customer Azure inference and feature gaps · documented · Source date not stated · Retrieved 2026-10-21
MCP server administration cohere-north:cohere-north:n-doc-126
Customer/remote MCP support scoped OAuth/tokens/static headers; remote registration needs internet and dynamic registration.
Registration, custom headers, permissions and remote limits · documented · Source date not stated · Retrieved 2026-10-21
Ollama typingmind:typingmind:ollama
A customer Ollama model endpoint can be added; network accessibility must be configured.
Ollama · documented · Source date not stated · Retrieved 2026-10-21
LM Studio typingmind:typingmind:lmstudio
Customer local LM Studio can supply an OpenAI-compatible model endpoint.
LM Studio · documented · Source date not stated · Retrieved 2026-10-21
Cloud host vs self host typingmind:typingmind: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.
Cloud host vs self host · documented · Source date not stated · Retrieved 2026-10-21
Creating custom agents cohere-north:cohere-north:n-doc-18-20261026
Agents combine instructions/models/tools/libraries; shared agents inherit owner model access.
Instructions, versioning, sharing and model permission model; public representation of https://private.docs.cohere.com/north/docs/get-started/agents/creating-custom-agents.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 6ae6b9abfe4e5de1679146a003d858f773f48d669e0c579e530654feba66aba9 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Flow control cohere-north:cohere-north:n-doc-137-20261026
User/group/model/source/provider rules enforce request/input/output token limits only after Helm services deployed; fail-open option and unlimited default.
Alpha model rate-limit proxy; public representation of https://private.docs.cohere.com/north/docs/admin/flow-control.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 b0aabd0e2334636f4ff1d4bea234db5f41b155a385923fbce27a1face1df2312 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Usage limits typingmind:typingmind:usage-limits
Reusable limit groups cover messages, characters and tokens by period, applicable globally or to users, groups, models, agents and plugins.
Usage limits · documented · Source date not stated · Retrieved 2026-10-21
Connect Knowledge Base to your AI Agents typingmind:typingmind:connect-knowledge-base-to-your-ai-agents
Tagged knowledge is assigned to agents through Knowledge Base Access.
Connect Knowledge Base to your AI Agents · documented · Source date not stated · Retrieved 2026-10-21
Roles and Permissions typingmind:typingmind:roles-and-permissions
Owners delegate granular Admin Panel permissions through custom roles; group-role assignment is described as coming soon.
Roles and Permissions · documented · Source date not stated · Retrieved 2026-10-21
Supported files cohere-north:cohere-north:n-doc-73-20261026
Documents text/Office/tabular/image/audio formats and configurable processing; My files limit differs from its dedicated guide.
Formats and100 MB/500 MB limit wording; public representation of https://private.docs.cohere.com/north/docs/get-started/supported-files.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 9bc5a3f6698e34d553cd9b9efd32964736dbe6989a31fc138e6eaec28fe9e680 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
My files cohere-north:cohere-north:n-doc-66-20261026
Guide states50 MB/file and configured totals; image-only PDFs require parser setup and images are not indexed for general Smart Search.
Upload limit, OCR and Smart Search; public representation of https://private.docs.cohere.com/north/docs/get-started/tools/my-files/home.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 d6f571cfecc507841ce963c91571a3822f44b24d28d0192f21498d4abdcc1c30 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Multimodality configuration cohere-north:cohere-north:n-doc-100-20261026
Image input currently limited to Cohere vision models; smart parser and infrastructure are separately required.
Alpha parser/model/feature prerequisites; public representation of https://private.docs.cohere.com/north/docs/admin/multimodality.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 2e036dc55b465b41bcff9b28bb0fc83bb5ff07d7750137f983ef0461fc1ef593 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
How Knowledge Base works in TypingMind Team typingmind:typingmind: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.
Early Access; indexing; limits and refresh · documented · Source date 2025-11-10 · Retrieved 2026-10-21
Training Files vs Knowledge Base typingmind:typingmind:training-files-vs-knowledge-base
Agent training-file text is injected into system context; the separate KB retrieves chunks and advertises multiple source integrations.
Training Files vs Knowledge Base · documented · Source date not stated · Retrieved 2026-10-21
Libraries cohere-north:cohere-north:n-doc-42-20261026
Libraries bind to agents/chats/nodes; source libraries and uploads have different sharing/access rules.
Beta persistence, source/sharing and binding; public representation of https://private.docs.cohere.com/north/docs/get-started/tools/libraries.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 dbe8dc45b308026365048a6e52ee685ac8fedfe257517c688f624e9e2ebf4374 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Projects cohere-north:cohere-north:n-doc-11-20261026
Private indexed project files are isolated to the project; default per-user aggregate storage2 GiB.
Alpha workspace and storage; public representation of https://private.docs.cohere.com/north/docs/get-started/projects.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 f7d3bab16beb3744f5def211a909d7acebcb6a00cd68b747a826b2d608fd0a0e on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Admin library directory cohere-north:cohere-north:n-doc-133-20261026
Admins manage library access without seeing contents; groups and company access supported, email libraries private.
Beta user/group access; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 f4248f5cd4bf98f610b6f39c57494e2834de07e117db292498eca4707a592b8f on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Get started with Knowledge Base typingmind:typingmind:get-started-with-knowledge-base
Admins add documents or connected sources, tag data, bind tags to agents and optionally show clickable references.
Get started with Knowledge Base · documented · Source date not stated · Retrieved 2026-10-21
Restrict AI Agents access typingmind:typingmind:restrict-ai-agents-access
Agent access and usage can be limited for groups.
Restrict AI Agents access · documented · Source date not stated · Retrieved 2026-10-21
Data syncing cohere-north:cohere-north:n-doc-151-20261026
Atlas periodic indexing differs from live APIs; generic freshness minutes to hours.
Atlas copies versus live Gmail/Google Drive Full Access; public representation of https://private.docs.cohere.com/north/docs/security/data-syncing.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 9098552e0be35967acf545ee4d3c6487281481833795c49d487dfe417382184e on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
MCP server administration cohere-north:cohere-north:n-doc-126-20261026
Customer/remote MCP support scoped OAuth/tokens/static headers; remote registration needs internet and dynamic registration.
Registration, custom headers, permissions and remote limits; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 8b401a0257b45f4b284dd89368b795118eb74b1a2b0d193d56a9b1687e804ea9 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
SharePoint Server connector setup cohere-north:cohere-north:n-doc-53-20261026
Documents customer-network SharePoint Server integration with deployment/auth prerequisites.
On-prem SharePoint Server prerequisites; public representation of https://private.docs.cohere.com/north/docs/get-started/tools/microsoft-connectors/sharepoint-server-connector-setup.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 10f8e3e90ba4fcf31095515a6fe687de0e080d90e1d72e9d0257a555486a2475 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Data sharing cohere-north:cohere-north:n-doc-152-20261026
Atlas/source permission checks fail closed for retrieval; old email storage descriptions conflict with live Gmail guide.
Agent/library scope, runtime checks and private email; public representation of https://private.docs.cohere.com/north/docs/security/data-sharing.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 b001f4de791c2eadc7d050e3863bbd26d4476540f6516d632b1b420bf025ccbd on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
North 2 product launch cohere-north:cohere-north:north2-launch-20261026
The first-party announcement names shared Libraries, Skills, applications, third-party models, user/group governance and built-in enterprise connector families; planned financial connectors are distinguished from current release-specific alpha documentation.
Core feature and connector lists; model and governance sections · vendor-claimed · Source date 2026-10-05 · Retrieved 2026-10-26
Connect with Notion pages typingmind:typingmind:connect-with-your-notion-pages
Admins select Notion pages/databases for an instance, with initial sync taking a few minutes.
Connect with Notion pages · documented · Source date not stated · Retrieved 2026-10-21
Self-host external knowledge connectors typingmind:typingmind:setup-external-connectors-for-knowledge-base
Optional self-host KB external connectors need separate OAuth configuration and Firecrawl for web scraping.
Self-host external knowledge connectors · documented · Source date not stated · Retrieved 2026-10-21
LLM Automated Workflows overview typingmind:typingmind:overview
JavaScript, HTTP and MCP plugins can perform multi-step business actions; example flows are not evidence of a scheduler.
LLM Automated Workflows overview · documented · Source date not stated · Retrieved 2026-10-21
MCP in TypingMind typingmind:typingmind:mcp
The client connects remote HTTP or local-command MCP servers, supports OAuth and individual tool controls, and separates Teams sessions per user/chat.
Remote and local connectors; Teams sessions; tool control · documented · Source date not stated · Retrieved 2026-10-21
SharePoint implementation cohere-north:cohere-north:n-doc-64
Selected content is indexed;10-minute sync detects updates/deletes, after source-side indexing permits discovery.
Compass indexing,10-minute sync and source search dependency · documented · Source date not stated · Retrieved 2026-10-21
Libraries cohere-north:cohere-north:n-doc-42
Libraries bind to agents/chats/nodes; source libraries and uploads have different sharing/access rules.
Beta persistence, source/sharing and binding · documented · Source date not stated · Retrieved 2026-10-21
Data syncing cohere-north:cohere-north:n-doc-151
Atlas periodic indexing differs from live APIs; generic freshness minutes to hours.
Atlas copies versus live Gmail/Google Drive Full Access · documented · Source date not stated · Retrieved 2026-10-21
Data sharing cohere-north:cohere-north:n-doc-152
Atlas/source permission checks fail closed for retrieval; old email storage descriptions conflict with live Gmail guide.
Agent/library scope, runtime checks and private email · documented · Source date not stated · Retrieved 2026-10-21
Sharing and collaborating with chat cohere-north:cohere-north:n-doc-4
Shared snapshots expose full messages, citations, thinking trace and sandbox files to signed-in recipients.
Snapshot contents and debug visibility · documented · Source date not stated · Retrieved 2026-10-21
Tool authorization cohere-north:cohere-north:n-doc-149
Per-user access and runtime source checks documented; revocation immediacy not independently measured.
OAuth/source permission checks · documented · Source date not stated · Retrieved 2026-10-21
JIT provisioning cohere-north:cohere-north:n-doc-111
First successful login creates users; groups refresh at authentication/session renewal; admin deprovisioning APIs documented.
First login and refreshed groups · documented · Source date not stated · Retrieved 2026-10-21
North tools overview cohere-north:cohere-north:n-doc-33
Names first-party sources and states, including Jira/Slack MCP beta, Atlas SharePointGA and Gmail alpha.
Per-tool state and categories · documented · Source date not stated · Retrieved 2026-10-21
Deployment model cohere-north:cohere-north:n-doc-165-20261026
North application Helm chart deployed on customer Kubernetes; GitOps/ArgoCD recommended for production.
Helm and production GitOps; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 39b2586fa7cca8f9c540e2c02dc9471ed0b3c89484c9f776421e78e477711721 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
EU data center typingmind:typingmind:eu-data-center
EU instances use Vercel and AWS EU storage but model API calls may leave the EU.
EU data center · documented · Source date not stated · Retrieved 2026-10-21
North Large 01-2026 cohere-north:cohere-north:n-doc-32
North partnership model accepts text/images with256K input/32K output and48 languages; citation gaps acknowledged.
Model card and limitations · documented · Source date not stated · Retrieved 2026-10-21
Chat cohere-north:cohere-north:n-doc-1
Chat model choice, source-linked responses, eight UI languages and configurable voice/image input are documented.
Model picker, UI languages, image input and dictation · documented · Source date not stated · Retrieved 2026-10-21
Projects cohere-north:cohere-north:n-doc-11
Private indexed project files are isolated to the project; default per-user aggregate storage2 GiB.
Alpha workspace and storage · documented · Source date not stated · Retrieved 2026-10-21
System Prompts on Admin Panel typingmind:typingmind:system-prompts-on-admin-panel
Global system instructions, few-shot examples and post-message reminders apply across chats and agents.
System Prompts on Admin Panel · documented · Source date not stated · Retrieved 2026-10-21
Creating custom agents cohere-north:cohere-north:n-doc-18
Agents combine instructions/models/tools/libraries; shared agents inherit owner model access.
Instructions, versioning, sharing and model permission model · documented · Source date not stated · Retrieved 2026-10-21
Preamble and prompt settings cohere-north:cohere-north:n-doc-86
Optional organisation instructions apply across models alongside platform/agent preambles.
Company instructions · documented · Source date not stated · Retrieved 2026-10-21
Memory cohere-north:cohere-north:n-doc-8
Personal memories can be edited or deleted; agent archival memory cannot be viewed or edited.
Alpha personal/archival memory · documented · Source date not stated · Retrieved 2026-10-21
Memory settings cohere-north:cohere-north:n-doc-96
Instance toggles jointly control core/archival/conversation memory and extraction timing.
Alpha admin controls · documented · Source date not stated · Retrieved 2026-10-21
Memory typingmind:typingmind:memory
Users can enable memory globally or for an agent/project and inspect saved memories.
Memory · documented · Source date not stated · Retrieved 2026-10-21
Skills cohere-north:cohere-north:n-doc-12
Built-in/custom skills create/edit DOCX/PPTX/XLSX/CSV using code sandbox and supported models.
Beta skills and Office file packages · documented · Source date not stated · Retrieved 2026-10-21
Roles and permissions cohere-north:cohere-north:n-doc-114
Roles/groups delegate permissions; some direct grants cannot be packaged into roles; individual role assignment can expire.
System/custom roles and grants · documented · Source date not stated · Retrieved 2026-10-21
Browsing agents cohere-north:cohere-north:n-doc-21
Internal starred/personal/shared/company agent directory supports search and duplication.
Agent catalogue and duplication · documented · Source date not stated · Retrieved 2026-10-21
Build a Shared AI Agent collection typingmind:typingmind:build-a-shared-ai-agent-collection
Admins create an agent collection exposed in the team chat interface and control group access.
Build a Shared AI Agent collection · documented · Source date not stated · Retrieved 2026-10-21
Build a Shared Prompt Library typingmind:typingmind:build-a-shared-prompt-library
Admins can publish reusable prompts to the team interface.
Build a Shared Prompt Library · documented · Source date not stated · Retrieved 2026-10-21
Code sandbox cohere-north:cohere-north:n-doc-34
Persistent per-chat Python/bash runtime creates files/charts and shows executed code; admin deployment/access required.
Beta execution, files and activity visibility · documented · Source date not stated · Retrieved 2026-10-21
Tool action approvals cohere-north:cohere-north:n-doc-150
Approval modal can edit/deny action parameters, but tool hints and persistent global bypass limit per-action assurance.
Destructive actions and global Allow Always · documented · Source date not stated · Retrieved 2026-10-21
Consuming automations cohere-north:cohere-north:n-doc-30
Schedules support cron/natural language; run viewer shows inputs/outputs and cancellation; action permission accepted at launch.
Run, cron schedule, approval and cancel · documented · Source date not stated · Retrieved 2026-10-21
Restrict Plugin access typingmind:typingmind:restrict-plugin-access
Plugins can be made available or unavailable to specified user groups.
Restrict Plugin access · documented · Source date not stated · Retrieved 2026-10-21
Deep Research plugin typingmind:typingmind:deep-research
A multi-step search/read/report plugin requires customer SerpAPI and Firecrawl keys and has a two-minute execution limit.
Requirements and operation · documented · Source date not stated · Retrieved 2026-10-21
GPT Image 2.5 plugin typingmind:typingmind:image
The plugin generates and edits images using the customer OpenAI API route.
Image generation, editing and API key · documented · Source date not stated · Retrieved 2026-10-21
Web search cohere-north:cohere-north:n-doc-74
Tavily defaultGA; Brave/LinkUp alpha; API keys needed; live web page content is not ingested.
GA provider choices and handling · documented · Source date not stated · Retrieved 2026-10-21
Deep research cohere-north:cohere-north:n-doc-15
Multi-step cited research requires enabled sources and user/group access, with downloadable reports.
Alpha feature and administrator grants · documented · Source date not stated · Retrieved 2026-10-21
Automations cohere-north:cohere-north:n-doc-16
Node-based workflows combine models, tools and reusable versioned definitions.
Visual builder, roles and workflow lifecycle · documented · Source date not stated · Retrieved 2026-10-21
Saving and publishing automations cohere-north:cohere-north:n-doc-29
Automation definitions export JSON with graph/dependencies; credentials and schedules excluded.
Versioning and JSON import/export · documented · Source date not stated · Retrieved 2026-10-21
North execute automation API cohere-north:cohere-north:n-api-run
External authenticated clients can start workflows with typed inputs; this is not a native source-event watcher.
POST /v1/automations/{id}/execute · documented · Source date not stated · Retrieved 2026-10-21
Human-in-the-loop automations cohere-north:cohere-north:n-doc-26
Workflows can pause for review and route by human decisions; review timeouts apply.
Human Review node · documented · Source date not stated · Retrieved 2026-10-21
API integration overview typingmind:typingmind:api-integration-overview
REST chat/agent API uses API-key-associated api-users subject to user restrictions and usage limits.
API integration overview · documented · Source date not stated · Retrieved 2026-10-21
About the North API cohere-north:cohere-north:n-north-api
Instance REST API covers chat, agents, automations and files with bearer/OAuth/workload identity.
Authentication and API scope · documented · Source date not stated · Retrieved 2026-10-21
North create response API cohere-north:cohere-north:n-api-response
North exposes model response API with tool and reasoning parameters and permission/rate-limit errors.
Request/response and authentication · documented · Source date not stated · Retrieved 2026-10-21
North file upload API cohere-north:cohere-north:n-api-upload
Authenticated multipart upload stores a file with ID and downloadable content endpoints.
POST /v1/files · documented · Source date not stated · Retrieved 2026-10-21
North library API cohere-north:cohere-north:n-api-libraries
Authenticated library creation complements file APIs and library permissions.
Create library endpoint · documented · Source date not stated · Retrieved 2026-10-21
Data controls cohere-north:cohere-north:n-doc-89
Blocks new API/web share links; existing conversation links stop, existing automation/table links remain.
Alpha sharing restrictions · documented · Source date not stated · Retrieved 2026-10-21
Audits cohere-north:cohere-north:n-doc-140
Admin changes/compliance decisions have searchable event rows and programmatic audit endpoints.
Alpha admin events and GET API · documented · Source date not stated · Retrieved 2026-10-21
Voice settings cohere-north:cohere-north:n-doc-97
Dictation and long-form mobile recording are separately off by default and require configured transcription service.
Alpha dictation and beta mobile recording · documented · Source date not stated · Retrieved 2026-10-21
TypingMind vs TypingMind Team typingmind:typingmind:typingmind-vs-typingmind-team
The personal app and Teams with an Admin Panel, managed users and centrally preset keys are separate offerings.
TypingMind vs TypingMind Team · documented · Source date not stated · Retrieved 2026-10-21
Install TypingMind app typingmind:typingmind:install
Installation uses browser PWA technology; browser storage remains separate and this does not establish native app-store clients.
PWA installation on Windows, Mac, iOS and Android · documented · Source date not stated · Retrieved 2026-10-21
TypingMind personal licence checkout typingmind:typingmind:r2-personal-bulk-licence
Personal licences normally cover five devices for one user; a separate shareable Bulk License is offered, without establishing a Teams Admin Panel entitlement.
How many devices/users? and Team/Bulk License FAQ; self-host FAQ · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Document mode cohere-north:cohere-north:n-doc-9
Canvas supports manual/prompt edits, tone/translation actions, versions and DOCX/PDF/MD/HTML exports.
Editing, quick actions and exports · documented · Source date not stated · Retrieved 2026-10-21
Ad creative generator workflow typingmind:typingmind:ad-creative-generator
Public examples include marketing automation built with AI and plugins.
Ad creative generator workflow · documented · Source date not stated · Retrieved 2026-10-21
Terms of Service typingmind:typingmind: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.
Sections 1, 4-6, 13 and 16 · documented · Source date 2026-09-17 · Retrieved 2026-10-21
Text to speech typingmind:typingmind:tts
Answers can be read aloud using browser speech, ElevenLabs or OpenAI TTS.
Browser, ElevenLabs and OpenAI options · documented · Source date not stated · Retrieved 2026-10-21
Meeting summarizer workflow typingmind:typingmind:meeting-summarizer
The guide offers an audio-transcription and summarisation workflow, not a demonstrated meeting bot.
Meeting summarizer workflow · documented · Source date not stated · Retrieved 2026-10-21
North release notes cohere-north:cohere-north:n-north-changelog-20261026
Dated releases document new models, beta/alpha capabilities and removal/deprecation of legacy connectors and APIs.
October 20 v2.0.1 andOctober 16 v2.0.0; migrations; public representation of https://private.docs.cohere.com/north/changelog.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 be38218043c7eb99d836db5d02f86ce71b5af7c2c267327410f58f81936ed720 on 2026-10-26 · documented · Source date 2026-10-20 · Retrieved 2026-10-26
Document mode cohere-north:cohere-north:n-doc-9-20261026
Canvas supports manual/prompt edits, tone/translation actions, versions and DOCX/PDF/MD/HTML exports.
Editing, quick actions and exports; public representation of https://private.docs.cohere.com/north/docs/get-started/north-document-mode.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 19535713d7c2ccff7e98fa4e94dde5dcdb6aae67809de5a1e27cb22d286812a1 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Compare TypingMind Team plans typingmind:typingmind:compare-typingmind-team-plans
The comparison lists monthly USD99/199/299, five users plus USD8 additional users, Growth knowledge and Professional identity/governance.
Compare TypingMind Team plans · documented · Source date not stated · Retrieved 2026-10-21
Translation collaboration typingmind:typingmind:translations
A translation project exists, but the retrieved page does not establish completeness of German, French, Italian or Admin Panel translations.
Multilingual app translation project · documented · Source date not stated · Retrieved 2026-10-21
About SSO cohere-north:cohere-north:n-doc-105
OIDC preferred; SAML, LDAP shim/hybrid and authentication proxy documented; group claims required for group access.
Protocols and Dex identity broker · documented · Source date not stated · Retrieved 2026-10-21
Single Sign-On (SSO) typingmind:typingmind:sso
SAML identity-provider metadata, entity ID and reply URL are configured in Teams.
SAML configuration and multiple connections · documented · Source date not stated · Retrieved 2026-10-21
OAuth 2.0 typingmind:typingmind:o-auth-2-0
OAuth/OIDC supports built-in Microsoft and Google logins and JIT seats; revoking IdP authorization alone does not remove the user.
OAuth 2.0 · documented · Source date not stated · Retrieved 2026-10-21
Data Processing Agreement typingmind:typingmind:data-processing-agreement
The public GDPR processor form includes confidentiality, subprocessor flow-down, SCC transfers and customer-choice deletion or return.
Clauses 7.4, 7.8-7.10 and Appendices I-IV · documented · Source date not stated · Retrieved 2026-10-21
Data deletion cohere-north:cohere-north:n-doc-153
Deletion has asynchronous external cleanup and explicit preserved shared-resource exceptions.
Conversation, user and connector cleanup · documented · Source date not stated · Retrieved 2026-10-21
SCIM provisioning cohere-north:cohere-north:n-doc-112
Bidirectional user/group sync; disable is reversible, delete re-creates a new identity if later added.
Alpha SCIM2 and deactivation/deletion · documented · Source date not stated · Retrieved 2026-10-21
Graceful delete settings cohere-north:cohere-north:n-doc-90
Access ends immediately; configurable private cleanup grace period, shared resources preserved except nontransferable Microsoft libraries.
Beta account removal and shared-resource exceptions · documented · Source date not stated · Retrieved 2026-10-21
Directory Sync (SCIM v2) typingmind:typingmind:scim
SCIM sync creates and suspends users, updates profiles and assigns corresponding groups from the IdP.
Create, update, suspend users and groups · documented · Source date not stated · Retrieved 2026-10-21
Invite team members typingmind:typingmind:invite-team-members
Teams admins invite members to the instance and manage seats.
Invite team members · documented · Source date not stated · Retrieved 2026-10-21
Models and providers cohere-north:cohere-north:n-doc-134
Custom endpoints/providers, group access and defaults; grants additive and alias may silently fall back to provider default.
Beta UI, alpha RBAC, aliases and fallback · documented · Source date not stated · Retrieved 2026-10-21
Compute requirements cohere-north:cohere-north:n-doc-158
North licensed by compute units and separately administered application instances; licence rates absent.
Sizing and licensing metrics · documented · Source date not stated · Retrieved 2026-10-21
Create and manage user groups typingmind:typingmind:create-and-manage-user-groups
Groups control access and are usable for limits and analytics.
Create and manage user groups · documented · Source date not stated · Retrieved 2026-10-21
Analytics v2 cohere-north:cohere-north:n-doc-78
Self-hosted analytics reports users/groups/models/agents/tools; named-user CSV and sampled metrics have limits.
Alpha metrics and CSV/PNG exports · documented · Source date not stated · Retrieved 2026-10-21
Analytics settings cohere-north:cohere-north:n-doc-95
Operators can turn event collection off and configure retention for database analytics events.
Alpha event collection and retention · documented · Source date not stated · Retrieved 2026-10-21
Chatbot analytics typingmind:typingmind:chatbot-analytics
Reporting covers active users, messages, conversations, estimated tokens and characters, with model/agent/group/user breakdowns and chart downloads.
Chatbot analytics · documented · Source date not stated · Retrieved 2026-10-21
Flow control cohere-north:cohere-north:n-doc-137
User/group/model/source/provider rules enforce request/input/output token limits only after Helm services deployed; fail-open option and unlimited default.
Alpha model rate-limit proxy · documented · Source date not stated · Retrieved 2026-10-21
Token usage monitoring cohere-north:cohere-north:n-doc-207
Operators collect billed/raw tokens by model/provider/operation; no per-user labels, scrape gaps and incomplete paths prevent billing-ledger equivalence.
Prometheus/Grafana collection and limits · documented · Source date not stated · Retrieved 2026-10-21
Audits cohere-north:cohere-north:n-doc-140-20261026
Admin changes/compliance decisions have searchable event rows and programmatic audit endpoints.
Alpha admin events and GET API; public representation of https://private.docs.cohere.com/north/docs/admin/audits.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 4694734d3c4deaa7540b7df9604377266d387b5b92dea6b958aebbfdd74d20fc on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
Compliance cohere-north:cohere-north:n-doc-139-20261026
Approved investigators get24-hour conversation access/CSV including blocked/redacted content; self-approval forbidden.
Alpha dual-control investigation and CSV; public representation of https://private.docs.cohere.com/north/docs/admin/compliance.md; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 8d8d2439993a46e02f92eaf3dc040bacc2a9b59f3ad61352c04278648157c37c on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26
View and export user chat logs typingmind:typingmind: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.
View and export user chat logs · documented · Source date not stated · Retrieved 2026-10-21
Export chat logs typingmind:typingmind: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.
Export chat logs · documented · Source date not stated · Retrieved 2026-10-21
Guardrails admin cohere-north:cohere-north:n-doc-138
HiddenLayer supports allow/block/redact with monitor-only default; timeouts/unsupported entities and advisory content safety can fail open.
Selected-customer beta PII and alpha content safety · documented · Source date not stated · Retrieved 2026-10-21
Guardrails deployment cohere-north:cohere-north:n-doc-193
GPU scanning engine runs inside customer cluster without external HiddenLayer cloud traffic in documented configuration.
Selected-customer beta in-cluster HiddenLayer · documented · Source date not stated · Retrieved 2026-10-21
Terms and conditions cohere-north:cohere-north:n-doc-145
Sign-up/tool-specific multilingual terms require acceptance again after new versions; external URL overrides hosted terms.
Alpha required policy acceptance · documented · Source date not stated · Retrieved 2026-10-21
North security cohere-north:cohere-north:n-doc-146
Recommends operator encryption/network/SSO controls and stdout-to-SIEM forwarding; no observed hardened configuration implied.
Customer deployment hardening and log forwarding · documented · Source date not stated · Retrieved 2026-10-21
Cohere private deployments cohere-north:cohere-north:n-private
Vendor offers customer-managed VPC and air-gapped on-prem delivery with deployment assistance.
VPC/on-prem/air-gap and rollout support · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Model Vault with North cohere-north:cohere-north:n-doc-217
North stays customer-hosted; Cohere processes model inputs in dedicated Vault; ZDR option removes prompt retention.
Customer app plus Cohere inference · documented · Source date not stated · Retrieved 2026-10-21
Backup and restore cohere-north:cohere-north:n-doc-214
Operator controls backup placement and retention; encryption master key needed for restore.
Database, secrets and object storage · documented · Source date not stated · Retrieved 2026-10-21
Distributed tracing cohere-north:cohere-north:n-doc-208
Optional tracing sends deployment telemetry to operator-selected collectors; geographic placement is not fixed.
Operator OpenTelemetry export · documented · Source date not stated · Retrieved 2026-10-21
Enterprise data commitments cohere-north:cohere-north:n-commitments
Private deployments do not send prompts to Cohere; SaaS Platform has opt-out training and30-day logs with exceptions; Model Vault integration has its own inference scope.
Private/third-party versus SaaS Platform; retention and ZDR FAQ · documented · Source date 2025-12-05 · Retrieved 2026-10-21
TypingMind Teams Self Host typingmind:typingmind:selfhost
Commercial self-host requires an annual quote, includes five users, uses compiled/minified code, checks licence/updates externally and can use customer model endpoints.
Technical requirements, licensing, network, updates and pricing FAQ · documented · Source date not stated · Retrieved 2026-10-21
Privacy policy typingmind:typingmind:privacy-policy
The policy distinguishes personal local storage from Teams multitenant server storage, and lists inactive unpaid account deletion.
Storage scope, API keys and section on account deletion · documented · Source date 2026-09-19 · Retrieved 2026-10-21
Model Vault overview cohere-north:cohere-north:n-vault
Cohere-managed dedicated inference is separate from the North control plane.
Dedicated inference deployment and choices · documented · Source date not stated · Retrieved 2026-10-21
Deployment model cohere-north:cohere-north:n-doc-165
North application Helm chart deployed on customer Kubernetes; GitOps/ArgoCD recommended for production.
Helm and production GitOps · documented · Source date not stated · Retrieved 2026-10-21
Networking requirements cohere-north:cohere-north:n-doc-159
Operator network/DNS/TLS controls; hosted model API optional, image supply needs mirroring for disconnected installations.
Optional external model API and registry access · documented · Source date not stated · Retrieved 2026-10-21
Compliance cohere-north:cohere-north:n-doc-139
Approved investigators get24-hour conversation access/CSV including blocked/redacted content; self-approval forbidden.
Alpha dual-control investigation and CSV · documented · Source date not stated · Retrieved 2026-10-21
Data Usage and Model Training Policy typingmind:typingmind: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.
TypingMind role and provider API comparison · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Data retention settings cohere-north:cohere-north:n-doc-88
Age-based retention off by default; enabled defaults90day soft-delete plus30-day timeout; hourly hard-delete still runs for manually deleted conversations.
Alpha conversation retention and jobs · documented · Source date not stated · Retrieved 2026-10-21
Cohere and Aleph Alpha combination agreement cohere-north:cohere-north:n-combination-20261026
Combination remains subject to regulatory approvals; future dual headquarters and leadership depend on closing.
September 16 definitive agreement and closing conditions; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 972ee8d4e3dd868bf9d5986f00e66c0543ffd55cf519b78909aa7ec0cad9c399 on 2026-10-26 · documented · Source date 2026-09-16 · Retrieved 2026-10-26
Cohere AISLE proposed acquisition announcement cohere-north:cohere-north:corporate-aisle-20261026
The current text calls AISLE a proposed acquisition and calls Aleph Alpha a partnership. It does not provide closing/approval evidence for the September business-combination agreement.
October 15 announcement, opening paragraphs and closing transaction conditions; HTTP 200, body SHA256 e17b07229ecb36abb9f98b4d36e6541d3c74db64f0758fa93b8b48df3c7ccf58 · vendor-claimed · Source date 2026-10-15 · Retrieved 2026-10-26
Cohere public terms of use cohere-north:cohere-north:n-terms-20261026
Public general terms identify Cohere Inc and Ontario/Toronto law; North commercial subscription terms were not retrieved.
2022 terms; scope and choice of law; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 09c6e9b556c82d0e47438f044477298abb536b98fb30622371806a82ea1f3cbd on 2026-10-26 · documented · Source date 2022-09-07 · Retrieved 2026-10-26
Cohere Trust Center cohere-north:cohere-north:n-trust-20261026
Lists request-gated SOC 2/ISO 27001/42001 reports, USA subprocessors, NDA-gated DPA and SaaS US-Central hosting; not a whole-North private deployment policy.
Reports, subprocessors and regulatory FAQs; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 be106d8cf80369b1d1adf72c7912bf7c8af1221b76a8a381c6a95455d2666401 on 2026-10-26 · vendor-claimed · Source date not stated · Retrieved 2026-10-26
Cohere Trust Center cohere-north:cohere-north:n-trust
Lists request-gated SOC 2/ISO 27001/42001 reports, USA subprocessors, NDA-gated DPA and SaaS US-Central hosting; not a whole-North private deployment policy.
Reports, subprocessors and regulatory FAQs · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Cohere public terms of use cohere-north:cohere-north:n-terms
Public general terms identify Cohere Inc and Ontario/Toronto law; North commercial subscription terms were not retrieved.
2022 terms; scope and choice of law · documented · Source date 2022-09-07 · Retrieved 2026-10-21
TypingMind Teams self-host typingmind:typingmind:r4-soc2-selfhost-claim
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.
Maximum security, SOC 2 Type II badge; updates and licence checks · vendor-claimed · Source date not stated · Retrieved 2026-10-26
Data encryption at rest cohere-north:cohere-north:n-doc-154
Customer-held Kubernetes master key encrypts chat columns; automation/workflow data excluded.
Optional AES256GCM chat-column envelope encryption · documented · Source date not stated · Retrieved 2026-10-21
TypingMind Teams pricing FAQ typingmind:typingmind:r2-teams-server-route
The Teams-specific FAQ says users do not see the key and OpenAI requests are sent from the Teams server.
Do my users see my OpenAI API key? · vendor-claimed · Source date not stated · Retrieved 2026-10-21
TypingMind DPA confidentiality typingmind: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.
7.4(c),7.8(d)-(e); AppendixII andIII · documented · Source date not stated · Retrieved 2026-10-21
Cohere pricing cohere-north:cohere-north:n-pricing
North pricing is custom; model API trials and Model Vault instance rates are separate products.
North custom pricing; separate Model Vault/API tables · documented · Source date not stated · Retrieved 2026-10-21
ECB historical FX cohere-north:cohere-north:fx-ecb
EUR1=USD1.1215=CHF0.9237; rates recorded without inventing an unpriced North total.
2026-10-20 USD/CHF rates · documented · Source date 2026-10-20 · Retrieved 2026-10-21
OpenAI API pricing typingmind:typingmind:openai-price
gpt-6-luna Standard input is USD0.10 and output USD0.50 per million tokens, excluding cache and optional regional uplifts.
Standard short-context gpt-6-luna row · documented · Source date not stated · Retrieved 2026-10-21
GPT-6 Luna model documentation typingmind:typingmind:openai-model
Reasoning effort none is the lowest option; the shared cost proxy does not use reasoning tokens.
Reasoning effort and API support · documented · Source date not stated · Retrieved 2026-10-21
ECB reference exchange rates typingmind:typingmind:fx
EUR1 equals USD1.1215 and CHF0.9237.
Cube time=2026-10-20 · documented · Source date 2026-10-20 · Retrieved 2026-10-21
North 2 product page cohere-north:cohere-north:n-home
North offers agents, automations, libraries, applications and private deployment.
Platform and private deployment overview · vendor-claimed · Source date not stated · Retrieved 2026-10-21
Manage your subscription typingmind:typingmind:manage-your-subscription
Cloud customers manage the recurring subscription through billing settings.
Manage your subscription · documented · Source date not stated · Retrieved 2026-10-21
White labeling cohere-north:cohere-north:n-doc-142
Operators configure branding; commercial branding licence terms not established.
Branding configuration · documented · Source date not stated · Retrieved 2026-10-21
End User License Agreement typingmind:typingmind:end-user-license-agreement
The software is commercially licensed with restrictions on redistribution and modification.
End User License Agreement · documented · Source date not stated · Retrieved 2026-10-21
Custom branding typingmind:typingmind:custom-branding
Teams supports instance logo, theme and branded presentation within its commercial licence.
Custom branding · documented · Source date not stated · Retrieved 2026-10-21
Export and import data typingmind:typingmind:export-import-data
User app settings export/import chats, prompts, plugins, folders, agents and model settings as JSON.
Export and import data · documented · Source date not stated · Retrieved 2026-10-21
Cohere and Aleph Alpha combination agreement cohere-north:cohere-north:n-combination
Combination remains subject to regulatory approvals; future dual headquarters and leadership depend on closing.
September 16 definitive agreement and closing conditions · documented · Source date 2026-09-16 · Retrieved 2026-10-21
Cohere status cohere-north:cohere-north:n-status
Public hosted service status is available; it does not establish customer-hosted North SLA.
Hosted API service status · documented · Source date not stated · Retrieved 2026-10-21
TypingMind status typingmind:typingmind:status
The status site loaded a status shell but reported an error fetching data; incident history and measured uptime were not retrieved.
Public status shell · documented · Source date not stated · Retrieved 2026-10-21
North user guide cohere-north:cohere-north:n-guide
Lists planned November 13 v2.1 andDecember 11 v2.2 releases, subject to change; not individual feature delivery promises.
Release calendar and feature-state definitions · documented · Source date not stated · Retrieved 2026-10-21
Data Interpreter cohere-north:cohere-north:n-doc-36
Legacy spreadsheet Python tool is deprecated in favor of code sandbox; whole-sheet analysis differs from indexed metadata search.
Deprecated tool and successor · documented · Source date not stated · Retrieved 2026-10-21