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

# Enterprise Template

The enterprise template is one request that sets the posture most enterprises want. Nobody uses an API key, automation runs on service account tokens, and every token lives at most ninety days. Single sign-on is optional and is set up in Mission Control Portal.

> [!WARNING]
>
> **Preview.** Not available yet.

## Applying It

```json POST /v2/iam/settings/actions/apply_template theme={null}
{
  "template": "enterprise"
}
```

The template writes two things, which the organization can read and change afterwards.

| Setting | What the Template Writes |
| - | - |
| [Guardrail](https://developers.telnyx.com/docs/iam/access/guardrails.md) | Nobody can create an API key, and a request with an API key is denied, the owner's included. |
| Token rules | Every new [service account token](https://developers.telnyx.com/docs/iam/principals/service-accounts.md#tokens) lives at most ninety days. |

```json GET /v2/iam/settings theme={null}
{
  "data": {
    "service_account_tokens": {
      "max_lifetime_days": 90
    },
    ...
  }
}
```

## Single Sign-On

Single sign-on is optional, and the template does not change it. An organization that wants it connects its identity provider and makes sign-in through it mandatory in Mission Control Portal, where the user who created the organization stays exempt as the way in if the identity provider is down. See [Identity Provider](https://developers.telnyx.com/docs/iam/organization/identity-provider.md).

## For an Existing Organization

The guardrail line stops API keys working at all, so an organization applies the template last, after every integration has moved to a [service account](https://developers.telnyx.com/docs/iam/principals/service-accounts.md) with its own token.
