---
title: "alpacon acl"
description: "Manage pre-approved commands for service tokens and the Command ACL admins who may change them. Check the browser sign-in it needs, its flags, and examples."
---

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

# alpacon acl

Manage the command pre-approval ledger: the pre-approved commands a service token may run without human approval, and the Command ACL admins who may change them. The web console shows the same entries under **Pre-approved commands** on a service token's page.

On Alpacon Cloud, a service token's command that matches no entry is refused with `command_acl_denied`. It isn't sent for human approval.

## Usage

```text
alpacon acl [flags]
alpacon acl [command]
```

## Key facts

- Only a Command ACL admin of the workspace may read or change the ledger. The role is separate from the workspace role.
- Sign in with `alpacon login` through the browser. A login with an API token (`-t`) is refused.
- A personal API token has no command list on the ledger. Only a service token can be given a pre-approved command.
- On a workspace that still manages command ACL rules, such as a self-hosted deployment without the ledger, every `alpacon acl` command says so and exits `1`. Use [`alpacon token acl command`](/reference/cli/token/acl-command/) there.

## Flags

| Flag | Type | Description | Default |
| --- | --- | --- | --- |
| `-h, --help` | `bool` | help for acl | `false` |
| `--output` | `string` | Output format: table or json | `table` |

## Examples

List the workspace's pre-approved commands

```bash
alpacon acl entry ls
```

## Authorizing the ledger

The ledger needs its own authorization, separate from `alpacon login`. The first `alpacon acl` command prints a link and a code and opens your browser, the same way `alpacon login` does. Confirm the code and sign in, and the command continues.

The authorization is saved for the workspace it was given for and isn't renewed in the background. When it expires, the next `alpacon acl` command asks again. `alpacon logout` and a new `alpacon login` remove it. If you decline in the browser or the code expires, run the command again.

Alpacon Cloud workspaces need no configuration. On a self-hosted deployment with its own ledger, set `ALPACON_AI_URL`, and `ALPACON_AI_AUDIENCE` if its sign-in uses another audience. The URL must use `https`, except for a loopback host. The MCP server reads a separate pair; see [Signing in to the ledger](/reference/mcp/tools/security/#signing-in-to-the-ledger).

## Related commands

  
    Manage pre-approved command entries
  
  
    Manage Command ACL admins

Source: https://docs.alpacax.com/reference/cli/acl/
