Skip to main content
Single sign-on through an identity provider is optional, and IAM decides requests the same way with or without it. An organization that wants it sets it up in Mission Control Portal. With an identity provider connected, its groups become principals that grants can name, and, with SCIM, joiners and leavers are provisioned automatically.
Preview. Groups as principals and SCIM are not available yet. Single sign-on itself is configured in Mission Control Portal, outside the IAM API.

Sign-In

The organization connects its identity provider in Mission Control Portal and chooses there whether sign-in through it is mandatory. The support site shows the setup for Okta and other SAML providers. IAM decides a request the same way whether the user signed in with a password or through the identity provider.

Groups

The identity provider’s groups become group principals, named okta/voice-team for the Okta group voice-team. A grant that names a group reaches each of its members, and moving someone between groups changes their access with it.

SCIM

With SCIM, the identity provider creates and removes Telnyx users and keeps group membership in step, so nobody touches Telnyx when people join, move, or leave.
PATCH /v2/iam/settings
Output
The response holds what to paste into the identity provider. Someone removed there loses Telnyx access at once, open sessions included, and a person who leaves a manager organization loses access to every managed organization at the same moment.