> ## 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.

# Coming From AWS IAM

Telnyx IAM uses the same ideas as AWS IAM, so most of its vocabulary maps one to one. The deliberate difference is the role. A Telnyx role is a set of permissions a principal holds, never an identity anyone assumes.

## Vocabulary

| AWS IAM | Telnyx IAM |
| - | - |
| Account | Organization |
| Root user | [Organization owner](https://developers.telnyx.com/docs/iam/principals/organization-owner.md) |
| IAM user | [User](https://developers.telnyx.com/docs/iam/principals/users.md) |
| Application with access keys | [Service account](https://developers.telnyx.com/docs/iam/principals/service-accounts.md) with a token |
| Identity-based policy | [Role](https://developers.telnyx.com/docs/iam/access/roles.md), attached by a [grant](https://developers.telnyx.com/docs/iam/access/grants.md) |
| Policy statement | [Statement](https://developers.telnyx.com/docs/iam/access/statements.md) in a role |
| Action, such as `ec2:StartInstances` | [Action](https://developers.telnyx.com/docs/iam/access/actions.md), such as `number.update` |
| Resource ARN | `type/id`<sup>Preview</sup> in a statement |
| Condition | `conditions`<sup>Preview</sup> in a statement |
| Session policy, permissions boundary | [Scope](https://developers.telnyx.com/docs/iam/credentials/scoped-keys.md)<sup>Preview</sup> on a user's API key |
| Service control policy | [Guardrail](https://developers.telnyx.com/docs/iam/access/guardrails.md)<sup>Preview</sup> |
| Assume a role, cross-account role | No equivalent. A [delegation](https://developers.telnyx.com/docs/iam/access/delegations.md#a-delegation)<sup>Preview</sup> names principals from the manager organization |
| OIDC identity provider for CI | [Trusted workload](https://developers.telnyx.com/docs/iam/principals/trusted-workloads.md)<sup>Preview</sup> on a service account |
| Policy simulator | [Explain and simulate](https://developers.telnyx.com/docs/iam/troubleshooting/explain-and-simulate.md) |

## No Assuming Roles

An AWS principal assumes a role to work with that role's permissions for a while. A Telnyx principal holds its roles all the time, through [grants](https://developers.telnyx.com/docs/iam/access/grants.md), and every request is decided on them. The jobs that assuming a role does in AWS have their own tools.

* Preview A workload outside Telnyx, such as a CI job, trades its own token for a one-hour token of a [service account](https://developers.telnyx.com/docs/iam/principals/trusted-workloads.md).
* Preview A person who works in a customer's organization does it as themselves, through a [delegation](https://developers.telnyx.com/docs/iam/access/delegations.md#a-delegation) that names them with a role.
* Preview An API key that needs less than its user holds carries a [scope](https://developers.telnyx.com/docs/iam/credentials/scoped-keys.md). A job that needs less gets a service account of its own.

## Evaluation

Requests are decided the way AWS decides them. Nothing is allowed by default, an allow in any granted role is enough, and an explicit deny wins over any allow. Preview An API key's scope and the organization's guardrails narrow the result the way session policies, permission boundaries, and service control policies do. See [Evaluation Sequence](https://developers.telnyx.com/docs/iam/troubleshooting/evaluation-sequence.md).
