Service accounts are non-interactive user accounts that are not tied to a human user or email address. They can participate in RBAC (similar to users) and inherit permissions based on the groups they belong to and any direct permissions granted to the user account, allowing you to control what the account can and can't do on the platform.

What are service accounts used for?

Service accounts are useful in use cases like the following:

• Automated API access. Use service accounts to authenticate automated scripts or tools that interact with the Observe API so that the account can trigger queries, pull telemetry, or manage resources programmatically.
• Integrations and automation. Use a service account to provide a machine-friendly identity with specific permissions for integration Observe with external systems like CI/CD pipelines, incident response tools, and data workflows.
• Background processes. Tasks such as scheduled data exports, automated report generation, or internal tooling that needs to act as Observe can use a service account to authenticate without requiring a person to log in at inconvenient times.

• How do I create a service account?

You can create service accounts by using the API, or the Observe UI.

• Manage service accounts using the API
• Manage service accounts using the UI