---
question: Can this person do this action on this resource, and which statement decides it?
kind: task
via_web: available
via_cli: na
via_python: na
via_api: available
via_config: na
ref_web: Roles & permissions › Simulator
ref_api: POST /api/iam/admin/simulate
prereq: You are the platform admin, or you hold `iam:Explain` at the platform.
next:
  - /capabilities/platform/give-someone-access
  - /capabilities/platform/view-as-another-person
---

# Test access with the simulator

The simulator asks IAM the question every service asks, for a principal you name: may it do this action on this resource? It answers Allowed or Denied, why, and the statement that decided, with its policy, where it is attached and through which group. It changes nothing.

To see the pages as a person sees them, rather than one decision, use [View as another person](/capabilities/platform/view-as-another-person).

## Web UI

### Open the Simulator

Open the account menu, **Platform Settings**, then **Roles & permissions** under Access, then **Simulator**.

### Ask

Fill the three fields:

- **Can this principal…**: a user or service account id, such as `usr_01jexample0000000000000000`. The field suggests them as you type.
- **…do this action…**: an action, such as `module:UseAgent`.
- **…on this resource?**: a resource name, such as `abi:nexus:organization/<org>/nexus:workspace/<ws>/module:agent/harbor.tickets/Triage`.

Choose **Simulate**.

### Read the answer

The answer is **Allowed** or **Denied**, with the reason:

| Reason | Means |
|---|---|
| A statement allows it and no Deny excludes it. | Allowed. |
| A Deny statement matches: an explicit Deny always wins. | Denied by a Deny. |
| No statement allows it: everything is denied unless a policy allows it. | Denied by default. |
| The principal is suspended or deleted: it is denied everything. | Denied: the principal is inactive. |
| The resource is sealed: only its owner opens it, whatever the policies say. | Denied: a sealed resource. |

**Deciding statement** shows its **Effect**, who **Held by**, the **Policy**, the **Statement** number and sid, the **Attachment**, where it is **Attached at** and **Through group**, and the statement itself when you may read its policy. "No statement decided this: nothing names it." means no policy names that action on that resource.

## CLI

Not applicable. `abi iam` has no command that explains a decision. Use the Web UI.

## Python

Not applicable. The SDK checks the module's own access; it does not explain another principal's. Use the Web UI.

## REST API

:::warning Session only
The routes under `/api/iam/admin/` take a signed-in session only. A personal API key (`abi_pk_…`) is refused with 403 on `/api/iam/`, so a script that holds one cannot call them.
:::

```http
POST /api/iam/admin/simulate
Content-Type: application/json

{
  "principal_id": "usr_01jexample0000000000000000",
  "action": "module:UseAgent",
  "resource": "abi:nexus:organization/<org>/nexus:workspace/<ws>/module:agent/harbor.tickets/Triage"
}
```

The answer has `allowed`, the `reason` (`allow`, `explicit_deny`, `implicit_deny`, `suspended` or `sealed`) and the deciding statement. For a sub-policy it also names each parent statement that allowed it too, and the sub-policies a parent's Deny was reached through.

## Config

Not applicable. The simulator only reads what IAM holds.
