Skip to main content
A user is a person in the organization. Every request a user sends, with a session, an API key, or an OAuth token, is decided by the roles granted to that user.

Identity

A user is identified by the id the Organization Users API returns, and that ID is the principal_id of a grant.
GET /v2/organizations/users
The organization owner is not in this list and cannot hold a grant.

Grants

Each grant gives a user one role. A user can hold up to ten roles, and their statements add up.
POST /v2/iam/grants
Once the organization has enabled IAM, a user without a grant is refused every action. Until then, a user keeps the permissions managed in Mission Control Portal, and grants have no effect. The permission groups in Mission Control Portal keep applying to a user on top of the user’s roles, until they retire.

Credentials

Whatever credential a user presents, IAM decides the request for the user.
  • A session, after signing in to Mission Control Portal.
  • An API key the user created.
  • An OAuth token an application holds for the user, such as the Telnyx CLI. The scope approved for that application still narrows the request after IAM allows it.
A credential proves who the user is. It never augments what the user’s roles allow. See Credentials.

Groups

Preview A grant also names a group of the organization’s identity provider, so access follows group membership.