> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IAM

Telnyx IAM decides what each person and each workload in an organization may do with the Telnyx API. The organization writes roles from the exact actions a job needs, grants them to its users and service accounts, and every request to every product is checked against those roles.

> [!WARNING]
>
> **Items marked Preview** are not available yet. Their pages show the intended behavior and API, which may change before they are made available.

## Without IAM and With IAM

Without IAM, an API key carries every permission of the user who created it, and the owner's keys can do everything in the organization. Limiting that means working across several separate systems. Each covers part of the API, and none can take a single action away.

| | Without IAM | With IAM |
| - | - | - |
| API key | Everything its user may do, and everything for the owner | What the roles of its user allow |
| Permissions | Spread across portal groups, user policies, and service account action lists | [Roles](https://developers.telnyx.com/docs/iam/access/roles.md), [granted](https://developers.telnyx.com/docs/iam/access/grants.md) to users and service accounts alike |
| Permission unit | A resource category with read, create, update, or delete | One [action](https://developers.telnyx.com/docs/iam/access/actions.md), such as `number.update` |
| Unrestricted user | Refused some products and unrestricted in others | Refused everything until a role allows it, once IAM is [enabled](https://developers.telnyx.com/docs/iam/organization/enable-iam.md) |
| Exceptions | Not possible, because every system only allows | A [deny statement](https://developers.telnyx.com/docs/iam/troubleshooting/evaluation-sequence.md) wins over any allow |
| Managed organizations | Full owner access | The person's own [roles in the manager org](https://developers.telnyx.com/docs/iam/access/delegations.md), and a [delegation](https://developers.telnyx.com/docs/iam/access/delegations.md#a-delegation)<sup>Preview</sup> per managed org |
| Refused requests | Not permitted, with no reason | The action needed and the [roles that denied it](https://developers.telnyx.com/docs/iam/troubleshooting/denied-requests.md) |
| Narrowing an API key | Allowed networks | A [scope](https://developers.telnyx.com/docs/iam/credentials/scoped-keys.md)<sup>Preview</sup> of actions and networks |
| CI pipelines | A stored long-lived token | A [one-hour token](https://developers.telnyx.com/docs/iam/principals/trusted-workloads.md)<sup>Preview</sup>, nothing stored |
| Prod and staging | Separate organizations | [Projects](https://developers.telnyx.com/docs/iam/access/projects.md)<sup>Preview</sup> in one organization |
| Org-wide rules | None that bind the owner | [Guardrails](https://developers.telnyx.com/docs/iam/access/guardrails.md)<sup>Preview</sup> that bind everyone |
| Identity provider | Groups mapped to portal permission groups | [Groups](https://developers.telnyx.com/docs/iam/principals/groups.md)<sup>Preview</sup> as principals, and SCIM |
| Testing a change | Not possible | [Explain and simulate](https://developers.telnyx.com/docs/iam/troubleshooting/explain-and-simulate.md) |

## Managing IAM

The organization owner manages IAM through the API at `/v2/iam`. Roles and grants can be written while IAM is off and change nothing until the owner [enables IAM](https://developers.telnyx.com/docs/iam/organization/enable-iam.md), so an organization moves at its own pace, one user or service account at a time. An organization that already uses Telnyx keeps everything as it is until then.

The [Quick Start](https://developers.telnyx.com/docs/iam/quickstart.md) gives a release pipeline its own service account and a role with three actions. [How IAM Works](https://developers.telnyx.com/docs/iam/how-it-works.md) explains how a request is decided, and [IAM and Permission Groups](https://developers.telnyx.com/docs/iam/permission-groups.md) sets IAM beside the permission groups in Mission Control Portal. The scenarios walk through [setting up a new organization](https://developers.telnyx.com/docs/iam/scenarios/new-organization.md), [migrating an existing account](https://developers.telnyx.com/docs/iam/scenarios/existing-organization.md), and [managing customer organizations](https://developers.telnyx.com/docs/iam/scenarios/customer-organizations.md) step by step.
