Revert "Standardize API token docs and migrate team → workspace terminology"

This reverts commit 76ca25c.

Author: samaybar

redirects.js

@@ -99,11 +99,6 @@ const redirects = [
     destination: "/reference/errors",
     permanent: true,
   },
-  {
-    source: "/reference/teams",
-    destination: "/reference/workspaces",
-    permanent: true,
-  },
 ];
 
 const hashRedirects = [

src/docs/guides/cli.md

@@ -96,23 +96,23 @@ In situations where user input or interaction isn't possible, such as in CI/CD p
 
 A [Project Token](/guides/public-api#project-token) is set via the `RAILWAY_TOKEN` environment variable.
 
-An [Account](/guides/public-api#using-an-account-token) or [Workspace](/guides/public-api#using-a-workspace-token) Token is set via the `RAILWAY_API_TOKEN` environment variable.
+An [Account](/guides/public-api#personal-token) or [Team](/guides/public-api#team-token) Token is set via the `RAILWAY_API_TOKEN` environment variable.
 
-**Note:** If both environment variables are set, `RAILWAY_TOKEN` takes precedence. This allows you to use a project token for specific deployments while having a broader account token configured.
+**Note:** You can only use one type of token at a time. If both are set, the `RAILWAY_TOKEN` variable will take precedence.
 
 #### Project Tokens
 
-You can use [Project Tokens](/guides/public-api#project-token) to authenticate project-level actions within a single environment.
+You can use [Project Tokens](/guides/public-api#project-token) to authenticate project-level actions.
 
-Project tokens are scoped to a specific environment within a project. If you need to perform actions across multiple environments, use an account or workspace token instead.
+Project Tokens allow the CLI to access all the project-level actions in the environment set when the token was created.
 
-Some actions you can perform with a project token include:
+Some actions you can perform with a project token include -
 
 - Deploying code - `railway up`
 - Redeploying a deployment - `railway redeploy`
 - Viewing build and deployment logs - `railway logs`
 
-Some actions you **cannot** perform with a project token include:
+Some actions you **cannot** perform with a project token include -
 
 - Creating a new project - `railway init`
 - Printing information about the user - `railway whoami`
@@ -126,32 +126,26 @@ RAILWAY_TOKEN=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX railway up
 
 #### Account Tokens
 
-You can use [Account Tokens](/guides/public-api#using-an-account-token) to authenticate all CLI actions across all your resources and workspaces. This is the broadest scope—all CLI commands are available with an account token.
+Account Tokens come in two types - [Personal Account Tokens](/reference/public-api#personal-token) and [Team Tokens](/reference/public-api#team-token).
 
-Some actions you can **only** perform with an account token include:
+You can use Account Tokens to authenticate all CLI actions across all workspaces.
 
-- Printing information about the user - `railway whoami`
-- Linking to projects in any of your workspaces - `railway link`
-
-Use the token by setting the `RAILWAY_API_TOKEN` environment variable and then running `railway <command>`.
+However, you can only use Team tokens to authenticate actions on projects within the workspace the token was scoped to when it was created.
 
-```bash
-RAILWAY_API_TOKEN=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX railway whoami
-```
+Some actions you can perform with a personal account token include -
 
-#### Workspace Tokens
-
-You can use [Workspace Tokens](/guides/public-api#using-a-workspace-token) to authenticate CLI actions on projects within a specific workspace. Use this when you want to share a token with teammates without giving access to your other workspaces.
+- Creating a new project - `railway init`
+- Printing information about the user - `railway whoami`
 
-Some actions you **cannot** perform with a workspace token include:
+Some actions you **cannot** perform with [Team Token](/reference/public-api#team-token) include -
 
 - Printing information about the user - `railway whoami`
-- Linking to projects outside the token's workspace - `railway link` (you can still link to other projects within the workspace)
+- Linking to another workspace - `railway link`
 
 Use the token by setting the `RAILWAY_API_TOKEN` environment variable and then running `railway <command>`.
 
 ```bash
-RAILWAY_API_TOKEN=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX railway up
+RAILWAY_API_TOKEN=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX railway whoami
 ```
 
 ## Common Examples of CLI Usage
@@ -162,17 +156,17 @@ Below are some of the most commonly used CLI commands. Find a complete list of C
 
 To associate a project and environment with your current directory:
 
-<Image src="https://res.cloudinary.com/railway/image/upload/v1770156020/docs/railway-link-2026_dwz6mi.png"
-alt="Screenshot of railway link command"
+<Image src="https://res.cloudinary.com/railway/image/upload/v1631917786/docs/railway-link_juslvt.png"
+alt="Screenshot of Railway"
 layout="intrinsic"
-width={824} height={294} quality={80} />
+width={389} height={116} quality={80} />
 
 ```bash
 # Link to a project
 railway link
 ```
 
-This prompts you to select a workspace, project, and environment to associate with
+This prompts you to select a team, project, and environment to associate with
 your current directory. Any future commands will be run against this project and environment.
 
 ### Link to a Service
@@ -195,7 +189,7 @@ Create a new project directly from the command line.
 railway init
 ```
 
-This prompts you to name your project and select a workspace to create the project in.
+This prompts you to name your project and select a team to create the project in.
 
 ### Local Development
 

src/docs/guides/create.md

@@ -35,7 +35,7 @@ Note that your template will not be available on the template marketplace, nor w
 
 It's now possible to specify a private GitHub repo when creating a template.
 
-This feature is intended for use among [Teams](/reference/workspaces) and [Organizations](/reference/workspaces). Users supporting a subscriber base may also find this feature helpful to distribute closed-source code.
+This feature is intended for use among [Teams](/reference/teams) and [Organizations](/reference/teams). Users supporting a subscriber base may also find this feature helpful to distribute closed-source code.
 
 To deploy a template that includes a private repo, look for the `GitHub` panel in the `Account Integrations` section of [General Settings](https://railway.com/account). Then select the `Edit Scope` option to grant Railway access to the desired private repos.
 

src/docs/guides/environments.md

@@ -51,7 +51,7 @@ When enabled, a temporary environment is spun up to support the Pull Request dep
 
 #### How Come my GitHub PR Won't Deploy?
 
-Railway will not deploy a PR branch from a user who is not in your workspace or invited to your project without their associated GitHub account.
+Railway will not deploy a PR branch from a user who is not in your team or invited to your project without their associated GitHub account.
 
 #### Domains in PR Environments
 

src/docs/guides/optimize-usage.md

@@ -13,9 +13,9 @@ Visit the <a href="https://railway.com/workspace/usage" target="_blank">Workspac
 
 <Image src="https://res.cloudinary.com/railway/image/upload/v1743193518/docs/usage-limits_pqlot9.png" alt="Usage Limits Modal" layout="responsive" width={1200} height={1075} />
 
-#### Setting Limits for Workspaces
+#### Setting Limits for Teams
 
-If you want to set a usage limit for a different workspace that you are an admin of, use the account switcher in the top left corner of your dashboard to access that workspace's usage page.
+If you want to set a usage limit for your team, use the account switcher in the top left corner of your dashboard to access the team's usage page.
 
 ### Custom Email Alert
 

src/docs/guides/projects.md

@@ -49,11 +49,11 @@ Each project generates a project invite link. To invite someone via a link:
 
 ## Transferring Projects
 
-Projects can be transferred between workspaces or to other users. Both the source and destination must have an active [Hobby or Pro plan](/reference/pricing#plans) subscription.
+Depending on your plan, you can transfer Projects to other users or Teams.
 
-#### Transferring to Another User
+#### Hobby User to Hobby User
 
-To transfer a project to another user, you must first [add the user as a member](#inviting-members) of the project.
+To transfer a project from one Hobby User to another Hobby User, you must first [add the user as a member](#inviting-members) in the project.
 
 You can then transfer the project to the new member by selecting the three dots next to the user and choosing `Transfer Ownership`.
 
@@ -62,15 +62,15 @@ alt="Screenshot of Project Transfer Menu"
 layout="intrinsic"
 width={411} height={253} quality={80} />
 
-The recipient receives an email to confirm the transfer. They have 24 hours to accept.
+The transferee receives an email requesting to transfer the project.
 
-#### Transferring Between Workspaces
+#### Hobby User to Team || Team to Team
 
-You can transfer a project to another workspace that you're a member of. Inside your project, visit the `Settings` page and click the `Transfer Project` button to view the project transfer modal.
+You can transfer a Project in your Hobby workspace to a Team (or between Teams) in which you are an Admin. Inside your project, visit the `Settings` page and click the `Transfer Project` button to view the project transfer modal.
 
 <Image src="https://res.cloudinary.com/railway/image/upload/v1692378671/project-transfer_iukfwb.png" alt="Project Transfer" layout="responsive" height={968} width={1240} />
 
-Note: You must be an Admin of the project to initiate a transfer. The destination workspace must have an active Hobby or Pro subscription. See the [Workspaces reference](/reference/workspaces#inviting-members) for more information on workspace roles.
+Note: If you do not see the Transfer Project section in your Project Settings, you may not be an Admin of the Team to which you wish to transfer the Project. See the [reference page for Teams](/reference/teams#inviting-members) for more information on team member permissions.
 
 ## Viewing Recent Activity
 

src/docs/guides/public-api.md

@@ -30,28 +30,21 @@ https://backboard.railway.com/graphql/v2
 
 ### Creating a Token
 
-To use the API, you will need an API token. There are three types of tokens you can create in the Railway dashboard. If you're building an application that authenticates users, you can also use OAuth.
+To use the API, you will need an API token. There are three types of tokens you can create.
 
-#### Choosing a Token Type
+#### Team Tokens and Account Tokens
 
-| Token Type | Scope | Best For |
-|------------|-------|----------|
-| Account token | All your resources and workspaces | Personal scripts, local development |
-| Workspace token | Single workspace | Team CI/CD, shared automation |
-| Project token | Single environment in a project | Deployments, service-specific automation |
-| OAuth | User-granted permissions | Third-party apps acting on behalf of users |
+You can create an API token from the [tokens page](https://railway.com/account/tokens) in your account settings.
 
-#### Account Tokens and Workspace Tokens
-
-You can create a workspace or account token from the [tokens page](https://railway.com/account/tokens) in your account settings.
-
-<Image src="https://res.cloudinary.com/railway/image/upload/v1770147536/docs/new_token_2026_v4yrmw.png"
+<Image src="https://res.cloudinary.com/railway/image/upload/v1667386744/docs/new-token-form_rhrbw8.png"
 alt="New token form"
 layout="responsive"
-width={1674} height={374} quality={80} />
+width={1618 } height={378} quality={80} />
 
-- **Account token**: If you select "No workspace", the token will be tied to your Railway account. This is the broadest scope. The token can perform any API action you're authorized to do across all your resources and workspaces. Do not share this token with anyone else.
-- **Workspace token**: Select a specific workspace in the dropdown to create a token scoped to that workspace. A workspace token has access to all the workspace's resources, and cannot be used to access your personal resources or other workspaces on Railway. You can share this token with your teammates.
+- **Team token** - Select a team in the `Team` dropdown to create a token tied to a team. A team token has access to all the team's resources, and cannot be used to access your personal resources on Railway. Feel free to share this token with your teammates.
+- **Account token** - If you do not select a team, the token will be tied to your Railway account and will have access to all your resources including the teams you are a part of. Do not share this token with anyone else.
+
+_Note that Teams are a Pro feature._
 
 #### Project Token
 
@@ -79,21 +72,21 @@ curl --request POST \
   --data '{"query":"query { me { name email } }"}'
 ```
 
-**Note:** This query **cannot** be used with a workspace or project token because the data returned is scoped to your personal account.
+**Note:** This query **cannot** be used with a team or project token because the data returned is scoped to your personal account.
 
-#### Using a Workspace Token
+#### Using a Team Token
 
-If you have a workspace token, you can use it to authenticate requests scoped to that workspace. The query below should return the workspace name and ID:
+If you have a team token, you can use it to authenticate requests to a specific team. The query below should return the team name and ID:
 
 ```bash
 curl --request POST \
   --url https://backboard.railway.com/graphql/v2 \
-  --header 'Authorization: Bearer <WORKSPACE_TOKEN_GOES_HERE>' \
+  --header 'Team-Access-Token: <TEAM_TOKEN_GOES_HERE>' \
   --header 'Content-Type: application/json' \
-  --data '{"query":"query { workspace(workspaceId: \"<WORKSPACE_ID_GOES_HERE>\") { name id } }"}'
+  --data '{"query":"query { team(id: \"<TEAM_ID_GOES_HERE>\") { name id } }"}'
 ```
 
-**Note:** This query **can** also be used with an account token as long as you are a member of the workspace.
+**Note:** This query **can** also be used with an account token as long as you are a member of the team.
 
 #### Using a Project Token
 
@@ -107,8 +100,6 @@ curl --request POST \
   --data '{"query":"query { projectToken { projectId environmentId } }"}'
 ```
 
-**Note:** Project tokens use the `Project-Access-Token` header, not the `Authorization: Bearer` header used by account, workspace, and OAuth tokens.
-
 ## Viewing the Schema
 
 Use popular tools like [Postman](https://www.postman.com/) or [Insomnia](https://insomnia.rest/) to connect to the API and query the schema. Simply set up your connection with the endpoint and Authorization token, and fetch the schema.
@@ -125,18 +116,12 @@ Alternatively, you can use our [GraphiQL playground](https://railway.com/graphiq
 
 <Image src="https://res.cloudinary.com/railway/image/upload/v1694611003/rw-graphiql_zs2l28.png" alt="GraphiQL Playground" layout="responsive" width={6568} height={3886} quality={80} />
 
-Make sure to set a header with your [authorization token](/reference/public-api#authentication). Click the "Headers" tab at the bottom of the GraphiQL page and enter this json, using your own token based on your use case:
+Make sure to set an Authorization header with an [auth token](/reference/public-api#authentication). Click the "Headers" tab at the bottom of the GraphiQL page and enter this json, using your own token:
 
-For an account or workspace token:
 ```json
 { "Authorization": "Bearer <API_TOKEN_GOES_HERE>" }
 ```
 
-For a project token:
-```json
-{ "Project-Access-Token": "<PROJECT_TOKEN_GOES_HERE>" }
-```
-
 ## Tips and Tricks
 
 ### Resource IDs

src/docs/guides/templates-best-practices.md

@@ -119,7 +119,7 @@ A clean, minimal repository helps users quickly understand the template's struct
 
 ## Workspace Naming
 
-When users deploy a template, the template author appears as the name of the <a href="/reference/workspaces" target="_blank">workspace</a> that created and published it.
+When users deploy a template, the template author appears as the name of the <a href="/reference/teams" target="_blank">workspace</a> that created and published it.
 
 Since the author is publicly visible and shown with the template to the users, it is important to make sure the workspace name is professional and **accurately represents your relationship to the software**.
 

src/docs/overview/the-basics.md

@@ -53,7 +53,7 @@ width={1365} height={765} quality={100} />
 
 Some of the most commonly used project settings are -
 
-- [Transfer Project](/reference/workspaces#transferring-projects) - Transfer your project between workspaces.
+- [Transfer Project](/reference/teams#transferring-projects) - Transfer your project between workspaces.
 
 - [Environments](/reference/environments) - Manage various settings regarding environments.
 

src/docs/reference/audit-logs.md

@@ -3,7 +3,7 @@ title: Audit Logs
 description: Learn more about how Railway keeps a record of actions in workspaces.
 ---
 
-Audit logs provide a record of actions performed within your Railway [workspace](/reference/workspaces). This includes changes to projects, services, deployments, variables, and workspace settings.
+Audit logs provide a record of actions performed within your Railway [workspace](/reference/teams). This includes changes to projects, services, deployments, variables, and workspace settings.
 
 Audit logs can be accessed by workspace admins through the <a href="https://railway.com/workspace/audit-logs" target="_blank">**Audit Logs**</a> link in the workspace settings.
 
@@ -28,7 +28,7 @@ To view audit logs:
 1. Navigate to your workspace dashboard
 2. Click on <a href="https://railway.com/workspace/audit-logs" target="_blank">**Audit Logs**</a> in the sidebar
 
-For more information about workspace roles and permissions, see the [Workspaces documentation](/reference/workspaces).
+For more information about workspace roles and permissions, see the [Workspaces documentation](/reference/teams).
 
 ## Log Contents