Administration
Administration is where you control who can do what in your Ema workspace, how the workspace is configured, how personally identifiable information (PII) is handled, and how every action is recorded. These pages cover the admin screens under Settings → Admin Settings: governance and permissions, user management, workspace settings and single sign-on (SSO), PII and data governance, and the audit log.
How Ema is hosted. Most customers use Ema as a managed cloud service, where Ema runs and secures the infrastructure. Some customers run Ema on a dedicated or on-premises deployment. Ask your Ema representative which applies to you.
Who can administer a workspace
Everyone has one role in the workspace. These roles open Admin Settings:
- System admin sees every section: Workspace (workspace details, Autopilot, sign-in and SSO, LLM providers, and API keys), User Management, and Governance (the audit log, and PII controls where they are turned on). Directory sync also appears where it is turned on, and User Management has a Roles tab where it is turned on.
- User admin sees User Management, to invite people, change their roles, and deactivate or remove them. User Management also has a Roles tab where it is turned on.
Builders don't see Admin Settings. They can create custom integrations and manage the ones they are an integration admin of. See Integration admins.
See Governance and permissions for every role, including older roles you may see in the members list.
What you can administer
| Page | What it covers |
|---|---|
| Governance and permissions | The roles at each level, integration admins, how access is enforced, and the permissions reference. |
| User management | Invite people by email, give and change roles, and deactivate or remove people. |
| Tenant management and SSO | Workspace overview and branding, Autopilot settings, SSO (OIDC and SAML), email domain claims, LLM providers, and API keys. |
| PII and data governance | PII detection, per-entity display levels (original, partial, tokenized, masked), and integration egress policy. |
| Audit log | The workspace-wide event log, Activity feeds on individual screens, the PII access log, and CSV export. |
| Security & Compliance | Encryption at rest, workspace isolation, PII detection and masking, the audit trail, and data retention with legal holds. |
| AI Employee export and import | Export an AI Employee as a bundle file or save it as a template, import it into another workspace, and the version and permission rules that govern each way. |
Where to find these screens
Admin screens open from the sidebar: select Settings to open Admin Settings. Its left side lists the sections your role can open:
- Workspace: one tabbed page with Overview (workspace details, hierarchy, security, branding, and OTP email), Autopilot, SSO, Email Domains, LLM Providers, and API Keys. In workspaces where it is turned on, Workspace also has a User Personalization tab. See Tenant management and SSO.
- User Management: memberships and roles, with Users, Teams, and (where it is turned on) Roles tabs. See User management.
- Governance: the audit log and PII governance. See Audit log and PII and data governance. In workspaces where it is turned on, Governance also has Call records, the stored prompt and reply of each model call.
- Directory sync, in workspaces where it is turned on.
What's next
- Governance and permissions: start here to understand roles and permissions.
- User management: invite teammates and give them roles.
- Tenant management and SSO: set up how people sign in.
- PII and data governance: control how sensitive data is shown and shared.
- Audit log: review and export the record of every action.
- Security & Compliance: the platform's encryption, isolation, audit, and retention posture.
- AI Employee export and import: move an AI Employee between workspaces and environments.