Applications
Create an application for automated access and issue service tokens for it.
Application identity
An application is an identity for a CI/CD pipeline, monitoring system, automation job, or AI agent that needs programmatic access to your servers. Create an application and issue it service tokens to give automation its own scoped credentials and activity record.
You need permission to create an application.
Create an application
Open Applications under IAM and select New application. To create an application, set:
- Name: a short name to identify the application.
- Description (optional): what the application is used for.
- Service type: choose AI agent, CI/CD, Monitoring, Automation, Integration, or Other.
The list shows each application’s name, service type, creator, server account, and creation date. To issue a token without opening an application first, select New token on the list and pick the application in the first step.
Application detail
An application’s detail page has these tabs:
- Tokens: the application’s service tokens and the permissions they may hold. Select Create token to issue one.
- Server access: configure provisioning and review the application’s server accounts. See Provisioning.
- Roles: roles assigned to the application; its tokens inherit these.
- Activity: what the application’s tokens did, when available on your plan.
Members without admin rights see only the Tokens tab.
Let an application manage one alert rule
As a workspace admin, you can let an application’s service tokens update or delete one alert rule.
First, give the application a workspace-wide role that covers the required token scopes. In the application’s Roles tab, select Assign role, choose that role, and save it without limiting it to a resource. See Grant the application a global role for the API steps.
- Open the application’s detail page and go to Roles.
- Select Assign role and choose
alert_rule:maintainerin Role. - Turn on Limit to specific resource. Set Resource type to
metrics.alertrule, then select one rule under Object. - Optionally fill in Reason (optional), then select Save.
- Check the assigned role: it shows the rule’s type and name. To revoke access, select Remove role on that role and confirm the removal. You can add a Reason (optional) when removing it too.
If the application has no workspace-wide role, the console warns before saving and the API refuses the grant with 400 rbac_application_role_global_required. Remove its rule-scoped roles before removing its last workspace-wide role; otherwise the API returns 400 rbac_application_rule_roles_remain.
Each service token still needs alert_rule:update to update the selected rule or alert_rule:delete to delete it, within the application’s workspace-wide role permissions. The alert_rule:maintainer grant must name a rule; a workspace-wide grant of that role is refused. The application’s workspace-wide roles alone do not give its tokens access to a rule. The alert rules API describes the restrictions on default rules and the core disk usage rule.
How it relates to API tokens
Service tokens are issued to an application and inherit its roles and provisioning. A standalone personal API token instead belongs to a user. Use applications and service tokens for shared automation that should be owned and audited as its own identity.