• Welcome to Skillset
  • Integrations
    • API access
    • Service accounts
    • Skillset MCP
  • Knowledge and support
    • Create, review, and publish knowledge articles
    • Troubleshooting and support
  • Tickets
    • Configure AI assistance
    • Manage access and data protection
    • Set up your workspace and integrations

Powered by Skillset

Powered by Skillset

  1. Home
  2. /Integrations

Service accounts

Updated 5 days ago

Use a service account for scripts, scheduled jobs, and integrations that need company-owned REST API access. It has its own permissions and workspace grants, and keeps working when its creator leaves.

Create a service account

Open Settings and go to General → Service accounts under the organization or workspace you administer.

Your roleWhereAccounts you can manage
Organization owner or adminOrganization → GeneralAll accounts, with access to one or more workspaces
Workspace adminYour workspace → GeneralAccounts restricted to that workspace

Members without an admin role cannot create accounts or manage keys.

  1. Select Create service account and enter a name, such as Support reporting.
  2. Choose permissions and workspaces. In workspace settings, the workspace is fixed.
  3. Select Save account.
  4. Select Manage keys → Create key, enter a key name, and choose an expiration.
  • Copy the key into a secret manager. It is shown only once.
  • Send it as Authorization: Bearer <key>. See API access for endpoints and examples. Service-account keys work with REST, not MCP.

    Access and scopes

    Access is limited to assigned workspaces and granted scopes. The account does not inherit its creator's permissions. Defaults are ticket read and public-only knowledge read.

    ScopeGrants
    knowledge:read:publicSearch and read articles published for anonymous access
    knowledge:readSearch and read all collections in assigned workspaces, including restricted collections
    tickets:readList and read tickets
    tickets:writeCreate and update tickets
    tickets:deleteDelete tickets

    For knowledge, choose None, Public only, or Normal read. Ticket scopes are independent: write and delete do not include read.

    Use Edit access to change permissions or workspaces. Reductions take effect on the next request. Keys retain their original scope ceiling, so adding a scope requires a new key. Accounts spanning multiple workspaces are managed from organization settings.

    Expiration and rotation

    Keys expire after 30, 90, or 365 days, or have No expiration. The default is 90 days. The account itself does not expire; keys do not renew automatically.

    To rotate, create a replacement in Manage keys, update your integration, then revoke the old key. Revocation takes effect on the next request. To pause all keys, clear Account enabled in Edit access. Re-enabling restores unexpired, unrevoked keys.

    Rate limits

    Each service account has a separate budget of 120 reads and 30 writes per minute by default. All its keys share that budget across workspaces. It is separate from regular users' budgets, including its creator's. Creating or rotating keys does not increase it.

    Over the limit, the API returns 429. Wait for the seconds in Retry-After before retrying.