Applications
An application is a non-human identity—a CI/CD pipeline, monitoring system, automation job, or AI agent that needs programmatic access to your servers. Instead of sharing a person’s credentials, you create an application and issue it service tokens, so automated access is scoped, owned, and fully audited.
Note: Applications are an administrator-only feature.
Create an application
Applications live under IAM > Applications. To create one, set:
- Name — a short name to identify the application.
- Description (optional) — what the application is used for.
- Service type — CI/CD, Monitoring, Automation, or Integration.
- Owner — the person responsible for the application.
The list shows each application’s name, service type, owner, and server username.
Application detail
An application’s detail page has these tabs:
- Provisioning — configure the server account and how it’s created. See Provisioning.
- System users — server accounts linked to the application (manually or by username match).
- Credentials — the application’s service tokens.
- Roles — roles assigned to the application; its tokens inherit these.
- Activity — an audit timeline of events for the application.
How it relates to API tokens
Service tokens are issued to an application and inherit its roles and provisioning. A standalone API access token instead belongs to a user. Use applications and service tokens for shared automation that should be owned and audited as its own identity.