Enterprise organizations can now create service accounts: dedicated, organization-owned identities for programmatic access such as CI/CD pipelines, automation scripts, and backend integrations. They aren't tied to any individual, so automated workflows keep running even as team members join or leave the organization.
Admins manage them from the organization settings, where access is granted exclusively through fine-grained tokens scoped to what each workflow needs. Tokens can be generated, updated, rotated, or revoked at any time. Service accounts can also be added to resource groups, making it easy to align automated workflows with your organization's existing access structure. Because service accounts don't consume a paid seat, they can be scoped and isolated without impacting member quotas or billing.
