---
title: "Provisioning"
description: "Choose the server account an Alpacon application's tokens run as. Set the default account, decide when it is created, and assign existing accounts per server."
---

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

# Provisioning

Choose which server account an application's tokens run as, and when Alpacon creates it.

## Server access

Open the application's **Server access** tab. Only workspace admins see it. It lists the connected servers the application's tokens reach, with the account each one runs as under **Runs as** and the reason under **Decided by**:

- **Assigned**: you assigned an account on that server.
- **Default account**: the server already has the default account.
- **Created on first use**: the default account is created when a token first sends work there.
- **Created at next sync**: the default account is created at the next sync.
- **No account, so work fails**: commands and file transfers from the application's tokens fail on that server.

If the tab shows **No server reached**, the application's roles cover no server. Select **Open Roles** and set the roles' scope again.

## Default account

The default account is the account the application uses on every server where you have not assigned one. Select **Edit** beside **Default account** to set:

- **Account name**: the Unix account name. It must not match an IAM user or another application's account. A server that already has an account with this name uses it.
- **UID** (optional): 1000 or higher and unique. Left blank, one is picked.
- **Shell** (optional): left blank, `/usr/sbin/nologin` is used, which blocks terminal sign-in.
- **Home directory** (optional): left blank, the OS default is used. Applies to Linux servers only.

UID, shell, and home directory apply only to accounts created after you save. Existing accounts keep their values.

## When the account is created

Under **On servers without the account**, choose one option. Each shows how many servers it affects, and changing it asks you to confirm.

- **Only where it exists**: Alpacon creates no new accounts. Token work fails on servers without the account; accounts already created stay.
- **Create on first use**: the account is created on a server the first time a token sends work there.
- **Create everywhere now**: the account is created on every server the application's tokens reach, at the next sync.

The last two need a default account first.

## Assign an existing account

To use a different account on particular servers, select **Assign accounts** and pick accounts that exist on a server and are not linked to anyone yet. You can assign one account per server, and an assigned account takes precedence over the default account there. Select **Unassign** on a row to return that server to the default account.

## Related docs

- [Applications](/use/iam/applications/)
- [Service tokens](/use/iam/applications/service-tokens/)
- [Access control overview](/use/iam/)

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