# Service Access Tokens


We have expanded access to our APIs and services with [Service Access Tokens (SATs)]({{< ref "access-management/service-access-tokens.md" >}}). SATs can be created at the organization or workspace level and are not tied to individual user accounts. 

SATs are ideal for production use cases and centralized management of tokens across the RudderStack platform. 

Previously, access to RudderStack APIs required you to create [Personal Access Tokens](https://www.rudderstack.com/docs/dashboard-guides/personal-access-token/), which are tied to an individual user’s account. If that user account was removed, or permissions on the account were changed, access to APIs and services was impacted as well. 

With this release, you can create and manage central SATs to ensure stability and security for critical production workflows.

{{< info >}}
Contact the [RudderStack team](mailto:support@rudderstack.com) to get access to this feature.
{{< /info >}}

## How it works

Org Admins can create SATs at the organization or workspace level. 

**Organization-level SATs** can be used to access [SSO SCIM](https://www.rudderstack.com/docs/user-guides/sso-setup/) and the [Audit Log API](https://www.rudderstack.com/docs/api/audit-logs-api/), used for managing SCIM users and accessing audit logs from the platform, respectively.

**Workspace-level SATs** can be used to access resources in a specific workspace. These are used to manage programmatic workflows that leverage RudderStack APIs. Some examples are:

- Using the [Transformations API](https://www.rudderstack.com/docs/api/transformation-api/) to manage Transformations programmatically.
- Using the [Data Catalog API](https://www.rudderstack.com/docs/api/data-catalog-api/) to programmatically manage your Data Catalog and Tracking Plans.
- Using the [Test API](https://www.rudderstack.com/docs/api/test-api/) to run programmatic end-to-end pipeline tests.

Operations performed by both SAT types are logged and are available through the [Audit Logs view](https://www.rudderstack.com/docs/dashboard-guides/audit-logs/) and the [Audit Logs API](https://www.rudderstack.com/docs/api/audit-logs-api/).

## Create a SAT

To create SATs, Org Admins can access the Service Access Token view by going to **Settings** > **Organization** > **Service Access Tokens** tab.

Click the **Organization** or **Workspace** tab followed by **Generate new Token** to generate a new [Organization-level SAT]({{< ref "access-management/service-access-tokens.md#organization-level-sats" >}}) or [Workspace-level SAT]({{< ref "access-management/service-access-tokens.md#workspace-level-sats" >}}).

See the [Service Access Token documentation]({{< ref "access-management/service-access-tokens.md" >}}) for more information.

### Screenshots

The following screenshots highlight the SAT generation flow:

- Generate an organization-level SAT:

{{< image src="images/dashboard-guides/service-access-tokens/service-access-tokens-1.webp" alt="Service Access Tokens tab in RudderStack dashboard" >}}

- Copy newly-generated organization-level SAT:

{{< image src="images/dashboard-guides/service-access-tokens/org-sat.webp" alt="Note org level SAT value" >}}

- Generate a workspace-level SAT:

{{< image src="images/dashboard-guides/service-access-tokens/service-access-tokens-2.webp" alt="Service Access Tokens tab in RudderStack dashboard" >}}

- Specify workspace-level SAT permissions:

{{< image src="images/dashboard-guides/service-access-tokens/workspace-sat-generate.webp" alt="Generate workspace level SAT" >}}

- Copy newly-generated workspace-level SAT:

{{< image src="images/dashboard-guides/service-access-tokens/workspace-sat.webp" alt="Create workspace level SAT" >}}

<br />