ref(settings): Rename auth tokens (#13914)

Rename `Auth Token` and `User Auth Token` to `Organization Token` and
`Personal Token` respectively.
Update screenshots on affected pages.

- part of [TET-556: Merge sections and rename Auth Tokens and User Auth
Tokens](https://linear.app/getsentry/issue/TET-556/merge-sections-and-rename-auth-tokens-and-user-auth-tokens)
- requires getsentry/sentry#92803

Author: ArthurKnaus

docs/account/auth-tokens/img/org-auth-token-create.png

@@ -18,32 +18,32 @@ We recommend using a separate auth token for each use case. For example, you wou
 
 There are three key types of auth tokens in Sentry:
 
-- [Organization Auth Tokens](#organization-auth-tokens):
+- [Organization Tokens](#organization-tokens):
   These tokens are bound to an organization, and have access to all projects within that organization. They have a limited set of permissions and are designed to be used in CI environments and with Sentry CLI.
 
 - [Internal Integrations](#internal-integrations):
-  These tokens are bound to an organization, and have access to all projects within that organization. They can be created with a custom set of permissions, and are designed to be used in cases where organization auth tokens don't have sufficient access rights.
+  These tokens are bound to an organization, and have access to all projects within that organization. They can be created with a custom set of permissions, and are designed to be used in cases where organization tokens don't have sufficient access rights.
 
-- [User Auth Tokens](#user-auth-tokens):
+- [Personal Tokens](#personal-tokens):
   These tokens are bound to a user, and have access to all organizations and projects that user has access to.
 
 ### When Should I Use Which?
 
-For most scenarios, we recommend using [Organization Auth Tokens](#organization-auth-tokens). They are designed to be used in CI environments and have a limited set of permissions. This means that if the place you stored the auth token is compromised, the attacker can only do limited damage.
+For most scenarios, we recommend using [Organization Tokens](#organization-tokens). They are designed to be used in CI environments and have a limited set of permissions. This means that if the place you stored the auth token is compromised, the attacker can only do limited damage.
 
-Organization auth tokens permissions aren't customizable. They are set to allow most CI-related tasks, without any unnecessary permissions.
+Organization tokens permissions aren't customizable. They are set to allow most CI-related tasks, without any unnecessary permissions.
 
-[Internal Integrations](#internal-integrations) should be used when you need full API access (which the organization auth tokens cannot grant), and you want to interact with the Sentry API on behalf of an organization. For example, to programmatically create a new project, you would use an internal integration.
+[Internal Integrations](#internal-integrations) should be used when you need full API access (which the organization tokens cannot grant), and you want to interact with the Sentry API on behalf of an organization. For example, to programmatically create a new project, you would use an internal integration.
 
 Permissions for auth tokens created as part of an internal integration are customizable and editable.
 
-[User Auth Tokens](#user-auth-tokens) should be used to interact with the Sentry API on behalf of a user. For example, to fetch all issues for a user, you would use a user auth token. We don't recommend using user auth tokens for CI tasks because if the user who created the token is removed from the Organization, the token will stop working.
+[Personal Tokens](#personal-tokens) should be used to interact with the Sentry API on behalf of a user. For example, to fetch all issues for a user, you would use a personal token. We don't recommend using personal tokens for CI tasks because if the user who created the token is removed from the Organization, the token will stop working.
 
-User auth token permissions are customizable but cannot be edited later.
+Personal token permissions are customizable but cannot be edited later.
 
-### Organization Auth Tokens
+### Organization Tokens
 
-[Organization auth tokens](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/) can be created in [sentry.io](https://sentry.io) on the **Auth Tokens** page under **Settings > Developer Settings > Auth Tokens**.
+[Organization tokens](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/) can be created in [sentry.io](https://sentry.io) on the **Auth Tokens** page under **Settings > Developer Settings > Organization Tokens**.
 
 ![](./img/org-auth-tokens-overview.png)
 
@@ -53,36 +53,36 @@ They can also be generated on certain pages of Sentry's docs if you're signed in
 
 </Alert>
 
-Organization auth token names are generated for you unless you create the token through the Sentry UI. This name is only used for display purposes - it helps to identify an auth token in case you want to revoke it later. You can change the name for an organization auth token at [sentry.io](https://sentry.io) on the **Edit Auth Token** page under **Settings > Developer Settings > Auth Tokens**.
+Organization token names are generated for you unless you create the token through the Sentry UI. This name is only used for display purposes - it helps to identify an auth token in case you want to revoke it later. You can change the name for an organization token at [sentry.io](https://sentry.io) on the **Edit Auth Token** page under **Settings > Developer Settings > Organization Tokens**.
 
-For security reasons, organization auth tokens are only visible _once_, right after you create them. If you lose the auth token, you will have to create a new one. This means you can't see the full token on the overview page or on the token detail page, you can only see the last characters of the token to help identify it.
+For security reasons, organization tokens are only visible _once_, right after you create them. If you lose the auth token, you will have to create a new one. This means you can't see the full token on the overview page or on the token detail page, you can only see the last characters of the token to help identify it.
 
-Any user can create organization auth tokens for any of their organizations. This allows any user (not only organization owners) to configure a Sentry SDK and set up CI processes by creating and using organization auth tokens. Since organization auth tokens have limited access, there is limited potential for abuse.
+Any user can create organization tokens for any of their organizations. This allows any user (not only organization owners) to configure a Sentry SDK and set up CI processes by creating and using organization tokens. Since organization tokens have limited access, there is limited potential for abuse.
 
 ![](./img/org-auth-token-create.png)
 
-All owners of the organization will receive a security email when a new organization auth token is created and can revoke these tokens at any point. _Only_ organization owners & managers can revoke organization auth tokens .
+All owners of the organization will receive a security email when a new organization token is created and can revoke these tokens at any point. _Only_ organization owners & managers can revoke organization tokens .
 
 ### Internal Integrations
 
 We recommend only using an internal integration when you want to interact with the Sentry API on behalf of an organization. See Sentry's API [Authentication](/api/auth/) docs for more information on how to do this.
 
 To get started, see our docs on [Internal Integrations](/organization/integrations/integration-platform/).
 
-### User Auth Tokens
+### Personal Tokens
 
-[User auth tokens](https://sentry.io/settings/account/api/auth-tokens/) can be created in [sentry.io](https://sentry.io) on the **User Auth Tokens** page under the Account dropdown in the top left.
+[Personal tokens](https://sentry.io/settings/account/api/auth-tokens/) can be created in [sentry.io](https://sentry.io) on the **Personal Tokens** page under the Account dropdown in the top left.
 
 ![](./img/user-auth-tokens-menu.png)
 
-User auth tokens can be created by any user, and are bound to that user. The tokens can be given permissions to all organizations and projects that user has access to. This means a user auth token's _maximum_ scope is all the scopes that the user has access to for a given organization. A user auth token cannot exceed the permissions of the user who created it. See [Organization and User Management](/organization/membership/) for more details on how permissions work in Sentry.
+Personal tokens can be created by any user, and are bound to that user. The tokens can be given permissions to all organizations and projects that user has access to. This means a personal token's _maximum_ scope is all the scopes that the user has access to for a given organization. A personal token cannot exceed the permissions of the user who created it. See [Organization and User Management](/organization/membership/) for more details on how permissions work in Sentry.
 
-When you create a new user auth token, you can select which [scopes](/api/permissions/) the token should have in the UI:
+When you create a new personal token, you can select which [scopes](/api/permissions/) the token should have in the UI:
 
 ![](./img/user-auth-token-create.png)
 
-Currently, you can view user auth tokens in the UI after creating them. This is a legacy behavior that may change in the future. We recommend only using each user auth token once, and creating a new token for each use case. Any user can always revoke any of their user auth tokens.
+Currently, you can view personal tokens in the UI after creating them. This is a legacy behavior that may change in the future. We recommend only using each personal token once, and creating a new token for each use case. Any user can always revoke any of their personal tokens.
 
 ![](./img/user-auth-tokens-overview.png)
 
-We recommend only using a user auth token to interact with the Sentry API on behalf of a user. See Sentry's API [Authentication](/api/auth/) docs for more information on how to do this.
+We recommend only using a personal token to interact with the Sentry API on behalf of a user. See Sentry's API [Authentication](/api/auth/) docs for more information on how to do this.

docs/account/auth-tokens/img/org-auth-tokens-overview.png

@@ -23,7 +23,7 @@ You can create authentication tokens within Sentry by [creating an internal inte
 
 ### User authentication tokens
 
-Some API endpoints require an authentication token that's associated with your user account, rather than an authentication token from an internal integration. These auth tokens can be created within Sentry on the "User settings" page (**User settings > User Auth Tokens**) and assigned specific scopes.
+Some API endpoints require an authentication token that's associated with your user account, rather than an authentication token from an internal integration. These auth tokens can be created within Sentry on the "User settings" page (**User settings > Personal Tokens**) and assigned specific scopes.
 
 The endpoints that require a user authentication token are specific to your user, such as [Retrieve an Organization](/api/organizations/retrieve-an-organization/).
 

docs/account/auth-tokens/img/user-auth-token-create.png

@@ -13,7 +13,7 @@ See our documentation on [authentication](/api/auth/) to learn more about the di
 
 ## Create an Internal Integration
 
-[Internal integrations](/organization/integrations/integration-platform/internal-integration/) are used to create custom Sentry integrations for your organization. They can also be used to create and manage your organization auth tokens.
+[Internal integrations](/organization/integrations/integration-platform/internal-integration/) are used to create custom Sentry integrations for your organization. They can also be used to create and manage your organization tokens.
 
 1. Open [sentry.io](https://sentry.io/)
 

docs/account/auth-tokens/img/user-auth-tokens-menu.png

@@ -14,7 +14,7 @@ APIs used in this tutorial:
 
 - A Sentry authentication token with team:write scopes or higher and project:read scopes or higher.
 
-  > If you don't have an authentication token, follow the [Create a Sentry Authentication Token](/api/guides/create-auth-token) tutorial to create an organization auth token with the following permissions, or higher:
+  > If you don't have an authentication token, follow the [Create a Sentry Authentication Token](/api/guides/create-auth-token) tutorial to create an organization token with the following permissions, or higher:
   >
   > - Organization: Read
   > - Team: Write