--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/glean-vs-unique-ai/" data_url: "https://onaihq.com/compare/agents/glean-vs-unique-ai/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # Glean vs Unique AI > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 48 criteria with sourced findings for both products, including 48 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - Glean source checks: 2026-10-21 to 2026-10-26. - Unique AI source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/glean-vs-unique-ai/ - Machine-readable JSON: https://onaihq.com/compare/agents/glean-vs-unique-ai/data.json - Methodology: https://onaihq.com/compare/agents/methodology/ ## Models ### MOD-01: Model catalogue and providers Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Model Hub documents multi-provider choice and Auto routing. New department Auto policies require opt-in rollout as of October 21, with GA scheduled October 29. Availability: unknown Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=As of 2026-10-21: established model catalog plus opt-in new Auto-policy rollout; no tenant observed; plan=Core Suite + Model Hub Usage with Universal Model Key or Customer Key; new department policies only on Glean-key deployments with rollout enabled. Enterprise Flex billing is separate.; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - This criterion combines established model choice with an opt-in policy rollout; no blanket current GA status is asserted for the new policies. Enabled tenant models and per-request routing were not observed. - providers — Which model providers are available? [supported]: Model Hub lists OpenAI, Anthropic, Google, Amazon, Glean and open models through Baseten/Fireworks. Availability is conditional on enabled model and route. Sources: glean:glean:models, glean:glean:r2-core-entitlements. - current_models — Which current models are selectable on this plan? [partial]: Representative listed models include GPT-6.1 Sol, GPT-6 Astra/Sol/Luna, Claude Sonnet 5.5, Opus 5.5, Gemini 3.8 Flash, Waldo and GLM 5.3. Actual tenant-enabled selections were not observed. Sources: glean:glean:models, glean:glean:r2-core-entitlements. - user_choice — Can users pick the model per chat? [supported]: With Glean Universal Model Key users can select a specific enabled model or Auto. Customer Key uses configured defaults and has separate availability constraints. Sources: glean:glean:models, glean:glean:key-matrix, glean:glean:r2-core-entitlements. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Universal Model Key Auto routes among enabled models. The new department policies require Feature rollouts opt-in from October 15 as of this October 21 check; GA is scheduled October 29. Customer Key Auto uses admin defaults. Per-request selected-model visibility was not established. Sources: glean:glean:models, glean:glean:key-matrix, glean:glean:r2-core-entitlements, glean:glean:r3-october-rollout-migration. - multimodal_input — Which models accept images, audio or files? [partial]: Uploads, image generation and real-time voice are documented; supported input types vary by model and the key-feature matrix. A complete per-model input matrix was not verified. Sources: glean:glean:uploads, glean:glean:key-matrix, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:models, glean:glean:r2-core-entitlements, glean:glean:key-matrix, glean:glean:r3-october-rollout-migration, glean:glean:uploads #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform catalogue supports several providers, subject to tenant credentials, contracts and validation status. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number. - providers — Which model providers are available? [partial]: Catalogue includes Azure OpenAI/OpenAI, Anthropic, Google Gemini/Vertex, Together AI and xAI. Provider use must be agreed with each client; a catalogue row is not proof every tenant has it. Sources: unique-ai:unique-ai:models. - current_models — Which current models are selectable on this plan? [partial]: Release 2026.42, hosted 14 October, explicitly adds Azure GPT-6.1 Sol and Claude Opus/Sonnet 5.5 through Anthropic/Vertex. Availability overview also lists Gemini3.8 Flash; provider/tenant credentials and validation differ. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:models. - user_choice — Can users pick the model per chat? [partial]: Space admins set enabled models; release notes describe chat model switching and API per-message model selection under the same rules. Conduct choices depend on administrator configuration. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? Unknown. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number. - multimodal_input — Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42 ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated release notes and model deprecation guidance are public; comparable release-lag measurements remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex Model Hub; Customer Key deprecation policy distinguished from Universal Model Key; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? The release notes were checked, but provider general-release dates and scoped product-availability dates were not paired for the last three releases per provider. - changelog — Is there a dated public model changelog? [supported]: Public dated release notes include October 15, 2026 and model announcements. Sources: glean:glean:release, glean:glean:r2-core-entitlements. - deprecation_notice — How much notice is given before a model is removed? [partial]: For Customer Key Assistant, email notices are described at 60 and 15 days. The page also describes automatic migration for deprecated configurations; application to each removal needs confirmation. Sources: glean:glean:deprecation, glean:glean:r2-core-entitlements. - version_pinning — Can an admin keep an older model version? [partial]: Customer Key admins manage upgrades but deprecated models stop being usable. No indefinite version-pinning entitlement is established. Sources: glean:glean:deprecation, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:release, glean:glean:r2-core-entitlements, glean:glean:deprecation #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unique publishes dated model additions and retirement/migration notes; a complete provider-release lag series remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented. - changelog — Is there a dated public model changelog? [supported]: Availability overview has a dated Recent changes table through 13 October 2026, with provider retirement sources. Sources: unique-ai:unique-ai:models. - deprecation_notice — How much notice is given before a model is removed? [partial]: Dated 14 October release announces migrations ahead of o-series provider retirement on 19 November 2026. No guaranteed Unique contractual notice period is established. Sources: unique-ai:unique-ai:release42. - version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:release42 ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Customer Key supports named provider accounts; it has documented feature and cloud restrictions. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Customer Key + Glean-family Model Hub Usage; Enterprise Flex Customer Key/private-cloud discounts are separately contractual; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - own_api_keys — Can the customer use its own provider API keys? [supported]: Customer Key supports customer provider credentials including OpenAI and direct Anthropic keys. Sources: glean:glean:models, glean:glean:r2-core-entitlements. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Customer Key supports Azure OpenAI and named provider credentials. The supported-LLMs matrix permits Vertex only on GCP and Bedrock only on AWS; Configure LLMs separately says customer AWS can use Vertex, while its Vertex setup heading says GCP-only. AWS/Vertex eligibility is therefore unknown; no cross-cloud promise is made. Sources: glean:glean:models, glean:glean:key-matrix, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-core-entitlements. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [unknown]: Can an admin add any OpenAI-compatible endpoint? The supported-provider configuration and key matrix were checked; arbitrary OpenAI-compatible customer endpoints are not established. - byo_pricing — Does BYO change the licence price? [partial]: Core Suite Customer Key limits Glean Model Hub charges to Glean-family usage; customer provider use is paid directly. Enterprise Flex says seats/credits are discounted for own-key/private-cloud customers but publishes no numeric adjustment. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - byo_restrictions — Which features stop working with BYO? [supported]: The key matrix marks Meeting Notes and podcast artifacts unsupported on Customer Key. Text defaults share one provider; image models may differ. Memory depends on deployment readiness. Sources: glean:glean:key-matrix, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:models, glean:glean:r2-core-entitlements, glean:glean:key-matrix, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-flex-entitlements #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Operators can configure customer model endpoints and credentials through GraphQL. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public. - own_api_keys — Can the customer use its own provider API keys? [supported]: ExternalLanguageModel accepts provider API credentials stored encrypted as immutable write-only values; OAuth2 is also documented. Sources: unique-ai:unique-ai:customllm. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Custom Azure OpenAI deployment examples specify customer endpoint, deployment, API version and token. Compliance docs mention Bedrock; exact supported Bedrock/Vertex contract routes need deployment scoping. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [partial]: Documents self/cloud-hosted LXM endpoints and an Azure-compatible connection object. Universal support for any OpenAI-compatible endpoint is not guaranteed. Sources: unique-ai:unique-ai:customllm. - byo_pricing — Does BYO change the licence price? [unknown]: Does BYO change the licence price? Unknown. BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public. - byo_restrictions — Which features stop working with BYO? [partial]: Azure Chat Code Execution requires compatible Azure Responses models; switching a custom model group name/deleting an in-use group can break configured assistants. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:code. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial The documented Universal Model Key open models run in the US. Supported customer-operated chat and embedding routes remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public open-model guide retrieved 2026-10-26; no deployment observed; plan=Universal Model Key open-model route; current guide does not name a Core Suite/Flex entitlement for customer-operated models; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - The US inference finding is limited to the Universal Model Key open models described by the source. No absence of every conceivable private deployment is inferred. - self_hosted_chat — Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? The public Model Hub, Customer Key matrix and deployment guides describe named hosted-provider routes. They do not establish supported vLLM/Ollama/TGI chat, customer embeddings, parity or vendor-hosted open-model inference in a named EU/CH region. Creator-region model toggles do not prove inference location. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? The public Model Hub, Customer Key matrix and deployment guides describe named hosted-provider routes. They do not establish supported vLLM/Ollama/TGI chat, customer embeddings, parity or vendor-hosted open-model inference in a named EU/CH region. Creator-region model toggles do not prove inference location. - feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? The public Model Hub, Customer Key matrix and deployment guides describe named hosted-provider routes. They do not establish supported vLLM/Ollama/TGI chat, customer embeddings, parity or vendor-hosted open-model inference in a named EU/CH region. Creator-region model toggles do not prove inference location. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [unsupported]: For Universal Model Key open models described in the region-control guide, inference is hosted in the US regardless of creator country. That documented route does not provide EU/CH-hosted open-model inference; other private contracts are unverified. Sources: glean:glean:r4-open-model-inference. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: glean:glean:r4-open-model-inference #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform documents custom model and embedding connections. Tool parity depends on the selected route: Code Execution lists Azure and LiteLLM OpenAI compatibility, while arbitrary self-hosted model parity is unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform; custom-model/embedding connectors and optional Code Execution availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Code Execution has a listed Responses-capability/model matrix, not universal support for every custom-hosted model. Azure sandbox controls are not extended to every LiteLLM route. - No customer runtime or feature-parity fixture was used; QA-only Phoeniqs is not presented as GA. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Custom LXM and on-premises architecture allow customer-hosted model connections. Models, endpoint compatibility and enabled modules are selected for the contracted deployment. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [partial]: An instance maintainer can configure embedding endpoint, key and deployment; the operator overview allows self-hosted embeddings. Supported non-Azure runtimes and a particular customer configuration were not verified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators. - feature_parity — Which features fail with self-hosted models? [partial]: Changing embeddings requires re-embedding existing files. The Code Execution compatibility section explicitly lists Azure Responses-capable IDs and LiteLLM OpenAI IDs, so no blanket Azure-only restriction is asserted. Its introduction/security section describes an Azure sandbox; the actual LiteLLM execution route and parity for arbitrary self-hosted models remain unverified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:review2-code. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: The model catalogue describes Swiss Phoeniqs open models in QA only, not the UAT01/Prod offer. Production entitlement to a vendor-hosted Swiss open model was not established. Sources: unique-ai:unique-ai:review2-models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators, unique-ai:unique-ai:review2-code, unique-ai:unique-ai:review2-models ### MOD-05: Model control and usage limits Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Model restrictions and blocking usage limits are documented; new department Auto policies remain an opt-in rollout on October 21. Availability: unknown Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=As of 2026-10-21: existing controls plus opt-in Auto policies; policy GA scheduled 2026-10-29; plan=Core Suite/Enterprise Flex model governance and usage limits; new Auto policies require Glean-key deployment and Feature rollouts opt-in. Legacy Enterprise exclusions preserved.; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Existing controls and the new policy rollout have different availability. No two-user enforcement test was run; hiding premium models alone does not prevent Auto from using them. - model_allowlist_by_group — Can admins limit models per group? [supported]: Eligible models can be allowed by department or synced IdP group. Default models cannot carry these restrictions; membership refresh is not immediate. Sources: glean:glean:model-controls, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: Admins can exclude connectors, folders/sites or individual documents from all LLM responses. This is an all-LLM content boundary; per-model data classification rules were not established. Sources: glean:glean:restrictions, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - default_model — Can admins set the default model? [partial]: Customer Key admins set defaults. Universal Model Key admins manage available models; the new department Auto policies require rollout opt-in on October 21, with GA scheduled October 29. They are not a verified generally available policy entitlement on the check date. Sources: glean:glean:model-config, glean:glean:key-matrix, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:r3-october-rollout-migration. - user_limits — What per-user message or token limits apply, and are they published? [supported]: Core Suite and Enterprise Flex support configurable monthly per-user defaults and overrides. Limits reset each calendar month; legacy Enterprise lacks user/agent limits. Sources: glean:glean:limits, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - limit_behaviour — What happens when a limit is reached? [supported]: Admins select alert-only or block. An in-flight run finishes, then subsequent billable use is blocked until reset; slight overage can occur. Sources: glean:glean:limits, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:model-controls, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:restrictions, glean:glean:model-config, glean:glean:key-matrix, glean:glean:r3-october-rollout-migration, glean:glean:limits #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Models and knowledge/tools are configured per access-controlled Space; optional beta daily spending caps block calls. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No two-group restriction fixture was run. Exact contract token/message limits, platform-wide model allow-lists and provider data-routing policy remain unverified. - model_allowlist_by_group — Can admins limit models per group? [partial]: Admins bind deployed/approved models to Spaces and grant people/groups space access. Direct per-group model lists across all chats are not documented. Sources: unique-ai:unique-ai:agent. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: A Space binds one model, selected KB sources and tools, and people/group access. A global connector-content model policy is not established. Sources: unique-ai:unique-ai:agent. - default_model — Can admins set the default model? [supported]: Administrators select the model for each Space. Sources: unique-ai:unique-ai:agent. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Off-by-default beta cost management supports daily USD limits at company/group/user levels, reset at user-local midnight. Public fixed token/message quotas are not established. Sources: unique-ai:unique-ai:cost. - limit_behaviour — What happens when a limit is reached? [supported]: With limits enabled, the next model call is blocked when daily spend reaches the cap. Most permissive group limit wins unless a user override exists. Sources: unique-ai:unique-ai:cost. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:cost ## 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat uploads support common office formats with explicit size limits and OCR prerequisites. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Assistant + Model Hub Usage; Enterprise Flex doc uploads follow its named Assistant mode allowances; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Shared long-PDF, scan, spreadsheet and presentation fixture was not run. - formats — Which formats are accepted? [supported]: Documented formats include PDF, DOC/DOCX, XLS/XLSX/XLSM, PPT/PPTX, text and image files; audio/video uploads are excluded. Sources: glean:glean:uploads, glean:glean:r2-core-entitlements. - limits — What size and count limits apply per file and chat? [supported]: 128K models allow 5 files at 64 MB each; 32K models 4 at 32 MB; 8K models 2 at 16 MB. Minimum file size is 1 KB. Sources: glean:glean:uploads, glean:glean:r2-core-entitlements. - ocr — Are scanned PDFs read? [supported]: Scanned PDFs require OCR enabled by an administrator or support. Sources: glean:glean:uploads, glean:glean:r2-core-entitlements. - spreadsheets — Are Excel tables read with structure intact? [partial]: Data Analysis handles uploaded spreadsheets, but merged cells, hierarchical tables, charts and complex structures have limited support. Fixture formula and structure fidelity was not tested. Sources: glean:glean:analysis, glean:glean:r2-core-entitlements. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Uploaded analysis files expose full raw content within size limits; referenced indexed spreadsheets may be truncated. Archives are inspected on demand in Thinking mode. Complete visibility into selected chunks was not verified. Sources: glean:glean:analysis, glean:glean:uploads, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:uploads, glean:glean:r2-core-entitlements, glean:glean:analysis #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat upload defaults are 512 MB/file and 30 files/batch, with source retrieval for large documents. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Configured scanned-PDF OCR is documented: MDI supports image-based PDFs, Docling has partial support, and Base Unique Ingestion does not support them. MDI must be provisioned and enabled for the folder or chat Space. - Scanned-PDF accuracy, formula preservation, embedded-figure extraction and shared fixture outcomes were not measured. Older general ingestion limits differ from current production chat defaults. - formats — Which formats are accepted? [supported]: Chat supports PDF, DOCX, XLSX, PPTX, CSV, HTML, MD and TXT; PNG/JPEG when enabled per Space. Sources: unique-ai:unique-ai:files. - limits — What size and count limits apply per file and chat? [partial]: Production Chat defaults 512 MB/file, 30 files/upload. Code Execution has separate 100 MB and 10-file limits. Environment overrides and aggregate chat caps need tenant confirmation. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code. - ocr — Are scanned PDFs read? [partial]: The file-ingestion guide explicitly distinguishes methods: Base Unique Ingestion does not support image-based scanned PDFs, MDI supports them, and Docling has partial support. MDI must be provisioned and enabled for the folder or in the chat Space ingestion settings. Experimental image-content extraction and deprecated agentic ingestion are separate. No scanned-document fixture or accuracy measurement was run. Sources: unique-ai:unique-ai:file-ingestion-20261026. - spreadsheets — Are Excel tables read with structure intact? [partial]: Chat guide says default extraction can fail beyond 5,000 rows x 100 columns. General format guide lists 1,000 x 40; formulas and structure retention were not tested. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:filetypes. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: Checked uploads force retrieval each turn. Large files contribute selected chunks, not necessarily the full file, and users do not see full coverage. Experimental full-PDF mode is separate. Sources: unique-ai:unique-ai:files. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code, unique-ai:unique-ai:filetypes, unique-ai:unique-ai:file-ingestion-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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Core Suite includes Library Collections; the replacement Projects rollout and plan entitlement remain qualified. Availability: unknown Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Library Collections included; current Projects rollout/entitlement not separately established; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Projects are rolling out gradually and may not be enabled for a given deployment. Chat and artifact sharing is separate from project membership. - Projects is documented as a gradual replacement for Collections, but its current Core Suite/Enterprise Flex entitlement and rollout were not verified. - persistent_collections — Can users keep document collections across chats? [partial]: Core Suite includes persistent Library Collections. Projects documentation describes a replacement containing chats/documents/files/artifacts, but current Core Suite/Enterprise Flex Projects entitlement and migration rollout were not verified. Sources: glean:glean:r2-core-entitlements, glean:glean:projects. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [unknown]: The Projects guide describes private-by-default and people/group sharing, but current Projects rollout/entitlement under Core Suite or Enterprise Flex is not separately established. No current plan-scoped project-sharing guarantee is made. - size_limits — What are the collection limits? [unknown]: What are the collection limits? The Projects guide and agent builder were checked, but a current project size cap and direct knowledge-binding contract are not specified. - assistant_binding — Can collections be bound to an assistant? [unknown]: Projects and Agent Builder were checked; direct binding of a persistent Project or Collection to an assistant was not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:r2-core-entitlements, glean:glean:projects #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge folders persist and can be scoped to users/groups and bound to Spaces. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring. - persistent_collections — Can users keep document collections across chats? [supported]: Ingested content lives in knowledge-base folders/scopes beyond a chat. Sources: unique-ai:unique-ai:kbpermissions. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: ScopeAccess grants users or groups read/write access. A flat folder permission does not automatically grant subfolder access. Sources: unique-ai:unique-ai:kbpermissions. - size_limits — What are the collection limits? [unknown]: What are the collection limits? Unknown. Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring. - assistant_binding — Can collections be bound to an assistant? [supported]: Space Internal Search binds selected folders/files and further narrows user permissions. Sources: unique-ai:unique-ai:agent. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:agent ### 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). #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Glean documents M365, Google and Atlassian connectors, with indexed and live patterns depending on source. Availability: generally-available Delivery: official-integration Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite native connectors included; individual connector setup/consent still required; Enterprise Flex platform connections use applicable feature allowances; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [supported]: SharePoint and OneDrive support indexing and live retrieval. Outlook and Teams are listed separately; Teams includes channels and opt-in private/meeting chats. M365 indexing requires application permissions and admin consent. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:outlook, glean:glean:teams-connector, glean:glean:r2-core-entitlements. - google_workspace — Which Google sources are connected? [supported]: Google Drive and Gmail have official indexing documentation; Drive setup uses directory delegation. Plan-specific connector entitlements remain contractual. Sources: glean:glean:drive, glean:glean:gmail, glean:glean:r2-core-entitlements. - atlassian — Confluence and Jira? [partial]: The official catalog lists Confluence and Jira, including Cloud and Data Center documentation. Tenant setup and per-plan limits were not tested. Sources: glean:glean:connectors, glean:glean:r2-core-entitlements. - other_systems — Which other business systems? [partial]: The catalog includes Box, Salesforce, Notion, Slack, Zendesk and other systems. Individual entitlements, scopes and consent were not verified for every connector. Sources: glean:glean:connectors, glean:glean:r2-core-entitlements. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Deployment guidance supports private connectivity for on-premise connectors. This establishes a network option, not every file share/database or a locally hosted whole platform. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements. - connector_provider — Who builds and maintains each connector? [partial]: Glean publishes native connector guides; custom connectors and MCP routes are separate. Maintenance ownership for every listed third-party integration was not established. Sources: glean:glean:connectors, glean:glean:gateway, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:outlook, glean:glean:teams-connector, glean:glean:r2-core-entitlements, glean:glean:drive, glean:glean:gmail, glean:glean:connectors, glean:glean:deploy, glean:glean:gateway #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Indexed SharePoint and Confluence are documented. Current architecture also names Google Drive/Salesforce, and release notes describe Salesforce/Yahoo Finance MCP connector dashboards; detailed entitlements and source permissions remain connector-specific. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Architecture labels and release examples do not prove that every source is enabled or included in every contract. - Future items on the roadmap are not promoted to current connector support. - No source-connection or two-user permission fixture was run. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint Online connector copies selected content with application consent and optional permission sync. Platform documentation also exposes Teams and Outlook MCP operator guides, but their exact contracted scope and OneDrive coverage were not verified. Sources: unique-ai:unique-ai:sharepoint. - google_workspace — Which Google sources are connected? [partial]: The current Platform Overview names Google Drive as a Knowledge Source feeding the Knowledge Base. It does not establish Gmail/Calendar coverage, a deployment guide, source consent scopes or inclusion in a particular customer contract. This is a documented architecture listing, not an observed enabled connector. Sources: unique-ai:unique-ai:platform-overview-20261026. - atlassian — Confluence and Jira? [partial]: Official Confluence connector supports Cloud and Data Center; Jira connector coverage was not established. Sources: unique-ai:unique-ai:confluence. - other_systems — Which other business systems? [partial]: Release 2026.40 names Salesforce and Yahoo Finance as examples in GA MCP connector dashboards that admins can list, enable and sign in to. Platform Overview also names Salesforce as a Knowledge Source. Exact origin implementation, connector rights, credentials and commercial inclusion vary by configured connector and contract. Sources: unique-ai:unique-ai:release40-20261026, unique-ai:unique-ai:platform-overview-20261026. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Confluence Data Center sources are supported via REST. Generic file-share/database connector scope was not established. Sources: unique-ai:unique-ai:confluence. - connector_provider — Who builds and maintains each connector? [supported]: Unique publishes Kubernetes operator guides for SharePoint and Confluence; client IT supplies source credentials, consent, scope and deployment configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:platform-overview-20261026, unique-ai:unique-ai:release40-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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Permission-aware indexed and live retrieval is documented; the restricted-document test is outstanding. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect permission enforcement and connector access; fine-grained source rules documented per connector; add_ons=Glean Protect+ and account-team enablement for O365 sensitivity-label redlisting only; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Permission claims are documented only; no leak-free outcome or measured propagation delay is claimed. - source_permissions_respected — Are source permissions enforced per user? [supported]: SharePoint, OneDrive and Teams docs describe per-user permissions checked at query time. This is documentary evidence, not a passed two-user test. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:teams-connector, glean:glean:r2-core-entitlements. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Indexed routes copy source ACLs into Glean and evaluate them at query time; live SharePoint/OneDrive routes avoid a stored content index. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:r2-core-entitlements. - revocation_delay — How quickly does a removed permission take effect? [partial]: For indexed Drive, activity changes are checked every 10 minutes and group membership hourly. These are crawl schedules, not a measured revocation guarantee. Sources: glean:glean:drive, glean:glean:r2-core-entitlements. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins can include/exclude connectors, containers and documents from LLM access. Changes may take up to an hour. Sources: glean:glean:restrictions, glean:glean:r2-core-entitlements. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [partial]: Glean Protect+ can exclude SharePoint/OneDrive files by Purview label priority after account-team enablement. It requires crawling, may need days for the first full crawl, and does not cover Teams message text. This is index exclusion, not a passed live-permission test. Sources: glean:glean:r4-purview-label-redlist. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:teams-connector, glean:glean:r2-core-entitlements, glean:glean:drive, glean:glean:restrictions, glean:glean:r4-purview-label-redlist #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial SharePoint permission mirroring is optional; Confluence does not synchronise source permissions. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No two-user restricted-document/revocation fixture was run. End-to-end revocation SLA and label enforcement are not established. Older folder-permissions documentation says SharePoint never mirrors permissions, conflicting with the newer optional-sync guide. - source_permissions_respected — Are source permissions enforced per user? [partial]: SharePoint content_and_permissions mirrors source rights, while content_only uses Unique scope rules. Confluence explicitly has no source-permission sync, so Unique folder access needs configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Indexed content is filtered through Unique user/group ScopeAccess. This is not source-system live query-time enforcement. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:sharepoint. - revocation_delay — How quickly does a removed permission take effect? [partial]: SharePoint source rights refresh periodically, default scans 15 minutes. Internal gatekeeper changes usually propagate under one second but have no hard upper bound; degraded/missed broadcasts can leave old rules active. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:permissioncache. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins allow SharePoint sites/libraries and require a sync flag, Confluence labels, and Space KB restrictions. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:agent. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [partial]: July SharePoint connector explicitly excludes sensitivity/classification-level detection. Separately, release2026.42 documents experimental Purview-protected-file decryption using uploader rights, gated by MIP_DECRYPTION_ENABLED and Entra/operator changes. This is not proof of general label-policy enforcement. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:sharepoint. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:permissioncache, unique-ai:unique-ai:agent, unique-ai:unique-ai:release42 ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Glean combines indexed and live connector routes; refresh timing is source-specific. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite connector/index platform; Customer Hosted location/contract separately selected; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - live_or_indexed — Is content searched live or copied into an index? [supported]: SharePoint/OneDrive document indexed, live and tool routes. Indexed routes copy content; live routes do not store content in the index. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:r2-core-entitlements. - sync_interval — How often does an index refresh? [supported]: Drive documents 10-minute activity crawls, hourly people/group crawls, 3-hour incremental crawls and normally 28-day full crawls. Sources: glean:glean:drive, glean:glean:r2-core-entitlements. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Drive activity processing includes deletions, but no fixture deletion-to-answer interval or universal maximum was verified. Sources: glean:glean:drive, glean:glean:r2-core-entitlements. - index_location — Where is indexed content stored? [partial]: Indexes run in the selected isolated Glean Hosted or Customer Hosted environment. Exact country and any secondary log/backup locations need deployment confirmation. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:sharepoint, glean:glean:onedrive, glean:glean:r2-core-entitlements, glean:glean:drive, glean:glean:deploy #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial SharePoint and Confluence copy content to Unique indexes on configurable scans, default every 15 minutes. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No source-edit/delete fixture was run. Actual sync duration, strict deletion SLA and index/backup region per contract remain unverified. - live_or_indexed — Is content searched live or copied into an index? [supported]: Connectors ingest documents/page attachments into the Unique knowledge base for RAG. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - sync_interval — How often does an index refresh? [supported]: Default 15-minute scan for both connectors; schedules are configurable. Real-time sync is explicitly not supported. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Diff processing detects deleted source files/pages and removes them on a sync run. A strict completion bound is not provided. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - index_location — Where is indexed content stored? [partial]: Hosted documents use Azure storage; embeddings Qdrant and search vectors on managed disks in the selected deployment. Exact per-client index region needs the MSA/architecture. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:keys. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:retention, unique-ai:unique-ai:keys ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Linked source citations are documented; named-plan cross-language retrieval and observed grounding quality remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Assistant/Deep Research with Model Hub Usage; no verified Core Suite/Enterprise Flex cross-language entitlement; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Citation links do not establish citation accuracy. The Early Access language guide does not map cross-language retrieval to a verified named-plan entitlement. - citations — Are answers linked to specific sources? [supported]: Assistant documentation describes grounded answers with linked citations; Deep Research produces cited company/web reports. Sources: glean:glean:research, glean:glean:sharing, glean:glean:r2-core-entitlements. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? No shared multilingual question set or restricted corpus was run; citation accuracy, correct-answer count and no-answer behavior remain unmeasured. - cross_language — Does a question in one language find documents in another? [unknown]: The language guide labels answering across document/query languages Early Access, but its Core Suite/Enterprise Flex entitlement and enabled rollout were not established. Cross-language retrieval for those named plans remains unknown; no multilingual fixture was run. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? No shared multilingual question set or restricted corpus was run; citation accuracy, correct-answer count and no-answer behavior remain unmeasured. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? No shared multilingual question set or restricted corpus was run; citation accuracy, correct-answer count and no-answer behavior remain unmeasured. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:research, glean:glean:sharing, glean:glean:r2-core-entitlements, glean:glean:language #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unique documents source-linked answers and reference limits, without a shared-corpus accuracy result. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - citations — Are answers linked to specific sources? [supported]: Chat retrieval cites sources; Conduct links source facts, with PDF/Word page-level references and other formats at document level. Generated files are not citation-linked or hallucination-checked. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Glean documents personal saved and learned memory with user controls and a limited admin off switch. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite saved memory in seat and learned memory with Model Hub Usage; Enterprise Flex learned-memory rate/temporary waiver separate; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - custom_instructions — Can users set persistent instructions? [supported]: Saved preferences and explicit memories can persist across conversations. Sources: glean:glean:memory, glean:glean:r2-core-entitlements. - cross_chat_memory — Does the product remember facts across chats? [supported]: Saved and learned memories retain user work context and preferences across chats, subject to deployment availability. Sources: glean:glean:memory, glean:glean:r2-core-entitlements. - user_memory_controls — Can users view, edit and delete memories? [supported]: Users can view, edit and delete memories and control memory use in a conversation. Sources: glean:glean:memory, glean:glean:r2-core-entitlements. - admin_memory_controls — Can admins turn memory off? [partial]: Admins can disable learned memory; saved memories are user-controlled and cannot be disabled by admins through this setting. Sources: glean:glean:memory-admin, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:memory, glean:glean:r2-core-entitlements, glean:glean:memory-admin #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Context Memory provides a private cross-chat user profile with edit and opt-out controls. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No authenticated memory fixture or permanent deletion test was run. The guide explicitly contradicts the settings deletion promise. - custom_instructions — Can users set persistent instructions? [partial]: Admins configure Space instructions; memory learns preferences. A separate persistent user-authored global instruction field was not established. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory. - cross_chat_memory — Does the product remember facts across chats? [supported]: One per-user profile is loaded across enabled spaces/chats and updated after answers; stored in a private unindexed KB folder. Sources: unique-ai:unique-ai:memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users view/edit the profile and disable updates/loading. Docs explicitly say disabling does not delete the profile despite contrary settings text; a delete control is not established. Sources: unique-ai:unique-ai:memory. - admin_memory_controls — Can admins turn memory off? [supported]: Release2026.42 makes Context Memory GA, with per-company enable/disable feature flag and per-Space activation. Users can opt out; Web Search combinations remain restricted by default. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory, unique-ai:unique-ai:release42 ## 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Custom agents combine instructions, models, knowledge and tools and have an internal library. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Building/Governance/Sharing in seat; builder assistance/debugging/runtime use Model Hub as applicable; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Agent Builder configures instructions, model choice, knowledge and tools, with Workflow and Auto modes. Sources: glean:glean:builder, glean:glean:agents, glean:glean:r2-core-entitlements. - creator_permissions — Can admins limit who creates them? [partial]: Admin role and agent-sharing controls regulate creation and distribution; no trial creation-boundary check was performed. Sources: glean:glean:roles, glean:glean:agent-sharing, glean:glean:r2-core-entitlements. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Agents have controlled sharing/edit access, including department and IdP-group audiences where enabled. Sources: glean:glean:agent-sharing, glean:glean:groups, glean:glean:r2-core-entitlements. - catalogue — Is there an internal assistant directory? [supported]: The Agent library shows accessible agents for discovery and execution. Sources: glean:glean:library, glean:glean:r2-core-entitlements. - prompt_library — Are shared prompt templates available? [partial]: The former Prompt Library was retired August 5, 2025. Reusable prompts and apps moved to Agents; use current agents/templates rather than the retired interface. Sources: glean:glean:sunset, glean:glean:library, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:builder, glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:roles, glean:glean:agent-sharing, glean:glean:groups, glean:glean:library, glean:glean:sunset #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins configure Spaces with instructions, models, knowledge, tools, prompts and group access. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Assistant versioning, organisation-wide directory discovery and unrestricted end-user creation were not established. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Space setup includes model, instructions, knowledge sources and tools. Sources: unique-ai:unique-ai:agent. - creator_permissions — Can admins limit who creates them? [supported]: Space creation/management requires delegated role permissions; Can manage grants space configuration access. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Share through Access with people/groups as Can chat or Can manage. Sources: unique-ai:unique-ai:agent. - catalogue — Is there an internal assistant directory? [partial]: Space Management lists configured workspaces; a dedicated employee assistant-discovery directory is not described. Sources: unique-ai:unique-ai:agent. - prompt_library — Are shared prompt templates available? [supported]: Admins publish Suggested Prompts with a Space; users also have personal saved prompts. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:roles, unique-ai:unique-ai:chat ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Glean supports tools and external MCP with admin access controls; tool identities vary by route. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite native tools/MCP host and Developer Tools; LLM tool/API calls incur Model Hub Usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - External-tool access boundaries were not tested. Customer Key and tool-provider contracts remain separate. - builtin_tools — Which tools are built in? [supported]: Agents can search knowledge, analyze data and read/write connected records; available tools depend on enabled connectors. Sources: glean:glean:agents, glean:glean:r2-core-entitlements. - custom_actions — Can admins add API actions? [supported]: The MCP Gateway exposes customer-built read/write tools as well as connector tools. Sources: glean:glean:gateway, glean:glean:r2-core-entitlements. - mcp_client — Can it use remote MCP servers, and with what admin control? [partial]: Admins register external remote MCP servers and apply role/group controls in Glean. This pass did not execute a server call. Sources: glean:glean:gateway, glean:glean:r2-core-entitlements. - tool_auth — Do tools act as the user or as a shared account? [partial]: OAuth integrations can use Glean-managed or customer OAuth applications; agent service credentials are a distinct route. Identity must be checked per tool. Sources: glean:glean:oauth, glean:glean:r2-core-entitlements. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins control tool exposure. The Microsoft file-creation guide instructs interactive-agent builders to disable Run without user confirmation when user approval is required. Write confirmation is configurable, not an unconditional enforced rule; a universal approval policy for unattended agents remains unknown. Sources: glean:glean:gateway, glean:glean:r3-microsoft-write-confirmation, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:gateway, glean:glean:oauth, glean:glean:r3-microsoft-write-confirmation #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Built-in tools and beta MCP connectors are governed at organisation and Space levels. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted platform with MCP beta feature flag and configured connectors; add_ons=MCP entitlement and enablement per contract; deployment_mode=not specified; region=Tenant plus downstream connector/provider regions; os=not specified. Limitations: - Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released. - builtin_tools — Which tools are built in? [supported]: Internal search, web search, Deep Research and Code Execution are documented; Deep Research is experimental and code has model restrictions. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch. - custom_actions — Can admins add API actions? [unknown]: Can admins add API actions? Unknown. Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: MCP Tools for Spaces is beta, off until enabled for the organisation; connector admins and space managers can selectively expose connectors/tools. Sources: unique-ai:unique-ai:mcp. - tool_auth — Do tools act as the user or as a shared account? [supported]: MCP Hub maps user hub tokens to downstream per-user OAuth tokens; secrets are injected server-side. Sources: unique-ai:unique-ai:hub. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins restrict origin/connector/tool exposure. Conduct can pause for approve/deny of configured sensitive actions; it is not a universal confirmation guarantee. Sources: unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:mcp, unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Brave is the new web-search default; OpenAI search is a legacy route under migration. Deep Research produces cited read-only reports. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=2026-10-21, after the October 19 start of OpenAI-to-Brave migration; individual migration completion unobserved; plan=Core Suite Deep Research with Model Hub Usage; Brave for new web-search setups, configured Gemini route per setup guide, legacy OpenAI only until migrated; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - The dated release governs the new-versus-legacy route distinction. No per-tenant configuration, migration completion or provider-region test was performed. - web_search — Is web search available? [supported]: Brave is the default for new web-search setups. The setup guide also documents Google Gemini. OpenAI Web Search is closed to new setups; existing instances work only until Glean migrates them to Brave, beginning October 19. Sources: glean:glean:web, glean:glean:r2-core-entitlements, glean:glean:r3-october-rollout-migration. - admin_toggle — Can admins disable it per organisation or group? [partial]: Admins select enabled search tools and publication to Assistant, Agents and MCP. Universal per-group disabling was not verified. Sources: glean:glean:web, glean:glean:r2-core-entitlements. - search_provider — Which search provider handles queries, and where? [partial]: Brave is the new default and the provider named by Deep Research; Gemini is another documented configured route. OpenAI is legacy-only during the migration that began October 19. Per-tenant migration completion and query-processing countries remain unknown. Sources: glean:glean:web, glean:glean:research, glean:glean:r2-core-entitlements, glean:glean:r3-october-rollout-migration. - deep_research — Is multi-step research with a report available? [supported]: Deep Research writes cited multi-source reports from company sources and the web; it does not write to connected systems. Sources: glean:glean:research, glean:glean:r2-core-entitlements. - web_citations — Are web sources cited? [supported]: Deep Research reports contain linked web and company citations. Sources: glean:glean:research, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:web, glean:glean:r2-core-entitlements, glean:glean:r3-october-rollout-migration, glean:glean:research #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web search has provider/strategy controls; separate Deep Research is experimental. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No search/report fixture was run. Exact query/provider regions, contract enablement and current Deep Research production readiness remain unverified. - web_search — Is web search available? [supported]: Real-time web search/read is a Space tool, with stable V1/V2 modes and experimental V3. Sources: unique-ai:unique-ai:websearch. - admin_toggle — Can admins disable it per organisation or group? [supported]: Admins enable/disable tools per Space shared with groups. Deep Research tools are configured separately; disabling ordinary Web Search is not a universal external-search block. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch. - search_provider — Which search provider handles queries, and where? [partial]: Configured engines can include Google, Bing, Brave, Jina, Tavily, Firecrawl, Vertex or custom API; query context can leave the tenant. Exact provider region must be set per contract. Sources: unique-ai:unique-ai:websearch. - deep_research — Is multi-step research with a report available? [supported]: Experimental tool creates multi-source research and reports. Unique engine can use internal/web sources; OpenAI-native engine requires direct OpenAI-hosted models and lacks internal sources/hosting-location control. Sources: unique-ai:unique-ai:deepresearch. - web_citations — Are web sources cited? [supported]: Web answers include source references; Deep Research documents citation-linked reports. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:deepresearch. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: supported Workflow mode supports multi-step logic with schedule and content-event triggers. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Building, workflow mode and triggers in seat; LLM execution incurs Model Hub Usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. - workflow_builder — Is there a workflow or chain builder? [supported]: Workflow mode supports explicit steps, branches, loops and hand-offs; Auto mode builds from natural-language goals. Sources: glean:glean:agents, glean:glean:r2-core-entitlements. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Published agents can run on schedules after admin enablement; setup differs by Auto versus Workflow mode. Sources: glean:glean:triggers, glean:glean:r2-core-entitlements. - event_triggers — Can external events start a workflow? [supported]: Content triggers run when supported connected-system content changes; chat and form triggers are separate. Sources: glean:glean:triggers, glean:glean:r2-core-entitlements. - builder_audience — Is building aimed at business users, IT or developers? [supported]: The builder supports natural-language creation and explicit workflow editing; the documentation includes self-paced Agent Builder training. Sources: glean:glean:agents, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:triggers #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Recurring Scheduled Tasks run with user permissions; current release notes label the feature experimental. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits. - workflow_builder — Is there a workflow or chain builder? [unknown]: Is there a workflow or chain builder? Unknown. No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits. - scheduled_tasks — Can prompts or assistants run on a schedule? [partial]: User guide labels recurring Chat/Conduct tasks beta and off by default; release2026.42 instead labels Scheduled Tasks experimental, off by default, enabled on request, and describes scheduling/eligibility fixes. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:scheduled. - event_triggers — Can external events start a workflow? [partial]: SDK documents webhook-driven applications, which require developer-hosted modules; a packaged no-code external-event builder was not established. Sources: unique-ai:unique-ai:sdk. - builder_audience — Is building aimed at business users, IT or developers? [partial]: Business users author recurring tasks in the UI or Conduct; developers host webhook-driven SDK modules. Availability and scheduling behaviour depend on deployed release. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42 ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Auto mode agents plan and use tools, but end-to-end execution safety was not tested. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Harness/Agent Building with Model Hub Usage for LLM execution; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Auto mode agents dynamically choose tools and delegate subtasks; Workflow mode uses explicit steps. Sources: glean:glean:agents, glean:glean:r2-core-entitlements. - visible_steps — Are steps and tool calls shown? [partial]: Workflow steps and builder preview/debugging are documented. Complete runtime visibility for every Auto action was not verified. Sources: glean:glean:builder, glean:glean:agents, glean:glean:r2-core-entitlements. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Office creation tools describe a confirmation step before writing, without an editable inline preview. This does not establish confirmation for all scheduled operations. Sources: glean:glean:office-output, glean:glean:r2-core-entitlements. - stop_control — Can the user stop a running task? [partial]: The October 15 release documents that canceling an Assistant response terminates its tool calls and background tasks. Universal cancellation across scheduled/independent agents and every client was not verified by a fixture. Sources: glean:glean:r4-cancellation-release. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:builder, glean:glean:office-output, glean:glean:r4-cancellation-release #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Contract-enabled Conduct plans and executes multi-step tasks with visible tools and stop controls. Sensitive actions can ask for approval; separately enabled Experimental Scheduled Tasks offer automatic approval. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Conduct; version=Conduct 2026.40+; scheduling status/flags per 2026.42; plan=Contracted Unique AI platform; Conduct; Scheduled Tasks separately enabled per contract and feature flag availability and deployment/provider configuration depend on the customer agreement; add_ons=Conduct; optional Scheduled Tasks feature flag; deployment_mode=not specified; region=Configured tenant/models/tools; scheduled actions run with the owner permissions and configured approval policy; os=not specified. Limitations: - No agent fixture was run. Interactive sensitive-action approval and separately enabled unattended automatic approval are different execution modes. - Actual tools, entitlement, approval policy and deployed release depend on the customer contract/configuration. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Plans and executes Python/Bash, files, internal search and configured MCP tools in an autonomous workspace. Sources: unique-ai:unique-ai:conduct. - visible_steps — Are steps and tool calls shown? [supported]: Shows checklist, progress, code/tool inputs and outputs, and waiting/working indicators. Sources: unique-ai:unique-ai:conduct. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Conduct shows approve/deny for actions configured as sensitive. The separate Scheduled Tasks guide offers Automatic or Manual approval for Chat/Conduct unattended runs. Release 2026.42 labels scheduling Experimental and feature-flagged. Mandatory human approval of every side effect is therefore not established for all configured runs. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42. - stop_control — Can the user stop a running task? [supported]: Stop ends the turn within seconds; completed steps/files remain and interrupted work can be resumed. Sources: unique-ai:unique-ai:conduct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42 ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public platform APIs and a remote MCP server are documented. Availability: generally-available Delivery: native Scope: surfaces=Glean APIs and remote MCP server; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Platform/Admin/Indexing/Tools APIs in seat and LLM Client APIs/MCP with Model Hub Usage; Enterprise Flex Client APIs consume FlexCredits; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - chat_api — Is there an API for chat and assistants? [supported]: Core Suite lists Chat and Agents APIs plus platform APIs and Web SDK; LLM-using calls incur Model Hub consumption. Sources: glean:glean:core-price, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - knowledge_api — Can documents be loaded through an API? [supported]: Core Suite lists the Indexing API and Tools API; document upload APIs are linked from the file-upload guide. Sources: glean:glean:core-price, glean:glean:uploads, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Machine-scale API usage can incur extra fees, and MCP uses user permissions. Full audit/budget/model-rule parity across API credentials was not tested. Sources: glean:glean:core-price, glean:glean:mcp, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - mcp_server — Does the product expose itself to other agents over MCP? [supported]: Glean MCP exposes search, chat, document reading and other tools to external AI hosts. Sources: glean:glean:mcp, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:core-price, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:uploads, glean:glean:mcp #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public API/Python SDK and Knowledge Base MCP are documented. Availability: generally-available Delivery: native Scope: surfaces=Unique API and Python SDK, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted APIs and KB MCP deployment; model tracking requires enablement; add_ons=KB MCP and usage-tracking enablement per contract; deployment_mode=not specified; region=Configured deployment and external client region; os=not specified. Limitations: - No API/SDK fixture was run; complete endpoint catalogue, rate limits, budget enforcement and all-services audit parity remain unverified. - chat_api — Is there an API for chat and assistants? [partial]: SDK exposes the Unique public API, personal/app keys and webhook signatures. Exact endpoint entitlements/rate limits require the contracted deployment. Sources: unique-ai:unique-ai:sdk. - knowledge_api — Can documents be loaded through an API? [partial]: Connector/operator docs describe ingestion and knowledge APIs; public SDK supports platform integrations. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Feature-flagged model-use tracking covers public API/SDK/agentic and Azure SDK calls with company/user/app metadata. Complete budget/model-rule enforcement across all internal services is not established. Sources: unique-ai:unique-ai:api-usage. - mcp_server — Does the product expose itself to other agents over MCP? [supported]: Knowledge Base MCP lets external assistants search/read the Unique KB with the user permissions and admin scope restrictions. The documentation-only MCP endpoint is distinct. Sources: unique-ai:unique-ai:mcpkb. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:api-usage, unique-ai:unique-ai:mcpkb ## 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Glean has web, desktop, mobile and extension access, including managed mobile controls. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents, Glean for Desktop Windows and macOS, Glean iOS and Android, Glean browser extension and companion; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Glean surfaces included in seat; individual AI actions may incur Model Hub Usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=Windows, macOS, iOS, Android. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web — Is a full web client available? [supported]: The full browser app provides chat, Library and agents. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements. - desktop_apps — Windows and macOS apps? [supported]: Windows and macOS desktop clients are documented. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements. - mobile_apps — iOS and Android apps with SSO? [supported]: iOS and Android apps require an active SSO-configured tenant. Sources: glean:glean:mobile, glean:glean:r2-core-entitlements. - browser_extension — Is there a browser extension or sidebar? [supported]: The extension supplies sidebar chat/search and a companion for selected text. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements. - managed_deployment — Can IT deploy and configure clients through MDM? [supported]: Mobile integrates with Intune App Protection. Managed desktop and extension deployment are linked in official deployment guidance. Sources: glean:glean:mobile, glean:glean:surfaces, glean:glean:r2-core-entitlements. - client_feature_gaps — Which features are missing on mobile? [partial]: Deep Research is web-only. Real-time voice supports web, desktop and mobile; other complete parity differences were not verified. Sources: glean:glean:research, glean:glean:voice, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements, glean:glean:mobile, glean:glean:research, glean:glean:voice #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial A web workspace is documented; native-client and managed-deployment coverage is unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - web — Is a full web client available? [supported]: Public documentation describes browser chat, Space Management and administration. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial A Microsoft Teams app is documented; connectors and file-generation tools do not establish in-Office add-ins. Availability: generally-available Delivery: official-integration Scope: surfaces=Glean in Microsoft Teams, Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite embedded Microsoft Teams and other listed surfaces; selected Assistant actions incur Model Hub Usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? The Teams app, connector catalog and Office-output guides were checked. An assistant embedded inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; remote content access is not counted as in-app presence. - outlook — Does it work inside Outlook? [unknown]: Does it work inside Outlook? The Teams app, connector catalog and Office-output guides were checked. An assistant embedded inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; remote content access is not counted as in-app presence. - teams — Is there a Teams app or bot? [supported]: The Glean Teams app has an admin installation guide and tenant setup/consent requirements. Sources: glean:glean:teams-app, glean:glean:r2-core-entitlements. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? The Teams app, connector catalog and Office-output guides were checked. An assistant embedded inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; remote content access is not counted as in-app presence. - licence_prerequisites — Which licences or consents are needed? [partial]: Teams requires admin deployment in a configured Glean tenant and Microsoft permissions. Extra licence charges are not numerically specified in the guide. Sources: glean:glean:teams-app, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:teams-app, glean:glean:r2-core-entitlements #### Unique AI Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-03: Translation and writing Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Browser companion translation and general writing are documented; layout-preserving document translation is unverified. Availability: generally-available Delivery: native Scope: surfaces=Glean browser extension and companion, Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite browser Companion/Sidebar surfaces included; LLM writing/translation uses configured model usage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? The companion, file-upload and Office-generation guides were checked. No whole-document layout-preserving translation, company glossary, formality/de-CH control or DE-to-FR/IT fixture result was established. - translation_engine — Which engine translates? [partial]: The browser companion translates selected text through Glean. A dedicated translation service or exact translation-model route is not named here. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? The companion, file-upload and Office-generation guides were checked. No whole-document layout-preserving translation, company glossary, formality/de-CH control or DE-to-FR/IT fixture result was established. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? The companion, file-upload and Office-generation guides were checked. No whole-document layout-preserving translation, company glossary, formality/de-CH control or DE-to-FR/IT fixture result was established. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Configured agents support drafting; the browser companion explains, summarizes and translates selected text. Dedicated proofreading behavior was not verified. Sources: glean:glean:surfaces, glean:glean:agents, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:surfaces, glean:glean:r2-core-entitlements, glean:glean:agents #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial A beta Translator Space translates Office files and text with configurable glossaries. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No translated-contract fixture was run. Exact engine/model, formality/de-CH controls, supported glossary language pairs and layout fidelity need verification. - document_translation — Can whole documents be translated with formatting kept? [partial]: DOCX, XLSX and PPTX document translation is documented, with possible layout disruption. PDF input is explicitly excluded in this Translator mode. Sources: unique-ai:unique-ai:translation. - translation_engine — Which engine translates? [partial]: Translator V2 is a standalone AI module configured with a model; no dedicated DeepL engine was established. Sources: unique-ai:unique-ai:translation. - glossaries — Are company glossaries supported? [supported]: Admins can configure glossary pre/postprocessing. Sources: unique-ai:unique-ai:translation. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Postprocessing can change regional spelling, exemplified by US-to-UK English. Formality or de-CH-specific support was not verified. Sources: unique-ai:unique-ai:translation. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Chat generates and iterates on text; no distinct proofreading/rewriting tool scope was established. Sources: unique-ai:unique-ai:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:translation, unique-ai:unique-ai:chat ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Glean can generate and edit images using enabled image models. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite image generation/editing with Model Hub Usage; provider/key availability remains conditional; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - image_generation — Can users generate images, with which models? [supported]: Universal Model Key uses the managed GPT Image 2.5 or GPT Image 2 default; Customer Key admins select image models and Agents can select enabled models. Sources: glean:glean:images, glean:glean:r2-core-entitlements. - image_editing — Can users edit uploaded images? [supported]: The image guide documents editing uploaded images. Sources: glean:glean:images, glean:glean:r2-core-entitlements. - admin_control — Can admins restrict image generation? [supported]: An administrator must enable image generation and a supported image model. Sources: glean:glean:images, glean:glean:r2-core-entitlements. - usage_terms — What usage rights apply to output? [partial]: Customer rights in outputs are governed by the Terms and AI Addendum together with model-provider terms; no unique or exclusive image-output guarantee was verified. Sources: glean:glean:terms, glean:glean:ai-addendum, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:images, glean:glean:r2-core-entitlements, glean:glean:terms, glean:glean:ai-addendum #### Unique AI Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Real-time voice is available with provider streaming; meeting functionality depends on key mode. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents, Glean for Desktop Windows and macOS, Glean iOS and Android; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite real-time voice/Meeting Notes with Model Hub Usage; Meeting Notes requires Universal Model Key per feature matrix; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Raw voice audio streams to the configured model provider and is not stored according to the voice guide; transcripts follow chat retention. - dictation — Can users dictate prompts? [unknown]: Can users dictate prompts? The voice guide and key-mode matrix were checked; separate dictation and Swiss German recognition were not established or tested. - read_aloud — Can answers be read aloud? [partial]: Real-time voice speaks its responses; a separate read-aloud control for arbitrary text responses was not established. Sources: glean:glean:voice, glean:glean:r2-core-entitlements. - voice_conversation — Is a live voice mode available? [supported]: Interactive voice supports web, desktop and mobile, with interruptible spoken replies and a chat transcript. It does not invoke a chosen published agent. Sources: glean:glean:voice, glean:glean:r2-core-entitlements. - meeting_summaries — Are meetings transcribed and summarised? [partial]: The key matrix lists Meeting Notes as generally available with Universal Model Key and unsupported with Customer Key. Recording/language behavior was not tested. Sources: glean:glean:key-matrix, glean:glean:r2-core-entitlements. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? The voice guide and key-mode matrix were checked; separate dictation and Swiss German recognition were not established or tested. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:voice, glean:glean:r2-core-entitlements, glean:glean:key-matrix #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Voice dictation is documented with Azure Speech prerequisites; recording use is separately described in the DPA. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. - dictation — Can users dictate prompts? [supported]: Microphone transcribes into the prompt field, with audio discarded after live transcription. Requires configured Azure AI Speech Services; EN/DE/FR/IT are listed. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. - meeting_summaries — Are meetings transcribed and summarised? [partial]: DPA recording use case covers audio/transcripts, optional video and GPT summaries/follow-up emails. This is a contracted recording use case, not proof every Chat plan includes meeting capture. Sources: unique-ai:unique-ai:dpa. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user, unique-ai:unique-ai:dpa ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Data analysis and Office file output are documented, with spreadsheet and template limitations. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Assistant/Canvas/document output with Model Hub Usage; provider/tool prerequisites apply; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - No fixture analysis or output-file inspection. Code-interpreter provider and retention differ by route. - data_analysis — Can it analyse spreadsheets with executed code? [supported]: Thinking-mode uploaded spreadsheets can use a per-user/session sandbox. Indexed spreadsheets may be truncated and cross-indexed-file numeric aggregation is not supported by the documented Data Analysis route. Sources: glean:glean:analysis, glean:glean:r2-core-entitlements. - charts — Can it produce charts? [unknown]: The Data Analysis and Office-output guides were checked, but chart generation and chart-file fidelity were not established or observed in this pass. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Enabled tools create Word documents, Excel workbooks and PowerPoint decks, saved/downloaded through the documented route. Arbitrary Word/Excel template population is not supported by create tools. Sources: glean:glean:office-output, glean:glean:r2-core-entitlements. - canvas_editing — Is there a document or canvas editor for iterating on output? [supported]: Slide generation creates decks in Canvas for refinement and export; exact themes and embedded elements are not guaranteed. Sources: glean:glean:office-output, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:analysis, glean:glean:r2-core-entitlements, glean:glean:office-output #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enabled Chat Code Execution and Conduct can analyse data and produce downloadable files. Selected KB documents can be preloaded into the code container; ordinary unrestricted KB retrieval is separate. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct; version=not specified; plan=Contracted Unique AI platform; Chat Code Execution or Conduct; model compatibility and flags configured separately availability and deployment/provider configuration depend on the customer agreement; add_ons=Code Execution / Conduct enablement per contract; deployment_mode=not specified; region=Documented Azure code container for the Azure route; LiteLLM execution region unverified; Conduct sandbox per contracted deployment; os=not specified. Limitations: - Selected admin-preloaded KB files are supported; this is not arbitrary sandbox retrieval of the whole Knowledge Base. - The page lists Azure and LiteLLM-compatible model IDs but describes Azure-specific container controls. Actual provider execution routing and entitlement require deployment configuration. - No generated-file quality/editability fixture was run. - data_analysis — Can it analyse spreadsheets with executed code? [partial]: Chat Code Execution runs Python for CSV/XLSX analysis. The general limitation says KB files are not directly accessible, but admin configuration additionalUploadedDocuments preloads selected KB content_ids, for example templates, into the container. The documented Azure route has no outbound internet/runtime installs and a ten-file/100 MB per-file limit. The compatibility table also lists LiteLLM OpenAI models; that does not establish the same execution-region controls for every route. Conduct separately runs Python/Bash. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct. - charts — Can it produce charts? [supported]: The Code Execution guide documents matplotlib PNG/SVG and inline charts. Its described Azure container lacks kaleido, limiting Plotly static exports; no statement about every alternative runtime is inferred. Sources: unique-ai:unique-ai:review2-code. - office_file_output — Can it create Word, Excel or PowerPoint files? [partial]: The guide documents DOCX/XLSX generation and PPTX from supplied templates, with variable presentation quality. KB templates can be supplied by the admin preload setting. Generated files remain outside Conduct source-citation/hallucination checks. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct. - canvas_editing — Is there a document or canvas editor for iterating on output? [unknown]: No dedicated canvas editor or editable spreadsheet-to-PowerPoint fixture result was established. Downloadable file generation does not establish in-product canvas editing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Viewer chat sharing documents recipient-source redaction; current Projects and group-chat plan entitlements remain unknown. Availability: beta Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Assistant Viewer sharing; current Projects and Team-chat Editor entitlement under Core Suite/Enterprise Flex unverified; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Viewer redaction must not be generalized to Team-chat Editors. Projects and Team-chat commercial/rollout entitlements remain unknown; no two-user fixture was run. - share_chats — Can chats be shared inside the organisation? [supported]: Users can share chats with users, departments or the organization, with Viewer read-only access. Sources: glean:glean:sharing, glean:glean:r2-core-entitlements. - team_spaces — Are shared projects or workspaces available? [unknown]: The Projects guide describes gradual enablement but does not establish a current named Core Suite/Enterprise Flex entitlement. Shared-project availability remains unknown. - group_chat — Can several people chat together with the AI? [unknown]: The Team chat guide describes a beta enabled for selected users, but its current Core Suite/Enterprise Flex entitlement was not established. Multi-user AI chat availability for a named plan remains unknown. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: For Viewer chat sharing, the guide documents redaction of inaccessible citations and content. That finding does not establish the distinct Team-chat Editor entitlement or its availability for a Core Suite/Enterprise Flex tenant. No cross-group sharing test was run. Sources: glean:glean:sharing, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:sharing, glean:glean:r2-core-entitlements, glean:glean:projects, glean:glean:team-chat #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared Chats is GA in release 2026.42, with company settings and a per-Space toggle. Simultaneous group conversation and recipient source-permission handling remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=2026.42 or later; plan=Contracted Unique AI platform; Shared Chats and Spaces; sharing settings and deployed release availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - A shared conversation is not evidence of simultaneous group participation or recipient access to every source. - No cross-group shared-chat permission fixture was run. - share_chats — Can chats be shared inside the organisation? [supported]: Release 2026.42 makes whole-chat sharing GA and on by default for companies, while each Space still needs its Shared chat toggle. Explicit existing company preferences are preserved. Owners can search recipients and copy share links. Sources: unique-ai:unique-ai:review2-release42. - team_spaces — Are shared projects or workspaces available? [partial]: Admins publish shared Spaces with people/group Can chat and Can manage roles. These share agent configuration/knowledge, not necessarily a conversation. Sources: unique-ai:unique-ai:agent. - group_chat — Can several people chat together with the AI? [unknown]: Whole-chat sharing is documented. A simultaneous multi-person AI conversation, collaborative commenting or live co-editing mode was not established or tested. - share_permission_boundary — Does sharing respect the recipient's access to sources? [unknown]: Whole-chat sharing is documented, but whether a recipient can open every cited source or inherits source permissions was not established in the retrieved release/Space documentation. No cross-group fixture was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:review2-release42 ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial German, French, Italian and English end-user UIs are documented; admin setup is not localized. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite client surfaces; detailed language/localization entitlements not separately mapped by plan; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - The language/accessibility pages describe the common product, without a separate Core Suite/Enterprise Flex localization entitlement matrix. - ui_languages — Which UI languages are offered? [supported]: The support matrix lists English, German, French and Italian UI among other locales. Sources: glean:glean:language, glean:glean:r2-core-entitlements. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? The locale matrix and accessibility statement were checked, but translation completeness and naturalness were not observed in a logged-in German/French/Italian UI. - accessibility_statement — Is there a WCAG conformance statement? [partial]: Glean maintains a VPAT 2.5 ACR covering WCAG 2.0/2.1/2.2 A and AA, obtainable through the Trust Center; the report was not reviewed. Sources: glean:glean:accessibility, glean:glean:r2-core-entitlements. - admin_ui_languages — Is the admin interface available in German? [unsupported]: The language guide explicitly says external help documentation and admin workspace setup are not yet localized. Sources: glean:glean:language, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:language, glean:glean:r2-core-entitlements, glean:glean:accessibility #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Current release notes document German, French and Swiss German UI language behaviour; completeness and accessibility remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Release notes describe locale fixes, not a full UI audit or conformance statement. No authenticated UI was reviewed. - ui_languages — Which UI languages are offered? [partial]: Release2026.42 describes German/French label translations and selected-language login/notices/errors/side-panels, including Swiss German spellings. A complete language matrix was not provided. Sources: unique-ai:unique-ai:release42. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:release42 ## 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial SSO is mandatory with OIDC/SAML and identity-provider MFA and conditional access. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect includes SSO and role access; detailed IdP policy setup is separately documented; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - No SSO trial login was performed. - sso_protocols — Which SSO protocols and identity providers work? [supported]: OIDC and SAML work with Entra ID, Google, Okta, OneLogin and generic SAML providers as documented. Sources: glean:glean:sso, glean:glean:r2-core-entitlements. - sso_plan — Which plan includes SSO? [partial]: SSO is mandatory during deployment setup; no separate SSO price or plan gate is given in this guide. Sources: glean:glean:sso, glean:glean:r2-core-entitlements. - mfa — Can MFA be enforced? [supported]: Glean recommends enforcing MFA through the configured identity provider. Sources: glean:glean:sso, glean:glean:r2-core-entitlements. - conditional_access — Do Entra conditional-access policies apply? [supported]: Glean recommends appropriately secure IdP conditional-access policies; mobile documents Intune-compatible sign-in. Sources: glean:glean:sso, glean:glean:mobile, glean:glean:r2-core-entitlements. - domain_capture — Can the company claim its email domain? [partial]: Glean checks the user email domain against the expected customer domain before issuing a login cookie; broader domain-capture/migration semantics were not established. Sources: glean:glean:sso, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:sso, glean:glean:r2-core-entitlements, glean:glean:mobile #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Zitadel supports Entra OIDC, generic OIDC and SAML across documented deployment types. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented. - sso_protocols — Which SSO protocols and identity providers work? [supported]: Setup guides explicitly cover Entra ID OIDC, generic OIDC and SAML, including IdP metadata for closed networks. Sources: unique-ai:unique-ai:sso. - sso_plan — Which plan includes SSO? [partial]: Compliance matrix lists SSO for multi-tenant, single-tenant, client-hosted and on-premise modes. Numeric tariff prerequisites are not public. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance. - mfa — Can MFA be enforced? [partial]: Hosted compliance matrix lists enforced 2FA; SSO setup delegates authentication to the external IdP. Exact customer MFA policy controls need verification. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance ### 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. #### Glean Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial SCIM, group sync and SAML automatic user creation are documented. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run. - scim — Is SCIM provisioning supported? [supported]: Unique supplies SCIM URL/key for IdP synchronisation, with an Entra guide. Sources: unique-ai:unique-ai:scim. - group_sync — Are identity-provider groups synced? [supported]: SCIM syncs users/groups; SSO group claims can also sync on login, requiring optional Graph group permission/admin consent. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso. - jit_provisioning — Are users created at first login? [supported]: SAML setup explicitly enables automatic creation/update and account creation. Sources: unique-ai:unique-ai:sso. - deprovisioning — What happens to a removed user's data and shared assets? [unknown]: What happens to a removed user's data and shared assets? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run. - seat_assignment — Can admins assign and reclaim seats? [unknown]: Can admins assign and reclaim seats? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Glean has delegated admin roles, IdP-group permissions and feature access controls. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect/Agent Governance role controls; department and IdP group policy configuration as documented; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - No two-group restriction-enforcement test. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Setup Admin, Admin, Super Admin and specialist moderators have documented scopes; only Super Admin can assign certain privileges. Sources: glean:glean:roles, glean:glean:r2-core-entitlements. - groups — Can permissions be set per group? [supported]: Direct and IdP-group roles combine, with highest-precedence primary roles and union of secondary roles. Group permission behavior is feature-flag dependent. Sources: glean:glean:groups, glean:glean:r2-core-entitlements. - feature_toggles — Which features can be switched on or off per group? [partial]: Member permissions include content and agent creation; model access, scheduled triggers and beta features have specific controls. Every feature/group combination was not verified. Sources: glean:glean:users, glean:glean:groups, glean:glean:r2-core-entitlements. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Terms permit affiliates to use or order the service, while separate subsidiary data partitions within one contract were not established. Sources: glean:glean:terms, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:roles, glean:glean:r2-core-entitlements, glean:glean:groups, glean:glean:users, glean:glean:terms #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Four role/access layers separate identity, feature, Space and knowledge controls. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No two-user disabled-feature test was run. Full cross-Space per-group controls and legal-entity separation require contracted setup. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: IAM owner/viewer/org-manager plus Unique application roles delegate administration; Space Can manage grants local configuration. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent. - groups — Can permissions be set per group? [supported]: Users/groups receive Space and ScopeAccess permissions. Sources: unique-ai:unique-ai:roles. - feature_toggles — Which features can be switched on or off per group? [partial]: Tools and upload settings are configured per Space, then Spaces shared to groups. A global group-feature matrix is not established. Sources: unique-ai:unique-ai:agent. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Compliance docs describe workspace isolation for departments/client engagements. Multi-subsidiary contractual/billing boundaries are not specified. Sources: unique-ai:unique-ai:compliance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent, unique-ai:unique-ai:compliance ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Insights provides adoption and individual activity reporting with CSV export. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Billing & Insights included in seat; Enterprise Flex Admin console/Insights platform separate from usage rates; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - adoption_dashboard — Is there an adoption dashboard? [supported]: Insights includes daily, weekly and monthly active users and adoption metrics. Sources: glean:glean:insights, glean:glean:r2-core-entitlements. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Department filters and per-person Assistant, search, agent and MCP activity are documented. Model usage is a separate dashboard; a unified breakdown by every requested dimension was not verified. Sources: glean:glean:insights, glean:glean:core-price, glean:glean:r2-core-entitlements. - export — Can usage data be exported? [supported]: The All signed up users table exports CSV; customer event delivery supports downstream analysis. Sources: glean:glean:insights, glean:glean:events, glean:glean:r2-core-entitlements. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: Departments under five users are grouped. The same guide documents named user activity; an organization-wide pseudonymous mode was not established. Sources: glean:glean:insights, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:insights, glean:glean:r2-core-entitlements, glean:glean:core-price, glean:glean:events #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Analytics exports cover adoption, assistants, models and tools with privacy controls. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Exact group breakdowns, every dashboard entitlement and suppression beyond exported identifiers need verification. - adoption_dashboard — Is there an adoption dashboard? [supported]: Reports cover daily/weekly/monthly active users, assistant interactions and document reference statistics. Sources: unique-ai:unique-ai:analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Detailed exports include assistant/model, tool calls, skills, cost and tokens. Group and cost-centre breakdowns were not established. Sources: unique-ai:unique-ai:analytics. - export — Can usage data be exported? [supported]: Admins request and download reports with date/assistant filtering; model usage supports CSV. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost. - privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: Environment flags anonymise export emails, optionally with stable pseudonyms; detailed exports respect organisation settings. Sources: unique-ai:unique-ai:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Usage limits can alert or block; team limits are per-member defaults rather than pooled team budgets. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite / Enterprise Flex; legacy Enterprise exclusions stated; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - cost_visibility — Can admins see cost or consumption per user and group? [supported]: Usage dashboards expose user/team/agent consumption in dollars or FlexCredits depending on plan. Sources: glean:glean:limits. - budgets — Can budgets be set per user or group? [supported]: Organization, user, department/IdP-group and agent monthly limits are documented for Core Suite/Enterprise Flex; legacy Enterprise lacks user/agent limits. Sources: glean:glean:limits. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: An optional block stops later billable requests after the running action completes. Alert-only is also available; some overage can occur. Sources: glean:glean:limits. - chargeback — Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? The usage-limit and pricing guides were checked; cost-center chargeback export and cost allocation outside current department/group metadata were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:limits #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Off-by-default beta cost management offers estimated spend and enforced daily caps. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No small-budget fixture was run. Estimates are configurable cost-sheet values, not a public billing tariff; cost-centre and full invoice reconciliation remain gaps. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Tracks estimated USD/input/output tokens by user, model, assistant/app; a billed invoice reconciliation or group cost view is not established. Sources: unique-ai:unique-ai:cost. - budgets — Can budgets be set per user or group? [supported]: Company fallback, group and user daily USD caps; user override first, highest applicable group limit next. Sources: unique-ai:unique-ai:cost. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Before the next call, accumulated daily spend at cap blocks the model call; resets at local midnight. Docs warn caps may break background-job SLAs. Sources: unique-ai:unique-ai:cost. - chargeback — Can costs be exported per cost centre? [partial]: CSV exports contain user/app/assistant/model/token/cost metadata, with privacy controls. Cost-centre attribution is not documented. Sources: unique-ai:unique-ai:cost. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:cost ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Administrative change logs have documented CSV export and retention. Prompt/response compliance logging remains unknown because source scopes conflict. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect administrative audit logs; no verified prompt/response compliance-logging finding; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Only administrative/configuration events, their export and their stated retention are positive findings. Content logging, its compliance integrity model, eDiscovery and legal hold remain unverified. - admin_events — Are admin and security events logged? [supported]: Admin Audit Logs record configuration changes by admins and Glean support, excluding end-user events. Default retention is 30 days. Sources: glean:glean:audit, glean:glean:r2-core-entitlements. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [unknown]: Prompt/response retention and its configuration remain unknown. The deployment comparison says individual queries/responses are not logged, while Customer Event documentation describes CHAT response content and the history guide separates that logging from history. Their deployment/system scopes were not reconciled. - siem_export — Can logs stream to a SIEM or be exported? [partial]: The administrative audit-log guide documents self-serve CSV export. For Glean-hosted deployments, ongoing delivery of administrative logs can be configured by the account team and is not enabled by default or self-serve. This finding makes no prompt/response or Customer Event export guarantee. Sources: glean:glean:audit, glean:glean:r2-core-entitlements. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Administrative and Customer Event documentation was checked. eDiscovery/legal-hold behavior, integrity guarantees and per-destination content-log retention were not established. - log_retention — How long are logs kept? [partial]: Administrative audit logs have a documented 30-day default; extended periods require arrangement. Customer Event/content-log retention is unknown and no common retention term for all logs is inferred. Sources: glean:glean:audit, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:audit, glean:glean:r2-core-entitlements, glean:glean:deploy, glean:glean:events, glean:glean:history #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial API audit events, detailed interaction exports and Single-Tenant security-event streaming are documented. A single authoritative retention period for the customer's audit records is not established. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Audit Logs, Analytics and Single-Tenant Security Events Export availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE for the contracted Single-Tenant deployment; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - API security-event records, detailed prompt/answer interaction exports, SEE replay and generic operational logging are separate sources/data flows. Their public retention figures are not substituted for each other. - No executed customer retention override or legal-hold/eDiscovery fixture was inspected. - admin_events — Are admin and security events logged? [supported]: Event logging covers privileged public/internal API interactions; many self-identity/chat operations are excluded. Basic mode is default; verbose content mode is opt-in. Sources: unique-ai:unique-ai:audit. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [supported]: Detailed chat interaction exports contain prompts/answers for authorised admins and respect configured privacy. Verbose event logging can include CID but is discouraged. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:audit. - siem_export — Can logs stream to a SIEM or be exported? [supported]: SEE offers Single-Tenant Azure Defender and Activity events via Event Hub to Sentinel/Splunk, seven-day replay. It excludes tenant-level Entra events and is not a prompt-content audit stream. Sources: unique-ai:unique-ai:security-export. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: No public legal-hold/eDiscovery workflow or complete event-log immutability design was established. - log_retention — How long are logs kept? [unknown]: Different sources describe different record scopes. The API event guide gives basic-mode MT events 90 days and ST events five years, including post-termination ST retention. DPA 3.15 says audit logs ten years without mapping its audit-log category to those API events. The generic hosted policy says logging up to one year after termination or longer if legally required. SEE has a separate seven-day Event Hub replay window, not the lifetime of all audit records. No customer agreement or authoritative record-class/precedence mapping was retrieved; the applicable audit retention period is unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-audit, unique-ai:unique-ai:analytics, unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-retention ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Protect+ can flag or block configured sensitive patterns in prompts; file coverage and Swiss-fixture outcomes are unknown. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Enterprise Flex + Protect+ site-wide annual add-on; basic Core Suite CSV protection is a different mechanism; add_ons=Glean Protect+ AI security; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Prompt-only pattern policy is not evidence that file contents are filtered before every model call. No personal-data fixture was run. - pii_detection — Is personal data detected in prompts and files? [partial]: Prompt-only regex policy covers configured PII, credentials, IBAN and government-ID patterns. Templates start disabled; this policy excludes retrieved data and generated responses. Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - pii_action — Is it redacted, masked, blocked or only warned? [supported]: Admins choose monitoring with findings or immediate blocking of the run; the guide does not promise automatic redaction for this policy. Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - custom_patterns — Can admins add custom patterns or terms? [supported]: Admins can define RE2 pattern groups and test patterns before enabling them. Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - dlp_integration — Does it integrate with an existing DLP product? [partial]: Protect+ documents AI security integrations including Palo Alto Networks in the product/security material. Purview/Netskope integration and exact enterprise entitlement were not verified. Sources: glean:glean:protect, glean:glean:subprocessors, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - filter_location — Where does filtering run? [unknown]: Where does filtering run? Protect+ and prompt-policy guides were checked. Filtering location, upload scanning by this policy and Swiss AHV/IBAN behavior were not observed. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:protect, glean:glean:subprocessors #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial DLP is primarily customer infrastructure and integration; it is not a verified default native redaction feature. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - pii_detection — Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - pii_action — Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - custom_patterns — Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - dlp_integration — Does it integrate with an existing DLP product? [partial]: Documents customer HTTPS proxy/interceptor DLP and post-chat Analytics API scanning; Compliance Layer says pre-LLM calls can be implemented. Multi-Tenant matrix explicitly excludes DLP integration. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance. - filter_location — Where does filtering run? [partial]: Proxy inspection runs in customer egress infrastructure; Analytics API supports customer post-chat inspection. A deployment-specific pre-LLM service may be implemented. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise instructions and configurable AI security policies are documented. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Enterprise Flex Assistant instructions; Protect+ site-wide annual add-on for security monitoring/blocking; add_ons=Protect+ for AI security findings; not required for basic custom instructions; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Model-followed instructions are distinct from policy enforcement. - org_instructions — Can admins set organisation-wide instructions? [supported]: Admins can configure up to five enterprise custom instructions for Assistant. Sources: glean:glean:org-instructions, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? The custom-instruction and AI security guides were checked; a mandatory acceptable-use acknowledgement flow was not established. - content_filters — Are content filters configurable? [supported]: Protect+ policies can monitor/block configured sensitive prompts and restrict topics; enforcement depends on enabled policy. Sources: glean:glean:pii, glean:glean:protect, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - violation_reporting — Are policy hits visible to admins? [supported]: Monitoring creates admin findings with matched patterns, snippets and conversation links. Sources: glean:glean:pii, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:org-instructions, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:pii, glean:glean:protect #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Space instructions/banners and customer-specific login terms are documented. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement. - org_instructions — Can admins set organisation-wide instructions? [partial]: Admins set Space-level system instructions and persistent banners. A mandatory organisation-wide instruction hierarchy is not specified. Sources: unique-ai:unique-ai:agent. - usage_notice — Can users be required to accept a usage policy? [supported]: First login requires terms acceptance; custom terms/editing/deactivation depend on MSA eligibility and admin GraphQL role. Acceptance/version data can be exported. Sources: unique-ai:unique-ai:policy. - content_filters — Are content filters configurable? [partial]: Single-tenant Azure prompts pass through Azure content filters; Compliance matrix marks hosted modes with content filtering. Customer filter configuration and scope remain unspecified. Sources: unique-ai:unique-ai:single, unique-ai:unique-ai:compliance. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:policy, unique-ai:unique-ai:single, unique-ai:unique-ai:compliance ## 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosting is region-selectable, but storage, model processing and remote support must be scoped separately. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Glean Hosted regional single-tenant hosting included; Customer Hosted and provider regions remain contract/key choices; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - storage_region — Where are chats, files and indexes stored? [partial]: Tenant storage and index follow the selected isolated GCP/AWS deployment; the public GCP list includes Netherlands, Belgium and Frankfurt. Actual contracted country was not selected. Sources: glean:glean:deploy, glean:glean:regions, glean:glean:r2-core-entitlements. - inference_region — Where do model calls run, per provider? [partial]: Model routes depend on cloud and key mode; GCP/AWS Customer Key has cross-cloud restrictions. The subprocessor list allows customer-selected provider locations but does not establish every model remains in EU/CH. Sources: glean:glean:models, glean:glean:subprocessors, glean:glean:r2-core-entitlements. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Deployment documentation lists backups up to seven days but no full country map for backups, telemetry and central services was established. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements. - support_access_region — From where can vendor staff access data? [supported]: The subprocessor list names the Indian affiliate for remote support/security/debugging; the SLA names California and Bangalore support locations. Sources: glean:glean:subprocessors, glean:glean:sla, glean:glean:r2-core-entitlements. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Region and deployment pages were checked; Swiss hosting, exact backup/log/telemetry geography and all model-provider regional exceptions were not established. - residency_plan — Which plan or option provides residency? [partial]: Both vendor-hosted and customer-cloud modes offer region selection. Prices, thresholds and per-model regional conditions remain contractual. Sources: glean:glean:deploy, glean:glean:terms, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:deploy, glean:glean:regions, glean:glean:r2-core-entitlements, glean:glean:models, glean:glean:subprocessors, glean:glean:sla, glean:glean:terms #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Documentation offers CH North multitenant hosting and selectable single/customer-hosted regions, with model processing configured separately. The customer's binding residency schedule and full backup/log/support map remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted or customer-hosted platform; separately selected model/tool routes availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Documented options: CH North hosted MT; selected ST/customer region; provider/SKU/tool inference region separately configured; actual contracted boundaries unverified; os=not specified. Limitations: - Available architecture/region options are not a signed residency schedule. Storage, model inference, backups/logs, support access and external tools must be scoped separately. - DPA CH-storage and chosen-location statements are not reconciled by silently treating one as the current customer contract. - storage_region — Where are chats, files and indexes stored? [partial]: The deployment matrix documents Azure Switzerland North for hosted multitenant and chosen supported regions for Single Tenant. Tenant storage includes PostgreSQL, documents and vector data. These are configuration options; no customer-specific storage schedule was inspected. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-keys. - inference_region — Where do model calls run, per provider? [partial]: The model catalogue separates Azure regional/Data Zone/Global SKUs and external provider routes, with some Swiss deployments and some global-only services. Actual selected provider/SKU/tool routing must be configured for the contracted deployment. CH storage is not a verified CH inference guarantee. Sources: unique-ai:unique-ai:review2-models, unique-ai:unique-ai:deepresearch. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Single-tenant backup resources follow the configured landing-zone design and SEE sends events to a separately selected consumer region. An exhaustive physical replica/backup/log/telemetry country matrix was not retrieved. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export. - support_access_region — From where can vendor staff access data? [unknown]: The public DPA gives need-to-know access controls and customer-controlled on-premises support, but not an exhaustive physical country list for vendor/subprocessor support access. Office addresses are not used as support-access locations. - swiss_hosting — Is Swiss hosting available? [partial]: CH North is a documented hosted-MT option, and selected-region ST can be Swiss. This records available deployment options, not the customer's end-to-end storage/inference/support contract. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models. - residency_plan — Which plan or option provides residency? [unknown]: DPA 6.1 says storage stays in Switzerland, while its Appendix A allows a client-chosen Microsoft location and current platform docs offer selected jurisdictions. No current customer MSA, precedence clause or deployment schedule was inspected to resolve the binding scope. A contractual CH-wide residency commitment is not asserted. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:security-export, unique-ai:unique-ai:deepresearch ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Glean documents dedicated vendor hosting and Glean-operated deployment in customer cloud accounts. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Glean Hosted single tenant; separately contracted Customer Hosted private-cloud configuration under Core Suite/Enterprise Flex; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - multi_tenant_saas — Is a shared SaaS offered? [unsupported]: Deployment documentation explicitly says Glean uses single-tenant infrastructure in both supported modes. This is not a shared tenant offer. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: Glean Hosted runs isolated customer infrastructure in Glean cloud accounts; the public guide gives no numerical seat threshold. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - customer_cloud — Can it run in the customer's own cloud account, from what size? [supported]: Customer Hosted, formerly Cloud-Prem, runs a Glean-managed tenant in customer GCP or AWS. Glean handles upgrades and keeps support access; seat/contract minimum is not published. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. - 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? The deployment guide and terms describe supported cloud accounts, not a whole-platform on-premises or air-gapped entitlement. Numerical minimums for each mode were not found. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? The deployment guide and terms describe supported cloud accounts, not a whole-platform on-premises or air-gapped entitlement. Numerical minimums for each mode were not found. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: The guide describes the same product in both modes, but key/provider matrices document cloud and feature differences. Customer Hosted cannot be independently patched or re-architected by the customer. Sources: glean:glean:deploy, glean:glean:key-matrix, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:key-matrix #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Current docs offer shared SaaS, dedicated instances, customer cloud and customer-operated on-premise/air-gapped modes. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No deployed tenant was inspected. Seat/contract thresholds and an exhaustive offline feature-parity matrix remain unknown; docs establish an option, not universal entitlement. - multi_tenant_saas — Is a shared SaaS offered? [supported]: Installation overview lists Multi Tenant on Unique cloud. Sources: unique-ai:unique-ai:install. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [partial]: Unique-managed Single Tenant has its own Azure landing zone separated from other customers. Minimum seats/contract value are unpublished. Sources: unique-ai:unique-ai:single. - customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: Operator guide documents deployment in customer cloud account with Unique software/support; cloud-specific rollout is contracted. Sources: unique-ai:unique-ai:operators. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Customer provisions/manages infrastructure on own premises, may run own models and can exclude Unique access. Minimum commitment not published. Sources: unique-ai:unique-ai:onpremsecurity. - air_gapped — Can it run without internet access? [partial]: IT-operator overview explicitly offers a full air-gapped on-premise deployment. Compatibility and feature limitations depend on customer setup. Sources: unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: Compliance matrix separates SSO/content filter/DLP/PAM/key capabilities by mode. Azure Chat Code Execution/voice and external web/providers require those services and cannot be assumed in an isolated environment. Sources: unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:install, unique-ai:unique-ai:single, unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial The AI Addendum prohibits model training and scopes provider retention commitments to Glean-key use, with exceptions. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Any contracted plan incorporating the AI Addendum; Glean model key unless Customer Key explicitly discussed; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - vendor_training — Does the vendor train on customer content? [supported]: AI Addendum section 3(a)(i) prohibits Glean from using Customer Data to train, retrain, improve or fine-tune AI Models. Sources: glean:glean:ai-addendum. - provider_training — Do model providers train on it under this product's contracts? [supported]: For Glean model-key service, Glean contracts with providers to prohibit that training. Customer Key access remains the customer responsibility under section 4. Sources: glean:glean:ai-addendum. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: Glean-key section 3(b) prohibits stored/logged inputs and outputs except legal or trust-and-safety necessity. The Data Analysis guide also describes up to 30-day retention for abuse-flagged files. Sources: glean:glean:ai-addendum, glean:glean:analysis. - zero_retention — Is zero data retention available, and on which plan? [partial]: Zero-day retention is a contractual Glean-key commitment subject to law and trust/safety exceptions; it is not a blanket guarantee for Customer Key or every file-processing tool. Sources: glean:glean:ai-addendum, glean:glean:analysis. - human_review — Can provider staff review content? [unknown]: Can provider staff review content? The AI Addendum and Data Analysis security text were checked; provider human-review access under each exception was not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:ai-addendum, glean:glean:analysis #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosted Azure documentation says no model training and disabled Microsoft prompt storage/human review; other provider routes require separate terms. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No signed Azure amendment was inspected. Retention and review conditions for Anthropic, Gemini, Together, xAI and direct OpenAI research remain unverified; do not generalise the Azure-only policy. - vendor_training — Does the vendor train on customer content? [supported]: Hosted retention policy says no customer data is used for AI/neural-network training. Public terms allow service development and anonymised metadata use; that is not a blanket prohibition of all secondary processing. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms. - provider_training — Do model providers train on it under this product's contracts? [partial]: Hosted Azure deployment is separate from public OpenAI and training is excluded. Other catalogue providers/direct OpenAI research need their applicable customer terms. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [supported]: For hosted Azure OpenAI, documents/prompts/answers process in memory only, with logging/human-review opt-out. Ordinary application chats persist in Unique databases. Sources: unique-ai:unique-ai:retention. - zero_retention — Is zero data retention available, and on which plan? [partial]: Hosted Azure model calls use no provider content storage per opt-out; this is not zero retention of Unique application history, logs or other provider routes. Sources: unique-ai:unique-ai:retention. - human_review — Can provider staff review content? [partial]: Hosted Azure guide says Microsoft prompt/response human review is disabled. Vendor staff need-to-know access and alternate model-provider review conditions are separate. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:dpa ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial User-facing chat/file deletion and contract-end obligations are documented; default and effective admin retention remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex user history controls and applicable Terms/DPA; default/effective configured retention and shared-link lifetime unverified; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - User-facing deletion does not establish erasure from every retained copy. Default/effective configured retention, shared-link lifetime and contract-end completion timing remain unknown. - default_retention — What is retained and for how long by default? [unknown]: Default content retention is unknown. Chat Sharing states a fixed 30-day conversation/link lifetime, while Chat History describes organization-configured periods. The relationship between shared links, stored chats, uploads and other retained copies was not reconciled; no universal default is inferred. - admin_retention — Can admins set retention periods? [unknown]: The history guide lists Off, 30, 90, 180 and 365 days, but the sharing guide states a fixed 30-day conversation/link lifetime. The effective scope of admin settings versus shared-link/stored-chat retention remains unresolved, so a verified configurable retention entitlement is not asserted. - user_deletion — Can users delete their chats and files permanently? [partial]: The history guide lets users remove chats from their history; the upload guide allows file removal before the first query or by deleting the chat afterward. Permanent removal from every copy, backup or event log was not established. Sources: glean:glean:history, glean:glean:uploads, glean:glean:r2-core-entitlements. - contract_end_deletion — What is deleted at contract end, and when? [partial]: Terms section 12.3 and DPA section 7 require deletion at termination subject to legal retention. No fixed completion interval or destruction certificate was established. Sources: glean:glean:terms, glean:glean:dpa, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:history, glean:glean:uploads, glean:glean:r2-core-entitlements, glean:glean:terms, glean:glean:dpa, glean:glean:sharing #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat content clearing, chat uploads, KB documents, contract-end content deletion, recoverable files, backups and audit records have separate policies. No common purge deadline is established for all copies. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Chat, Knowledge Base and hosted retention configuration; customer-hosted policy separately controlled availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted storage/provider region; hosted-policy timings not extended to every customer-hosted system; os=not specified. Limitations: - Hosted content policy expressly permits contract-specific variation. Its timings do not define API/DPA audit-record retention. - No tenant configuration, customer MSA, final backup purge or external-provider deletion fixture was inspected. - default_retention — What is retained and for how long by default? [partial]: The chat-upload guide describes an admin-configured expiry, typically two weeks, for chat uploads. Hosted policy lists no minimum for KB/blob/vector/database content. Neither figure defines audit-event retention or proves a tenant's configured default. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:review2-retention. - admin_retention — Can admins set retention periods? [supported]: DATA_RETENTION_IN_DAYS drives the daily midnight chat-content clearing job; unset/zero disables it. This clears the content categories named by the redaction guide, not all uploads, KB, external tool records or audit events. Sources: unique-ai:unique-ai:redaction. - user_deletion — Can users delete their chats and files permanently? [partial]: The redaction guide says deleting a chat removes its Unique chat-content copy and marks the chat record deleted. Separate upload, KB, external-tool, soft-delete, backup and audit policies are not collapsed into that action. Sources: unique-ai:unique-ai:redaction. - contract_end_deletion — What is deleted at contract end, and when? [partial]: For Unique-hosted ordinary content, the published policy states a standard 30-day post-termination period unless the customer contract differs. It separately describes recoverable files for 30 days after deletion and database backups for two further weeks. DPA 6.1 requires return/deletion subject to legal record-keeping. Audit-log classes and their contractual lifetime remain unknown under ADM-06; this is not a deadline for deletion of every copy. Sources: unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:redaction, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial A dated processor list includes US providers and Indian remote support, with DPA transfer and change terms. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex under applicable public Terms, signed DPA and Order Form; no bespoke contract examined; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - subprocessor_list — Is a dated sub-processor list published? [supported]: Public list last updated July 28, 2026 identifies infrastructure, model, support and search subprocessors. Sources: glean:glean:subprocessors, glean:glean:r2-core-entitlements. - subprocessor_countries — Which countries do sub-processors operate in? [supported]: The table lists US provider entities and India for Glean Search Technologies remote support; selected cloud/provider processing locations can differ. Sources: glean:glean:subprocessors, glean:glean:r2-core-entitlements. - change_notification — Are customers notified of sub-processor changes? [supported]: DPA section 9 specifies at least 30 days notice before a new processor and a 30-day objection period, with a scoped termination remedy if unresolved. Sources: glean:glean:dpa, glean:glean:r2-core-entitlements. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The Terms identify Glean Technologies, Inc. as a Delaware corporation. A separate parent entity was not established. Sources: glean:glean:terms, glean:glean:r2-core-entitlements. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [supported]: The DPA incorporates EU SCCs, Swiss-recognized clauses and the UK Addendum for applicable transfers; SCC law/jurisdiction is Ireland. Sources: glean:glean:dpa, glean:glean:r2-core-entitlements. - government_access_policy — Is there a published government-access or transparency policy? [unknown]: Is there a published government-access or transparency policy? DPA, processor list and privacy page were checked. A separate government-access/transparency-request policy was not established; no legal exposure verdict is made. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:subprocessors, glean:glean:r2-core-entitlements, glean:glean:dpa, glean:glean:terms #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The dated public DPA lists Microsoft, but a complete applicable current subprocessor/country schedule for all contracted model/tool routes was not retrieved. A technical provider catalogue is not substituted for that legal schedule. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; current platform infrastructure and enabled model/tool integrations availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Actual customer provider/country/transfer schedule unverified; os=not specified. Limitations: - The provider catalogue establishes technical choices, not each party's processor role or the legal schedule for a customer contract. - No sales contact, executed current MSA or nonpublic schedule was obtained. - subprocessor_list — Is a dated sub-processor list published? [unknown]: The July 2025 public DPA Appendix A lists Microsoft for infrastructure, Cognitive/Azure OpenAI and email. The current technical catalogue offers other provider/tool routes, which may have different contractual roles. No applicable complete current legal schedule or executed customer supplement was retrieved; the Microsoft-only list is not presented as complete. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: DPA Appendix A names CH or a client-chosen Microsoft location; technical model routes separately include regional and global processing. A complete current legal provider/country and support-access schedule for the chosen deployment was not retrieved. - change_notification — Are customers notified of sub-processor changes? [unknown]: No applicable current processor-change notification/objection clause for the customer's full provider schedule was retrieved from the DPA or current contract-access documentation. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The current contact page identifies Unique AI AG in Switzerland and regional entities. The public DPA uses Unique AG. Ultimate parent/beneficial-owner jurisdiction and a customer-specific contracting entity were not independently established. Sources: unique-ai:unique-ai:contact, unique-ai:unique-ai:review2-dpa. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [unknown]: No complete customer-content transfer-instrument mapping per non-CH/EU provider was retrieved. The website visitor privacy policy is not substituted for customer-content terms. - government_access_policy — Is there a published government-access or transparency policy? [unknown]: No current customer-content government-request/transparency policy was retrieved for the complete contracted provider chain. General banking/DPA assurances do not establish such a policy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:contact ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public contractual and AI-law materials are available, with Swiss/EU data-law scope. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex applicable public Terms/DPA/AI Addendum; signed Order Form controls actual coverage; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dpa — Is a DPA available, and is it negotiable? [supported]: A public DPA form takes effect when signed and can sit under a mutually accepted agreement; negotiability was not tested. Sources: glean:glean:dpa, glean:glean:r2-core-entitlements. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [supported]: The DPA defines applicable data-protection law to include Switzerland and GDPR and describes Swiss transfer clauses. Applicability depends on the processing. Sources: glean:glean:dpa, glean:glean:r2-core-entitlements. - governing_law — Which law and court govern the contract? [partial]: Main Terms section 13.1 specifies New York and US law; SCCs select Ireland for their own governing law/jurisdiction. A specific court for the main contract was not established. Sources: glean:glean:terms, glean:glean:dpa, glean:glean:r2-core-entitlements. - ai_act_materials — Is EU AI Act documentation provided? [partial]: The AI Addendum includes applicable EU AI Act commitments and allocation of customer/provider responsibilities; a full procurement technical file was not retrieved. Sources: glean:glean:ai-addendum, glean:glean:r2-core-entitlements. - sector_materials — Are FINMA or other sector materials provided? [partial]: The public legal index links HIPAA BAA forms for Glean as Business Associate and as Subcontractor; actual coverage depends on the applicable agreement. The AI Addendum describes assurance commitments. FINMA/banking-secrecy outsourcing materials were not established. Sources: glean:glean:r3-legal-index, glean:glean:ai-addendum, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:dpa, glean:glean:r2-core-entitlements, glean:glean:terms, glean:glean:ai-addendum, glean:glean:r3-legal-index #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial A public DPA and finance-specific compliance material are available; actual contractual amendments were not inspected. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - DPA negotiability and signed sector amendments, product-specific EU AI Act roles and exact sector assurance scope remain unverified. This records materials, not a compliance verdict. - dpa — Is a DPA available, and is it negotiable? [partial]: DPA accepts click-through/use or signature and defines Unique as processor for hosted MT/ST. Negotiability is not specified. Sources: unique-ai:unique-ai:dpa. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: DPA addresses GDPR, Swiss FDPIC oversight and MSA-defined laws; Compliance Layer identifies nFDAP/Swiss M329 amendment. Exact signed revDSG/GDPR scope requires MSA. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance. - governing_law — Which law and court govern the contract? [supported]: DPA 7 specifies Swiss substantive law and Zürich 1 courts unless mandatory GDPR/MSA otherwise. Public ToS similarly names Swiss law. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Trust centre describes per-use-case conformity assessments; ISO42001 and AI governance material are public. A complete provider/deployer AI Act technical file is not established. Sources: unique-ai:unique-ai:trust, unique-ai:unique-ai:compliance. - sector_materials — Are FINMA or other sector materials provided? [partial]: Compliance Layer names Microsoft M453 FINMA audit-rights amendment, M744 professional/banking secrecy and M329 CH-DPA for Unique-hosted deployments. Actual annexes and current signed scope are not public. Sources: unique-ai:unique-ai:compliance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance, unique-ai:unique-ai:terms, unique-ai:unique-ai:trust ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial SOC 2 and ISO badges are vendor claims; issuer, report scope and validity were not independently checked. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect compliance material; vendor badges only, certificate/report scope and validity unverified; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - No evidence is certificate-verified. Cloud-provider certificates are not treated as Glean certificates. - iso_27001 — ISO 27001 with scope and validity? [partial]: Glean claims ISO 27001 on its security page. The actual certificate, issuer, service scope and validity dates were not obtained. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements. - soc2 — SOC 2 type, period and covered service? [partial]: Glean claims SOC 2 Type II, but auditor, examination period and exact covered service were not verified from a report. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? The public security page and trust.glean.com were checked; trust report content was inaccessible. BSI C5, independent pentest summaries and certificate/report validity were not established. - other_certifications — Which other certificates (27701, 42001, TISAX)? [partial]: The security page lists ISO 42001, HIPAA and TX-RAMP Level 2. These are vendor assertions, not verified certificates in this profile. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements. - report_access — How can customers obtain reports? [partial]: Security and accessibility material direct evaluators to the public Trust Center, whose report content was not readable without further access. Sources: glean:glean:security-page, glean:glean:accessibility, glean:glean:r2-core-entitlements. - pentest — Are independent penetration test summaries available? [unknown]: Are independent penetration test summaries available? The public security page and trust.glean.com were checked; trust report content was inaccessible. BSI C5, independent pentest summaries and certificate/report validity were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements, glean:glean:accessibility #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial New public 2026 ATTESTA renewals establish ISO27001 and ISO9001 validity to 31 May 2029; the public TÜV SÜD ISO42001 certificate runs to 6 March 2028. SOC2 Type2 is vendor-documented, with full report evidence NDA-gated. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=ATTESTA 10 June 2026 renewals; TÜV SÜD 7 March 2025 certificate; plan=Contracted Unique AI platform; platform assurance; certificates cover the named legal entity and stated scopes, not every module/provider availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Certificates name Unique AG, Zurich, Switzerland; module/provider coverage depends on the stated audit scope; os=not specified. Limitations: - Current ISO27001/9001 evidence is the 2026 renewal plus matching register entries; the stale website-linked PDF is not used to deny current certification. - SOC chronology and access process are vendor-documented, not a reviewed independent SOC report. Certificate scopes are entity-specific and not a universal module/provider assurance. - iso_27001 — ISO 27001 with scope and validity? [supported]: Inspected the 2026 ATTESTA Schweizer Zertifizierungsgesellschaft AG ISO27001:2022 certificate for Unique AG, registration 223-06-018.I. It covers software development/operation/trading/distribution and IT services, is issued 10 June 2026 after 4 June surveillance and expires 31 May 2029. The certificate-linked public register matches the number and expiry. The marketing-linked 2025 PDF is an older artifact, not the current renewal. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs. - soc2 — SOC 2 type, period and covered service? [partial]: The dedicated SOC page documents Type1 in December 2023 followed by Type2 in January 2025. This explains the historical Type1 references rather than proving an ongoing Type1-only state. Current Type2 status is a vendor claim; the auditor, actual report period and service/control scope were not inspected because the full report is NDA-gated. Sources: unique-ai:unique-ai:review2-soc. - c5 — BSI C5 attestation? [unknown]: No public BSI C5 attestation was retrieved from the certification pages/trust centre or targeted first-party search. - other_certifications — Which other certificates (27701, 42001, TISAX)? [partial]: Inspected ATTESTA ISO9001:2015 renewal 223-06-017.Q for the same Unique AG software/IT scope, expiring 31 May 2029, matched in the public register. Separately inspected TÜV SÜD South Asia ISO42001:2023 certificate 99 420 00001, valid 7 March 2025 to 6 March 2028, for development/deployment of financial-services SaaS using foundation or client models. Current full ISAE/FINMA report scope was not inspected. Sources: unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:iso42001. - report_access — How can customers obtain reports? [supported]: The ISO documentation provides public certificate downloads. It says the ISO27001 Statement of Applicability requires a valid NDA. The dedicated SOC page likewise makes the audit report/certificate available on request after NDA. No NDA or sales request was made. Sources: unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:review2-soc. - pentest — Are independent penetration test summaries available? [partial]: The public DPA describes internal/external security testing and the trust page describes tests/bug bounty. An independent penetration-test report, current scope or summary was not inspected. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:trust. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:iso42001, unique-ai:unique-ai:review2-soc, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai: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). #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Encryption, isolation and network controls are documented. Customer-managed keys are supported for Customer Hosted AWS; other key-custody scopes remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Protect encryption and single-tenant Glean Hosted; separately contracted Customer Hosted network configuration; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - encryption_at_rest — Is data encrypted at rest? [supported]: Deployment comparison documents AES-256 at rest and TLS in transit for both deployment modes. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements. - customer_managed_keys — Can the customer manage or hold the keys? [supported]: For Customer Hosted AWS, Glean supports KMS customer-managed encryption keys owned and controlled by the customer. The FAQ recommends default managed keys; Glean Hosted/GCP key custody and commercial prerequisites were not established. Sources: glean:glean:r4-aws-cmk-faq, glean:glean:r4-aws-key-control. - private_networking — Is private connectivity or IP restriction available? [supported]: IP-based access controls and private connectivity for on-prem connectors are documented; customer AWS supports local VPC endpoints. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements. - tenant_isolation — How are customers separated in shared SaaS? [supported]: Each deployment uses isolated single-tenant infrastructure, including the Glean-managed customer-cloud option. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: glean:glean:deploy, glean:glean:r2-core-entitlements, glean:glean:r4-aws-cmk-faq, glean:glean:r4-aws-key-control #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Deployment guides document encryption, isolated Single Tenant resources and optional IP filtering. Exact current MT PMK/CMK/HSM configuration and key sizes are not established across the conflicting pages. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted MT/ST encryption and optional customer-controlled self-hosting availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted Azure tenant/storage/backup region; actual key-vault/HSM location unverified; os=not specified. Limitations: - No exact RSA/HSM key size or actual MT PMK/CMK design is asserted. A customer-specific deployment/key diagram and key-vault region were not inspected. - Customer-generated imported keys held by Unique do not establish customer-exclusive key custody; full control is a separate self-hosting option. - encryption_at_rest — Is data encrypted at rest? [partial]: The compliance matrix documents encryption at rest and in transit across deployment options, with AES256/TLS1.2+ in its controls text. No exact current RSA key size is asserted: the ST architecture says 2048-bit RSA-HSM while the hosted retention page says 4096-bit. An implementation-specific key design was not retrieved. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention. - customer_managed_keys — Can the customer manage or hold the keys? [partial]: The infrastructure key guide allows a customer-generated key to be imported for a Unique-hosted Single Tenant, with Unique holding/managing it. It directs clients needing exclusive control of all storage keys to customer self-hosting. This is not HYOK or exclusive customer custody in Unique hosting. Actual MT PMK/CMK/HSM configuration is unknown because the key guide and hosted retention matrix disagree. Sources: unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-retention. - private_networking — Is private connectivity or IP restriction available? [partial]: The Single-Tenant WAF supports optional IP blocking. The separate SEE consumer endpoint is public TLS with optional allow-list and no standard private endpoint/peering. These are distinct scopes; other private-link options for the customer deployment were not verified. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export. - tenant_isolation — How are customers separated in shared SaaS? [supported]: The Single-Tenant architecture describes a separate customer landing zone under Unique's subscription, isolating its storage/processing from other customers. This documents that ST architecture, not the isolation configuration of every hosted or customer-managed instance. Sources: unique-ai:unique-ai:review2-single. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:security-export ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial General DPA confidentiality and provider/support access are documented; a specific German or Swiss professional-secrecy undertaking remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex public Terms/DPA confidentiality; no verified professional-secrecy-specific package; add_ons=none stated; deployment_mode=not specified; region=Selected hosting/provider regions; listed India support affiliate; no DE/CH-specific undertaking verified; os=not specified. Limitations: - DPA confidentiality and no-training provisions alone do not establish a professional-secrecy undertaking. - No legal suitability or compliance conclusion. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: Glean DPA section4 binds authorized personnel to confidentiality or statutory duties, but no signed/signon German §203 StGB or Swiss Art321 StGB professional-secrecy undertaking was retrieved. General DPA confidentiality is not treated as that undertaking. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: DPA section9 requires no-less-protective written subprocessor obligations and necessary access. No flow-down of a specific §203/Art321 professional-secrecy undertaking was established. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No publicly documented professional-secrecy-specific plan, dedicated package, paid add-on, minimum or regional contract entitlement was established in legal pages, administration docs, pricing or targeted first-party search. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Contractually authorized Glean personnel and necessary subprocessors may process customer personal data; the processor list names India remote support/security/debugging and model/hosting providers. Model routes receive prompts/context for inference. Exact plaintext privileges, exceptional support approval, provider human-access rights and their differences by key/deployment mode are not fully established. Sources: glean:glean:dpa-confidentiality, glean:glean:subprocessors, glean:glean:key-matrix, glean:glean:ai-addendum, glean:glean:r2-core-entitlements. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: A public DPA, AI Addendum, deployment docs and processor list were retrieved. No public §203/Art321 contract template, dedicated professional-secrecy data-flow statement or professional-body guidance for this offer was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:dpa-confidentiality, glean:glean:subprocessors, glean:glean:key-matrix, glean:glean:ai-addendum, glean:glean:r2-core-entitlements #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unique documents general staff/external-party access controls and customer-controlled on-premises access. A professional-secrecy undertaking under § 203 StGB or Art. 321 StGB, its subprocessor flow-down and qualifying plan/add-on remain unverified. Financial-sector banking-secrecy amendments are recorded separately under DATA-06. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI; profession-specific eligibility and fees unpublished; add_ons=none stated; deployment_mode=not specified; region=Contracted hosting jurisdiction; customer-controlled on-premises access described separately from Unique-hosted access; os=not specified. Limitations: - No executed professional-secrecy undertaking or § 203 / Art. 321 contract was inspected. General DPA confidentiality is not treated as such an undertaking. - The M744 professional-secrecy wording appears in a banking-secrecy/financial-services framework; no inference is made to lawyers, doctors, auditors or tax advisers. - Customer-controlled on-premises access does not establish the same access conditions for Unique-hosted deployments or all model-provider routes. Full plaintext-access mapping remains unknown. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No public Unique AI-specific § 203 StGB or Art. 321 StGB secrecy undertaking covering staff was located in the DPA, compliance documentation or targeted first-party search on 21 October 2026. The DPA confidentiality commitment alone does not establish a professional-secrecy undertaking. No executed or negotiated customer agreement was inspected. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The DPA says employees, contractual subprocessors and other service providers are bound to confidentiality of sensitive information. A professional-secrecy-specific obligation extending through the subprocessor/model-provider chain was not verified. The Microsoft M744 banking-secrecy amendment mentioned in the financial-services framework is not counted as evidence of § 203 / Art. 321 coverage for professional secrecy holders. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No qualifying professional-secrecy plan, dedicated offering, add-on tariff or named eligibility rule was located. The documented financial-services amendments and general deployment choices do not establish a separate § 203 / Art. 321 offering. Contract-specific terms and fees remain unknown. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: DPA Appendix B permits employees or external parties access to personal/confidential information on a need-to-know basis. For on-premises support, customers control remote connections and Unique staff cannot access a customer system without customer knowledge or full active participation. The on-premises architecture also allows operation without any Unique access under customer control. These sources do not exhaustively identify plaintext access at each hosted subprocessor/model provider or profession-specific access conditions. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: A public DPA and on-premises architecture describe confidentiality and access controls, but no profession-specific secrecy template or professional-body guidance was located. The compliance page describes Microsoft M453/M744/M329 in a financial-services context; those banking/FINMA disclosures belong to DATA-06 and do not establish the missing professional-secrecy contract. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance ## 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Glean publishes pricing mechanics and usage tables, while contracted seat fees remain quote-only. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Unspecified contracted plan unless Core Suite, Enterprise Flex, key mode or add-on is named below; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - pricing_unit — What is the pricing unit? [supported]: Core Suite is per user/month plus committed Model Hub Usage. Enterprise Flex combines seats with pooled FlexCredits; legacy Enterprise terms differ. Sources: glean:glean:core-price, glean:glean:flex-price. - list_prices — What are list prices per plan, with date and currency? [partial]: On 2026-10-21 no numerical Core Suite/Enterprise Flex seat or platform fee was established. Public model token-rate and credit-consumption tables are available; they are not a complete subscription quote. Sources: glean:glean:core-price, glean:glean:flex-price. - included_usage — What usage is included? [partial]: Core Suite includes platform/search and human-scale APIs in seats; LLM APIs and advanced work consume model usage. Flex uses plan-specific included capabilities and shared credits. Sources: glean:glean:core-price, glean:glean:flex-price. - add_ons — Which features cost extra? [partial]: Protect+ is an add-on and Premium Support is paid; Model Hub usage is separate. Public add-on seat/contract fees were not established. Sources: glean:glean:protect, glean:glean:sla. - overage — What do usage beyond limits and premium models cost? [partial]: Core Suite usage follows provider/model API rates with an upfront commitment; machine-scale API use may cost extra. Flex uses credit rate cards. Currency price per contracted FlexCredit is unverified. Sources: glean:glean:core-price, glean:glean:flex-price. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:core-price, glean:glean:flex-price, glean:glean:protect, glean:glean:sla #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Applicable current platform pricing unit, list tariff, included usage and overages remain unknown. A separately documented Single-Tenant SEE consumption/engineering charge is retained; legacy sales-conversation terms are excluded. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform subscription and separately enabled Single-Tenant SEE availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE scope only where contracted; deployment_mode=not specified; region=Vendor currency and applicable invoicing terms not established for the platform; SEE guide separately quotes indicative CHF consumption; os=not specified. Limitations: - The SEE cost finding is scoped only to that Single-Tenant integration. It does not price the platform subscription or all modules. - The 2023 sales-conversation ToS is excluded as evidence of current Unique AI commercial terms; no sales quote or private contract was requested. - pricing_unit — What is the pricing unit? [unknown]: No applicable current platform MSA/order form or tariff establishing seat, active-user, platform or usage pricing units was retrieved. The public 18 October 2023 ToS defines a sales-conversation intelligence service, so its subscription/Order Form clauses are not applied to current Unique AI. - list_prices — What are list prices per plan, with date and currency? [unknown]: No applicable current platform list tariff, tier names or primary invoicing currency was retrieved from platform/contract documentation or targeted first-party search. - included_usage — What usage is included? [unknown]: No applicable current platform agreement specifying included model tokens, storage or module allowances was publicly retrieved. - add_ons — Which features cost extra? [partial]: Single-Tenant SEE passes through Azure consumption without markup; guide observes CHF20-50/month/environment, not a fixed quote, with initial engineering at agreed rates. Other module charges are unpublished. Sources: unique-ai:unique-ai:security-export. - overage — What do usage beyond limits and premium models cost? [unknown]: No applicable current platform overage or premium-model sales tariff was retrieved. Cost-management model estimates are not substituted for a customer sales tariff. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Core Suite publishes model tariffs, but no public unique routine Auto model or fixed fee; a separate direct-provider Customer Key component is calculable. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents, Customer Hosted managed GCP or AWS tenant; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Universal Model Key usage unpriced without a fixed/recommended routine model; separate Customer Key direct-API proxy; Enterprise Flex quote/pool unknown; add_ons=none stated; deployment_mode=not specified; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - The priced Customer Key component is an assumption for direct provider payment, not a complete Glean price or a forecast of Auto routing. - No signed order, fixed fee, actual tenant defaults or task usage fixture. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4,2026-10-21:12 months exVAT,list prices,no invented discounts;60% light100/30% regular400/10% power1500 messages/user/month =>330;3000 input+600 output tokens/message. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Direct-provider Customer Key comparison uses gpt-6-luna effort none atUSD0.10 input/USD0.50 output per1M,no cache =>USD2.376/user/year. This proxy is not a Glean Universal Model Key tariff/default. For200 Customer Key users: identified direct-model component USD475.20/EUR423.72/CHF391.39 + unknown Core Suite seat fee, Glean-family usage, support/cloud costs. Universal Model Key total and Enterprise Flex total remain unknown. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-customer-default-example, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort, glean:glean:fx-ecb. - cost_1000 — Year-one cost at 1,000 users? [partial]: Same v1.4 assumptions:1000 Customer Key users, identified direct-model component USD2376/EUR2118.59/CHF1956.94 + unknown seat/Glean-family/support/cloud costs. Not an enterprise quote; Universal Model Key and Flex totals remain unknown. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort, glean:glean:fx-ecb. - cost_5000 — Year-one cost at 5,000 users? [partial]: Same v1.4 assumptions:5000 Customer Key users, identified direct-model component USD11880/EUR10592.96/CHF9784.71 + unknown seat/Glean-family/support/cloud costs. Not an enterprise quote; Universal Model Key and Flex totals remain unknown. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort, glean:glean:fx-ecb. - variable_share — Which part depends on usage? [partial]: Core Suite publishes input/output tariffs. Universal Model Key defaults to Balanced Auto, a policy choosing model and effort per request; recommendations are shown in the admin UI, not as a unique public routine model. The Customer Key guide calls GPT5.6 Luna an example, not a recommendation. Under v1.4, vendor-billed usage remains unknown; only the separate direct-API proxy is costed. Enterprise Flex has different mode/credit accounting. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-customer-default-example, glean:glean:r2-flex-entitlements, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort. - unknown_parts — Which costs could not be priced? [supported]: Unknown: seat/platform quotes, Universal Model Key realized model mix and Auto/tool overhead, FlexCredit purchase price and task consumption, Glean-family calls on Customer Key, Protect+/support fees, cloud operations and implementation. No zero fixed fee, fictitious discount or vendor-billed proxy substitution. Exchange rate is known and explicitly stated; quote-only total is not calculated. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-flex-entitlements, glean:glean:deploy, glean:glean:fx-ecb. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:r2-core-entitlements, glean:glean:r2-auto-policy-and-cloud-conflict, glean:glean:r2-customer-default-example, glean:glean:r2-direct-provider-proxy, glean:glean:r2-proxy-lowest-effort, glean:glean:fx-ecb, glean:glean:r2-flex-entitlements, glean:glean:deploy #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21. Public enterprise pricing is insufficient for the required 200/1,000/5,000-user annual totals. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - variable_share — Which part depends on usage? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - unknown_parts — Which costs could not be priced? [supported]: Subscription/order pricing, usage billing, provider contracts, deployment operation, connectors, execution, training and support charges are not publicly priced. SEE consumption example alone cannot price the platform. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export, unique-ai:unique-ai:ecb-fx ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public material supports product evaluation, but no unassisted business trial was established. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex prospective customer evaluation; public demo path, no verified self-serve trial entitlement; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - Core Suite/Enterprise Flex trial and evaluation entitlements were not publicly verified; a demo CTA is not proof of a mandatory sales gate. - free_tier — Is there a free tier for business use? [unknown]: Is there a free tier for business use? The live product/security site, documentation setup and pricing guides were checked. No public business free-tier entitlement, self-serve trial terms, card/duration/seat limits or SSO/connector trial scope was established. No sales contact or account registration was attempted. - self_serve_trial — Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? The live product/security site, documentation setup and pricing guides were checked. No public business free-tier entitlement, self-serve trial terms, card/duration/seat limits or SSO/connector trial scope was established. No sales contact or account registration was attempted. - trial_scope — Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? The live product/security site, documentation setup and pricing guides were checked. No public business free-tier entitlement, self-serve trial terms, card/duration/seat limits or SSO/connector trial scope was established. No sales contact or account registration was attempted. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Public Glean pages route prospective customers to Get a demo; meaningful tenant provisioning may require commercial access. This is not proof that every trial is sales-only. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:security-page, glean:glean:r2-core-entitlements #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public route is demo/evaluation by arrangement; self-service trial conditions were not established. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - free_tier — Is there a free tier for business use? [unknown]: Is there a free tier for business use? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - self_serve_trial — Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - trial_scope — Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Current platform CTA requests a demo; public baseline ToS says Unique may offer evaluation at its discretion. This does not prove every meaningful evaluation is sales-gated. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:terms ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Contract periods and fees depend on orders, with cancellation restricted during the subscription term. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex under Order Form and public Terms; seat commitments/prices and selected currency contractual; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - minimum_commitment — What seat or spend minimum applies? [unknown]: What seat or spend minimum applies? Terms and pricing guides were checked; minimum seat/spend commitment and plan-specific currency invoicing remain unpriced. - contract_length — What contract lengths are offered? [partial]: Terms define Subscription Term through the Order Form. No universal monthly or annual term is specified. Sources: glean:glean:terms, glean:glean:r2-core-entitlements. - cancellation — How can the contract be cancelled or reduced? [supported]: Except contractual causes and remedies, customers cannot cancel during the subscription term; each order ends at expiry unless otherwise stated. Sources: glean:glean:terms, glean:glean:r2-core-entitlements. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Terms default to USD or the currency in the order and allow Glean affiliates/resellers. CHF/EUR invoicing by a European entity was not confirmed. Sources: glean:glean:terms, glean:glean:r2-core-entitlements. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified: public pricing units and consumption tables, but subscription fees, minimum commitments and purchased-credit prices need an order/quote. Sources: glean:glean:core-price, glean:glean:flex-price, glean:glean:terms, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:terms, glean:glean:r2-core-entitlements, glean:glean:core-price, glean:glean:flex-price #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Current platform minimums, term, cancellation and local invoicing remain unknown because the applicable agreement was not publicly retrieved. Current documentation makes legal contracts available on request; legacy sales-conversation renewal clauses are excluded. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform commercial agreement; actual agreement not inspected availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CHF/EUR invoicing and legal entity for a specific platform contract unverified; os=not specified. Limitations: - No current customer agreement or sales quote was requested. Contract availability on request does not establish price, term or cancellation conditions. - minimum_commitment — What seat or spend minimum applies? [unknown]: No current platform seat/spend minimum was established from the public contract-access and platform pages. - contract_length — What contract lengths are offered? [unknown]: No applicable current Unique AI agreement establishing subscription duration, renewal term or notice period was retrieved. The 2023 sales-conversation service term is not applied. - cancellation — How can the contract be cancelled or reduced? [unknown]: Current Unique AI cancellation, refund, seat-reduction and nonrenewal rules were not retrieved. The 30-day renewal notice and quantity restrictions from the sales-conversation ToS are excluded. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: CHF/EUR invoice currency, billing entity and local invoicing eligibility for a current platform contract were not established. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: The current governance framework says legal contracts and end-user T&Cs are available on request. No applicable public platform list tariff or complete commercial agreement was retrieved. This records an access/transparency gap, not a price or a customer-specific commitment. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial The hosted platform is provided under restricted commercial terms; public SDK licences are separate. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite/Enterprise Flex proprietary hosted/managed Service under Terms; no public core-source licence inferred; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - licence_type — Which licence applies to each component? [supported]: Terms grant subscription access and prohibit deriving source code, modifying or redistributing the Service. This establishes a proprietary service contract, not an OSI licence for the platform. Sources: glean:glean:terms, glean:glean:r2-core-entitlements. - branding_restrictions — Do licence terms restrict branding or user counts? [supported]: Terms prohibit removing proprietary notices and limit use to licensed users/orders; no numerical standard user cap is given. Sources: glean:glean:terms, glean:glean:r2-core-entitlements. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Platform terms and the public gleanwork organization were checked; a complete component licence inventory or separate open/closed enterprise edition split was not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:terms, glean:glean:r2-core-entitlements #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public reference repository uses restricted Unique License v1, while the Python SDK has an explicit MIT exception. Hosted platform component terms and enterprise-edition boundaries remain unverified. Availability: source-only Delivery: native Scope: surfaces=Unique API and Python SDK, Unique AI Chat and administration; version=Unique-AG/ai commit afa596c9b4b0231895ff70f44029a9a525f746e9; plan=Public reference-code and Python SDK licences; current contracted Unique AI client/server/connector agreement remains unavailable; add_ons=none stated; deployment_mode=not specified; region=Public Unique License v1 specifies Swiss law and Zurich venue; this is not a hosted-service residency claim; os=not specified. Limitations: - The MIT exception applies to unique_sdk, not every directory or the hosted platform. - Root reference-code terms are not substituted for customer platform branding, seat or enterprise-edition conditions. - The 2023 sales-conversation service ToS remains excluded. - licence_type — Which licence applies to each component? [partial]: The public Unique-AG/ai repository at afa596c9b4b0231895ff70f44029a9a525f746e9 defaults to Unique License v1, which restricts commercial use, distribution and modification without written approval. The unique_sdk directory is an explicit MIT exception, confirmed by LICENSE and package metadata. This is a component-level source-available/MIT distinction; current hosted client/server/connector customer terms and a full dependency inventory remain unknown. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Unique License v1 requires written approval to modify or redistribute covered reference code; the MIT SDK exception requires retention of copyright/licence notices. A current hosted-platform white-label/logo-removal obligation or a numerical user cap is not established by these public component licences. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Current closed/open enterprise-edition boundaries were not established from an applicable component licence inventory. Public SDK/repository availability is not proof of the whole platform licence. Rechecked 2026-10-26 in Unique AI governance framework: contract access, Terms and Conditions Administration. No current customer MSA, quote, private schedule or gated contract was requested. The differently scoped 2023 sales-conversation ToS remains excluded. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin, unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026, unique-ai:unique-ai:review2-governance-20261026, unique-ai:unique-ai:review2-terms-admin-20261026 ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workflow agent configurations are portable as JSON; full tenant chat/knowledge export remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Governance import/export in seat; limited Auto ZIP export and complete organization exit separately unverified; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - Core Suite includes agent import/export, but limited Auto ZIP rollout and complete tenant-export entitlements remain unverified. - chat_export — Can admins export all chats? [unknown]: Can admins export all chats? Agent export and contractual termination pages were checked. No trial admin export was run; all-chat export, knowledge/source completeness and a post-termination retrieval window were not established. - assistant_export — Can assistants and prompts be exported in a reusable format? [supported]: Workflow-mode agent configuration exports to JSON and imports into another deployment; missing target tools must be reconfigured. Auto-mode ZIP export is limited availability for admins. Sources: glean:glean:builder, glean:glean:r2-core-entitlements. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Agent export and contractual termination pages were checked. No trial admin export was run; all-chat export, knowledge/source completeness and a post-termination retrieval window were not established. - export_format — Are formats documented and machine-readable? [supported]: Workflow exports use JSON; limited Auto exports contain spec.yaml and instructions.md in ZIP. Admin logs have CSV export. Sources: glean:glean:builder, glean:glean:audit, glean:glean:r2-core-entitlements. - post_termination_window — How long can data be retrieved after termination? [unknown]: How long can data be retrieved after termination? Agent export and contractual termination pages were checked. No trial admin export was run; all-chat export, knowledge/source completeness and a post-termination retrieval window were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:builder, glean:glean:r2-core-entitlements, glean:glean:audit #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Authorised content/report export exists, but full assistant/knowledge portability is unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run. - chat_export — Can admins export all chats? [partial]: Detailed interaction export includes user prompts/answers over a chosen period with privacy settings. Completeness across files, agent state and all historical chats was not tested. Sources: unique-ai:unique-ai:analytics. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run. - export_format — Are formats documented and machine-readable? [partial]: Model usage CSV and detailed analytics exports are documented. DPA promises return in existing format, not a universal reusable assistant/knowledge format. Sources: unique-ai:unique-ai:cost, unique-ai:unique-ai:analytics, unique-ai:unique-ai:dpa. - post_termination_window — How long can data be retrieved after termination? [partial]: Baseline ToS 11.4 offers recorded-call download/export on written request within 30 days; that does not establish a chat/assistant/KB exit window. DPA return is within reasonable time. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost, unique-ai:unique-ai:dpa, unique-ai:unique-ai:terms ### 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. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Support tiers are documented; a credited 99.9% SLA applies only to paid Premium Support. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Unspecified contracted plan unless Core Suite, Enterprise Flex, key mode or add-on is named below; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - support_channels — Which support channels are available on each plan? [supported]: The support portal is the channel eligible for response targets; Standard Support is included and Premium paid. Other channels do not have trackable SLA response times. Sources: glean:glean:sla. - support_languages — Is support available in German, French or Italian? [partial]: The SLA explicitly provides a Japanese support option for Japan and names California/Bangalore operations; German/French/Italian language commitments were not established. Sources: glean:glean:sla. - regional_presence — Is there a DACH or Swiss entity, team or partner? [unknown]: Is there a DACH or Swiss entity, team or partner? The SLA, site and status.glean.com were checked. The status URL returned HTTP 403, so incident history was not verified; DACH/Swiss support presence was not established. - uptime_sla — Is there an uptime SLA with credits? [supported]: Paid Premium Support has 99.9% monthly uptime. Credits are 10% below 99.9% down to 99.0%, and 20% below 99.0%, subject to exclusions and claim deadlines. Sources: glean:glean:sla. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? The SLA, site and status.glean.com were checked. The status URL returned HTTP 403, so incident history was not verified; DACH/Swiss support presence was not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:sla #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise support and a public multitenant status page are available; response times are contracted. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established. - support_channels — Which support channels are available on each plan? [supported]: Enterprise email and three-layer dedicated support escalation through customer team, CS and engineering. Hours/responses depend on SLA; extended-hours contract is extra. Sources: unique-ai:unique-ai:support. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: Unique AI AG lists Zürich, Unique Germany GmbH Berlin, plus UK/US/Singapore entities. Sources: unique-ai:unique-ai:contact. - uptime_sla — Is there an uptime SLA with credits? [partial]: Support docs defer hours and response times to SLA contract; no public uptime/credit schedule was obtained. Baseline terms only promise commercially reasonable availability efforts. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:terms. - status_page — Is there a public status page with history? [supported]: status.prod.unique.app publicly shows component/uptime history. Support docs scope it to multitenant accounts, not every dedicated environment. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:status. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:contact, unique-ai:unique-ai:terms, unique-ai:unique-ai:status ### VEN-08: Onboarding, training and adoption Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings. #### Glean Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public training and templates exist; exact onboarding-service entitlements and prices remain open. Availability: generally-available Delivery: native Scope: surfaces=Glean Hosted web Assistant and Agents; version=Public documentation retrieved 2026-10-21; deployed version not observed; plan=Core Suite Agent Library/templates and public Academy links; contracted onboarding and Premium Support separately scoped; add_ons=none stated; deployment_mode=dedicated-instance; region=Selected hosting and model-provider regions; no blanket EU or Swiss processing claim; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - Exact Academy access, included onboarding, language coverage and support/professional-services entitlement under the customer Order Form remain unknown. - onboarding_service — Is guided onboarding included? [unknown]: Is guided onboarding included? Academy, agent library, SLA and legal service links were checked; included vendor-led onboarding, champion/adoption programme terms and localized end-user training were not established. - user_training — Is end-user training offered, in which languages? [partial]: Glean documentation links self-paced Agent Builder training through Glean Academy; German/French/Italian course availability was not established. Sources: glean:glean:agents, glean:glean:r2-core-entitlements. - use_case_library — Are role-based use cases and templates provided? [supported]: The internal Agent library and documented templates support reusable role/task examples. Sources: glean:glean:library, glean:glean:r2-core-entitlements. - adoption_programme — Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Academy, agent library, SLA and legal service links were checked; included vendor-led onboarding, champion/adoption programme terms and localized end-user training were not established. - service_cost — Which services cost extra? [partial]: Premium Support is priced separately under the SLA. The legal index directly lists the Technical Services Addendum and named Outcomes Packages. Those listings do not establish included onboarding or complete professional-services fees. Sources: glean:glean:sla, glean:glean:r3-legal-index, glean:glean:r2-core-entitlements. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: glean:glean:agents, glean:glean:r2-core-entitlements, glean:glean:library, glean:glean:sla, glean:glean:r3-legal-index #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The vendor markets forward-deployed delivery and structured training; inclusion and cost remain unpriced. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published. - onboarding_service — Is guided onboarding included? [partial]: Homepage markets embedded forward-deployed experts helping business/IT ship use cases; exact licence-included rollout scope is contracted. Sources: unique-ai:unique-ai:homepage. - user_training — Is end-user training offered, in which languages? [partial]: Vendor homepage describes structured programmes teaching users to use/build/scale; current languages and course entitlement are not specified. Sources: unique-ai:unique-ai:homepage. - use_case_library — Are role-based use cases and templates provided? [supported]: Public documentation has finance-role workflows, Chat/Conduct guidance, configurable Suggested Prompts and agent examples. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct. - adoption_programme — Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published. - service_cost — Which services cost extra? [unknown]: Which services cost extra? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:homepage, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct ## Sources ### glean:glean:models Supported LLMs. The Model Hub lists text and image models, manual choice and Auto routing, with provider availability dependent on key and cloud. - URL: https://docs.glean.com/administration/llms - Locator: Supported models; availability by hosting environment and provider - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:key-matrix Feature availability by LLM key, provider, and cloud. Customer Key restricts cloud-provider routes and excludes Meeting Notes and podcast artifacts; some defaults must use the same provider. - URL: https://docs.glean.com/administration/llm-key-feature-availability - Locator: Provider and feature matrices - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:uploads Upload files in Assistant. Uploads support Office documents, PDFs, images and text, with context-dependent file caps and OCR prerequisite. - URL: https://docs.glean.com/user-guide/assistant/file-upload - Locator: Formats; upload limits; security; limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:r2-core-entitlements Glean Core Suite entitlements and Model Hub rates. Core Suite separates included platform seats from Model Hub usage, names client/API surfaces, and publishes token rates. - URL: https://docs.glean.com/glean-core-suite-pricing - Locator: Seat capabilities, surfaces, APIs, Model Hub Usage and rate table updated10/20/2026 - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### glean:glean:r3-october-rollout-migration October 15, 2026 release, version 563. Auto policies require rollout opt-in from October 15 with GA scheduled October 29; Brave is the new search default and existing OpenAI search migrates from October 19. - URL: https://docs.glean.com/release-notes/releases/2026-10-15-october-release - Locator: AI & Model Updates, Auto mode policies; Deprecations & Sunsets, OpenAI Web Search - Evidence kind: documented - Source date: 2026-10-15 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:models Unique LLM availability overview. Lists contract-dependent provider/model availability, region SKUs, dated additions and retirements; CH Phoeniqs remains QA-only. - URL: https://docs.unique.ai/administrators/models-llm-management/how-we-evaluate-models/llm-availability-overview - Locator: Per-client availability; Azure/LiteLLM/Phoeniqs matrices; Recent changes - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:agent Unique AI space configuration. Documents admin instructions, configured model/tools, knowledge binding, prompts and people/group Can chat/Can manage access. - URL: https://docs.unique.ai/administrators/space-management/create-spaces/unique-ai-space - Locator: Models; sources/tools; sharing; publishing - Evidence kind: documented - Source date: 2026-06-18 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:conduct Unique AI Conduct. Documents autonomous Python/Bash work, visible steps, approvals and stop, with per-chat files and restricted egress. - URL: https://docs.unique.ai/users/spaces/unique-ai-conduct - Locator: GA release 2026.40; execution UI; limitations - Evidence kind: documented - Source date: 2026-09-30 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:release42 Unique release 2026.42. Hosted release 14 October 2026 makes chat sharing and Context Memory GA, labels Scheduled Tasks experimental, changes protected-file ingestion and documents current model additions/migrations. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/release-notes-and-calendar/release-notes-2026/release-2026-42 - Locator: Release Overview; Chat Platform; RAG; Unique AI; Language Model - Evidence kind: documented - Source date: 2026-10-14 - Retrieved: 2026-10-21 ### glean:glean:deprecation Model deprecation. Customer Key deprecation emails are specified at 60 and 15 days, with removal and replacement behavior. - URL: https://docs.glean.com/administration/model-deprecation - Locator: Customer Key notice schedule; deprecated models - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:release October 15, 2026 release notes. Glean publishes dated release notes covering product and model changes. - URL: https://docs.glean.com/release-notes/releases/2026-10-15-october-release - Locator: Release entry - Evidence kind: documented - Source date: 2026-10-15 - Retrieved: 2026-10-21 ### glean:glean:r2-flex-entitlements Glean Enterprise Flex entitlements. Enterprise Flex separates seat allowances, metered client APIs/agent runs, included platform governance and annual Protect+/support add-ons. - URL: https://docs.glean.com/glean-enterprise-flex-pricing - Locator: Seats, Developer Tools, Platform, Protect+ and Premium Support - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:r2-auto-policy-and-cloud-conflict Configure LLMs in the Model Hub. Balanced is the default Auto policy with per-request model choice; the AWS Vertex note conflicts with the supported-provider matrix and GCP-only Vertex setup heading. - URL: https://docs.glean.com/administration/configure-llms - Locator: Auto policies; AWS Vertex note; provider setup headings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:customllm Custom LXM connection. Documents operator-created external model endpoints, API/OAuth credentials and model groups. - URL: https://docs.unique.ai/it-operators/custom-models-and-embeddings/connect-custom-lxm-llm-with-unique-ai - Locator: Technical insight; Create and Connect; Security - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:code Code Execution. Documents Azure Responses API Python execution, downloadable outputs, no outbound internet and model/file restrictions. - URL: https://docs.unique.ai/administrators/space-management/tools/code-execution - Locator: Compatibility; output; limitations; governance - Evidence kind: documented - Source date: 2026-07-30 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:compliance Compliance Layer 3.0. Describes FINMA/bank-secrecy/CH-DPA Microsoft amendments and deployment-specific assurance limitations. - URL: https://docs.unique.ai/security-and-compliance/compliance/compliance-layer-3-0 - Locator: Legal framework; FSI amendments; deployment feature matrix - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### glean:glean:r4-open-model-inference Glean open models by region. Universal Model Key open models are served through LLM providers under zero-retention agreements. Creator-region grouping is not inference location; the page states these models are hosted in the US. - URL: https://docs.glean.com/administration/open-models-by-region - Locator: Creator-region controls; Operational details - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:embeddings Custom embedding models. Documents custom embedding endpoints, one model per organisation and mandatory re-embedding after model/dimension changes. - URL: https://docs.unique.ai/it-operators/custom-models-and-embeddings/usage-or-change-of-custom-embedding-model - Locator: Setup; configuration; re-embedding - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:onpremsecurity On-premises security architecture. Documents full customer control and possible operation without Unique access, with customer models/infrastructure. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/on-premise-tenant/security-architecture-on-premises - Locator: Overview; custom setup - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:operators IT operator documentation overview. Describes dedicated Unique-managed, customer-cloud and full air-gapped on-premise modes. - URL: https://docs.unique.ai/it-operators - Locator: Supported deployment models - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-code Code Execution. The page allows selected Knowledge Base files to be preloaded with additionalUploadedDocuments. Its compatibility list includes Azure and LiteLLM OpenAI Responses-capable IDs despite Azure-only introduction/limitations. Azure sandbox controls are not proof of the LiteLLM execution region. - URL: https://docs.unique.ai/administrators/space-management/tools/code-execution - Locator: Functionality; Limitations; All available models; Security & Governance; additionalUploadedDocuments - Evidence kind: documented - Source date: 2026-07-30 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-models Unique LLM availability overview. The model catalogue separates provider routes, region/SKU choices and QA-only Swiss Phoeniqs. It is a technical availability inventory, not a complete legal subprocessor schedule. - URL: https://docs.unique.ai/administrators/models-llm-management/how-we-evaluate-models/llm-availability-overview - Locator: Provider and region matrices; Phoeniqs Model Service; recent changes - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### glean:glean:model-controls Exclude or restrict models. Admins can restrict eligible models by department or IdP group, but default models cannot be restricted and hiding premium pickers does not block Auto. - URL: https://docs.glean.com/administration/model-exclusion - Locator: Department and team allow-lists; premium-model toggle - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:model-config Configure LLMs in the Model Hub. Admins configure default models and department Auto policies. - URL: https://docs.glean.com/administration/configure-llms - Locator: Default models and Auto mode policies - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:restrictions Restrict LLM access to content. Admins can exclude connectors, containers and documents from LLM use; changes may take up to one hour. - URL: https://docs.glean.com/administration/assistant/configuration/content-restrictions - Locator: Exclusion and inclusion rules - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:limits Set usage limits and alerts. Core Suite and Enterprise Flex limits can alert or block later billable usage after the current run finishes; team defaults are not pooled budgets. - URL: https://docs.glean.com/administration/management/usage/set-usage-limits-and-alerts - Locator: Enforcement; organization, user, team and agent limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:cost Model usage and cost management. Documents off-by-default estimated usage dashboards and enforced daily company/group/user model-call limits. - URL: https://docs.unique.ai/administrators/models-llm-management/model-usage-and-cost-management - Locator: Beta flags; daily limits; cost calculation; CSV - Evidence kind: documented - Source date: 2026-07-21 - Retrieved: 2026-10-21 ### glean:glean:analysis Data analysis overview. Uploaded spreadsheets can be analyzed in per-session sandboxes; indexed files can be truncated, and abuse-flagged files may be retained up to 30 days. - URL: https://docs.glean.com/administration/assistant/data-analysis/about-data-analysis - Locator: Known limitations; code interpreter security - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:files Upload and Chat limits. Specifies 512 MB/file, 30 files/batch, default forced retrieval for selected uploads and configurable expiry. - URL: https://docs.unique.ai/users/upload-chat-file-limits-how-large-documents-are-handled - Locator: Production limits; retrieval; expiry - Evidence kind: documented - Source date: 2026-06-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:filetypes Supported file types. Lists common Office/PDF/text formats and general ingestion limitations that differ from the newer chat-specific limits. - URL: https://docs.unique.ai/users/supported-file-types - Locator: Types; exceptions; ingestion quality - Evidence kind: documented - Source date: 2026-05-09 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:file-ingestion-20261026 Unique file ingestion administration. Base ingestion lacks scanned-PDF OCR. MDI supports image-based PDFs; Docling has partial support. MDI must be provisioned and enabled per folder or chat Space, and the guide distinguishes experimental image-content extraction and deprecated agentic ingestion. - URL: https://docs.unique.ai/administrators/knowledge-base-for-admins/file-ingestion - Locator: Ingestion overview capability table; Enable MDI; Enable MDI for Upload in Chat - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### glean:glean:projects Organize content with Projects. Projects persist chats and documents, are private by default and replace Collections through a gradual rollout. - URL: https://docs.glean.com/user-guide/knowledge/projects/how-projects-work - Locator: Create; sharing; access; migration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:kbpermissions Knowledge scope permissions. Describes query filtering by user/group scopes, but older SharePoint permission statements differ from the newer connector guide. - URL: https://docs.unique.ai/administrators/knowledge-base-for-admins/folder-scope-access-permissions - Locator: Scopes; source integration limits - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### glean:glean:deploy Glean deployment models. Both modes use single-tenant infrastructure operated by Glean; Customer Hosted runs in customer GCP or AWS accounts with Glean support access. - URL: https://docs.glean.com/get-started/prepare/about-deployment - Locator: Glean Hosted; Customer Hosted; comparison table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:connectors Connectors hub. The official catalog lists M365, Google, Atlassian and other business-system connectors. - URL: https://docs.glean.com/connectors - Locator: Native connector catalog - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:sharepoint SharePoint overview. SharePoint supports indexed and live retrieval; indexing uses certificate-based application permissions and admin consent. - URL: https://docs.glean.com/connectors/native/sharepoint/about - Locator: Access patterns; permissions and security - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:onedrive OneDrive overview. OneDrive offers indexed and live search under the Microsoft 365 parent connector, with certificate-based application permissions. - URL: https://docs.glean.com/connectors/native/onedrive/about - Locator: Access patterns; permissions and security - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:outlook Outlook overview. The Outlook connector supports access to Outlook content through Glean. - URL: https://docs.glean.com/connectors/native/outlook/about - Locator: Connector overview - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:teams-connector Teams overview. Teams indexes channels and optionally private and meeting chats, with mirrored membership checked at query time. - URL: https://docs.glean.com/connectors/native/teams/about - Locator: Supported content; permissions and security - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:drive Google Drive overview. Drive content and permissions are indexed with directory delegation; documented activity and group-sync schedules are distinct. - URL: https://docs.glean.com/connectors/native/gdrive/about - Locator: Permissions; crawling and updates - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:gmail Gmail overview. Gmail has indexed search with source-specific crawl scope and controls. - URL: https://docs.glean.com/connectors/native/gmail/about - Locator: Indexed content and scope - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:gateway Set up external tools with MCP Gateway. Admins proxy external MCP servers and custom tools with role and group controls and OAuth 2.1. - URL: https://docs.glean.com/administration/platform/mcp/external-gateway-tools - Locator: Prerequisites; external servers; access control - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:sharepoint SharePoint connector. Documents periodic indexed sync, optional content-and-permissions mode, site selection and absent label-level detection. - URL: https://docs.unique.ai/it-operators/integrations-connectors/sharepoint-connector - Locator: Modes; permission sync; limitations - Evidence kind: documented - Source date: 2026-07-06 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:confluence Confluence connector. Documents Cloud/Data Center content sync without source-permission synchronisation. - URL: https://docs.unique.ai/it-operators/integrations-connectors/confluence-connector - Locator: Requirements; sync; limitations - Evidence kind: documented - Source date: 2026-06-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:platform-overview-20261026 Unique platform overview. The platform architecture names Google Drive and Salesforce among knowledge sources, alongside SharePoint/OneDrive, Confluence and Teams/Outlook. It does not provide per-connector consent, rollout or price entitlements. - URL: https://docs.unique.ai/administrators/platform-overview - Locator: Connectors and Knowledge Sources diagram - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:release40-20261026 Unique release 2026.40. GA HTML dashboards can list, enable and sign in to MCP connectors, with Salesforce and Yahoo Finance named examples. Contract/module enablement and personal connection state still apply. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/release-notes-and-calendar/release-notes-2026/release-2026-40 - Locator: Hosted September 30 2026; Chat Experience, GA HTML connector dashboards - Evidence kind: documented - Source date: 2026-09-30 - Retrieved: 2026-10-26 ### glean:glean:r4-purview-label-redlist Glean O365 sensitivity-label restrictions. Protect+ can exclude SharePoint/OneDrive items by Purview label priority. Glean configures the redlist after account-team enablement; initial full crawl and later recrawls govern propagation. Teams message text is excluded. - URL: https://docs.glean.com/administration/protect/sensitive-findings/restrict-content-via-sensitivity-labels - Locator: Glean Protect+; setup; label-processing FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:permissioncache Permission cache timing. Describes usual subsecond internal permission propagation without a hard upper bound, and stale rules after a missed broadcast. - URL: https://docs.unique.ai/administrators/access-management-for-admins/cache-permission-sla - Locator: Expected timing; degraded scenarios - Evidence kind: documented - Source date: 2026-09-22 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:keys Single-tenant key management. Explains why client-held keys are unavailable across all Single Tenant data stores and directs full key control to self-hosting. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant/key-management - Locator: Big picture; BYOK/CYOK/HYOK; storage locations - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:retention Retention and deletion at Unique. Documents no training, Azure abuse-monitoring opt-out, post-termination retention and backup exceptions. - URL: https://docs.unique.ai/security-and-compliance/data-protection/data-retention-and-data-deletion-at-unique - Locator: Hosted-only scope; Azure provider retention; deletion; encryption - Evidence kind: documented - Source date: 2026-05-04 - Retrieved: 2026-10-21 ### glean:glean:language Glean language support. German, French, Italian and English end-user UIs are listed; cross-language retrieval is early access and admin setup is not localized. - URL: https://docs.glean.com/administration/management/features/glean-language-support - Locator: Language support matrix; cross-language warning - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:research Use Deep Research. Deep Research creates cited read-only reports from company sources and Brave web search; key modes differ. - URL: https://docs.glean.com/user-guide/assistant/deep-research - Locator: Key modes; citations; limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:sharing Share chats. Viewer chat sharing describes citation redaction and states a fixed 30-day duration. - URL: https://docs.glean.com/user-guide/assistant/chat-sharing - Locator: Viewer controls; uploaded files; retention note - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:memory Memory and personalization. Users can manage saved and learned memory in settings and chat. - URL: https://docs.glean.com/user-guide/assistant/memory-personalization - Locator: Saved and learned memories; user controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:memory-admin Configure memory settings. Admins can disable learned memory but not user-controlled saved memory; pricing differs for legacy customers. - URL: https://docs.glean.com/administration/assistant/configuration/memory-personalization - Locator: Configure memory; billing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:memory Context Memory in Unique AI Chat. Documents private per-user cross-chat memory, edit/disable controls and an explicit warning that disabling does not delete the stored profile. - URL: https://docs.unique.ai/users/spaces/unique-ai-chat/context-memory-in-unique-ai-chat - Locator: Private profile; edit and disable; web-search restriction - Evidence kind: documented - Source date: 2026-09-15 - Retrieved: 2026-10-21 ### glean:glean:builder Agent Builder. Agents combine configured steps and models; Workflow JSON export is generally available while Auto ZIP export has limited availability. - URL: https://docs.glean.com/agents/concepts/agent-builder - Locator: Instructions, tools and models; import and export - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:agent-sharing Sharing and permissions. Agents have controlled sharing and edit access. - URL: https://docs.glean.com/agents/concepts/sharing-permissions - Locator: Agent sharing permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:library Agent library. Users discover and run accessible agents through the internal library. - URL: https://docs.glean.com/agents/concepts/agent-library - Locator: Browse and discover agents - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:agents How agents work. Agents support dynamic tool use and structured steps, loops and branches. - URL: https://docs.glean.com/agents/how-agents-work - Locator: Auto and Workflow modes; tools; steps - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:groups Group-based permissions. Glean syncs Entra, Google and Okta group membership with integration-dependent timing; feature flag controls group-derived roles. - URL: https://docs.glean.com/administration/identity/roles/group-based-permissions - Locator: Supported providers; sync behavior; limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:roles Administrator Roles. Setup Admin, Admin, Super Admin and specialized moderators have distinct permissions. - URL: https://docs.glean.com/administration/identity/roles/admin-roles - Locator: Role matrix - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:sunset Product and feature retirements. The retirement page records November 13, 2026 end of Glean Assist embedded integrations, past Prompt Library migration and legacy billing-dashboard removal. - URL: https://docs.glean.com/release-notes/sunset - Locator: Embedded support integrations; Prompt Library; legacy billing dashboard - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:chat Unique AI Chat. Describes the user chat workspace and configurable tools. - URL: https://docs.unique.ai/users/spaces/unique-ai-chat - Locator: Features and access - Evidence kind: documented - Source date: 2026-09-03 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:roles Access role concept. Defines identity, application, space and knowledge-scope permissions, including delegated management roles. - URL: https://docs.unique.ai/it-operators/identity-and-access-management-iam/access-role-concept - Locator: Four access layers - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### glean:glean:oauth OAuth options for tools. Connector tools support Glean-managed or customer OAuth applications. - URL: https://docs.glean.com/administration/actions/setup-actions/choose-central-or-custom-oauth - Locator: Central and custom OAuth - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:r3-microsoft-write-confirmation Create Microsoft 365 files. Interactive-agent builders can require write confirmation by disabling Run without user confirmation; confirmation is configurable. - URL: https://docs.glean.com/agents/generate-files-from-templates - Locator: Recommended agent instructions, Human approval - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:mcp MCP tools for spaces. Describes feature-flagged beta MCP clients with organisation and per-space connector/tool controls. - URL: https://docs.unique.ai/administrators/space-management/tools/mcp-tools - Locator: Beta warning; flags; selective tool enablement - Evidence kind: documented - Source date: 2026-05-21 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:hub MCP Hub security governance. Documents per-user token routing, approved origin restrictions and tool-call correlation; some DLP/elicitation pipeline measures are planned. - URL: https://docs.unique.ai/administrators/mcp/the-mcp-hub/govern/security-governance - Locator: Authentication; governance; planned request pipeline - Evidence kind: documented - Source date: 2026-08-26 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:deepresearch Deep Research tool. Documents experimental research/report engine, with separate external OpenAI-engine data flows and limited current tools. - URL: https://docs.unique.ai/administrators/space-management/tools/deep-research - Locator: Experimental warning; engines; user flow - Evidence kind: documented - Source date: 2026-05-09 - Retrieved: 2026-10-21 ### glean:glean:web Web Search tools setup. Admins configure OpenAI, Brave or Google search tools and publish them to selected Glean interfaces. - URL: https://docs.glean.com/administration/tools/setup-tools/web-search-tools-setup - Locator: Providers; surface enablement; data sent - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:websearch Web Search tool. Documents multiple search engines, source citations and experimental query review/screening; conversation context may leave through queries. - URL: https://docs.unique.ai/administrators/space-management/tools/web-search - Locator: Modes; engines; external-query warning - Evidence kind: documented - Source date: 2026-05-20 - Retrieved: 2026-10-21 ### glean:glean:triggers Types of agent triggers. Agents can start from messages, forms, connected-system content changes and schedules, subject to admin access. - URL: https://docs.glean.com/agents/concepts/triggers - Locator: Content and schedule triggers - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:sdk Python SDK documentation. Documents SDK/public API access and customer-operated modules with event-driven webhook integration. - URL: https://docs.unique.ai/developers/software-development-kit-sdk - Locator: Public API; webhook verification; personal/app keys - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:scheduled Scheduled Tasks. Documents off-by-default recurring tasks running with user permissions; unattended approvals/questions can stop a run. - URL: https://docs.unique.ai/users/scheduled-tasks - Locator: Beta warning; task settings; runs and limits - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### glean:glean:office-output Create Microsoft 365 files with agents. Enabled tools create Office files, with limitations on arbitrary templates and output fidelity. - URL: https://docs.glean.com/agents/generate-files-from-templates - Locator: Word, Excel and PowerPoint; template limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:r4-cancellation-release Glean October 15 release notes. Canceling or interrupting an Assistant response also stops tool calls and background tasks started by that response. This is a documented Assistant run behavior, not a tested universal stop guarantee. - URL: https://docs.glean.com/release-notes/releases/2026-10-15-october-release - Locator: Canceled Assistant responses now stop cleanly - Evidence kind: documented - Source date: 2026-10-15 - Retrieved: 2026-10-26 ### unique-ai:unique-ai:review2-scheduled Scheduled Tasks. Scheduled Chat/Conduct tasks offer Automatic or Manual approval. The newer release labels scheduling Experimental and feature-flagged; unattended automatic approval is not mandatory human confirmation. - URL: https://docs.unique.ai/users/scheduled-tasks - Locator: At a glance; task Approval setting; unattended runs - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-release42 Unique release 2026.42. Release 2026.42 makes Shared Chats GA, on by default per company with a per-Space toggle and preservation of explicit settings. Scheduled Tasks remain Experimental and feature-flagged. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/release-notes-and-calendar/release-notes-2026/release-2026-42 - Locator: Highlights; Chat Platform; Conduct scheduling flag - Evidence kind: documented - Source date: 2026-10-14 - Retrieved: 2026-10-21 ### glean:glean:mcp About Glean MCP server. Glean exposes enterprise search, chat, documents and agents to external hosts through MCP. - URL: https://docs.glean.com/administration/platform/mcp/about - Locator: Server capabilities; authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:core-price Glean Core Suite. Core Suite combines per-user monthly licensing with committed Model Hub consumption; the seat amount is not given. - URL: https://docs.glean.com/glean-core-suite-pricing - Locator: Seat fee; Model Hub Usage; provider rate table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:mcpkb Knowledge Base MCP user guide. Documents external-assistant search/read with user permissions, citations and optional KB scope restrictions. - URL: https://docs.unique.ai/it-operators/integrations-connectors/knowledge-base-mcp/knowledge-base-mcp-user-guide - Locator: Connecting; access; limitations - Evidence kind: documented - Source date: 2026-10-05 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:api-usage API model usage tracking. Documents public API/SDK model-call usage tracking; some other internal-service calls are outside scope and REST usage retrieval is planned. - URL: https://docs.unique.ai/it-operators/operations/api-model-usage-tracking - Locator: Coverage; flags; limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:mobile iOS and Android. Mobile clients use enterprise SSO and integrate with Intune App Protection. - URL: https://docs.glean.com/administration/management/features/mobile - Locator: SSO prerequisites; Intune MAM - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:surfaces Choose where to use Glean. Glean has web, desktop, extension and embedded access points. - URL: https://docs.glean.com/user-guide/apps/choose-where-to-use-glean - Locator: Surface table; browser; desktop; extension - Evidence kind: documented - Source date: 2026-10-19 - Retrieved: 2026-10-21 ### glean:glean:voice Use real-time voice. Real-time voice works on web, desktop and mobile; raw audio streams to the configured model provider while transcripts follow chat retention. - URL: https://docs.glean.com/user-guide/assistant/real-time-voice - Locator: Where to access; privacy; limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:teams-app Glean in Microsoft Teams: Admin guide. The Microsoft Teams app requires tenant admin setup and consent. - URL: https://docs.glean.com/administration/platform/embedded-integrations/glean-in-teams/glean-in-microsoft-teams--admin-guide - Locator: Installation prerequisites and deployment - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:translation Translator space. Documents beta Office-file/text translation with glossary pre/postprocessing and potential layout disruption. - URL: https://docs.unique.ai/administrators/space-management/create-spaces/translator-space - Locator: Beta; glossary; document types; limitations - Evidence kind: documented - Source date: 2026-05-06 - Retrieved: 2026-10-21 ### glean:glean:images Image Generation in Glean. Glean generates and edits images using enabled image models, independently of the text model. - URL: https://docs.glean.com/user-guide/assistant/image-generation - Locator: Model choice; editing; admin controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:terms Glean Terms of Service v5Jun2026. The contract defines customer-cloud hosting, restricted proprietary access, order-specific fees, termination deletion and New York governing law. - URL: https://www.glean.com/legal/terms - Locator: Sections 1, 2, 5, 12 and 13 - Evidence kind: documented - Source date: 2026-06-05 - Retrieved: 2026-10-21 ### glean:glean:ai-addendum Glean AI Addendum v5Jun2026. No-training commitments and Glean-key zero-day retention have legal and trust-and-safety exceptions; Customer Key responsibilities remain with the customer. - URL: https://www.glean.com/legal/ai-addendum - Locator: Sections 3 and 4 - Evidence kind: documented - Source date: 2026-06-05 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:voice Voice administration. Requires Azure AI Speech Services and describes potential public/backbone audio routing. - URL: https://docs.unique.ai/administrators/space-management/voice-administration - Locator: Dependencies; networking; limitations - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:dpa Unique data processing addendum. Public DPA covers hosted chat/recordings, lists Microsoft, Swiss storage, return/deletion, confidentiality and ten-year audit-log retention. - URL: https://www.unique.ai/data-processing-addendum - Locator: Sections 2-3, 6-7; Appendices A-B; July 2025 footer - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:voice-user Using Voice. Documents prompt dictation with EN/DE/FR/IT, immediate audio discard and dialect/recognition limitations. - URL: https://docs.unique.ai/users/spaces/using-voice - Locator: Prompt dictation; privacy note; supported languages - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:team-chat Team chat. Beta shared Editor chats run each request as its author but expose already-generated answers to all participants. - URL: https://docs.glean.com/user-guide/assistant/team-chat - Locator: How permissions work; behavior and limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:accessibility Accessibility Statement. Glean says a VPAT 2.5 ACR covering WCAG 2.0, 2.1 and 2.2 A/AA is available through its trust center. - URL: https://docs.glean.com/user-guide/about/accessibility - Locator: Conformance status - Evidence kind: documented - Source date: 2026-09-25 - Retrieved: 2026-10-21 ### glean:glean:sso About Glean SSO. SSO is mandatory through OIDC or SAML; identity-provider policies enforce authentication conditions. - URL: https://docs.glean.com/administration/identity/sso/about - Locator: Mandatory SSO; identity providers; access controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:sso Single sign-on setup. Documents Zitadel SSO across deployment types, group claims and automatic SAML account creation/update. - URL: https://docs.unique.ai/it-operators/identity-and-access-management-iam/how-to-setup-single-sign-on-sso - Locator: Entra ID OIDC; SAML; managed-tenant setup - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:scim SCIM provisioning. Documents Unique SCIM endpoint/key for IdP user/group synchronisation. - URL: https://docs.unique.ai/it-operators/identity-and-access-management-iam/user-and-group-provisioning/scim-system-for-cross-domain-identity-management - Locator: Prerequisites and Entra setup - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### glean:glean:users Managing Users. Admins assign roles and feature permissions and can revoke user sessions. - URL: https://docs.glean.com/administration/identity/roles/manage-users - Locator: Member permissions; sign out all sessions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:insights Insights overview. Adoption metrics and per-person activity are available; small departments are grouped and CSV export is documented. - URL: https://docs.glean.com/administration/insights/overview - Locator: Metrics; department filters; CSV; privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:events Glean Customer Event log overview. Customer Event logs include chats and responses separately from administrative logs and export as an unfiltered stream. - URL: https://docs.glean.com/administration/gce-logs/data-dictionary - Locator: CHAT events; unified export stream - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:analytics Analytics interface. Documents adoption reports, detailed chat/model/tool exports and randomised or stable pseudonymous identifiers. - URL: https://docs.unique.ai/administrators/insights-measurement/analytics-interface/analytics - Locator: Reports; anonymisation; detailed interactions - Evidence kind: documented - Source date: 2026-09-03 - Retrieved: 2026-10-21 ### glean:glean:audit Audit Logs. Admin configuration logs have CSV export and 30-day default retention; ongoing delivery needs account-team configuration. - URL: https://docs.glean.com/administration/management/audit-logs/admin-audit-logs - Locator: Coverage; export; default retention - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:history Chat History. Admins choose Off or 30/90/180/365-day conversation retention, independently of Customer Event logging. - URL: https://docs.glean.com/administration/assistant/configuration/chat-history - Locator: Retention choices; Customer Event logs - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:audit Audit logs. Defines privileged API event logging with self-service exclusions, deployment-specific retention and request-based export. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/audit-logs - Locator: Scope; exclusions; default basic mode; retention and export - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:security-export Security Events Export. Documents Single-Tenant-only Azure Activity/Defender Event Hub export with seven-day replay, client-region selection and consumption cost. - URL: https://docs.unique.ai/it-operators/integrations-connectors/security-events-export-see - Locator: Availability; delivered events; retention; cost - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-audit Audit logs. API audit-event guide specifies basic/verbose modes and MT 90-day/ST five-year operational retention. It does not reconcile those event classes to DPA audit logs or a customer-specific contractual override. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/audit-logs - Locator: About audit logs; modes; Single and Multi Tenant Clients - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-dpa Unique data processing addendum. The public July 2025 DPA specifies ten-year audit logs and CH storage, while Appendix A lists Microsoft and a client-chosen location. No signed current provider schedule, retention override or contract-precedence mapping was inspected. - URL: https://www.unique.ai/data-processing-addendum - Locator: Sections 3.15 and 6.1; Appendix A; July 2025 footer - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-retention Retention and deletion at Unique. Hosted-only policy separates ordinary post-termination content retention, recoverable files and backups and permits contract customisation. Its log/key statements are not reconciled to audit-event/DPA/key-management scopes. - URL: https://docs.unique.ai/security-and-compliance/data-protection/data-retention-and-data-deletion-at-unique - Locator: Purpose; Data retention; Deletion after termination; Backups; Encryption in Place - Evidence kind: documented - Source date: 2026-05-04 - Retrieved: 2026-10-21 ### glean:glean:pii Sensitive content in user prompt. Configured prompt-only regex policies can flag or block credentials, PII, IBANs and government IDs; built-in patterns start disabled. - URL: https://docs.glean.com/administration/protect/ai-security/sensitive-content-user-prompt - Locator: Prerequisites; regex templates; enforcement - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:protect About Glean Protect and Protect+. Protect+ adds recurring sensitive-content scanning and AI security guardrails to baseline Protect. - URL: https://docs.glean.com/administration/protect/overview - Locator: Capability comparison; AI security add-on - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:subprocessors Glean Subprocessors. The list names US providers and an Indian affiliate for remote support, security and debugging. - URL: https://www.glean.com/legal/subprocessors - Locator: Provider table; affiliate remote support - Evidence kind: documented - Source date: 2026-07-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:dlp Data leakage prevention integration. Describes customer-operated HTTPS/DLP proxy and post-chat analytics scanning rather than a default native PII-redaction feature. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/data-leakage-prevention-dlp - Locator: Proxy; analytics API; compatibility - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### glean:glean:org-instructions Configure custom instructions. Admins can configure up to five enterprise instructions for Assistant. - URL: https://docs.glean.com/administration/assistant/configuration/custom-instructions - Locator: Five custom instructions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:single Single-tenant security architecture. Documents separate Azure landing zone, network restrictions, retention and Unique-managed infrastructure keys. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant - Locator: Azure resources; SSO; encryption; monitoring - Evidence kind: documented - Source date: 2026-05-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:policy Terms and conditions administration. Documents first-login acceptance, custom terms under an MSA and version/agreement export through GraphQL. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/terms-and-conditions-administration - Locator: First-login acceptance; MSA condition; API export - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### glean:glean:regions Supported GCP regions. The GCP region list includes Netherlands, Belgium, Frankfurt and other regions, subject to required services. - URL: https://docs.glean.com/get-started/prepare/self-hosted-deployment/gcp/supported-gcp-regions - Locator: Preferred regions; EMEA - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:sla Glean Customer Support SLA v6Mar2026. Standard and paid Premium support differ; only Premium includes 99.9% monthly uptime and 10% or 20% service credits. - URL: https://www.glean.com/legal/sla - Locator: Sections 2, 4, 7 and 8 - Evidence kind: documented - Source date: 2026-03-06 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-keys Single-tenant key management. May 2026 key guide distinguishes imported customer-generated keys held by Unique from customer-exclusive key control via self-hosting. Its MT/ST CMK statement differs from the hosted retention page; actual MT configuration is unverified. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant/key-management - Locator: Infrastructure-only scope; PMK; BYOK/CYOK/HYOK; Summary - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-single Single-tenant security architecture. Single-tenant guide documents separate landing zone, WAF/IP controls and Unique-managed encryption. Its 2048-bit RSA-HSM description differs from the hosted retention page; this does not establish an exact current key design. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant - Locator: Overview; Encryption; Data classification - Evidence kind: documented - Source date: 2026-05-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-compliance Compliance Layer 3.0. The deployment matrix documents CH North multitenant hosting and selectable single/client-hosted regions, with deployment-specific controls. These are options, not proof of a particular customer contract or current key configuration. - URL: https://docs.unique.ai/security-and-compliance/compliance/compliance-layer-3-0 - Locator: Digital Sovereignty; Feature overview matrix - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:install Unique installation models. Enumerates multi-tenant, single-tenant, customer-managed and on-premise deployments. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique - Locator: Overview - Evidence kind: documented - Source date: 2025-08-06 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:terms Unique terms of service. Describes a sales-conversation service with Order Form subscription fees, nonrenewal notice, recording export and proprietary rights; applicability to the current AI MSA needs confirmation. - URL: https://www.unique.ai/terms-of-service - Locator: Sections 1-2, 4-6, 11, 17-18 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:dpa Glean Data Processing Addendum v6Mar2026. The DPA covers applicable Swiss and EU law, termination erasure, SCCs and 30-day subprocessor notice. - URL: https://www.glean.com/legal/dpa - Locator: Sections 1, 7, 9 and 10; SCC annexes - Evidence kind: documented - Source date: 2026-03-06 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:redaction Chat data redaction and retention. Documents scheduled clearing of chat content and workspace records, with separate upload/KB retention rules. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/data-redaction - Locator: What is cleared; exclusions; administrator settings - Evidence kind: documented - Source date: 2026-10-18 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:contact Unique AI contact. Lists Unique AI AG in Zürich, Unique Germany GmbH in Berlin and other regional entities. - URL: https://www.unique.ai/contact-us - Locator: Office addresses - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-governance Unique AI governance framework: contract access. The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses. - URL: https://docs.unique.ai/security-and-compliance/ai-governance-framework - Locator: Individual standards; Legal contracts; End-User Terms and Conditions - Evidence kind: documented - Source date: 2026-04-12 - Retrieved: 2026-10-21 ### glean:glean:r3-legal-index Glean legal. The index links both Business Associate Agreement forms, the Technical Services Addendum and named Outcomes Packages; inclusion and pricing depend on the applicable contract. - URL: https://www.glean.com/legal - Locator: Glean Customer Agreements and Policies - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:trust Unique AI trust centre. Describes CH Azure storage separately from globally routed inference and claims ISO/SOC assurances, with differing SOC types in the FAQ. - URL: https://www.unique.ai/trust-center - Locator: Enterprise security; compliance standards; FAQ - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:security-page Glean Protect security page. Glean claims SOC 2 Type II, ISO 27001 and ISO 42001; no issuer-scoped certificate was retrieved. - URL: https://www.glean.com/platform/security - Locator: Enterprise security and compliance badges - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:iso42001 Unique ISO/IEC 42001 certificate. TÜV SÜD certificate covers development/deployment SaaS for financial services using pretrained foundation models or client-provided models, valid to 6 March 2028. - URL: https://www.unique.ai/hubfs/ISO%2042001_Unique_EN_2025.pdf - Locator: One page; registration 99 420 00001; scope and dates - Evidence kind: certificate-verified - Source date: 2025-03-07 - Retrieved: 2026-10-21 - Issuer: TÜV SÜD South Asia Private Limited - Certificate scope: Unique AG, Stockerstr.34, Zurich. Development and deployment of SaaS for financial-services clients based on pretrained AI foundation models using Azure OpenAI or client-provided models, including client on-premise models. - Valid: 2025-03-07 to 2028-03-06 ### unique-ai:unique-ai:review2-iso-docs ISO Certifications and current downloads. The ISO documentation links 2026 English/German ATTESTA ISO27001 and ISO9001 renewals, plus the 2025 ISO42001 certificate; ISO27001 SoA requires an NDA. - URL: https://docs.unique.ai/security-and-compliance/compliance/certifications/iso-certifications - Locator: Certificate ISO27001; ISO9001; ISO42001; Statement of Applicability - Evidence kind: documented - Source date: 2026-08-05 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-iso27001 Unique AG ISO27001 ATTESTA 2026 renewal. Inspected ATTESTA ISO27001:2022 renewal for Unique AG, registration 223-06-018.I, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry. - URL: https://unique-ch.atlassian.net/wiki/rest/api/content/1384809423/child/attachment/att2423750716/download - Locator: One-page 2026 English certificate; scope, registration, surveillance, printed expiry - Evidence kind: certificate-verified - Source date: 2026-06-10 - Retrieved: 2026-10-21 - Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG - Certificate scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO27001:2022 information security management - Valid: start not stated to 2029-05-31 - Registry: https://www.ic-register.com/?qry=Unique&handler=Process ### unique-ai:unique-ai:review2-iso9001 Unique AG ISO9001 ATTESTA 2026 renewal. Inspected ATTESTA ISO9001:2015 renewal for Unique AG, registration 223-06-017.Q, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry. - URL: https://unique-ch.atlassian.net/wiki/rest/api/content/1384809423/child/attachment/att2423750710/download - Locator: One-page 2026 English certificate; scope, registration, surveillance, printed expiry - Evidence kind: certificate-verified - Source date: 2026-06-10 - Retrieved: 2026-10-21 - Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG - Certificate scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO9001:2015 quality management - Valid: start not stated to 2029-05-31 - Registry: https://www.ic-register.com/?qry=Unique&handler=Process ### unique-ai:unique-ai:review2-iso-register Certificate-linked public register: Unique AG. Public certificate-linked register lookup for Unique AG lists registrations 223-06-018.I and 223-06-017.Q, Zurich, software/IT scope and expiry 31 May 2029. Standard/status text fields are blank; certificate PDFs supply the standards. - URL: https://www.ic-register.com/?qry=Unique&handler=Process - Locator: Unique AG result rows; registration, scope, expiry - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-soc SOC2 Type2: chronology and report access. The dedicated SOC page explains Type1 in December 2023 followed by Type2 in January 2025; audit report and certificate are available only on request after NDA. Auditor, service scope and actual reporting period were not publicly inspected. - URL: https://docs.unique.ai/security-and-compliance/compliance/certifications/soc-2-type-2 - Locator: SOC2 Type2 timeline; Certificates/report access - Evidence kind: vendor-claimed - Source date: 2026-04-12 - Retrieved: 2026-10-21 ### glean:glean:r4-aws-cmk-faq Glean customer-hosted AWS FAQ. Customer-managed CMKs are supported for AWS, although the FAQ recommends default AWS-managed KMS keys and documents SCP-based emergency controls. - URL: https://docs.glean.com/security/cloud-prem/aws/faq - Locator: Are customer managed keys supported? - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### glean:glean:r4-aws-key-control Glean AWS account access and deployment model. The customer-hosted AWS deployment guide says customers own and control KMS customer-managed keys used for data at rest. This does not establish key control for Glean Hosted or GCP. - URL: https://docs.glean.com/security/cloud-prem/aws/account-access-and-deployment-model - Locator: Customer controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### glean:glean:dpa-confidentiality Glean DPA. General DPA confidentiality binds authorized personnel and no-less-protective subprocessor agreements; no specific §203/Art321 undertaking was retrieved. - URL: https://www.glean.com/legal/dpa - Locator: Section4 authorized personnel confidentiality; section9 subprocessor written agreement and necessary access - Evidence kind: documented - Source date: 2026-03-06 - Retrieved: 2026-10-21 ### glean:glean:flex-price Glean Enterprise Flex. Enterprise Flex pools credits and separately meters advanced features and premium models; learned-memory billing starts November 7, 2026 for the stated scope. - URL: https://docs.glean.com/glean-enterprise-flex-pricing - Locator: Enterprise Flex seats; FlexCredits; rate card - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-terms-admin Terms and Conditions Administration. Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/terms-and-conditions-administration - Locator: Overview; MSA exceptions; Modifying/Exporting Terms and Conditions - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-21 ### glean:glean:fx-ecb ECB historical euro reference rates. The 2026-10-20 reference is EUR 1 = USD 1.1215 = CHF 0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20, USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### glean:glean:r2-customer-default-example Change your default model on Customer Key. Customer Key admins choose defaults; GPT5.6 Luna is expressly an example, not a fixed or recommended routine model. - URL: https://docs.glean.com/administration/change-default-model - Locator: Opening note and prerequisites - Evidence kind: documented - Source date: 2026-10-19 - Retrieved: 2026-10-21 ### glean:glean:r2-direct-provider-proxy OpenAI direct API pricing. The shared direct-provider comparison uses USD0.10 input andUSD0.50 output per1M tokens; vendor usage is not replaced by this proxy. - URL: https://developers.openai.com/api/docs/pricing - Locator: Standard short-context gpt-6-luna - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### glean:glean:r2-proxy-lowest-effort GPT6 Luna model documentation. Lowest effort none is used only for the direct-provider comparison assumption. - URL: https://developers.openai.com/api/docs/models/gpt-6-luna - Locator: Reasoning effort - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:platform Unique AI platform. Markets a modular finance platform with governed connectors, frontend, financial agents and APIs. - URL: https://www.unique.ai/en/platform - Locator: Frontend, financial agents, MCP Hub; deployment section - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:ecb-fx ECB euro foreign exchange reference rates, 20 October 2026. ECB records EUR 1 = USD 1.1215 and CHF 0.9237 on 20 October 2026; derived USD to EUR is 1/1.1215 and CHF to EUR is 1/0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time="2026-10-20": USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-governance-20261026 Unique AI governance framework: contract access. The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses. - URL: https://docs.unique.ai/security-and-compliance/ai-governance-framework - Locator: Individual standards; Legal contracts; End-User Terms and Conditions - Evidence kind: documented - Source date: 2026-04-12 - Retrieved: 2026-10-26 ### unique-ai:unique-ai:reference-licence-20261026 Unique public reference repository licence. The public repository defaults to Unique License v1 unless an explicit licence says otherwise; commercial use, distribution and modifications require prior approval. The default is restricted source-available, not an OSI open-source licence. - URL: https://github.com/Unique-AG/ai/blob/afa596c9b4b0231895ff70f44029a9a525f746e9/LICENSE - Locator: LICENSE, repository-wide disclaimer and exceptions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:unique-licence-v1-20261026 Unique License v1. The published full licence permits personal noncommercial use and requires prior written approval for commercial use, distribution and modification, with separate component-licence exceptions. Swiss law and Zurich venue are specified. - URL: https://github.com/Unique-AG/license/releases/tag/unique-license.v1 - Locator: Grant, Restrictions, Open Source Components, Governing Law - Evidence kind: documented - Source date: 2024-09-24 - Retrieved: 2026-10-26 ### unique-ai:unique-ai:sdk-licence-20261026 Unique Python SDK MIT licence. The Python SDK directory has an explicit MIT licence permitting commercial use and modification subject to notice requirements; this exception does not license the hosted platform. - URL: https://github.com/Unique-AG/ai/blob/afa596c9b4b0231895ff70f44029a9a525f746e9/unique_sdk/LICENSE - Locator: unique_sdk/LICENSE, explicit component exception - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:sdk-package-20261026 Unique SDK package metadata. At the pinned October 23 repository commit, unique_sdk package metadata declares MIT, consistent with its component licence. Repository/package version is not treated as the hosted release date. - URL: https://github.com/Unique-AG/ai/blob/afa596c9b4b0231895ff70f44029a9a525f746e9/unique_sdk/pyproject.toml - Locator: project name/version and licence - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:review2-terms-admin-20261026 Terms and Conditions Administration. Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/terms-and-conditions-administration - Locator: Overview; MSA exceptions; Modifying/Exporting Terms and Conditions - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-26 ### unique-ai:unique-ai:support Enterprise support. Provides public multitenant status link, enterprise email and a contract-specific dedicated support model. - URL: https://docs.unique.ai/enterprise-support - Locator: Contact; dedicated support model; hours - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:status Unique public system status. Public status page displays service/API/collector components and historical uptime panels; dedicated environments are outside the documented status scope. - URL: https://status.prod.unique.app/ - Locator: Component and 90-day uptime panels - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:homepage Unique AI finance platform. Markets embedded experts and structured training programmes for finance users and IT. - URL: https://www.unique.ai/ - Locator: Forward-Deployed Engineers and training section - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21