Skip to main content
A statement allows or denies a list of actions, and every role is a set of statements.

A Statement

A statement has an effect and a list of actions, and lives in a role.
Preview A statement also names resources, projects, and conditions.
Preview A statement matches as a whole, never field by field. A role allowed in staging and a read-only role in prod never add up to a change in prod.

Three Places a Statement Takes Effect

A statement does nothing until it is attached, and it can be attached in three places.
A request needs an allow from a role’s statements and no deny. Preview It also needs an allow from the scope, if the credential has one, and from every guardrail that applies, with no deny in any of them.

Specific Resources, Plainly

Preview A statement can name specific resources, such as two sending numbers.
  • The IDs live in the statement and nowhere else.
  • Telnyx does not check that they exist. Saving a statement checks each ID’s format and warns if one is not found, but saves it anyway.
  • A wrong ID never matches. In an allow it grants nothing, and in a deny it protects nothing.
  • The product that owns the resource does the checking. IAM allows the action and passes the list along, and the product compares it with the resource the request names, in the URL or in the body.
  • Lists of specific resources are capped. For larger sets, use a project or a managed organization.