A service account is a service account designed for non-human identities. It provides a secure way for scripts, CI jobs, automated services, and other workloads to interact with your 3B environment.
Service accounts are visually distinguished in the user interface by a robot icon, making them easy to identify separately from human team members.
How service accounts are used
Service accounts operate similarly to service accounts in other platforms, providing dedicated identities for automation.
Authentication methods
To ensure secure access, service accounts support several authentication methods:
API keys: Use long-lived secret keys for persistent authentication.
Temporary credentials: Generate short-lived keys that expire automatically for enhanced security.
Federation: Utilize OIDC tokens from trusted providers (such as GitHub Actions) to authenticate without needing to store static keys.
Permissions and access
Service accounts function as independent identities with their own specific permissions and roles. You can:
Grant service accounts access to specific spaces, connectors, skills, and networks.
Assign tenant-wide roles to service accounts for administrative tasks.
Authorize applications via OAuth to obtain credentials on behalf of a service account.
Learn how to create service accounts here.