Skip to content

Agent-readable comparison

Claude Team / Enterprise vs Cohere North

Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI.

This comparison has 48 criteria with sourced findings for both products, including 48 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. No winner is declared. A missing sourced finding is not evidence that a capability is absent.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Team and Enterprise offer Anthropic model families with seat-specific Fable billing and visible safety fallback; organization controls can restrict the picker.

Availability: unknown · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients; version=Hosted commercial Chat documentation checked 2026-10-26; plan=Team Standard/Premium; current usage-based Enterprise; legacy seat-based Enterprise only where explicitly identified; add_ons=Usage credits for Fable on Team Standard and legacy Enterprise Standard; consumption billed separately on current Enterprise; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • current_models: The current selector/context guides list Haiku 5.5, Sonnet 5.5, Opus 5.5 and Fable 5.1, plus older choices. Pricing includes the Opus/Sonnet/Haiku families on Team and Enterprise. Fable 5/5.1 use paid credits on Team Standard and legacy Enterprise Standard, a capped included share on Premium, and API-rate consumption on current Enterprise. Admin restrictions can remove access; no authenticated tenant picker was observed.
  • user_choice: Users select a chat model and effort from the menu; changes apply to the next response. Enterprise model controls may restrict choices. Office and Cowork defaults are scoped separately.
  • auto_routing: Fable 5/5.1 safety fallback is enabled by default and may rerun a flagged request on an Opus model in the same chat. A visible notice and responding-model label disclose the switch, and users can disable it. General task-complexity routing is not established.
  • multimodal_input: The chat attachment guide documents images/PDF/documents; exact per-model modality and paid-seat compatibility remains unverified.
  • providers Which model providers are available? [supported]: The commercial plan table includes Anthropic Fable, Opus, Sonnet and Haiku families; this is a single-provider hosted chat catalogue. Sources: claude:cl-pricing-20261026.
  • current_models Which current models are selectable on this plan? [partial]: The current selector/context guides list Haiku 5.5, Sonnet 5.5, Opus 5.5 and Fable 5.1, plus older choices. Pricing includes the Opus/Sonnet/Haiku families on Team and Enterprise. Fable 5/5.1 use paid credits on Team Standard and legacy Enterprise Standard, a capped included share on Premium, and API-rate consumption on current Enterprise. Admin restrictions can remove access; no authenticated tenant picker was observed. Sources: claude:cl-model-menu-r2-20261026, claude:cl-context-plans-r2-20261026, claude:cl-pricing-20261026, claude:claude:fable-plan-20261026.
  • user_choice Can users pick the model per chat? [partial]: Users select a chat model and effort from the menu; changes apply to the next response. Enterprise model controls may restrict choices. Office and Cowork defaults are scoped separately. Sources: claude:cl-model-menu-r2-20261026, claude:cl-model-control-20261026.
  • auto_routing Does the product route between models automatically, and is the chosen model shown? [partial]: Fable 5/5.1 safety fallback is enabled by default and may rerun a flagged request on an Opus model in the same chat. A visible notice and responding-model label disclose the switch, and users can disable it. General task-complexity routing is not established. Sources: claude:claude:transparent-fallback-20261026, claude:claude:fable-plan-20261026.
  • multimodal_input Which models accept images, audio or files? [partial]: The chat attachment guide documents images/PDF/documents; exact per-model modality and paid-seat compatibility remains unverified. Sources: claude:cl-upload-r2-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: claude:cl-model-menu-r2-20261026, claude:cl-context-plans-r2-20261026, claude:cl-upload-r2-20261026, claude:cl-pricing-20261026, claude:claude:fable-plan-20261026, claude:cl-model-control-20261026, claude:claude:transparent-fallback-20261026.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Release notes and scoped retirement notices exist; comparative lag and pinning remain open.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: release_lag_days, version_pinning.
  • Read each atomic answer for its plan, access and feature limits.
  • 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? Unverified after checking release notes and Haiku notice; three provider/product release-date pairs and persistent enterprise model pinning not verified.
  • changelog Is there a dated public model changelog? [supported]: Claude publishes dated model and product release notes. Sources: claude:cl-release.
  • deprecation_notice How much notice is given before a model is removed? [partial]: Haiku 4.5 consumer removal has October 15-to-29 notice, explicitly excluding Team/Enterprise. A general commercial-model notice period was not established. Sources: claude:cl-haiku-notice.
  • version_pinning Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unverified after checking release notes and Haiku notice; three provider/product release-date pairs and persistent enterprise model pinning not verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-release, claude:cl-haiku-notice.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Office add-ins advertise customer cloud credentials; that does not establish BYO inference in regular Claude chat.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude for Microsoft 365 official add-ins, Claude Team and Enterprise web workspaces; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Paid Office add-ins; regular Team/Enterprise chat only as an explicit gap; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: own_api_keys, custom_endpoint, byo_pricing, byo_restrictions.
  • Read each atomic answer for its plan, access and feature limits.
  • own_api_keys Can the customer use its own provider API keys? [unknown]: Can the customer use its own provider API keys? Unverified after checking Office cloud-credential FAQ, regular chat model settings and commercial pricing; arbitrary API keys/endpoints, BYO price changes and feature parity not verified.
  • own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Claude for Microsoft 365 advertises Foundry, Bedrock and Gemini Enterprise Agent Platform credentials. Regular Claude chat BYO cloud-account support remains unverified. Sources: claude:cl-office.
  • custom_endpoint Can an admin add any OpenAI-compatible endpoint? [unknown]: Can an admin add any OpenAI-compatible endpoint? Unverified after checking Office cloud-credential FAQ, regular chat model settings and commercial pricing; arbitrary API keys/endpoints, BYO price changes and feature parity not verified.
  • byo_pricing Does BYO change the licence price? [unknown]: Does BYO change the licence price? Unverified after checking Office cloud-credential FAQ, regular chat model settings and commercial pricing; arbitrary API keys/endpoints, BYO price changes and feature parity not verified.
  • byo_restrictions Which features stop working with BYO? [unknown]: Which features stop working with BYO? Unverified after checking Office cloud-credential FAQ, regular chat model settings and commercial pricing; arbitrary API keys/endpoints, BYO price changes and feature parity not verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-office.

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

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.

Claude Team / Enterprise

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.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Enterprise has model/effort ceilings and ordinary defaults; always-start enforcement is a separate beta with project exceptions.

Availability: beta · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Enterprise organization/custom-role model access and defaults; Always start with the default model and effort level is beta; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Beta applies specifically to forced starting model/effort; ordinary model ceilings and defaults are documented separately. Team entitlement is not inferred.
  • Existing chat-project selection is an explicit exception. No two-group/model restriction fixture; Chrome/Security and client-version coverage limits still apply.
  • model_allowlist_by_group Can admins limit models per group? [partial]: Enterprise organization model/effort ceilings constrain custom roles; Haiku cannot be disabled. Per-source data-binding rules remain unverified. Sources: claude:cl-model-control-r2.
  • data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? Unverified after checking Claude Team/Enterprise pricing, identity, connector, privacy and release documentation retrieved 2026-10-21; no paid organization or shared fixture.
  • default_model Can admins set the default model? [partial]: Enterprise can choose an ordinary organization/role default. The Always start switch is beta, still permits in-chat switching, and does not override remembered choices in existing chat projects. New projects and new project Cowork tasks use the default; unavailable product models fall back to Anthropic's recommendation. Sources: claude:cl-default-r2.
  • user_limits What per-user message or token limits apply, and are they published? [supported]: Current usage-based Enterprise has no included token allowance or seat usage cap; Team/legacy plans differ. Sources: claude:cl-enterprise.
  • limit_behaviour What happens when a limit is reached? [partial]: Disabling an enabled Enterprise model can require fallback or explicit switching; default selection is not permission to access a disabled model. Spend-limit enforcement remains separate. Sources: claude:cl-model-control-r2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-model-control-r2, claude:cl-default-r2, claude:cl-enterprise.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Chat attachments, project knowledge files and code/file tools have separate published limits.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team/Enterprise Chat attachments and project Files; enabled Chat code/file path only where explicitly named; add_ons=Code execution/file creation must be enabled for XLSX and the computing/file-tool route; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Limits are assigned to the named UI/repository/tool path rather than treated as conflicting universal maxima. Exact large-attachment transfer into the computing environment remains untested.
  • Office/Cowork paths are excluded. No long PDF, scan, formula workbook or PowerPoint fixture.
  • formats Which formats are accepted? [supported]: Chat attachments support PDF/DOCX/CSV/TXT/HTML/ODT/RTF/EPUB/JSON and XLSX with code execution; JPEG/PNG/GIF/WebP images. This is not an Office/Cowork format matrix. Sources: claude:cl-upload-r2.
  • limits What size and count limits apply per file and chat? [partial]: Chat Add files/photo attachments:500 MB/file,20/chat, PDF 1000-page maximum. Project Files:30 MB/file. The separate code/file-creation guide specifies30 MB per upload/download in its computing/file-tool path, with a separate larger-PDF processing caveat. A500 MB attachment is not promised to work in that30 MB tool path. Sources: claude:cl-upload-r2, claude:cl-code-files-r2.
  • ocr Are scanned PDFs read? [partial]: For Chat PDF processing, up to 100 pages receive visual/text analysis;101–1000 pages text only. Scanned-contract OCR accuracy was not tested. Sources: claude:cl-upload-r2.
  • spreadsheets Are Excel tables read with structure intact? [partial]: Chat XLSX uploads require code/file creation; its file-tool guide has a30 MB upload/download limit. Formula/table preservation was not fixture-tested. Sources: claude:cl-upload-r2, claude:cl-code-files-r2.
  • full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [partial]: Paid projects switch to search-based RAG near context limits and show an indicator; this does not establish every chat-file reading path. Sources: claude:cl-rag.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-upload-r2, claude:cl-code-files-r2, claude:cl-rag.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Projects persist curated knowledge and instructions and support organizational sharing.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Read each atomic answer for its plan, access and feature limits.
  • persistent_collections Can users keep document collections across chats? [supported]: Projects retain a knowledge base and instructions for related chats. Sources: claude:cl-projects.
  • sharing_scope Can collections be shared with users, groups or the whole organisation? [supported]: Team/Enterprise share projects with organization members; Enterprise groups can receive shared resources. Sources: claude:cl-projects, claude:cl-groups.
  • size_limits What are the collection limits? [partial]: Project files have a 30 MB limit; paid RAG expands effective knowledge capacity, with no fixed total capacity verified. Sources: claude:cl-upload, claude:cl-rag.
  • assistant_binding Can collections be bound to an assistant? [partial]: Project instructions and knowledge provide persistent task context; binding tools/model into a separately versioned assistant was not fully verified. Sources: claude:cl-projects.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-projects, claude:cl-groups, claude:cl-upload, claude:cl-rag.

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.

Checked ; 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.

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

Claude Team / Enterprise

Agent cross-checked Support: partial

First-party Microsoft/Google connectors and custom MCP provide distinct enterprise-data routes.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • atlassian: Claude Enterprise documents Atlassian Rovo MCP for Jira, Confluence and Teamwork Graph, including organization-managed authorization through Okta. This does not establish a native indexed Confluence connector, universal Team entitlement or observed ACL fidelity.
  • other_systems: Enterprise docs list GitHub and Slack; Salesforce is a separately approved paid-plan beta in release notes. Box/ServiceNow details remain unverified.
  • on_prem_sources: Remote MCP must be reachable from Anthropic cloud; Desktop-local MCP is separate and unavailable in cloud chat/Cowork. Named file-share/database connectors were not verified.
  • microsoft_365 Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [supported]: Anthropic-hosted Graph connector covers SharePoint, OneDrive, Outlook and Teams; Claude owner enablement and Entra consent are separate. Sources: claude:cl-m365-20261026.
  • google_workspace Which Google sources are connected? [supported]: Gmail, Calendar and Drive are documented with owner enablement and user authorization; live Docs/Sheets/Slides are separate connectors. Sources: claude:cl-google-20261026.
  • atlassian Confluence and Jira? [partial]: Claude Enterprise documents Atlassian Rovo MCP for Jira, Confluence and Teamwork Graph, including organization-managed authorization through Okta. This does not establish a native indexed Confluence connector, universal Team entitlement or observed ACL fidelity. Sources: claude:claude:atlassian-enterprise-20261026, claude:cl-mcp-20261026.
  • other_systems Which other business systems? [partial]: Enterprise docs list GitHub and Slack; Salesforce is a separately approved paid-plan beta in release notes. Box/ServiceNow details remain unverified. Sources: claude:cl-enterprise-20261026, claude:cl-release-20261026.
  • on_prem_sources Can on-prem file shares or databases be connected? [partial]: Remote MCP must be reachable from Anthropic cloud; Desktop-local MCP is separate and unavailable in cloud chat/Cowork. Named file-share/database connectors were not verified. Sources: claude:cl-mcp-20261026.
  • connector_provider Who builds and maintains each connector? [supported]: Microsoft connector is Anthropic-hosted; custom MCP may be built/hosted by the customer or a third party. Sources: claude:cl-m365-20261026, claude:cl-mcp-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: claude:cl-m365-20261026, claude:cl-google-20261026, claude:cl-enterprise-20261026, claude:cl-release-20261026, claude:cl-mcp-20261026, claude:claude:atlassian-enterprise-20261026.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Documented live-source permissions do not replace the required two-user test.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • No observed permission assurance or revocation SLA is established. Shared conversation output can reveal retrieved content to recipients.
  • source_permissions_respected Are source permissions enforced per user? [supported]: Microsoft and Google connectors use the connected user account permissions. Sources: claude:cl-m365, claude:cl-google.
  • enforcement_point Does the source system, a mirrored index or nothing enforce them? [supported]: Microsoft Graph delegated calls check source access; the connector is a proxy without a copied file-content cache. Sources: claude:cl-m365.
  • revocation_delay How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unverified after checking connector security and user docs; no restricted-document or revocation-latency fixture.
  • admin_scope_controls Can admins exclude sites, folders or labels? [partial]: Owners control connectors/tools; Microsoft Sites.Selected and a SharePoint site allowlist are explicitly unavailable in this connector. Sources: claude:cl-m365-user.
  • sensitivity_labels Are Microsoft Purview or similar labels respected? [partial]: The Microsoft security guide says delegated access respects M365 DLP; exact Purview label exclusion behavior was not tested. Sources: claude:cl-m365.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-m365, claude:cl-google, claude:cl-m365-user.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Microsoft content is fetched on demand; Google project references have a separate sync path.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: sync_interval, deletion_propagation, index_location.
  • Read each atomic answer for its plan, access and feature limits.
  • live_or_indexed Is content searched live or copied into an index? [partial]: Microsoft uses on-demand Graph access without caching file content. Google Docs attached to private projects sync from Drive. Sources: claude:cl-m365, claude:cl-google.
  • sync_interval How often does an index refresh? [unknown]: How often does an index refresh? Unverified after checking Microsoft proxy and Google Workspace docs; full sync interval, deletion propagation and copied-index storage map not measured.
  • deletion_propagation How quickly does a deleted document disappear? [unknown]: How quickly does a deleted document disappear? Unverified after checking Microsoft proxy and Google Workspace docs; full sync interval, deletion propagation and copied-index storage map not measured.
  • index_location Where is indexed content stored? [unknown]: Where is indexed content stored? Unverified after checking Microsoft proxy and Google Workspace docs; full sync interval, deletion propagation and copied-index storage map not measured.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-m365, claude:cl-google.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Google-source citations are documented; grounding accuracy remains unmeasured.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • No observed accuracy or cross-language retrieval ranking.
  • citations Are answers linked to specific sources? [partial]: Google connector answers cite original email/calendar/document sources when available. Sources: claude:cl-google.
  • citation_accuracy Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unverified after checking Google connector citation docs; no multilingual shared corpus, cross-document, citation-accuracy or unanswerable-question test.
  • cross_language Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unverified after checking Google connector citation docs; no multilingual shared corpus, cross-document, citation-accuracy or unanswerable-question test.
  • no_answer_behaviour Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unverified after checking Google connector citation docs; no multilingual shared corpus, cross-document, citation-accuracy or unanswerable-question test.
  • observed_accuracy How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unverified after checking Google connector citation docs; no multilingual shared corpus, cross-document, citation-accuracy or unanswerable-question test.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-google.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Improved memory and legacy memory have different Team/Enterprise administration and Cowork behavior.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Team/Enterprise improved Settings>Memory experience; legacy Settings>Capabilities memory is separately qualified; project instructions are independent; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Identify experience by Settings>Memory versus legacy Memory under Settings>Capabilities; neither control set is applied universally.
  • No organization memory fixture. Current page retains a legacy section for a small number of Team/Enterprise organizations.
  • custom_instructions Can users set persistent instructions? [supported]: Projects have persistent instructions for context and style. Sources: claude:cl-projects.
  • cross_chat_memory Does the product remember facts across chats? [partial]: Improved memory: owners enable availability and members opt in; cloud Cowork shares Chat memory, local Cowork does not. Legacy memory is chat-only and unavailable in Cowork. Sources: claude:cl-memory-r2.
  • user_memory_controls Can users view, edit and delete memories? [partial]: Improved memory users inspect/delete topics, pause/reset and choose sensitive-topic opt-in. Incognito remains subject to organization export/retention. Legacy settings and summary-memory behavior differ. Sources: claude:cl-memory-r2.
  • admin_memory_controls Can admins turn memory off? [partial]: Improved memory: Owners/Primary Owners control availability; disabling it deletes existing entries. Legacy Team explicitly lacks org-level memory controls. Improved memory is unavailable under the named HIPAA/public-sector/custom-retention agreements. Sources: claude:cl-memory-r2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-projects, claude:cl-memory-r2.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Projects, skills, plugins and artifacts provide reusable task context; full assistant governance remains partly unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • No HR-policy assistant was built or shared with a test group.
  • create_assistants Can users create assistants with instructions, knowledge and tools? [partial]: Projects pair instructions/knowledge; skills and plugins provide reusable task behavior, while custom agent model/tool binding was not fully audited. Sources: claude:cl-projects, claude:cl-academy.
  • creator_permissions Can admins limit who creates them? [partial]: Enterprise groups/custom roles control plugin access and shared resources; a complete assistant-creator matrix was not verified. Sources: claude:cl-groups.
  • sharing_scope Can assistants be shared with users, groups or everyone? [supported]: Team/Enterprise projects share with organization members; Enterprise groups can receive projects/skills/plugins. Sources: claude:cl-projects, claude:cl-groups.
  • catalogue Is there an internal assistant directory? [partial]: Organization resources and plugins can be shared; a complete internal assistant directory was not inspected. Sources: claude:cl-groups.
  • prompt_library Are shared prompt templates available? [partial]: Skills capture reusable instructions/processes across Office apps; plain prompt-template catalogue behavior was not verified. Sources: claude:cl-office.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-projects, claude:cl-academy, claude:cl-groups, claude:cl-office.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Claude supports remote and local MCP with different execution and identity boundaries.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • No external-tool call or fixture permission test was performed.
  • builtin_tools Which tools are built in? [supported]: Code execution, web search, Research and connector tools are listed for commercial plans. Sources: claude:cl-pricing.
  • custom_actions Can admins add API actions? [partial]: Custom remote MCP can expose action tools; OpenAPI-specific action configuration was not separately verified. Sources: claude:cl-mcp.
  • mcp_client Can it use remote MCP servers, and with what admin control? [supported]: Remote MCP works through Anthropic cloud. Desktop-local MCP is a separate local-network mechanism; Cowork/cloud chat cannot use that local configuration. Sources: claude:cl-mcp.
  • tool_auth Do tools act as the user or as a shared account? [supported]: Remote connectors can use per-user OAuth or fixed shared request-header credentials; the latter exposes that credential's access to users. Sources: claude:cl-mcp.
  • tool_approval Can admins approve or block tools, and can users confirm actions before they run? [partial]: Owners enable connectors and tools; Microsoft Teams sends require Ask, while other tools have configurable permission behavior. Sources: claude:cl-m365, claude:cl-mcp.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-pricing, claude:cl-mcp, claude:cl-m365.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Web search and Research are offered; detailed search-provider geography and group policy remain open.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • search_provider: Which search provider handles queries, and where? Unverified after checking commercial plan comparison, connector and release docs; current search provider, query location, web-specific citation behavior and full admin toggle matrix not established. Search on 2026-10-26: https://claude.com/pricing, https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork, https://support.claude.com/en/articles/10684626-enable-and-use-web-search. No additional scoped evidence established this answer.
  • web_search Is web search available? [supported]: Commercial plans include web search. Sources: claude:cl-pricing-20261026.
  • admin_toggle Can admins disable it per organisation or group? [supported]: An Owner or Primary Owner enables web search for the Team/Enterprise workspace under Organization settings > Capabilities. Members then enable it in chat; the new unified experience can invoke search without a per-chat toggle. Sources: claude:claude:web-search-controls-20261026.
  • search_provider Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? Unverified after checking commercial plan comparison, connector and release docs; current search provider, query location, web-specific citation behavior and full admin toggle matrix not established. Search on 2026-10-26: https://claude.com/pricing, https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork, https://support.claude.com/en/articles/10684626-enable-and-use-web-search. No additional scoped evidence established this answer.
  • deep_research Is multi-step research with a report available? [supported]: Commercial plans list Research; no shared-corpus report was run. Sources: claude:cl-pricing-20261026.
  • web_citations Are web sources cited? [supported]: The web-search guide documents direct citations and links to the sources used in searched answers. Citation correctness was not fixture-tested. Sources: claude:claude:web-search-controls-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: claude:cl-pricing-20261026, claude:claude:web-search-controls-20261026.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Cowork documents scheduled multi-step tasks; external-event triggers remain unverified.

Availability: beta · Delivery: native
Scope: surfaces=Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Team and Enterprise Cowork; cloud execution in beta; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: event_triggers.
  • Read each atomic answer for its plan, access and feature limits.
  • workflow_builder Is there a workflow or chain builder? [partial]: Cowork turns outcome instructions into multi-step tasks and reusable scheduled work; a separate no-code graph builder was not verified. Sources: claude:cl-cowork.
  • scheduled_tasks Can prompts or assistants run on a schedule? [partial]: Scheduled Cowork tasks run in the cloud with no device online, subject to commercial beta and admin access. Sources: claude:cl-cowork.
  • event_triggers Can external events start a workflow? [unknown]: Can external events start a workflow? Unverified after checking Cowork task/schedule and connector docs; no external-event trigger contract or event fixture.
  • builder_audience Is building aimed at business users, IT or developers? [supported]: Cowork is aimed at knowledge work with no terminal required. Sources: claude:cl-cowork.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-cowork.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Cowork documents multi-step execution; broad action and stop-control behavior remains untested.

Availability: beta · Delivery: native
Scope: surfaces=Claude Cowork cloud and desktop task execution, Claude connectors and remote MCP integrations; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Team/Enterprise Cowork; cloud beta where stated; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • visible_steps: The documented task flow includes planning and subtasks; complete tool-step visibility was not independently observed.
  • side_effect_confirmation: Microsoft connector has required confirmations for specified email/calendar/Teams actions; this does not establish mandatory confirmation for every Cowork side effect.
  • stop_control: The paid-plan Cowork safety guide documents user stopping/monitoring of tasks. It does not guarantee that stopping reverses a completed write or cancels every submitted external action.
  • agent_mode Is there an agent mode for multi-step tasks? [supported]: Paid Cowork plans and executes multi-step tasks with code, files and browser access where permitted. Sources: claude:cl-cowork-20261026.
  • visible_steps Are steps and tool calls shown? [partial]: The documented task flow includes planning and subtasks; complete tool-step visibility was not independently observed. Sources: claude:cl-cowork-20261026.
  • side_effect_confirmation Must the user confirm actions with side effects? [partial]: Microsoft connector has required confirmations for specified email/calendar/Teams actions; this does not establish mandatory confirmation for every Cowork side effect. Sources: claude:cl-m365-20261026.
  • stop_control Can the user stop a running task? [partial]: The paid-plan Cowork safety guide documents user stopping/monitoring of tasks. It does not guarantee that stopping reverses a completed write or cancels every submitted external action. Sources: claude:claude:cowork-stop-20261026, claude:cl-cowork-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: claude:cl-cowork-20261026, claude:cl-m365-20261026, claude:claude:cowork-stop-20261026.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

A public model API and separate compliance/analytics interfaces exist; workspace feature parity is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: knowledge_api, mcp_server.
  • Read each atomic answer for its plan, access and feature limits.
  • chat_api Is there an API for chat and assistants? [partial]: Claude Platform has a public separately priced model API; this does not establish API access to the same Claude Team/Enterprise assistant conversations. Sources: claude:cl-api-prices.
  • knowledge_api Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? Unverified after checking Claude Platform pricing and commercial Compliance API docs; workspace knowledge ingestion and product MCP-server exposure not verified.
  • api_governance Do audit, budgets and model rules apply to API use? [partial]: Enterprise Compliance API covers eligible deployments; automatic parity of model, budget and audit policy with separately purchased API usage was not established. Sources: claude:cl-compliance.
  • mcp_server Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unverified after checking Claude Platform pricing and commercial Compliance API docs; workspace knowledge ingestion and product MCP-server exposure not verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-api-prices, claude:cl-compliance.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Web, native clients and Chrome access are documented, with distinct admin and beta eligibility.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Read each atomic answer for its plan, access and feature limits.
  • web Is a full web client available? [supported]: Commercial Claude is available on the web. Sources: claude:cl-enterprise.
  • desktop_apps Windows and macOS apps? [supported]: Cowork supports macOS and Windows desktop clients on paid plans. Sources: claude:cl-cowork.
  • mobile_apps iOS and Android apps with SSO? [partial]: iOS/Android clients support commercial accounts; SSO mobile login was not tested. Sources: claude:cl-cowork, claude:cl-m365-user.
  • browser_extension Is there a browser extension or sidebar? [partial]: Claude in Chrome is available with plan/Enterprise admin eligibility. Sources: claude:cl-cowork.
  • managed_deployment Can IT deploy and configure clients through MDM? [partial]: Team and Enterprise plan comparisons list enterprise desktop deployment; exact MDM packages/policies were not reviewed. Sources: claude:cl-pricing.
  • client_feature_gaps Which features are missing on mobile? [partial]: Exports require web/Desktop; cloud Cowork rollout and admin enablement differ from local desktop execution. Sources: claude:cl-export-user, claude:cl-cowork.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-enterprise, claude:cl-cowork, claude:cl-m365-user, claude:cl-pricing, claude:cl-export-user.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Native Microsoft add-ins and a separate Google Workspace beta have different approval and data paths.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude for Microsoft 365 official add-ins, Claude connectors and remote MCP integrations, Claude native Google Workspace sidebar beta; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Team/Enterprise Office; Outlook beta; Google Workspace native beta; add_ons=Microsoft/Google subscriptions and administrator deployment approval where required; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • No deployment or native-edit fixture. Google extension retains its own local per-file history and does not inherit custom organization retention.
  • word_excel_powerpoint Does it work inside Word, Excel and PowerPoint? [supported]: Claude advertises native Excel/PowerPoint/Word add-ins as generally available on paid plans. Sources: claude:cl-office.
  • outlook Does it work inside Outlook? [supported]: Outlook add-in is beta and opens drafts in the native composer for user sending. Sources: claude:cl-office.
  • teams Is there a Teams app or bot? [partial]: Teams read/write is through the separate Microsoft connector; a native Teams app was not established. Sources: claude:cl-m365.
  • google_workspace_apps Does it work inside Docs, Sheets or Gmail? [supported]: Native Google Docs/Sheets/Slides sidebar is beta for Team/Enterprise, installed via Google Marketplace. It edits the open file under the user identity with ask-before-edits by default; connectors are a separate feature. Sources: claude:cl-google-addon.
  • licence_prerequisites Which licences or consents are needed? [partial]: Paid Claude or supported cloud credentials are advertised for Office; Google add-in needs a paid supported plan and Marketplace approval. Microsoft source connector needs work-account/Entra consent. Sources: claude:cl-office, claude:cl-google-addon, claude:cl-m365-user.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-office, claude:cl-m365, claude:cl-google-addon, claude:cl-m365-user.

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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Office rewriting/review is documented; translation fidelity and glossary controls remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: document_translation, translation_engine, glossaries, formality_and_variants.
  • Read each atomic answer for its plan, access and feature limits.
  • document_translation Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Unverified after checking Office and project-instruction docs; layout-preserving DE-to-FR/IT translation, dedicated engine, glossary and Swiss-language controls not established.
  • translation_engine Which engine translates? [unknown]: Which engine translates? Unverified after checking Office and project-instruction docs; layout-preserving DE-to-FR/IT translation, dedicated engine, glossary and Swiss-language controls not established.
  • glossaries Are company glossaries supported? [unknown]: Are company glossaries supported? Unverified after checking Office and project-instruction docs; layout-preserving DE-to-FR/IT translation, dedicated engine, glossary and Swiss-language controls not established.
  • formality_and_variants Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unverified after checking Office and project-instruction docs; layout-preserving DE-to-FR/IT translation, dedicated engine, glossary and Swiss-language controls not established.
  • writing_tools Are dedicated rewrite and proofreading tools available? [partial]: Word add-in advertises tracked revisions, comments and company styles; no proofreading/translation fixture was run. Sources: claude:cl-office.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-office.

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-9.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Claude explicitly excludes native photo/illustration generation; HTML/SVG visuals and uploaded-image analysis are separate capabilities.

Availability: unknown · Delivery: unknown
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients; version=Public help checked 2026-10-26; plan=Team/Enterprise native Claude web and desktop; third-party image tools excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Supported commercial regions; os=not specified.

Limitations

  • image_editing: Can users edit uploaded images? Unverified after checking Claude pricing, artifacts and code/file-creation docs; design/artifact creation does not establish a native raster image model, uploaded-image editing, per-image controls or image-specific licence terms. Search on 2026-10-26: https://support.claude.com/en/articles/9002504-can-claude-produce-images, https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language. No additional scoped evidence established this answer.
  • admin_control: Can admins restrict image generation? Unverified after checking Claude pricing, artifacts and code/file-creation docs; design/artifact creation does not establish a native raster image model, uploaded-image editing, per-image controls or image-specific licence terms. Search on 2026-10-26: https://support.claude.com/en/articles/9002504-can-claude-produce-images, https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language. No additional scoped evidence established this answer.
  • usage_terms: What usage rights apply to output? Unverified after checking Claude pricing, artifacts and code/file-creation docs; design/artifact creation does not establish a native raster image model, uploaded-image editing, per-image controls or image-specific licence terms. Search on 2026-10-26: https://support.claude.com/en/articles/9002504-can-claude-produce-images, https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language. No additional scoped evidence established this answer.
  • image_generation Can users generate images, with which models? [unsupported]: The official image FAQ explicitly says Claude does not generate photos or illustrations like dedicated image-generation tools. Its beta HTML/SVG diagrams/charts are not a native raster image-generation model. Sources: claude:claude:image-generation-boundary-20261026.
  • image_editing Can users edit uploaded images? [unknown]: Can users edit uploaded images? Unverified after checking Claude pricing, artifacts and code/file-creation docs; design/artifact creation does not establish a native raster image model, uploaded-image editing, per-image controls or image-specific licence terms. Search on 2026-10-26: https://support.claude.com/en/articles/9002504-can-claude-produce-images, https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language. No additional scoped evidence established this answer.
  • admin_control Can admins restrict image generation? [unknown]: Can admins restrict image generation? Unverified after checking Claude pricing, artifacts and code/file-creation docs; design/artifact creation does not establish a native raster image model, uploaded-image editing, per-image controls or image-specific licence terms. Search on 2026-10-26: https://support.claude.com/en/articles/9002504-can-claude-produce-images, https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language. No additional scoped evidence established this answer.
  • usage_terms What usage rights apply to output? [unknown]: What usage rights apply to output? Unverified after checking Claude pricing, artifacts and code/file-creation docs; design/artifact creation does not establish a native raster image model, uploaded-image editing, per-image controls or image-specific licence terms. Search on 2026-10-26: https://support.claude.com/en/articles/9002504-can-claude-produce-images, https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language. No additional scoped evidence established this answer.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: claude:claude:image-generation-boundary-20261026.

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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Voice and Office dictation are listed; meeting and dialect details need evidence.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: read_aloud, meeting_summaries, swiss_german_speech.
  • Read each atomic answer for its plan, access and feature limits.
  • dictation Can users dictate prompts? [supported]: Claude for Microsoft 365 advertises dictation in its sidebar. Sources: claude:cl-office.
  • read_aloud Can answers be read aloud? [unknown]: Can answers be read aloud? Unverified after checking commercial Voice listing, Office and connector docs; standalone read-aloud, live meeting transcription and Swiss German accuracy not verified.
  • voice_conversation Is a live voice mode available? [partial]: Team/Enterprise feature comparison lists Voice mode; exact client/language/audio-processing scope was not fully verified. Sources: claude:cl-pricing.
  • meeting_summaries Are meetings transcribed and summarised? [unknown]: Are meetings transcribed and summarised? Unverified after checking commercial Voice listing, Office and connector docs; standalone read-aloud, live meeting transcription and Swiss German accuracy not verified.
  • swiss_german_speech Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unverified after checking commercial Voice listing, Office and connector docs; standalone read-aloud, live meeting transcription and Swiss German accuracy not verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-office, claude:cl-pricing.

Cohere North

Agent cross-checked Support: partial

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

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

  • 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 ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Enabled Chat code/file tools provide sandboxed analysis and Office/PDF output; Team egress defaults are not established by this finding.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Team/Enterprise Chat code execution, file creation and artifact editing where enabled; excludes native Office and Cowork execution defaults; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Narrowed to verified file creation/execution. The guide's conflicting Team default is retained as a named configuration gap, not a claim about an enabled tenant.
  • No formula/PPT/PDF output fixture. Separate enabled MCP routes are not controlled by the code-sandbox egress setting.
  • data_analysis Can it analyse spreadsheets with executed code? [supported]: Enabled Chat code/file creation runs code in a sandboxed container and can create Python analysis scripts. This does not establish a particular Team egress default. Sources: claude:cl-code-files-r2.
  • charts Can it produce charts? [supported]: The Chat computing path can create PNG data visualizations; native Office add-in charts are outside this narrowed scope. Sources: claude:cl-code-files-r2.
  • office_file_output Can it create Word, Excel or PowerPoint files? [supported]: Enabled Chat file creation produces downloadable XLSX/PPTX/DOCX/PDF, subject to the file-tool guide's30 MB upload/download path. Sources: claude:cl-code-files-r2.
  • canvas_editing Is there a document or canvas editor for iterating on output? [partial]: Docs/Design/Slides artifact templates support editing; template availability differs by type and plan. Sources: claude:cl-artifacts-admin.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-code-files-r2, claude:cl-artifacts-admin.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Commercial projects and artifacts support shared work; recipient source boundaries need tests.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: group_chat.
  • Read each atomic answer for its plan, access and feature limits.
  • share_chats Can chats be shared inside the organisation? [partial]: Shared project members can see project content and chat within it; a full chat-link audience matrix was not verified. Sources: claude:cl-projects.
  • team_spaces Are shared projects or workspaces available? [supported]: Team/Enterprise have shared projects; Enterprise groups receive shared projects/skills/plugins. Sources: claude:cl-projects, claude:cl-groups.
  • group_chat Can several people chat together with the AI? [unknown]: Can several people chat together with the AI? Unverified after checking project sharing, group controls and connector security; synchronous group AI chat and cross-group sharing fixture not verified.
  • share_permission_boundary Does sharing respect the recipient's access to sources? [partial]: Microsoft connector guide says shared-chat recipients see the response incorporating tool data; original source authorization does not prove recipient-safe output sharing. Sources: claude:cl-m365.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-projects, claude:cl-groups, claude:cl-m365.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Web and desktop interface languages include German, French and Italian; UI quality, complete admin localization and WCAG conformance remain unverified.

Availability: unknown · Delivery: unknown
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Team and Enterprise using the documented web/desktop language setting; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • dach_language_quality: Are German, French and Italian UIs complete and natural? Unverified after checking Claude support/pricing/client documentation and language-setting searches; no plan-specific German/French/Italian UI inventory, linguistic inspection, localized admin inspection or WCAG conformance report retrieved. Search on 2026-10-26: https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language, https://support.claude.com/en/articles/9002504-can-claude-produce-images. No additional scoped evidence established this answer.
  • accessibility_statement: Is there a WCAG conformance statement? Unverified after checking Claude support/pricing/client documentation and language-setting searches; no plan-specific German/French/Italian UI inventory, linguistic inspection, localized admin inspection or WCAG conformance report retrieved. Search on 2026-10-26: https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language, https://support.claude.com/en/articles/9002504-can-claude-produce-images. No additional scoped evidence established this answer.
  • admin_ui_languages: Is the admin interface available in German? Unverified after checking Claude support/pricing/client documentation and language-setting searches; no plan-specific German/French/Italian UI inventory, linguistic inspection, localized admin inspection or WCAG conformance report retrieved. Search on 2026-10-26: https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language, https://support.claude.com/en/articles/9002504-can-claude-produce-images. No additional scoped evidence established this answer.
  • ui_languages Which UI languages are offered? [supported]: The public display-language guide lists German, French and Italian, alongside English, Hindi, Indonesian, Japanese, Korean, Brazilian Portuguese and two Spanish variants, for web and desktop. Sources: claude:claude:display-languages-20261026.
  • dach_language_quality Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unverified after checking Claude support/pricing/client documentation and language-setting searches; no plan-specific German/French/Italian UI inventory, linguistic inspection, localized admin inspection or WCAG conformance report retrieved. Search on 2026-10-26: https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language, https://support.claude.com/en/articles/9002504-can-claude-produce-images. No additional scoped evidence established this answer.
  • accessibility_statement Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unverified after checking Claude support/pricing/client documentation and language-setting searches; no plan-specific German/French/Italian UI inventory, linguistic inspection, localized admin inspection or WCAG conformance report retrieved. Search on 2026-10-26: https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language, https://support.claude.com/en/articles/9002504-can-claude-produce-images. No additional scoped evidence established this answer.
  • admin_ui_languages Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unverified after checking Claude support/pricing/client documentation and language-setting searches; no plan-specific German/French/Italian UI inventory, linguistic inspection, localized admin inspection or WCAG conformance report retrieved. Search on 2026-10-26: https://support.claude.com/en/articles/12111783-create-and-edit-files-with-claude, https://support.claude.com/en/articles/10769299-how-to-use-claude-in-your-preferred-language, https://support.claude.com/en/articles/9002504-can-claude-produce-images. No additional scoped evidence established this answer.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: claude:claude:display-languages-20261026.

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-1.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Commercial SSO and domain controls are documented; exact client MFA/Conditional Access coverage remains open.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Connector token/device policy caveats must not be generalized to Claude SSO itself. No trial login was performed.
  • sso_protocols Which SSO protocols and identity providers work? [partial]: The SSO/provisioning guides document SAML IdPs including Entra, Okta, Google and others; full OIDC/direct-LDAP matrix was not established. Sources: claude:cl-sso, claude:cl-provision.
  • sso_plan Which plan includes SSO? [supported]: SSO is available on Team and Enterprise. Sources: claude:cl-sso.
  • mfa Can MFA be enforced? [unknown]: Can MFA be enforced? Unverified after checking SSO/provisioning and Microsoft connector security docs; direct MFA policy enforcement and client Conditional Access compatibility not tested.
  • conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unverified after checking SSO/provisioning and Microsoft connector security docs; direct MFA policy enforcement and client Conditional Access compatibility not tested.
  • domain_capture Can the company claim its email domain? [partial]: SSO requires domain verification; Enterprise account claiming and Team migration differ. Sources: claude:cl-sso, claude:cl-pricing.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-sso, claude:cl-provision, claude:cl-pricing.

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-doc-105.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Team JIT and Enterprise SCIM have different synchronization and removal behavior.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • No leaver fixture or asset transfer test was performed.
  • scim Is SCIM provisioning supported? [supported]: SCIM is available on Enterprise and explicitly unavailable on Team. Sources: claude:cl-provision.
  • group_sync Are identity-provider groups synced? [partial]: Enterprise SCIM can synchronize groups; JIT group mappings change role/seat at login and do not synchronize custom-role groups. Sources: claude:cl-provision.
  • jit_provisioning Are users created at first login? [supported]: Team/Enterprise JIT can provision at first SSO login; unassigned JIT users can retain their seat until manual removal. Sources: claude:cl-provision.
  • deprovisioning What happens to a removed user's data and shared assets? [partial]: Enterprise SCIM automatically removes users when IdP access is revoked; underlying chat/project ownership and retention were not fixture-tested. Sources: claude:cl-provision.
  • seat_assignment Can admins assign and reclaim seats? [supported]: Admins/owners manage standard/premium or current Enterprise access seats; group mappings can assign role/tier on supported plans. Sources: claude:cl-provision.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-provision.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Enterprise custom roles/groups add granular controls beyond Team owner/admin roles.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Read each atomic answer for its plan, access and feature limits.
  • admin_roles Which admin roles exist, and can admin rights be delegated? [supported]: Team has Owner/Admin/User; Enterprise also has custom roles and Primary Owner responsibilities. Sources: claude:cl-provision, claude:cl-compliance.
  • groups Can permissions be set per group? [supported]: Enterprise groups can be manual or SCIM-synchronized and receive roles/resources. Sources: claude:cl-groups.
  • feature_toggles Which features can be switched on or off per group? [partial]: Enterprise roles control model/effort and plugin access; owners manage connectors, artifacts and egress. A full feature-by-group matrix was not tested. Sources: claude:cl-model-control, claude:cl-groups, claude:cl-artifacts-admin.
  • multi_entity Can subsidiaries or departments be separated within one contract? [partial]: Parent/linked organization identity and compliance are documented, but full subsidiary data-isolation behavior was not verified. Sources: claude:cl-compliance.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-provision, claude:cl-compliance, claude:cl-groups, claude:cl-model-control, claude:cl-artifacts-admin.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Commercial analytics expose adoption and spend with plan-specific roles and CSV exports.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: privacy_modes.
  • Read each atomic answer for its plan, access and feature limits.
  • adoption_dashboard Is there an adoption dashboard? [supported]: Team owners and Enterprise owners/admins have usage analytics; Enterprise admins cannot see Spend. Sources: claude:cl-analytics.
  • breakdowns Can usage be broken down by group, model, feature and assistant? [partial]: Product, group, member, model, skill and connector read/write activity are documented; availability varies by billing mode. Sources: claude:cl-analytics.
  • export Can usage data be exported? [supported]: CSV spend reports include user/model token and estimated-spend fields, updated daily, with up to 90-day selectable history. Sources: claude:cl-analytics.
  • privacy_modes Can per-person reporting be limited or pseudonymised? [unknown]: Can per-person reporting be limited or pseudonymised? Unverified after checking analytics and role docs; organization-wide pseudonymization/works-council reporting settings not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-analytics.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Enterprise has user/group limits, with pooled group budgets in beta.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • No small-budget enforced-stop fixture was run.
  • cost_visibility Can admins see cost or consumption per user and group? [supported]: Enterprise analytics show model/member spend; legacy seat-based reports cover overage only. Sources: claude:cl-analytics.
  • budgets Can budgets be set per user or group? [partial]: Enterprise supports organization/user limits and group per-user limits; shared monthly group budgets are beta. Sources: claude:cl-enterprise, claude:cl-groups.
  • budget_enforcement Does reaching a budget alert, block or downgrade? [partial]: Docs expose blocked-by-limit behavior and individual/group resolution order; exact overshoot/timing was not tested. Sources: claude:cl-groups.
  • chargeback Can costs be exported per cost centre? [partial]: Per-user/model CSVs can inform allocation; a native cost-centre chargeback export was not established. Sources: claude:cl-analytics.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-analytics, claude:cl-enterprise, claude:cl-groups.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Enterprise audit metadata and content/compliance exports are distinct.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • CMEK disables the UI Export logs route; audit events remain accessible through Compliance API. No export or integrity fixture was run.
  • admin_events Are admin and security events logged? [supported]: Enterprise audit events cover member, SSO, configuration, file and conversation metadata; exported fields include actor/device/IP. Sources: claude:cl-audit.
  • content_logging Can prompts and answers be retained for compliance, and is it configurable? [supported]: Audit export excludes chat titles/content; organization data exports or Compliance API provide eligible content. Sources: claude:cl-audit, claude:cl-compliance.
  • siem_export Can logs stream to a SIEM or be exported? [supported]: Enterprise Compliance API and partner integrations provide event/chat/file access for security tools. Sources: claude:cl-compliance, claude:cl-compliance-partners.
  • ediscovery Are eDiscovery and legal hold supported? [partial]: Partner integrations include preservation/eDiscovery workflows; a native legal-hold setting was not verified. Sources: claude:cl-compliance-partners.
  • log_retention How long are logs kept? [partial]: UI audit export aggregates the past 180 days; its download link lasts 24 hours. API retention/integrity guarantees were not fully inspected. Sources: claude:cl-audit.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-audit, claude:cl-compliance, claude:cl-compliance-partners.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Eligible Enterprise organizations can use Compliance API partner monitoring; native inline PII handling remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude connectors and remote MCP integrations; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Enterprise with Primary-Owner-enabled Compliance API and separately configured partner integration; no Team entitlement; add_ons=Enterprise plan, Compliance API activation by Primary Owner, Applicable partner subscription and configuration; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • The positive integration statement is Enterprise-only. Team integration support remains unverified.
  • No Swiss AHV/IBAN fixture, custom-pattern behavior, pre-model blocking/redaction or filter geography verified.
  • pii_detection Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unverified after checking Compliance API integration, connector and security docs; no Swiss AHV/IBAN test, native PII action/custom patterns or filter geography verified.
  • pii_action Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unverified after checking Compliance API integration, connector and security docs; no Swiss AHV/IBAN test, native PII action/custom patterns or filter geography verified.
  • custom_patterns Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unverified after checking Compliance API integration, connector and security docs; no Swiss AHV/IBAN test, native PII action/custom patterns or filter geography verified.
  • dlp_integration Does it integrate with an existing DLP product? [partial]: Enterprise Compliance API partners offer monitoring/security/DLP integrations after Primary Owner activation. Claude Platform is a separate scope, and these integrations do not prove native inline pre-model redaction. Sources: claude:cl-compliance-partners-r2.
  • filter_location Where does filtering run? [unknown]: Where does filtering run? Unverified after checking Compliance API integration, connector and security docs; no Swiss AHV/IBAN test, native PII action/custom patterns or filter geography verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-compliance-partners-r2.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Enterprise has feature/model and plugin safeguards; broader policy enforcement remains partly unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: org_instructions, usage_notice.
  • Read each atomic answer for its plan, access and feature limits.
  • org_instructions Can admins set organisation-wide instructions? [unknown]: Can admins set organisation-wide instructions? Unverified after checking commercial terms, Enterprise controls and security scanning releases; organization-wide enforced instructions and mandatory AUP acknowledgment not established.
  • usage_notice Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Unverified after checking commercial terms, Enterprise controls and security scanning releases; organization-wide enforced instructions and mandatory AUP acknowledgment not established.
  • content_filters Are content filters configurable? [partial]: Enterprise release notes announce skill/plugin security scanning beta; it does not establish a configurable prompt/topic content-filter system. Sources: claude:cl-release.
  • violation_reporting Are policy hits visible to admins? [partial]: Security/compliance integrations can analyze events; a complete native policy-violation dashboard was not verified. Sources: claude:cl-compliance-partners.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-release, claude:cl-compliance-partners.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Commercial privacy documentation describes US storage and global inference; US-only Enterprise inference is a separate option.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Do not substitute cloud-provider model availability for residency of the hosted Claude workspace. Design and Google add-in retention have separate rules.
  • storage_region Where are chats, files and indexes stored? [partial]: The commercial server-location article specifies US storage for Enterprise/API; exact Team and per-feature chat/file/index mapping was not established. Sources: claude:cl-servers.
  • inference_region Where do model calls run, per provider? [supported]: Default commercial inference may run in the US, Europe, Asia or Australia; usage-based Enterprise can select US-only inference. Sources: claude:cl-servers, claude:cl-us-only.
  • backups_logs_region Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? Unverified after checking commercial location and US-only inference guides; no EU/Swiss-only hosting guarantee or backup/log/telemetry country matrix retrieved.
  • support_access_region From where can vendor staff access data? [partial]: Internal support/safety processing can take place in countries with Anthropic affiliates; the full personnel/country/access map is not enumerated here. Sources: claude:cl-servers.
  • swiss_hosting Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unverified after checking commercial location and US-only inference guides; no EU/Swiss-only hosting guarantee or backup/log/telemetry country matrix retrieved.
  • residency_plan Which plan or option provides residency? [supported]: US-only inference is limited to usage-based Enterprise, excludes Team and legacy seat-based Enterprise, and has model-specific 1.1x pricing. It does not control storage or third-party services. Sources: claude:cl-us-only.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-servers, claude:cl-us-only.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Team/Enterprise are vendor-hosted workspaces; whole-platform private deployment is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Local Cowork tasks, Desktop MCP and Office cloud credentials do not establish deployment of the whole hosted workspace.
  • multi_tenant_saas Is a shared SaaS offered? [supported]: Team/Enterprise provide Anthropic-operated commercial SaaS; the DPA specifies logical separation of customer data. Sources: claude:cl-enterprise, claude:cl-dpa.
  • dedicated_instance Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? Unverified after checking commercial plans, DPA, remote MCP and Office cloud-credential documentation; dedicated instance, whole-platform customer cloud/on-premises, air-gap and feature/seat thresholds not verified.
  • customer_cloud Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Unverified after checking commercial plans, DPA, remote MCP and Office cloud-credential documentation; dedicated instance, whole-platform customer cloud/on-premises, air-gap and feature/seat thresholds not verified.
  • on_premise Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? Unverified after checking commercial plans, DPA, remote MCP and Office cloud-credential documentation; dedicated instance, whole-platform customer cloud/on-premises, air-gap and feature/seat thresholds not verified.
  • air_gapped Can it run without internet access? [unknown]: Can it run without internet access? Unverified after checking commercial plans, DPA, remote MCP and Office cloud-credential documentation; dedicated instance, whole-platform customer cloud/on-premises, air-gap and feature/seat thresholds not verified.
  • mode_feature_gaps Which features are missing outside SaaS? [unknown]: Which features are missing outside SaaS? Unverified after checking commercial plans, DPA, remote MCP and Office cloud-credential documentation; dedicated instance, whole-platform customer cloud/on-premises, air-gap and feature/seat thresholds not verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-enterprise, claude:cl-dpa.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Hosted commercial Chat/Cowork retention is separate from API/Code/provider ZDR arrangements and limited Fable exceptions.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Direct hosted Claude Team/Enterprise Chat and Cowork under Commercial Terms; API/ClaudeCode/third-party-provider ZDR routes discussed only as separate exceptions; add_ons=Standard hosted commercial retention; no assumed special ZDR agreement; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Reconciliation: the Covered Model minimum is a default rule; its temporary agreement-based exception is conditional. The current route guide expressly excludes notified exception customers from the general ZDR-transition instructions.
  • No-training, saved history, safety-monitoring copies and specialized ZDR agreements are distinct. No sales contact or agreement signing.
  • vendor_training Does the vendor train on customer content? [supported]: Commercial Terms section B prohibits training on Customer Content; the privacy guide describes explicit feedback/bug submissions as an exception to default no-training. Sources: claude:cl-terms, claude:cl-training.
  • provider_training Do model providers train on it under this product's contracts? [partial]: Direct hosted Claude uses Anthropic models under its commercial no-training terms. Separate API, Office BYO cloud or third-party integrations require their own contracts and are outside this hosted inference finding. Sources: claude:cl-terms.
  • provider_retention How long do model providers keep prompts, including for abuse monitoring? [partial]: Hosted saved commercial chats persist until deletion; normal backend deletion is within 30 days with safety/legal exceptions. Covered Models have an additional default minimum 30-day safety-retention rule; ordinary saved-chat history is not thereby limited to30 days. Sources: claude:cl-retention-r2, claude:cl-covered-r2.
  • zero_retention Is zero data retention available, and on which plan? [partial]: The route guide says hosted Enterprise Chat/Cowork already operate with standard retention. Separately, Console/API, Enterprise Code and provider ZDR configurations follow their own rules. The default Covered Model rule has a limited temporary Fable exception for eligible notified/agreement-based internal business applications; no general hosted Chat/Cowork ZDR entitlement is established. Sources: claude:cl-covered-r2, claude:cl-covered-routes-r2.
  • human_review Can provider staff review content? [partial]: Commercial confidentiality/DPA measures permit authorized, least-privileged personnel processing. The detailed approved-reviewer path concerns the described Covered Model retained-monitoring configurations; it is not a complete hosted-chat human-access map. No no-human-access guarantee is made. Sources: claude:cl-terms, claude:cl-dpa, claude:cl-covered-routes-r2.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-terms, claude:cl-training, claude:cl-retention-r2, claude:cl-covered-r2, claude:cl-covered-routes-r2, claude:cl-dpa.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Current Enterprise retention guidance schedules deletion on save and removes content through a daily process, with project precedence and feature exclusions.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Team/Enterprise saved commercial Chat; Enterprise owner-configured Chat/project retention. Cowork is included only for documented project-activity effects, not blanket cloud-Code retention; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Reconciliation: current English text is authoritative for this snapshot; the earlier cached immediate-deletion wording is superseded and is not a current factual claim. Scheduling on save does not mean instant physical deletion.
  • No retention/deletion fixture. Google Workspace add-in and the named excluded cloud features have separate retention behavior.
  • default_retention What is retained and for how long by default? [partial]: Saved commercial chats persist until deletion; Enterprise chats/projects default to indefinite retention without configured periods. Incognito normally deletes within 30 days. Other file/index/log schedules are not fully mapped. Sources: claude:cl-retention-r2, claude:cl-retention-admin-r2.
  • admin_retention Can admins set retention periods? [supported]: Enterprise Owners/Primary Owners set a minimum 30-day Chat/project period. Project retention overrides contained chats, including indefinite projects. Shortening a period schedules over-age data on save; a daily process can take several days. Design/Tag/Managed Agents and other cloud-Code features are excluded. Sources: claude:cl-retention-admin-r2.
  • user_deletion Can users delete their chats and files permanently? [partial]: User-deleted chats leave visible history immediately and normally delete from backend within 30 days, subject to legal/safety exceptions. This is different from the daily custom-retention job. Sources: claude:cl-retention-r2.
  • contract_end_deletion What is deleted at contract end, and when? [partial]: DPA H requires return on request within 30 days and deletion within 30 days after expiry/termination, except legal requirements, disputes or combating harmful use. Confirmation/copy completeness were not tested. Sources: claude:cl-dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-retention-r2, claude:cl-retention-admin-r2, claude:cl-dpa.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

The DPA provides subprocessor and transfer rules; the current country list remains inaccessible in this pass.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: subprocessor_countries.
  • Read each atomic answer for its plan, access and feature limits.
  • subprocessor_list Is a dated sub-processor list published? [partial]: DPA Schedule 4 links to a published trust-portal list; its entries and revision were not extractable during retrieval. Sources: claude:cl-dpa, claude:cl-trust-route.
  • subprocessor_countries Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? Unverified after checking DPA Schedule 4, trust redirect and commercial terms; full current subprocessor countries, list date and ownership chain not retrieved.
  • change_notification Are customers notified of sub-processor changes? [supported]: DPA C.3 provides notice before a new subprocessor gains data access and a 15-day objection window on reasonable privacy/security concerns. Sources: claude:cl-dpa.
  • parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: Commercial Terms contract with Anthropic Ireland Limited for EEA/Swiss/UK customers and Anthropic PBC elsewhere; the ultimate ownership/entity chain was not independently established. Sources: claude:cl-terms.
  • transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA incorporates controller-to-processor/processor-to-processor SCCs and UK/Swiss schedules where applicable. Sources: claude:cl-dpa.
  • government_access_policy Is there a published government-access or transparency policy? [supported]: Published policy requires valid process with emergency exceptions, reviews deficient requests, usually redirects enterprise requests to the customer and provides notice subject to exceptions. Sources: claude:cl-gov.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-dpa, claude:cl-trust-route, claude:cl-terms, claude:cl-gov.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Public commercial contracts include a DPA and Swiss transfer terms; this is not a regulatory suitability verdict.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Generic confidentiality/DPA language does not establish a German section 203 or Swiss article 321 professional-secrecy undertaking.
  • dpa Is a DPA available, and is it negotiable? [partial]: Commercial Terms incorporate the public DPA; standard acceptance is documented, while negotiability for this account was not verified. Sources: claude:cl-terms, claude:cl-dpa.
  • revdsg_gdpr Does the DPA cover revDSG and GDPR? [supported]: DPA defines GDPR and includes a Swiss Addendum covering Swiss data protection laws and new/revised versions. Sources: claude:cl-dpa.
  • governing_law Which law and court govern the contract? [supported]: For EEA/Swiss/UK customers, Terms M.7 specify Irish law and Irish courts for proceedings not subject to section J arbitration; specific orders may differ. Sources: claude:cl-terms.
  • ai_act_materials Is EU AI Act documentation provided? [partial]: Provider materials describe transparency-code commitments, text watermarking and an eligible-organization detection API private preview. A complete deployer compliance pack was not inspected. Sources: claude:cl-ai-act.
  • sector_materials Are FINMA or other sector materials provided? [partial]: Enterprise plan documentation lists HIPAA-ready configurations; scope/BAA conditions and FINMA/banking/public-sector materials were not fully retrieved. Sources: claude:cl-enterprise.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-terms, claude:cl-dpa, claude:cl-ai-act, claude:cl-enterprise.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

The DPA documents report and penetration-test access; actual certification scope and validity remain open.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • iso_27001: Anthropic publicly claims ISO 27001:2022 for its commercial products. The issuing body, full certificate scope and validity dates were not inspected; this is vendor-claimed evidence.
  • soc2: The commercial privacy page lists SOC 2 Type I and Type II. The auditor, report period and detailed service scope were not inspected.
  • c5: BSI C5 attestation? Unverified after checking public DPA and Trust Center; issuer, covered entity/product, period and validity of ISO/SOC/C5/other attestations were not verified. Search on 2026-10-26: https://www.anthropic.com/legal/data-processing-addendum, https://www.anthropic.com/legal/commercial-terms, https://trust.anthropic.com/. No additional scoped evidence established this answer.
  • other_certifications: The commercial privacy page claims ISO/IEC 42001:2023. No issuing-body certificate, validity dates or TISAX/ISO 27701 scope was inspected.
  • pentest: DPA Schedule 2 G.2 commits to annual external penetration tests and a customer-request summary; no summary or testing period was inspected.
  • iso_27001 ISO 27001 with scope and validity? [partial]: Anthropic publicly claims ISO 27001:2022 for its commercial products. The issuing body, full certificate scope and validity dates were not inspected; this is vendor-claimed evidence. Sources: claude:claude:commercial-certifications-20261026.
  • soc2 SOC 2 type, period and covered service? [partial]: The commercial privacy page lists SOC 2 Type I and Type II. The auditor, report period and detailed service scope were not inspected. Sources: claude:claude:commercial-certifications-20261026.
  • c5 BSI C5 attestation? [unknown]: BSI C5 attestation? Unverified after checking public DPA and Trust Center; issuer, covered entity/product, period and validity of ISO/SOC/C5/other attestations were not verified. Search on 2026-10-26: https://www.anthropic.com/legal/data-processing-addendum, https://www.anthropic.com/legal/commercial-terms, https://trust.anthropic.com/. No additional scoped evidence established this answer.
  • other_certifications Which other certificates (27701, 42001, TISAX)? [partial]: The commercial privacy page claims ISO/IEC 42001:2023. No issuing-body certificate, validity dates or TISAX/ISO 27701 scope was inspected. Sources: claude:claude:commercial-certifications-20261026.
  • report_access How can customers obtain reports? [supported]: DPA F and Schedule 2 direct customers to the Trust Center and offer applicable reports/certificates on written request under confidentiality. No protected report was requested or downloaded. Sources: claude:cl-dpa-20261026.
  • pentest Are independent penetration test summaries available? [partial]: DPA Schedule 2 G.2 commits to annual external penetration tests and a customer-request summary; no summary or testing period was inspected. Sources: claude:cl-dpa-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: claude:cl-dpa-20261026, claude:claude:commercial-certifications-20261026.

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 ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: cohere-north:cohere-north:n-trust.

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

Claude Team / Enterprise

Agent cross-checked Support: partial

The DPA specifies encryption and logical isolation; Enterprise adds eligible customer keys and IP controls.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Read each atomic answer for its plan, access and feature limits.
  • encryption_at_rest Is data encrypted at rest? [supported]: DPA Schedule 2 E specifies at least AES-256 at rest and TLS 1.2+ over public networks. Sources: claude:cl-dpa.
  • customer_managed_keys Can the customer manage or hold the keys? [partial]: Eligible Enterprise organizations can connect AWS/GCP/Azure KMS keys for specified content; key locations and all feature exclusions need account-specific verification. Sources: claude:cl-cmek.
  • private_networking Is private connectivity or IP restriction available? [partial]: Enterprise IP CIDR allowlisting is enabled through support; externally shared artifacts can remain outside it. Private Link/VPN-only service endpoints were not established. Sources: claude:cl-ip.
  • tenant_isolation How are customers separated in shared SaaS? [supported]: DPA Schedule 2 H specifies logical separation of customer data and network segmentation; no independent isolation test was performed. Sources: claude:cl-dpa.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-dpa, claude:cl-cmek, claude:cl-ip.

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.

Checked ; 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.

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Personnel confidentiality and controlled safety review are documented; a qualified professional-secrecy contract or add-on remains unverified.

Availability: unknown · Delivery: unknown
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=German §203 StGB and Swiss Art.321 StGB use cases; existing hosting, support and provider-location exceptions still apply.; os=not specified.

Limitations

  • General confidentiality, a DPA and no-training commitments do not establish a professional-secrecy undertaking. No vendor/sales contact or agreement signing was performed.
  • No legal compliance verdict; unknown does not mean the offering is unavailable.
  • secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? Unverified after checking Commercial Terms E, DPA B.7/C.2 and technical measures, Trust Center, Covered Model access/retention rules and official searches for professional secrecy/§203/Art.321. No qualified staff undertaking, corresponding subprocessor undertaking chain, public contract template or dedicated plan/add-on was retrieved.
  • subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: Does the undertaking extend to its sub-processors, and is that documented? Unverified after checking Commercial Terms E, DPA B.7/C.2 and technical measures, Trust Center, Covered Model access/retention rules and official searches for professional secrecy/§203/Art.321. No qualified staff undertaking, corresponding subprocessor undertaking chain, public contract template or dedicated plan/add-on was retrieved.
  • secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: Is it a dedicated offering or add-on, and on which plan? Unverified after checking Commercial Terms E, DPA B.7/C.2 and technical measures, Trust Center, Covered Model access/retention rules and official searches for professional secrecy/§203/Art.321. No qualified staff undertaking, corresponding subprocessor undertaking chain, public contract template or dedicated plan/add-on was retrieved.
  • content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Commercial Terms E and DPA B.7/Schedule2 constrain authorized personnel and subprocessor processing; Covered Model retained data can be accessed by approved safety reviewers through a logged controlled path. A complete subprocessor plain-text access matrix and §203/Art.321-specific restriction were not verified. Sources: claude:cl-terms, claude:cl-dpa, claude:cl-covered-review.
  • secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? Unverified after checking Commercial Terms E, DPA B.7/C.2 and technical measures, Trust Center, Covered Model access/retention rules and official searches for professional secrecy/§203/Art.321. No qualified staff undertaking, corresponding subprocessor undertaking chain, public contract template or dedicated plan/add-on was retrieved.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-terms, claude:cl-dpa, claude:cl-covered-review.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Team bundles usage while current Enterprise separates seat access from all token usage.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Read each atomic answer for its plan, access and feature limits.
  • pricing_unit What is the pricing unit? [supported]: Team uses Standard/Premium seats with included limits; usage-based Enterprise uses access seats plus separate API-rate token consumption. Legacy Enterprise has different billing. Sources: claude:cl-pricing, claude:cl-enterprise.
  • list_prices What are list prices per plan, with date and currency? [supported]: Retrieved 2026-10-21: Team Standard USD 20/month annual or USD 25 monthly; Premium USD 100 annual or USD 125 monthly. Enterprise USD 20/seat/month billed annually, before usage/tax. Sources: claude:cl-pricing, claude:cl-enterprise.
  • included_usage What usage is included? [partial]: Team Premium advertises five times Standard usage; exact reproducible message/token quotas were not established. Current Enterprise includes no token usage. Sources: claude:cl-pricing, claude:cl-enterprise.
  • add_ons Which features cost extra? [partial]: Enterprise model usage costs extra; applicable US-only inference adds 10%. Third-party services/credits and optional-service charges are not fully priced. Sources: claude:cl-enterprise, claude:cl-us-only.
  • overage What do usage beyond limits and premium models cost? [partial]: Enterprise bills all usage at current API rates; Sonnet 5.5 list rate is USD 2/M input and USD 10/M output. Team/legacy overage and each tool surcharge were not exhaustively priced. Sources: claude:cl-enterprise, claude:cl-api-prices.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-pricing, claude:cl-enterprise, claude:cl-us-only, claude:cl-api-prices.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Enterprise list-cost scenarios separate the USD 240 annual access seat floor from modeled Sonnet usage and unpriced services.

Availability: generally-available · Delivery: unknown
Scope: surfaces=Claude Team and Enterprise web workspaces; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Current usage-based Enterprise; standard global inference; admin-configured Sonnet 5.5 low-effort chat scenario; add_ons=All token usage at API list rates, Third-party services and implementation unpriced; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • All figures exclude VAT and invented discounts. Team is capped at 150 seats and is not extrapolated to these sizes. Annual Enterprise access commitment is separate from consumption.
  • cost_200 Year-one cost at 200 users? [partial]: From USD 57,504.00 / EUR 51,274.19 / CHF 47,361.97 + unknown services under the disclosed Sonnet 5.5 low-effort chat workload: USD 48,000.00 access seats + USD 9,504.00 modeled tokens. The seat-only floor is USD 48,000.00 / EUR 42,799.82 / CHF 39,534.20. This is modeled list cost, not observed usage or a quote. Sources: claude:cl-enterprise, claude:cl-api-prices, claude:cl-consumption, claude:fx-20261020.
  • cost_1000 Year-one cost at 1,000 users? [partial]: From USD 287,520.00 / EUR 256,370.93 / CHF 236,809.83 + unknown services under the disclosed Sonnet 5.5 low-effort chat workload: USD 240,000.00 access seats + USD 47,520.00 modeled tokens. The seat-only floor is USD 240,000.00 / EUR 213,999.11 / CHF 197,670.98. This is modeled list cost, not observed usage or a quote. Sources: claude:cl-enterprise, claude:cl-api-prices, claude:cl-consumption, claude:fx-20261020.
  • cost_5000 Year-one cost at 5,000 users? [partial]: From USD 1,437,600.00 / EUR 1,281,854.66 / CHF 1,184,049.15 + unknown services under the disclosed Sonnet 5.5 low-effort chat workload: USD 1,200,000.00 access seats + USD 237,600.00 modeled tokens. The seat-only floor is USD 1,200,000.00 / EUR 1,069,995.54 / CHF 988,354.88. This is modeled list cost, not observed usage or a quote. Sources: claude:cl-enterprise, claude:cl-api-prices, claude:cl-consumption, claude:fx-20261020.
  • variable_share Which part depends on usage? [supported]: ALM-14 shared cost assumptions v1.4, 2026-10-21: 12 months, 60% light 100/30% regular 400/10% power 1500 messages monthly = 330/user/month; 3000 input+600 billable output tokens/message incl retrieval/thinking. At Sonnet 5.5 USD 2/M input+USD 10/M output, 11.88M input+2.376M output/year costs USD 47.52/user; access USD 240 => modeled USD 287.52/user/year. Sonnet low effort is the scenario choice, with an admin-configurable default, based on the consumption guide; not a universal fixed default. Sources: claude:cl-consumption, claude:cl-api-prices, claude:cl-enterprise.
  • unknown_parts Which costs could not be priced? [partial]: Unpriced: implementation, onboarding/support add-ons, third-party subscriptions and workflow-specific extra tool/context/repeated-step tokens. Scenario excludes US-only 1.1x premium, tax, discounts, cache/batch benefits and agent workloads beyond the fixed token allowance; these require separate pricing. EUR=USD/1.1215; CHF=EUR*0.9237, ECB 2026-10-20. Sources: claude:cl-enterprise, claude:cl-us-only, claude:cl-api-prices, claude:fx-20261020.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-enterprise, claude:cl-api-prices, claude:cl-consumption, claude:fx-20261020, claude:cl-us-only.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Commercial self-service purchase is documented; free consumer access is not a scoped Enterprise trial.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: self_serve_trial, trial_scope.
  • Read each atomic answer for its plan, access and feature limits.
  • free_tier Is there a free tier for business use? [partial]: Claude Free is a separate consumer plan; no free Team/Enterprise organization entitlement was established. Sources: claude:cl-pricing.
  • self_serve_trial Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? Unverified after checking pricing and Enterprise acquisition guides; no self-serve business trial duration, card rule or trial identity/compliance/connector inclusion confirmed.
  • trial_scope Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? Unverified after checking pricing and Enterprise acquisition guides; no self-serve business trial duration, card rule or trial identity/compliance/connector inclusion confirmed.
  • sales_gate Does meaningful evaluation require sales contact? [supported]: Team can be bought self-serve. Enterprise self-serve starts at 20 seats; sales-assisted Enterprise starts at 50. No purchase or sales contact was performed. Sources: claude:cl-enterprise.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-pricing, claude:cl-enterprise.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Seat prices are public, with plan caps, annual Enterprise commitment and variable usage.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Read each atomic answer for its plan, access and feature limits.
  • minimum_commitment What seat or spend minimum applies? [supported]: Team: 2-150 seats. Current Enterprise self-serve: 20-seat minimum; sales-assisted: 50. Sources: claude:cl-pricing, claude:cl-enterprise.
  • contract_length What contract lengths are offered? [supported]: Team lists monthly and annual billing; Enterprise access seats are annual. Consumption is additional under the purchase route. Sources: claude:cl-pricing, claude:cl-enterprise.
  • cancellation How can the contract be cancelled or reduced? [partial]: General Terms I.2 permit customer termination with notice and vendor convenience termination with30-day notice; annual seat refunds, reductions and renewal cancellation depend on plan/order and were not verified. Sources: claude:cl-terms.
  • local_invoicing Can it be invoiced in CHF or EUR from a European entity? [partial]: Enterprise self-serve bills USD by credit/ACH; sales-assisted supports multicurrency/invoicing. Irish contracting is stated for Swiss/EEA customers, but a CHF/EUR invoice tariff was not verified. Sources: claude:cl-enterprise, claude:cl-terms.
  • transparency_class Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified: public seat/API rates and minimums, but actual consumption, third-party services, Enterprise optional charges and local invoice terms require more detail. Sources: claude:cl-enterprise, claude:cl-api-prices.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-pricing, claude:cl-enterprise, claude:cl-terms, claude:cl-api-prices.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Commercial service rights are public; a complete component-source licence inventory was not established.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: branding_restrictions, enterprise_features_closed.
  • Read each atomic answer for its plan, access and feature limits.
  • licence_type Which licence applies to each component? [partial]: Commercial Terms grant service use and allocate customer input/output rights; this does not establish an OSI licence for the hosted platform, clients or connector code. Sources: claude:cl-terms.
  • branding_restrictions Do licence terms restrict branding or user counts? [unknown]: Do licence terms restrict branding or user counts? Unverified after checking Commercial Terms and public Claude Code issue repository; component revisions, client/server/connector source licences, branding restrictions and separate enterprise-edition source status not verified.
  • enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unverified after checking Commercial Terms and public Claude Code issue repository; component revisions, client/server/connector source licences, branding restrictions and separate enterprise-edition source status not verified.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-terms.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Team/Enterprise exports provide conversations but do not prove portable assistants and knowledge.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • chat_export: Team/Enterprise Primary Owners export organization conversation/user data, excluding deleted items. Members can export their own chats if enabled; uploaded-file contents are excluded.
  • assistant_export: Can assistants and prompts be exported in a reusable format? Unverified after checking organization/member export and Compliance API docs; no export fixture, reusable assistant/prompts or complete knowledge-base/source-file package verified. Search on 2026-10-26: https://support.claude.com/en/articles/13346720-export-your-organization-s-data, https://support.claude.com/en/articles/9450526-export-your-claude-data, https://support.claude.com/en/articles/13015708-access-the-compliance-api. No additional scoped evidence established this answer.
  • knowledge_export: The organization export guide covers conversation/user data and excludes generated Office/PDF files; members’ personal exports exclude uploaded-file contents. A complete reusable project/knowledge-source archive was not established and no export fixture was run.
  • export_format: Documented exports and Compliance API support structured access; the complete archive schema/file manifest was not downloaded or inspected.
  • chat_export Can admins export all chats? [partial]: Team/Enterprise Primary Owners export organization conversation/user data, excluding deleted items. Members can export their own chats if enabled; uploaded-file contents are excluded. Sources: claude:cl-export-org-20261026, claude:cl-export-user-20261026.
  • assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unverified after checking organization/member export and Compliance API docs; no export fixture, reusable assistant/prompts or complete knowledge-base/source-file package verified. Search on 2026-10-26: https://support.claude.com/en/articles/13346720-export-your-organization-s-data, https://support.claude.com/en/articles/9450526-export-your-claude-data, https://support.claude.com/en/articles/13015708-access-the-compliance-api. No additional scoped evidence established this answer.
  • knowledge_export Can knowledge bases and their sources be exported? [partial]: The organization export guide covers conversation/user data and excludes generated Office/PDF files; members’ personal exports exclude uploaded-file contents. A complete reusable project/knowledge-source archive was not established and no export fixture was run. Sources: claude:cl-export-org-20261026, claude:cl-export-user-20261026.
  • export_format Are formats documented and machine-readable? [partial]: Documented exports and Compliance API support structured access; the complete archive schema/file manifest was not downloaded or inspected. Sources: claude:cl-export-org-20261026, claude:cl-compliance-20261026.
  • post_termination_window How long can data be retrieved after termination? [supported]: DPA H requires a return request within 30 days after expiry/termination, with deletion obligations and legal/dispute/harmful-use exceptions. Sources: claude:cl-dpa-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: claude:cl-export-org-20261026, claude:cl-export-user-20261026, claude:cl-compliance-20261026, claude:cl-dpa-20261026.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Public support/status channels exist; local-language commitments and contractual SLA remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • support_channels: Help Center support is available; Enterprise self-serve and sales-assisted support/CSM arrangements differ. Exact response times/hours were not established.
  • support_languages: Is support available in German, French or Italian? Unverified after checking Enterprise support comparison, official Help Center, status history and Commercial Terms; DE/FR/IT support guarantees, DACH/Swiss staffing, response targets and uptime/credit SLA not verified. Search on 2026-10-26: https://support.claude.com/en/articles/9797531-what-is-the-enterprise-plan, https://status.claude.com/, https://claude.com/pricing. No additional scoped evidence established this answer.
  • regional_presence: Anthropic’s November 2025 company announcement identifies an existing Zurich office and planned Munich expansion. Current staffing, Swiss contracting terms and local-language support guarantees were not established.
  • uptime_sla: Is there an uptime SLA with credits? Unverified after checking Enterprise support comparison, official Help Center, status history and Commercial Terms; DE/FR/IT support guarantees, DACH/Swiss staffing, response targets and uptime/credit SLA not verified. Search on 2026-10-26: https://support.claude.com/en/articles/9797531-what-is-the-enterprise-plan, https://status.claude.com/, https://claude.com/pricing. No additional scoped evidence established this answer.
  • support_channels Which support channels are available on each plan? [partial]: Help Center support is available; Enterprise self-serve and sales-assisted support/CSM arrangements differ. Exact response times/hours were not established. Sources: claude:cl-enterprise-20261026.
  • support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unverified after checking Enterprise support comparison, official Help Center, status history and Commercial Terms; DE/FR/IT support guarantees, DACH/Swiss staffing, response targets and uptime/credit SLA not verified. Search on 2026-10-26: https://support.claude.com/en/articles/9797531-what-is-the-enterprise-plan, https://status.claude.com/, https://claude.com/pricing. No additional scoped evidence established this answer.
  • regional_presence Is there a DACH or Swiss entity, team or partner? [partial]: Anthropic’s November 2025 company announcement identifies an existing Zurich office and planned Munich expansion. Current staffing, Swiss contracting terms and local-language support guarantees were not established. Sources: claude:claude:regional-presence-20261026.
  • uptime_sla Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? Unverified after checking Enterprise support comparison, official Help Center, status history and Commercial Terms; DE/FR/IT support guarantees, DACH/Swiss staffing, response targets and uptime/credit SLA not verified. Search on 2026-10-26: https://support.claude.com/en/articles/9797531-what-is-the-enterprise-plan, https://status.claude.com/, https://claude.com/pricing. No additional scoped evidence established this answer.
  • status_page Is there a public status page with history? [supported]: status.claude.com publishes component health and incident history; it is not a contractual reliability score. Sources: claude:cl-status-20261026.

Checked ; agent cross-checked 2026-10-26; check again by 2026-12-20. Sources: claude:cl-enterprise-20261026, claude:cl-status-20261026, claude:claude:regional-presence-20261026.

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

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.

Claude Team / Enterprise

Agent cross-checked Support: partial

Academy tutorials and use-case material are public; commercial service entitlements need clarification.

Availability: generally-available · Delivery: native
Scope: surfaces=Claude Team and Enterprise web workspaces, Claude desktop and mobile clients, Claude connectors and remote MCP integrations, Claude for Microsoft 365 official add-ins, Claude Cowork cloud and desktop task execution; version=Continuously updated commercial service, retrieved 2026-10-21; plan=Claude Team Standard/Premium versus current usage-based Enterprise; legacy Enterprise only when explicitly named; add_ons=Enterprise token usage at API rates, Optional US-only inference surcharge, External provider/app subscriptions and Office deployment approval where applicable, CMEK and compliance only on eligible Enterprise configurations; deployment_mode=multi-tenant-saas; region=Commercial supported regions; default global inference and US storage where documented; no EU/Swiss-only residency assumption; os=not specified.

Limitations

  • Unverified parts: onboarding_service, adoption_programme, service_cost.
  • Read each atomic answer for its plan, access and feature limits.
  • onboarding_service Is guided onboarding included? [unknown]: Is guided onboarding included? Unverified after checking Academy, pricing and Enterprise comparison; included guided onboarding, champion programme, paid professional-services scope and charges not established.
  • user_training Is end-user training offered, in which languages? [partial]: Claude Academy provides written/video training for chat, Cowork, Office, connectors and skills; German/French/Italian delivery was not established. Sources: claude:cl-academy.
  • use_case_library Are role-based use cases and templates provided? [partial]: Academy has workflow/tutorial examples and Office use cases; the library was not exhaustively mapped to organizational roles. Sources: claude:cl-academy.
  • adoption_programme Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Unverified after checking Academy, pricing and Enterprise comparison; included guided onboarding, champion programme, paid professional-services scope and charges not established.
  • service_cost Which services cost extra? [unknown]: Which services cost extra? Unverified after checking Academy, pricing and Enterprise comparison; included guided onboarding, champion programme, paid professional-services scope and charges not established.

Checked ; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: claude:cl-academy.

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

Sources

  1. Claude Fable models on your plan claude:claude:fable-plan-20261026

    Fable 5/5.1 are available on paid plans. Team/legacy Enterprise Premium include a capped share of weekly usage; Standard uses paid usage credits. Current usage-based Enterprise bills at API rates. Organization model access can restrict availability.

    How Fable models work on each plan and model-picker access; HTTP 200, body SHA256 c7e39ae19952ae2186de8c95a8034bd16a43b7da9e5b6750eca0b7c30614456a · documented · Source date 2026-09-02 · Retrieved 2026-10-26

  2. Claude Fable automatic model switching claude:claude:transparent-fallback-20261026

    Hosted Fable safety fallbacks rerun requests on an Opus model with a visible switch notice and response model label. Users can disable automatic switching. This is a safety fallback, not general task-based multi-provider routing.

    What happens after a fallback, settings and where switching applies; HTTP 200, body SHA256 98a2769ab04b54a170b3034afde3b042c016f76ccd332e98c4065288a60ea846 · documented · Source date not stated · Retrieved 2026-10-26

  3. Change the model, effort, and thinking settings claude:cl-model-menu-r2-20261026

    The chat-selector guide names model families and effort controls but does not provide a complete Team seat-tier or per-product entitlement matrix.

    Chat selector; supported effort models; Enterprise restrictions; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 74026587f919fac61d5fc3f4747ea1c889b2d3b2b6b2ee895dfbcc2dfae25cae on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  4. Context windows on paid Claude plans claude:cl-context-plans-r2-20261026

    The paid-plan guide distinguishes Chat and Cowork context/model tables; it does not guarantee every model on each Team seat tier or Office add-in.

    Paid-plan scope; separate Chat and Cowork tables; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 6f8fa356708c3a887106e33876dea65b71a3a9dae2ec09600ef035e14cb448e4 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  5. Upload files to Claude claude:cl-upload-r2-20261026

    The attachment guide specifies500 MB chat uploads,30 MB project files, and separate PDF visual/text behavior; these are not universal tool-path limits.

    Chat attachments versus project Files; PDF handling; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 640974fd8725ee528375e7fca7fe66265f94a30fb0c82071022d3da529b437ed on 2026-10-26 · documented · Source date 2026-07-23 · Retrieved 2026-10-26

  6. Claude pricing claude:cl-pricing-20261026

    Team is listed for 2-150 seats with Standard/Premium pricing; current Enterprise lists USD 20/seat/month annual access plus usage and a 20-seat self-serve minimum.

    Team/Enterprise cards; commercial comparison; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 9dac8ef940d7d07738f28ea203879b59cd98dfefd0bef624a91b361049a23a9f on 2026-10-26 · vendor-claimed · Source date not stated · Retrieved 2026-10-26

  7. Manage model access for your organization claude:cl-model-control-20261026

    Enterprise controls model/effort access by organization and custom role, while Haiku cannot be disabled and coverage has named exceptions.

    Organization and custom-role ceilings; Haiku exception; coverage; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 449e547e02b145fe3878d3591a80eca230ddff996580d601b38f007b78aba179 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

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

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

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

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

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

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

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

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

  16. Claude release notes claude:cl-release

    Dated notes distinguish current models, cloud/unified Cowork rollout, memory defaults and connector changes.

    Model launches; memory; Office/connector changes; Cowork transition · documented · Source date not stated · Retrieved 2026-10-21

  17. Claude Haiku 4.5 is leaving the model selector claude:cl-haiku-notice

    The dated consumer Haiku retirement excludes Team/Enterprise, so it does not prove removal from their model catalogue.

    October 15 notice; October 29 removal; Team/Enterprise exceptions · documented · Source date not stated · Retrieved 2026-10-21

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

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

  20. Claude for Microsoft 365 claude:cl-office

    Claude advertises native Excel/PowerPoint/Word add-ins, Outlook beta and optional Foundry/Bedrock/Gemini Enterprise Agent Platform credentials.

    App capabilities; GA/beta; cloud credentials; review controls · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  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

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

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

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

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

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

  27. What is the Enterprise plan? claude:cl-enterprise

    Current Enterprise has no included tokens, bills all usage at API rates and differs from legacy seat-based arrangements.

    Pricing; self-serve versus sales-assisted; legacy sections · documented · Source date 2026-09-01 · Retrieved 2026-10-21

  28. Manage model access for your organization claude:cl-model-control-r2

    Enterprise model and effort access uses organization ceilings/custom roles; Haiku cannot be disabled and product/version limits apply.

    Enterprise eligibility; role ceilings; Haiku; fallback/coverage · documented · Source date not stated · Retrieved 2026-10-21

  29. Set a default model for your organization claude:cl-default-r2

    Enterprise defaults are distinct from the beta forced-start switch, which preserves existing chat-project choices and permits in-chat changes.

    Ordinary defaults; Always start beta; projects and product fallback · documented · Source date not stated · Retrieved 2026-10-21

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

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

  32. Retrieval augmented generation for projects claude:cl-rag

    Paid projects automatically switch to retrieval when knowledge approaches context limits and show a RAG indicator.

    Activation; search tool; context indicator · documented · Source date not stated · Retrieved 2026-10-21

  33. Upload files to Claude claude:cl-upload-r2

    The attachment guide specifies500 MB chat uploads,30 MB project files, and separate PDF visual/text behavior; these are not universal tool-path limits.

    Chat attachments versus project Files; PDF handling · documented · Source date 2026-07-23 · Retrieved 2026-10-21

  34. Create and edit files with Claude claude:cl-code-files-r2

    Chat code/file tools create Office/PDF output and document a30 MB upload/download path; the same page has inconsistent Team egress defaults.

    Availability; computing/file-tool limits; file output; network sections · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  38. Upload files to Claude claude:cl-upload

    The page distinguishes 500 MB chat uploads, 30 MB project files and PDF visual processing up to 100 pages.

    Formats; chat/project limits; visual PDF processing · documented · Source date 2026-07-23 · Retrieved 2026-10-21

  39. What are projects? claude:cl-projects

    Projects persist selected knowledge/instructions and provide organization sharing with view/edit permissions.

    Knowledge; instructions; Team/Enterprise collaboration · documented · Source date 2026-07-23 · Retrieved 2026-10-21

  40. Manage groups and group spend limits on Enterprise plans claude:cl-groups

    Enterprise groups support roles and shared resources, per-user limits and optional shared monthly budgets in beta.

    Group sharing; SCIM; role controls; budgets · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  44. Enterprise-managed authorization for MCP connectors claude:claude:atlassian-enterprise-20261026

    Claude Enterprise documents generally available organization-managed authorization through Okta for named MCP providers including Atlassian. Its Atlassian section names Jira, Confluence and Teamwork Graph.

    August 24 GA update and Atlassian Rovo MCP description; HTTP 200, body SHA256 5d973cd85982883fc28f409f6919e829a1e3791223634ca167e12524c411284e · documented · Source date 2026-08-24 · Retrieved 2026-10-26

  45. Get started with custom connectors using remote MCP claude:cl-mcp-20261026

    Remote MCP originates from Anthropic cloud, can use per-user OAuth or shared credentials, and differs from Desktop-local MCP.

    Network route; owner publication; OAuth/request headers; local distinction; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 e6307ff6f907b387075c5f8db3a45fae8cf8ea9eb15fd576b44f3368e1c5ed43 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  46. Claude release notes claude:cl-release-20261026

    Dated notes distinguish current models, cloud/unified Cowork rollout, memory defaults and connector changes.

    Model launches; memory; Office/connector changes; Cowork transition; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 07f9dcfff3c0fc1f7a6060ad0b718558075286175f3b4e1b13c665d79cab3616 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  47. What is the Enterprise plan? claude:cl-enterprise-20261026

    Current Enterprise has no included tokens, bills all usage at API rates and differs from legacy seat-based arrangements.

    Pricing; self-serve versus sales-assisted; legacy sections; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 de2b461205d4426c558e88750f5be23f7d495804c407827fc5695ecd5e1a20ee on 2026-10-26 · documented · Source date 2026-09-01 · Retrieved 2026-10-26

  48. Microsoft 365 connector security guide claude:cl-m365-20261026

    The Anthropic-hosted Microsoft Graph proxy retrieves on demand without file-content caching and has separately enabled write tools and delegated permissions.

    On-demand proxy; delegated permissions; consent; write controls; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 8965fd2ee1dbdd7b494b834a1cbae1cd4194bf096abd2d916244178108738d3f on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  49. Use Google Workspace connectors claude:cl-google-20261026

    Google connectors retrieve user-authorized data, sync referenced Google Docs and support live editing with separate app controls.

    Sources; private project sync; live Docs/Sheets/Slides; authorization; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 b61eb14f3e2efb4ab2a9cc441eb6beb363b5514d3c55e6f9dc8cd2565d48d135 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

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

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

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

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

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

  55. Microsoft 365 connector security guide claude:cl-m365

    The Anthropic-hosted Microsoft Graph proxy retrieves on demand without file-content caching and has separately enabled write tools and delegated permissions.

    On-demand proxy; delegated permissions; consent; write controls · documented · Source date not stated · Retrieved 2026-10-21

  56. Connect to Microsoft 365 claude:cl-m365-user

    Microsoft 365 connects SharePoint/OneDrive/Outlook/Teams, excludes Sites.Selected allowlisting and OneNote reads, and requires organizational consent.

    Setup; supported content; site restrictions; permissions · documented · Source date not stated · Retrieved 2026-10-21

  57. Use Google Workspace connectors claude:cl-google

    Google connectors retrieve user-authorized data, sync referenced Google Docs and support live editing with separate app controls.

    Sources; private project sync; live Docs/Sheets/Slides; authorization · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

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

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

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

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

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

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

  70. Chat search and memory claude:cl-memory-r2

    Improved memory has Team/Enterprise owner controls and cloud-Cowork sharing; legacy Team lacks org controls and legacy memory is chat-only.

    Improved Settings>Memory versus legacy; owners; Cowork; exclusions · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  75. Claude Academy tutorials claude:cl-academy

    Academy publishes written/video guides for chat, connectors, agents, Office work and skills.

    Chat; Cowork; Office; AI fluency guides · vendor-claimed · Source date not stated · Retrieved 2026-10-21

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

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

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

  79. Claude pricing claude:cl-pricing

    Team is listed for 2-150 seats with Standard/Premium pricing; current Enterprise lists USD 20/seat/month annual access plus usage and a 20-seat self-serve minimum.

    Team/Enterprise cards; commercial comparison · vendor-claimed · Source date not stated · Retrieved 2026-10-21

  80. Get started with custom connectors using remote MCP claude:cl-mcp

    Remote MCP originates from Anthropic cloud, can use per-user OAuth or shared credentials, and differs from Desktop-local MCP.

    Network route; owner publication; OAuth/request headers; local distinction · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  84. Enable and use Claude web search claude:claude:web-search-controls-20261026

    Team/Enterprise Owners first enable web search for the workspace, after which members use it in chat. Search answers include citations and source links. The article does not identify a universal search backend or query-processing region.

    Team/Enterprise workspace enablement and How web search works; HTTP 200, body SHA256 76f79d8a3eb4181b4e1028b23a4df9821c316008015fe0290feb4582d6b9a83d · documented · Source date not stated · Retrieved 2026-10-26

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

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

  87. Get started with Claude Cowork claude:cl-cowork

    Paid Cowork runs multi-step tasks with local access where permitted and cloud task persistence, with Team/Enterprise cloud availability in beta.

    Availability; cloud beta; task flow; tools; scheduling · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  92. Use Claude Cowork safely claude:claude:cowork-stop-20261026

    The paid-plan Cowork safety guide instructs users to monitor and stop a task when needed. It does not promise rollback of completed external actions or a guaranteed cancellation boundary.

    Paid-plan availability, monitoring tasks and stopping suspicious behavior; HTTP 200, body SHA256 363aa11b90d168d68950bcf4820d677b076c63c1f27598be7d17ef04c727da24 · documented · Source date not stated · Retrieved 2026-10-26

  93. Get started with Claude Cowork claude:cl-cowork-20261026

    Paid Cowork runs multi-step tasks with local access where permitted and cloud task persistence, with Team/Enterprise cloud availability in beta.

    Availability; cloud beta; task flow; tools; scheduling; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 0c2c6bcedbe79e9bc84268a92da091133ea4c9737d6790eb74583def73350c02 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  94. Access the Compliance API claude:cl-compliance

    Enterprise Compliance API exposes events, chats and file content with primary-owner activation and scoped organization keys.

    Eligibility; primary-owner activation; event/chat/file data · documented · Source date not stated · Retrieved 2026-10-21

  95. Claude Platform pricing claude:cl-api-prices

    Current public API prices include Sonnet 5.5 at USD 2/M input and USD 10/M output, while model choice, tokens and features change usage cost.

    Model pricing table; regional rates; tool token charges · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

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

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

  102. Export your Claude data claude:cl-export-user

    Organization members can export their own chats when enabled, without uploaded-file contents; exports are web/Desktop only.

    Team/Enterprise owner enablement; contents; 24-hour link · documented · Source date not stated · Retrieved 2026-10-21

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

  104. Use Claude in Google Docs, Sheets, and Slides claude:cl-google-addon

    A native Google Workspace sidebar beta supports Team/Enterprise, separate from connectors; edits require approval by default and extension data does not inherit organization retention.

    Beta eligibility; native extension; approvals; data retention · documented · Source date not stated · Retrieved 2026-10-21

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

  106. Can Claude produce images? claude:claude:image-generation-boundary-20261026

    The vendor explicitly says Claude does not generate photos or illustrations like image-generation tools. HTML/SVG diagrams, charts and interactive visuals are a separate beta web/desktop capability; uploaded-image analysis is also separate.

    Native image generation versus HTML/SVG custom visuals; HTTP 200, body SHA256 4d918af1acc08fe9d2c1ea21ae840029c1c9109acad12cb2eaeeb8b8daab4da9 · documented · Source date not stated · Retrieved 2026-10-26

  107. Artifacts admin guide for Team and Enterprise plans claude:cl-artifacts-admin

    Admins control artifact templates, while standalone Claude Design closes 2026-12-14 and in-Claude design continues.

    Templates; October defaults; standalone Design closure; data handling · documented · Source date not stated · Retrieved 2026-10-21

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

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

  110. Claude display-language settings claude:claude:display-languages-20261026

    Claude documents English, French, German, Italian, Hindi, Indonesian, Japanese, Korean, Brazilian Portuguese and Latin American/Spain Spanish interfaces on web and desktop. Voice language is a separate setting.

    Supported Languages and On Web and Desktop; HTTP 200, body SHA256 9a6fd87cbba7b558c9972e24b7bcd94249d6cb04003eea26541794f93dbae61b · documented · Source date not stated · Retrieved 2026-10-26

  111. Set up single sign-on claude:cl-sso

    SSO and JIT are available to Team/Enterprise with owner configuration and verified domains.

    Team/Enterprise eligibility; IdP; owner roles; provisioning · documented · Source date not stated · Retrieved 2026-10-21

  112. Set up JIT or SCIM provisioning claude:cl-provision

    Team supports JIT but not SCIM; Enterprise SCIM synchronizes membership and role/seat mappings with documented removal differences.

    Plan eligibility; provisioning matrix; group mapping · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  117. Manage model access for your organization claude:cl-model-control

    Enterprise controls model/effort access by organization and custom role, while Haiku cannot be disabled and coverage has named exceptions.

    Organization and custom-role ceilings; Haiku exception; coverage · documented · Source date not stated · Retrieved 2026-10-21

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

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

  120. View usage analytics for Team and Enterprise plans claude:cl-analytics

    Admins have plan-scoped adoption and spend views, including per-user/model CSVs and separate seat-based overage reporting.

    Roles; product/model/user data; CSV exports · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  125. Access audit logs claude:cl-audit

    Enterprise audit export covers 180 days of metadata, excludes prompt content and has a CMEK export limitation with a Compliance API alternative.

    Enterprise export; 180 days; fields; content exclusion; CMEK · documented · Source date 2026-06-15 · Retrieved 2026-10-21

  126. Get started with Claude Compliance API integrations claude:cl-compliance-partners

    The documentation lists partner compliance/eDiscovery/monitoring integrations; each integration needs separate scope and behavior verification.

    Security, archive and eDiscovery partners · documented · Source date not stated · Retrieved 2026-10-21

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

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

  129. Get started with Claude Compliance API integrations claude:cl-compliance-partners-r2

    Enterprise Compliance integrations are Primary-Owner-enabled; Claude Platform has a separate scope and this is not a Team entitlement or proof of inline redaction.

    Eligibility and Enterprise activation; monitoring/DLP partners · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  133. Where are your servers located? Do you host your models on EU servers? claude:cl-servers

    Commercial documentation says data is stored in the US, inference can route globally and internal support/safety processes can occur in affiliate countries.

    Commercial global routing; US storage; internal processing · documented · Source date 2026-06-15 · Retrieved 2026-10-21

  134. Enable US-only inference for your organization claude:cl-us-only

    Usage-based Enterprise offers US-only inference at 1.1 times standard rates for applicable newer models, excluding storage and third-party processing.

    Eligibility; billing; exclusions · documented · Source date 2026-06-15 · Retrieved 2026-10-21

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

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

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

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

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

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

  141. Data Processing Addendum claude:cl-dpa

    The DPA covers confidential processing, subprocessors, audit access, security and post-termination return/deletion with transfer schedules.

    B.7; C; E/F; H; SCC/Swiss schedules · documented · Source date 2025-02-24 · Retrieved 2026-10-21

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

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

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

  145. Commercial Terms of Service claude:cl-terms

    Commercial terms prohibit model training on customer content, define EEA/Swiss/UK Irish contracting and provide confidentiality and commercial-use restrictions.

    Customer content; confidentiality; contracting party; fees · documented · Source date 2025-06-17 · Retrieved 2026-10-21

  146. Is my data used for model training? claude:cl-training

    Commercial content is not used for training by default; explicit feedback can be used and retained up to five years, with owner controls.

    Commercial default; feedback; disable feedback · documented · Source date 2026-08-18 · Retrieved 2026-10-21

  147. Covered Models claude:cl-covered-r2

    Covered Models have default minimum retention, with a separate limited agreement-based Fable ZDR exception for eligible internal-business applications.

    Default retention; temporary eligible Fable exception; EFS · documented · Source date 2026-09-01 · Retrieved 2026-10-21

  148. Data retention practices for Covered Models claude:cl-covered-routes-r2

    The updated guide excludes notified exception customers from the standard ZDR-transition instructions and says hosted Enterprise Chat/Cowork already use standard retention.

    ZDR configurations; eligible notices; cloud-provider storage; hosted Chat/Cowork · documented · Source date 2026-09-05 · Retrieved 2026-10-21

  149. How long do you store organization data? claude:cl-retention-r2

    Commercial saved-chat retention differs from API retention; backend deletion normally takes up to 30 days and safety/legal/feedback exceptions remain.

    Saved commercial chats; deletion; safety and feedback exceptions · documented · Source date 2026-07-01 · Retrieved 2026-10-21

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

  151. Configure custom data retention controls for Enterprise plans claude:cl-retention-admin-r2

    Current English guidance schedules over-age content on save and deletes through a daily background process, preserving project precedence and feature exclusions.

    Project precedence; daily deletion process; role and feature limits · documented · Source date not stated · Retrieved 2026-10-21

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

  153. Government requests for user information claude:cl-gov

    Anthropic documents valid-process review, rejection of deficient requests, notice exceptions and generally directing enterprise requests to the customer.

    Valid process; challenge; customer notice; exceptions · documented · Source date 2026-03-16 · Retrieved 2026-10-21

  154. Anthropic subprocessor list access route claude:cl-trust-route

    The public list URL redirects to a trust portal that returned no extractable entries in this research; countries and revision remain unverified.

    DPA Schedule 4 link; redirect to trust.anthropic.com/subprocessors · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

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

  159. Introducing Claude Fable 5.1 and Claude Mythos 5.1 claude:cl-ai-act

    The provider announcement describes transparency-code signing, watermarking for later models and a restricted-preview detection API; this is not a deployer compliance verdict.

    Compliance with the EU AI Act · vendor-claimed · Source date not stated · Retrieved 2026-10-21

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

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

  162. Anthropic commercial compliance credentials claude:claude:commercial-certifications-20261026

    The commercial privacy page claims ISO 27001:2022, ISO/IEC 42001:2023 and SOC 2 Type I/II. Copies are request-gated; issuer, certificate/report scope, period and validity were not inspected.

    Commercial-products applicability and credential list; HTTP 200, body SHA256 d44ecb66e9cf7636e39a9b9da3c61cc6513dfca890e68fcdaa1bc7051f310335 · vendor-claimed · Source date 2026-03-16 · Retrieved 2026-10-26

  163. Data Processing Addendum claude:cl-dpa-20261026

    The DPA covers confidential processing, subprocessors, audit access, security and post-termination return/deletion with transfer schedules.

    B.7; C; E/F; H; SCC/Swiss schedules; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 c11e0d2d380f6155e900d4357d2a154e85cd0b38db427ca11e5048e02c375218 on 2026-10-26 · documented · Source date 2025-02-24 · Retrieved 2026-10-26

  164. What are customer-managed encryption keys? claude:cl-cmek

    Eligible Enterprise organizations can use customer AWS/GCP/Azure master keys for certain chats, projects and files, with feature limitations.

    Eligibility; customer KMS; scope · documented · Source date 2026-06-15 · Retrieved 2026-10-21

  165. Restrict access to Claude with IP allowlisting claude:cl-ip

    Enterprise supports source-IP CIDR restrictions configured through support; externally shared artifacts can remain outside that restriction.

    Enterprise eligibility; coverage; external sharing exception · documented · Source date not stated · Retrieved 2026-10-21

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

  167. Data retention practices for Covered Models claude:cl-covered-review

    Controlled reviewers may inspect safety-flagged retained data, with logged access; normal chat/Cowork already use standard retention.

    Human review; 30 days; affected ZDR configurations · documented · Source date 2026-09-05 · Retrieved 2026-10-21

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

  169. ECB euro reference historical rates claude:fx-20261020

    Directly retrieved ECB XML gives EUR 1 = USD 1.1215 = CHF 0.9237.

    Cube time=2026-10-20; USD and CHF · documented · Source date 2026-10-20 · Retrieved 2026-10-21

  170. Claude Enterprise consumption guide claude:cl-consumption

    The guide recommends Sonnet for routine/high-volume work and lower effort, while administrators configure the actual default and usage controls.

    Model/effort recommendations; defaults; limits · documented · Source date not stated · Retrieved 2026-10-21

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

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

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

  174. Export your organization data claude:cl-export-org-20261026

    Team/Enterprise Primary Owners can export organization conversation/user data; deleted content is excluded and links expire in 24 hours.

    Primary owner; scope; deleted items; link expiry; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 57af2f5ad8f732b35209851f2ba150423ac16e9d6a5c59718d6b0dd9ef672cae on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  175. Export your Claude data claude:cl-export-user-20261026

    Organization members can export their own chats when enabled, without uploaded-file contents; exports are web/Desktop only.

    Team/Enterprise owner enablement; contents; 24-hour link; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 5fe1cfd761095719efd95b5bc63049b1ceed6ddc3ed081373247053022153bfc on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  176. Access the Compliance API claude:cl-compliance-20261026

    Enterprise Compliance API exposes events, chats and file content with primary-owner activation and scoped organization keys.

    Eligibility; primary-owner activation; event/chat/file data; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 f641744bc193c80154bdb21a45e3c0527566f256728552432047c12936b79225 on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

  177. Anthropic European office announcement claude:claude:regional-presence-20261026

    The dated company announcement identifies an existing Zurich office and plans for Munich and Paris. It does not establish current staffing, a Swiss contracting entity or guaranteed local-language support.

    November 7, 2025 announcement, Zurich and planned Munich offices; HTTP 200, body SHA256 f73fca94192490d5216bd82ba233110af7093cfb2d08e3848eb79d3c055eea72 · vendor-claimed · Source date 2025-11-07 · Retrieved 2026-10-26

  178. Claude Status claude:cl-status-20261026

    Claude publishes separate hosted-product components and an incident history without providing a scoped contractual SLA in this page.

    Component health; incident history; retrieved without credentials with Python3 requests, HTTP 200, body SHA256 dabd165cf98d3b64e94051b42876be9d30ed1383af03d4c1a201674b97acb34e on 2026-10-26 · documented · Source date not stated · Retrieved 2026-10-26

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

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

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

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