---
title: "Applications"
description: "Create Alpacon applications for CI/CD, monitoring, automation, and AI agents. Issue service tokens so each non-human identity has scoped, audited server access."
---

> Full documentation index: https://docs.alpacax.com/llms.txt

# 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](/use/iam/applications/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](/use/iam/applications/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](/use/iam/applications/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, make sure the application's workspace-wide roles, taken together, can both update and delete alert rules (`alert_rule:update` and `alert_rule:delete`). The built-in `operator` role has both; `member` alone, or a role with only one of the two, is not enough. To add such a role, select **Assign role** in the application's **Roles** tab, choose the role, and save it without limiting it to a resource. See [Grant the application a global role](/reference/api/#3-grant-the-application-a-global-role) for the API steps.

1. Open the application's detail page and go to **Roles**.
2. Select **Assign role** and choose `alert_rule:maintainer` in **Role**.
3. Turn on **Limit to specific resources**. Set **Resource type** to `metrics.alertrule`, then select one rule under **Object**.
4. Optionally fill in **Reason (optional)**, then select **Save**.
5. 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 workspace-wide roles lack either permission, the drawer shows which of the two is missing as soon as you limit `alert_rule:maintainer` to an alert rule, and you can't save. Select **Grant a workspace-wide role first** to grant one from the same drawer; once you save it, the drawer returns to the rule role you were choosing. The API refuses the grant with `400 rbac_application_role_global_required`.

While the application holds a rule-scoped role, its workspace-wide roles must keep both permissions. Removing a workspace-wide role from it, deleting a role, or removing the alert rule update or delete permission from a role is refused with `400 rbac_application_rule_roles_remain` when the change would leave the application without both permissions or without any workspace-wide role. When you remove such a role from the application, the confirmation warns you before you confirm, and a refusal stays in the confirmation with its reason. Remove the rule-scoped roles first, or grant another workspace-wide role that has both permissions.

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. No other role can be limited to an alert rule. The application's workspace-wide roles alone do not give its tokens access to a rule. The [alert rules API](/reference/api/metrics/rules/#who-can-edit-or-delete-a-rule) 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](/use/settings/api-tokens/) instead belongs to a user. Use applications and service tokens for shared automation that should be owned and audited as its own identity.

## Related docs

- [Service tokens](/use/iam/applications/service-tokens/)
- [Provisioning](/use/iam/applications/provisioning/)
- [Personal API token](/use/settings/api-tokens/)
- [Access control overview](/use/iam/)

Source: https://docs.alpacax.com/use/iam/applications/
