Service Accounts
Service Accounts is the admin screen for non-human identities used by external services, scheduled jobs, and workload automation.
Service accounts are Roster identities. They do not authenticate through the web login form. Automation normally acts through an API key owned by the service account.
The table shows:
- Service account display name
- Identity ID
- Optional email
- Platform role
- Updated and created timestamps
- Active, disabled, or deleted status
Use search and the role filter to find accounts quickly.
Create or Edit
Section titled “Create or Edit”Admins can set:
- Name
- Optional email
- Platform role
Use a service account when the actor is an integration or workload rather than an autonomous agent. Use AI Agents when the actor should represent agent-owned work.
Lifecycle
Section titled “Lifecycle”Admins can disable, enable, or delete service accounts. Disable or delete an account before revoking or rotating its API keys when a workload is retired.
Keep API keys scoped to the service account’s job. Effective access is always the intersection of key scopes, owner rights, and resource authorization.