## About the changes Refactor the main nav, with the following goals: * Communicate the value of each section vs the format (ex: “Understanding Unleash” vs “Topic Guides”) * Make space for the Feature Flag tutorials section that we’re starting to build * Scope updates to navigation and pages that need updates based on new URLs & organization * Update URLs to follow the new hierarchy without breaking links (adding redirects & editing internal links between pages as needed) ### Important files sidebar.js docusaurus.config.js ## Discussion points * Redirects can't be tested out of prod, which is a bummer :/ * Some URLs have been preserved untouched while we monitor for potential negative SEO impact of client-side redirects * It's a large PR (sorry). Nav changes and file movements impacted lots of files. --------- Co-authored-by: Thomas Heartman <thomas@getunleash.ai>
1.6 KiB
title |
---|
Service Accounts |
:::info Availability
Service accounts is an enterprise feature available from Unleash 4.21 onwards.
:::
Service accounts are accounts that act as normal Unleash users and that respect the same set of permissions, but that don't represent real users. These accounts do not have a password and cannot log in to the Unleash UI. Instead, they are intended to be used to access the Unleash API programmatically, providing integrations an identity.
Use service accounts to:
- Provide a user-like identity to an integration or automation and manage it within Unleash
- Give access to the Unleash API without giving access to the Unleash UI
- Provide more fine-grained permissions than an admin token provides
In order to create a service account, you can follow the how to create service accounts guide.
Service account tokens
Service account tokens allow service accounts to use the Admin API as themselves with their own set of permissions, rather than using an admin token. See how to use the Admin API for more information.
These tokens act just like personal access tokens for the service accounts, except that they are managed by Unleash admins.
When using a service account token to modify resources, the event log will display the service account name for that operation.
Service account tokens can be managed by editing the respective service account: