---
title: Permissions
description: The IAM actions the Titan Harness checks, and what each
  organization role can do by default.
url: https://hexelstudio.com/docs/harness/permissions
---

Every harness request is checked against your organization's [policies](https://hexelstudio.com/docs/identity/policies). The organization comes from the access token; `X-Workspace-Id` and `X-Environment-Id` select where the request acts and never grant access by themselves.

Organization roles give harness access by default: Owners have every action, Admins have every `harness:*` action, Members can apply agents and work with their own tasks, and Viewers can read. For a [service user](https://hexelstudio.com/docs/identity/service-users), attach a policy with only the actions it needs.

| Action | What it allows | Owner | Admin | Member | Viewer |
| --- | --- | --- | --- | --- | --- |
| `harness:agent:read` | List agents, versions and channels | ✓ | ✓ | ✓ | ✓ |
| `harness:agent:apply` | Apply a spec bundle as a new version | ✓ | ✓ | ✓ | |
| `harness:agent:promote` | Point and roll back channels; promotions | ✓ | ✓ | | |
| `harness:task:create` | Create tasks, estimates and forks | ✓ | ✓ | ✓ | |
| `harness:task:read` | Read tasks, runs, events and the attention inbox | ✓ | ✓ | own | own |
| `harness:task:steer` | Steer a task and answer its questions | ✓ | ✓ | own | |
| `harness:task:control` | Pause, resume, retry and cancel tasks; cancel swarms and resolve members | ✓ | ✓ | own | |
| `harness:task:delete` | Delete tasks | ✓ | ✓ | own | |
| `harness:approval:decide` | Forward an approval decision to Titan | ✓ | ✓ | own | |
| `harness:task:admin` | Act on every person's tasks, not only your own | ✓ | ✓ | | |
| `harness:swarm:run` | Start swarms | ✓ | ✓ | ✓ | |
| `harness:artifact:read` | List and download artifacts | ✓ | ✓ | own | own |
| `harness:trigger:manage` | Create, change, delete and fire triggers | ✓ | ✓ | | |
| `harness:webhook:manage` | Create, change, delete and test webhooks | ✓ | ✓ | | |
| `harness:environment:admin` | Data retention settings and legal holds | ✓ | ✓ | | |
| `harness:audit:read` | Create and download evidence packs | ✓ | ✓ | | |
| `harness:agent:check` | Post CI check results (promotions, on request) | ✓ | ✓ | | |

"own" means the task the person created: without `harness:task:admin`, a caller sees and acts only on their own tasks.

Some actions need more than one permission:

- A trigger's `PUT` and `:fire` also need `harness:task:create`: its tasks are its maker's.
- A fork needs `harness:task:read` and `harness:task:create`.
- A swarm estimate needs `harness:task:create` and `harness:swarm:run`.
- Deciding an approval also needs Titan to accept your decision ([Approvals and autonomy](https://hexelstudio.com/docs/harness/approvals#decide-an-approval)).
- Downloading an evidence pack also needs Titan permissions ([Evidence packs](https://hexelstudio.com/docs/harness/evidence-packs#who-can-create-and-download-one)).
