Sim Enterprise adds organization controls for access, provisioning, operations, and branding. Organization owners and admins configure these features in Settings.
| Feature | Use it to |
|---|---|
| Permission groups | Restrict features, models, blocks, and tools by workspace and member |
| Single sign-on | Connect a SAML or OIDC identity provider |
| Verified domains | Prove domain ownership for SSO and provisioning |
| Directory provisioning | Sync users and group-based access from your directory |
| Session policies | Set session lifetimes and revoke member sessions |
| Audit logs | Investigate configuration and security events |
| Usage tracking | Review usage by member, workspace, model, and source |
| Data retention | Set retention windows and configure PII redaction |
| Data drains | Export logs and Chat records to your own destination |
| Custom blocks | Share a workflow as a block across the organization |
| Workspace forks | Copy a workspace and sync deployed workflow changes |
| White-labeling | Configure organization branding |
Self-hosted setup
Self-hosted deployments unlock enterprise features through environment configuration instead of billing. One switch turns on the whole set:
ENTERPRISE_ENABLED=true
NEXT_PUBLIC_ENTERPRISE_ENABLED=trueEach feature also keeps its own flag, so you can enable them one at a time or switch a single feature back off.
Most of these features read their settings from the organization that owns a workspace, so a deployment also needs an organization model — either one instance-wide organization that every user joins automatically, or organizations you provision yourself through the Admin API.
See the self-hosted enterprise guide for the full variable list, both organization patterns, the Admin API reference, and troubleshooting.
Once enabled, each feature is configured through the same Settings UI as Sim Cloud. When invitations are disabled (DISABLE_INVITATIONS, NEXT_PUBLIC_DISABLE_INVITATIONS), use the Admin API (x-admin-key header) to manage organization membership and workspace access. Internal members join the organization; external workspace members only receive access to a specific workspace.