> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Service accounts

> Prepare machine identities and access requirements while service-account operations are unavailable.

A service account represents an application or automated job independently of a person's sign-in. Define its owner, purpose, and required permissions before issuing machine credentials.

<Note>
  Service accounts are being rebuilt around machine-to-machine authentication. Listing, creation, and service-account API-key operations currently return HTTP 501. The dashboard page and public contracts do not establish a usable service-account lifecycle.
</Note>

## Prepare an automation identity

Work with the workspace administrator and the person responsible for the application.

<Steps>
  <Step title="Describe the workload" id="service-accounts-workload">
    Record the application name, environment, owner, and expected API operations. Separate a production workload from development or local testing.
  </Step>

  <Step title="Specify access" id="service-accounts-access">
    List required resources and read or write actions. Identify any publication, deletion, or credential-management actions that need an explicit review step.
  </Step>

  <Step title="Define credential operations" id="service-accounts-credentials">
    Assign responsibility for credential storage, rotation, revocation, and incident response. Record how the application should behave when access expires or is removed.
  </Step>
</Steps>

The [service-account list](/api-reference/workspace/list-workspace-service-accounts) and [creation contract](/api-reference/workspace/create-workspace-service-account) remain reference material for the unavailable operations. Repeated requests will not enable them.

[Personal API keys](/overview/administration/workspaces/api-keys) have a separate implemented lifecycle. They retain human ownership and should not be described as service accounts. If that ownership model does not meet your workload's requirements, keep the integration's identity setup pending.

<AccordionGroup>
  <Accordion title="Can I create one using the visible dashboard form?" id="service-accounts-faq-form">The current backend rejects service-account operations with HTTP 501, including requests from that form.</Accordion>
  <Accordion title="Can an old service-account key workflow be reused?" id="service-accounts-faq-legacy">The prior API-key-backed implementation has been removed. Wait for the supported replacement lifecycle.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.