Announcement
This page is also available in Deutsch, Español, Français, Italiano, 日本語, and Português.
Cloud Intelligence™ Service Accounts and API Tokens: Identity for Every Integration
You can create a dedicated Service Account identity owned by your organization, preventing reliance on user-level tokens for automation
By Eric E.
·Shipped by
Chaim, Josue, Benjamin H., Anthony M.
What's New
- Up to 10 tokens per user: Create a separate token for each integration, script, or environment tied to your account. No more sharing one credential across everything you've connected.
- Org-owned Service Accounts for automated work: A Service Account belongs to the organization, not a person. It keeps working through role changes and offboarding.
- Up to 10 API tokens per Service Account: Organizations get the same flexibility at the account level. Use one token per integration, environment, or workflow.
- Scoped permissions at both levels: A personal token carries only a slice of your existing role. A Service Account draws from a curated subset of org-level roles.
- Predictable expiration: All tokens default to a one-year lifetime.
- Independent lifecycle management: Rotate, disable, or delete one token without affecting the others.
Personal Tokens vs. Service Accounts
- Use a personal token when the integration is tied to you: a script you run, or a tool you connect under your own login.
- Use a Service Account when the integration needs to outlive any one person: a billing pipeline, a reporting job, or anything the team depends on regardless of who built it.
Token Lifecycle
Every token, personal or Service Account, moves through four states:
| State | Description |
|---|---|
| Active | In use and valid |
| Disabled | Suspended but recoverable |
| Expired | Past the expiration date (default: 1 year) |
| Deleted | Permanently revoked |
Why It Matters
- Eliminate credential sharing liabilities: A single token shared across five integrations is a liability. Rotate it, and everything breaks at once. Split tokens by integration instead, personal or org-owned, so each one rotates on its own.
- Remove individual dependencies: Most platforms tie automated access to whoever set it up. Service Accounts remove that dependency, so pipelines and reporting jobs keep running through team changes.
Get Started
- Manage your personal API tokens: Click your email address in the user menu, in the top-right corner of the header, under your organization name.
- Set up a Service Account: Go to Settings → Users & Access → Service Accounts.
- Learn more in our Help docs
Related documentation
