IDENTITY

Enterprise AI access that follows your identity rules

Plan roles, identity federation and provisioning around the organization’s actual directory and access lifecycle.

Evidence snapshot: 2026-10-22 · review by 2026-11-22 · partial_read_only

THE PRACTICAL TASK

What to agree for your team

01

Roles

Separate administration, ownership and everyday work.

02

Federation

Validate the chosen identity provider and supported login flow.

03

Lifecycle

Check onboarding, role changes and revocation.

From requirements to a pilot

  1. 01

    Map roles

  2. 02

    Configure the identity provider

  3. 03

    Test access and revocation

  4. 04

    Approve the deployment

Controls

Role-based accessEarly Access

Owner, Admin, Member, and Viewer roles bound administrative and workspace actions.

Production multi-tenant pilot pending.
Technical evidence
Scope
business_enterprise
Evidence
docs/business/rbac-matrix.md
SSOBeta

Enterprise identity federation is configured for a specific provider.

Production IdP registration and acceptance are deployment-specific.
Technical evidence
Scope
enterprise_deployment_specific
Evidence
docs/enterprise/sso-scim.md
SCIMEarly Access

The provisioning interface requires validation against the customer directory.

Customer conformance and directory validation pending.
Technical evidence
Scope
enterprise_deployment_specific
Evidence
docs/enterprise/sso-scim.md

Deployment profiles

SaaSBeta

A Wicsora-managed deployment with no published HA or SLA guarantee.

Current single-site runtime is not HA/SLA evidence.
Technical evidence
Region
deployment_specific
Evidence
docs/enterprise/deployment-profiles.md
On-PremBeta

Customer-environment packaging with outbound access denied by default.

Signed artifacts and a customer restore drill are still required.
Technical evidence
Region
customer_environment
Evidence
docs/enterprise/deployment-profiles.md;deploy/onprem

Evidence snapshot: 2026-10-22 · review by 2026-11-22 · partial_read_only