circleci · rosieyohannan · Mar 16, 2026 · Mar 12, 2026 · Mar 12, 2026 · Mar 12, 2026
@@ -72,7 +72,7 @@ Replace problematic terms with inclusive alternatives:
 
 ### Text Styling
 - **Use bold** for GUI menu options and button text:
-  - Select **Organization Settings** from the sidebar
+  - Select **Org** from the sidebar
   - Click **Set Up Project**
 - **Use italics** for commonly understood technical concepts (not CircleCI features):
   - _Continuous Integration_

@@ -8,7 +8,7 @@ pass:[<!-- vale off -->]
 == Styling text
 
 * Use **bold** for GUI menu options and button text. For example:
-** Select **Organization Settings** from the sidebar
+** Select **Org** from the sidebar
 ** Select **VCS** in the **Project Settings** window
 ** Select **Projects** from the sidebar and click **Set Up Project** for the project you want to follow
 

@@ -1,4 +1,4 @@
-. In the link:https://app.circleci.com/home[CircleCI web app], select **Organization Home** in the sidebar.
+. In the link:https://app.circleci.com/home[CircleCI web app], select **Home** in the sidebar.
 . Select btn:[Create Project] at the top of the page, or anywhere in the btn:[Create a project] card if this is your first project.
 +
 .Create a project button

@@ -16,7 +16,7 @@ For GitHub users, your account has the "Owner" role in your GitHub organization.
 
 For Bitbucket Cloud users, your account has "Admin" permissions in your Bitbucket repository.
 
-For GitLab users, your account is listed as "Org Admin" in the CircleCI web app under menu:Organization Settings[People].
+For GitLab users, your account is listed as "Org Admin" in the CircleCI web app under menu:Org[People].
 
 [#what-happens-upon-cancelling-a-performance-plan-subscription]
 === What happens upon cancelling a Performance Plan subscription?

@@ -6,7 +6,7 @@ If you would like to author your own registry orb, read more on the xref:orbs:au
 
 *URL orbs*:: URL orbs are stored in a publicly accessible location (for example, a git repository or a public S3 object) and are not published to the orbs registry.
 +
-URL orbs do not follow semantic versioning, and can be accessed directly using an `https` URL. An org-level allow list is used to manage the addresses of URL orbs that can be used in a project in that organization. Organization admins can manage the allow list at menu:Organization Settings[Orbs].
+URL orbs do not follow semantic versioning, and can be accessed directly using an `https` URL. An org-level allow list is used to manage the addresses of URL orbs that can be used in a project in that organization. Organization admins can manage the allow list at menu:Org[Orbs].
 +
 See the xref:orbs:use:managing-url-orbs-allow-lists.adoc[Managing URL Orb Allow Lists] guide for more information on scoping allowed URL orbs for your organization.
 +

@@ -9,7 +9,7 @@ In order to install self-hosted runners, you will need to create a namespace and
 
 NOTE: To create resource classes and tokens you need to be an organization administrator in the VCS provider.
 
-You can view your installed runners on the inventory page in the https://app.circleci.com/[web app] or your CircleCI server app, by clicking *Self-Hosted Runners* on the left navigation.
+You can view your installed runners on the inventory page in the link:https://app.circleci.com/[web app] or your CircleCI server app, by selecting *Runners* from the sidebar.
 
 . Create a namespace for your organization's self-hosted runners. *Each organization can only create a single namespace*. We suggest using a lowercase representation of your CircleCI organization's account name. If you already use orbs, this namespace should be the same namespace orbs use.
 +

@@ -1,9 +1,9 @@
 //== CircleCI web app installation: pre-steps
 In order to install self-hosted runners, you will need to create a namespace and resource class token. To create resource classes and tokens, you need to be an organization admin in the VCS provider. You can read about namespaces and resource classes on the <<runner-concepts#namespaces-and-resource-classes,Concepts>> page.
 
-You can view your installed runners on the inventory page, by clicking *Self-Hosted Runners* on the left navigation.
+You can view your installed runners on the inventory page, by selecting *Runners* from the sidebar.
 
-. On the https://app.circleci.com/[CircleCI web app], navigate to *Self-Hosted Runners* and select btn:[Create Resource Class].
+. On the https://app.circleci.com/[CircleCI web app], navigate to *Runners* and select btn:[Create Resource Class].
 +
 image::guides:ROOT:runner/runner-ui-step-one.png[Runner set up, step one - Get started]
 

@@ -7,18 +7,18 @@ Web app installation::
 +
 --
 
-Before you can install self-hosted runners through the web app, you will need to agree to the https://circleci.com/legal/runner-terms/[CircleCI Runner Terms]. To access the *Self-Hosted Runners* section of the https://app.circleci.com/[CircleCI web app] an organization admin must agree to the terms at menu:Organization Settings[Self-Hosted Runners].
+Before you can install self-hosted runners through the web app, you will need to agree to the https://circleci.com/legal/runner-terms/[CircleCI Runner Terms]. To access the *Runners* section of the https://app.circleci.com/[CircleCI web app] an organization admin must agree to the terms at menu:Org[Runners].
 
 .Runner terms and conditions
 image::guides:ROOT:runnerui_terms.png[Runner terms and conditions]
 
-Once the terms have been accepted, **Self-Hosted Runners** will appear permanently in the side navigation.
+Once the terms have been accepted, **Runners** will appear permanently in the side navigation.
 
 Your role within your org is determined differently depending on how you integrate with your code, as follows:
 
 * If you have a `github` or `bitbucket` type organization, CircleCI mirrors VCS permissions for organizations. If you are an admin on your organization's VCS, you are an admin on CircleCI. If you are unsure, https://support.circleci.com/hc/en-us/articles/360034990033-Am-I-an-Org-Admin[check the admin permissions] on your VCS.
 
-* If you have a `circleci` type organization, you can check roles by navigating to menu:Organization Settings[People]. Full details on roles and permissions are available in the xref:guides:permissions-authentication:roles-and-permissions-overview.adoc[Roles and Permissions Overview].
+* If you have a `circleci` type organization, you can check roles by navigating to menu:Org[People]. Full details on roles and permissions are available in the xref:guides:permissions-authentication:roles-and-permissions-overview.adoc[Roles and Permissions Overview].
 
 TIP: Find out about organization types in the xref:guides:permissions-authentication:users-organizations-and-integrations-guide.adoc[Users, Organizations and Integrations Guide].
 --

@@ -92,7 +92,7 @@ image::guides:ROOT:user_settings.png[User settings]
 
 == Organization homepage and navigation
 
-After selecting an organization you will find yourself on the Organization homepage, or Dashboard if you are using CircleCI Server. The organization homepage provides an overview of your org's projects, project health metrics, and compute and credit usage metrics for your org.
+After selecting an organization you will find yourself on the organization homepage (called **Home** in the sidebar), or Dashboard if you are using CircleCI Server. The organization homepage provides an overview of your org's projects, project health metrics, and compute and credit usage metrics for your org.
 
 .Organization Homepage
 image::guides:ROOT:org-homepage.png[Organization homepage]
@@ -109,9 +109,9 @@ From your organization home page you have access to org-level options. You can c
 
 **Insights**: Provides you with time-series data overviews of credit usage, success rates, pipeline duration, and more. For full details of the Insights feature, see the xref:insights:insights.adoc[Using Insights] page.
 
-**Self-Hosted Runners**: Set up self-hosted runners to use your own infrastructure for running jobs. Once set up the self-hosted runners dashboard displays a list of your resource classes and self-hosted runners. For full details covering installation, setup, and usage, see the xref:execution-runner:runner-overview.adoc[Self-Hosted Runners Overview] page.
+**Runners**: Set up self-hosted runners to use your own infrastructure for running jobs. Once set up the self-hosted runners dashboard displays a list of your resource classes and self-hosted runners. For full details covering installation, setup, and usage, see the xref:execution-runner:runner-overview.adoc[Self-Hosted Runners Overview] page.
 
-**Organization Settings**: Settings for your organization including org roles and groups, contexts, security, orbs and more. You can find your organization ID and organization slug on this page.
+**Org**: Settings for your organization including org roles and groups, contexts, security, orbs and more. You can find your organization ID and organization slug on this page.
 
 **Plan**: Displays your network and storage usage, as well as additional settings related to your plan.
 
@@ -285,7 +285,7 @@ Learn more and get started with self-hosted runners on the xref:execution-runner
 [#organization-settings]
 == Organization settings
 
-The following organization settings are available by selection "Organization Settings" in the sidebar:
+The following organization settings are available by selecting *Org* from the sidebar:
 
 [.table-scroll]
 --

@@ -73,7 +73,7 @@ In the following steps you will replace `namespace/resource_class` and `project_
 == 2. Update policy with your details
 
 . Replace `namespace/resource_class` with one of your runner resource classes:
-.. In the CircleCI web app, go to your self-hosted runner's inventory page by selecting **Self-Hosted Runners** in the sidebar. If you do not see this option, check that you have accepted the CircleCI Runner Terms and created a namespace and resource class, as outlined in the runner installation guides. Here you will see all your available self-hosted runner resource classes.
+.. In the CircleCI web app, go to your self-hosted runner's inventory page by selecting **Runners** in the sidebar. If you do not see this option, check that you have accepted the CircleCI Runner Terms and created a namespace and resource class, as outlined in the runner installation guides. Here you will see all your available self-hosted runner resource classes.
 .. Replace `namespace/resource_class` in the `runner.rego` file with the name of the resource class that you would like to restrict.
 
 . Replace `project_UUIDs` with a project ID:

@@ -64,7 +64,7 @@ machine:
 
 If you need immediate relief to restore workflows during an active brownout, you can temporarily disable brownouts. 
 
-Navigate to *Organization Settings > Advanced > Enable resource class brownouts* and toggle the setting off.
+Navigate to menu:Org[Advanced > Enable resource class brownouts] and toggle the setting off.
 
 [IMPORTANT]
 ====

@@ -15,12 +15,12 @@ This guide gets you started with creating a new project in CircleCI.
 
 The authorization method used to set up your CircleCI account determines the definition of "project" in CircleCI, as well as the permissions management processes available to you:
 
-On the **Organization Home** page, check which option you see:
+On the **Home** page, check which option you see:
 
 * If you see a btn:[Set up a project] button, follow steps to <<set-up-a-project>> below.
 * If you see a btn:[Create Project] button, follow steps to <<create-a-project>> below.
 
-NOTE: Using CircleCI Server? Use the <<set-up-a-project>> steps below. Rather than Organization Home you will see Dashboard in the web app sidebar.
+NOTE: Using CircleCI Server? Use the <<set-up-a-project>> steps below. Rather than Home you will see Dashboard in the web app sidebar.
 
 [#create-a-project]
 === Create a project
@@ -189,7 +189,7 @@ NOTE: If you authenticated CircleCI with either the xref:integration:github-inte
 
 Follow these steps to  set up a new project in CircleCI:
 
-. In the CircleCI web app, select **Organization Home** in the sidebar. The equivalent option in CircleCI Server is **Dashboard**.
+. In the CircleCI web app, select **Home** in the sidebar. The equivalent option in CircleCI Server is **Dashboard**.
 . Select btn:[Set up a project].
 +
 .Set up a project

@@ -61,7 +61,7 @@ If you choose not to connect your code at this time, you can still explore some
 * Or some of our own sample projects: a link:https://app.circleci.com/pipelines/github/CircleCI-Public/sample-javascript-cfd/[sample JavaScript app], and a link:https://app.circleci.com/pipelines/github/CircleCI-Public/sample-python-cfd/[sample Python app].
 ****
 
-. Invite your team by navigating to menu:Organization Settings[People]. For more information on inviting people to your org, see the xref:invite-your-team.adoc#invite-teammates[Join your teammates] page.
+. Invite your team by navigating to menu:Org[People]. For more information on inviting people to your org, see the xref:invite-your-team.adoc#invite-teammates[Join your teammates] page.
 
 [#sign-up-with-an-invite]
 == Sign up with an invite

@@ -163,7 +163,7 @@ Expand any step to view the build output. You can search, share or download the
 image:guides:ROOT:getting-started-guide-exp/invite.png[float=right]
 [%hardbreaks]
 *Invite teammates*
-Invite teammates to collaborate on your projects. Navigate to *Organization Settings > People* to generate invites and get further instructions. Collaborators can view and follow your projects. Teammates can make a free CircleCI account at any time to view your pipelines, even if they are not committing any code.
+Invite teammates to collaborate on your projects. Navigate to menu:Org[People] to generate invites and get further instructions. Collaborators can view and follow your projects. Teammates can make a free CircleCI account at any time to view your pipelines, even if they are not committing any code.
 
 == 3. Debug and iterate
 

@@ -63,11 +63,11 @@ include::ROOT:partial$tips/check-org-type.adoc[]
 +
 --
 . In the CircleCI web app, select your org from the org cards on your user homepage.
-. Navigate to menu:Organization Settings[People], then select btn:[Invite].
+. Navigate to menu:Org[People], then select btn:[Invite].
 . To send out email invites, enter your team members' email addresses. Multiple emails can be separated by a space. Then, assign their role in your CircleCI organization. If you need to assign different roles to different team members, add team members in the Invite form based on role.
 . Once they join your org, you can then also assign each team member a role on an individual project level. See the xref:permissions-authentication:manage-roles-and-permissions.adoc[Manage roles and permissions] page for more details.
 
-image::guides:ROOT:invite-teammates-standalone.png[Navigate to Organization Settings, People, use the Invite form]
+image::guides:ROOT:invite-teammates-standalone.png[Navigate to Org, People, use the Invite form]
 --
 `github` or `bitbucket` type organization::
 +
@@ -77,7 +77,7 @@ image::guides:ROOT:invite-teammates-standalone.png[Navigate to Organization Sett
 . Select btn:[Copy Invite Link] -- an invite message is now copied to your clipboard.
 . Past the invite message to your teammates via email or whatever method you prefer.
 
-image::guides:ROOT:invite-teammates-classic.png[Navigate to Organization Settings, People, use the Copy Invite Link button]
+image::guides:ROOT:invite-teammates-classic.png[Navigate to Org, People, use the Copy Invite Link button]
 --
 ====
 

@@ -153,9 +153,9 @@ In CircleCI, contexts allow you to secure and share environment variables across
 
 In CircleCI:
 
-. Select the **Organization Settings** page.
+. Select the **Org** page.
 +
-image::guides:ROOT:slack-orb-organization-settings.png[Organization Settings]
+image::guides:ROOT:slack-orb-organization-settings.png[Org]
 
 . Under Context, select the blue *Create Context* button and add a unique name, such as `slack-secrets` (that is the name specified in the `config.yml` file above).
 +

@@ -47,7 +47,7 @@ the status of the skipped builds will not be reported. The checks are still crea
 [#enable-github-checks]
 == Enable GitHub Checks
 
-. In the CircleCI app sidebar, select *Organization Settings*.
+. In the CircleCI app sidebar, select *Org*.
 . Select *VCS Connections*.
 . Select *Manage GitHub Checks*.
 +
@@ -68,9 +68,9 @@ NOTE: Your project will continue receiving job level status after GitHub Checks
 [#disable-github-checks-for-a-project]
 == Disable GitHub Checks for a project
 
-To disable the GitHub Checks integration, navigate to the *Organization Settings* page in the CircleCI app, then remove the repositories using GitHub Checks, as follows:
+To disable the GitHub Checks integration, navigate to the *Org* page in the CircleCI app, then remove the repositories using GitHub Checks, as follows:
 
-. Select *Organization Settings* in the CircleCI sidebar.
+. Select *Org* in the CircleCI sidebar.
 . Select *VCS Connections*.
 . Select *Manage GitHub Checks*. The Update CircleCI Checks repository access page appears.
 +
@@ -83,7 +83,7 @@ image::guides:ROOT:github-status-updates.png[CircleCI VCS Settings Page]
 [#uninstall-checks-for-the-organization]
 == Uninstall Checks for the organization
 
-. Select *Organization Settings* in the CircleCI sidebar.
+. Select *Org* in the CircleCI sidebar.
 . Select *VCS Connections*.
 . Select *Manage GitHub Checks*.
 +

@@ -47,7 +47,7 @@ image::guides:ROOT:jira_expand_app_details.png[Expand App Details]
 +
 [NOTE]
 ====
-Your CircleCI organization ID is only needed for the initial setup. You can find it by navigating to menu:Organization Settings[Overview] in the link:https://app.circleci.com/[CircleCI web app].
+Your CircleCI organization ID is only needed for the initial setup. You can find it by navigating to menu:Org[Overview] in the link:https://app.circleci.com/[CircleCI web app].
 
 This integration authenticates via xref:permissions-authentication:openid-connect-tokens.adoc[OpenID Connect] (OIDC). By default, the organization ID provided is used for audience validation, but this can be modified, or more can be added.
 ====

@@ -167,7 +167,7 @@ Organizations with `/github/` in their URL can leverage both GitHub integration
 
 Installing the CircleCI GitHub App is a one-time action that enables all new features across the entire organization. Only organization admins can take this action.
 
-. Navigate to menu:Organization Settings[VCS Connections].
+. Navigate to menu:Org[VCS Connections].
 . Select btn:[Install GitHub App].
 . Select repositories to grant access.
 . Create new GitHub App pipelines alongside existing OAuth pipelines. This can be achieved in the following ways:
@@ -217,7 +217,7 @@ Instead, if you want to stop building through the OAuth integration, duplicate t
 
 === Why can't I see GitHub App options?
 
-Ensure the GitHub App is installed via menu:Organization Settings[VCS Connections]. Then select btn:[Add pipeline] on the menu:Project Settings[Project setup] page to create a new GitHub App pipeline.
+Ensure the GitHub App is installed via menu:Org[VCS Connections]. Then select btn:[Add pipeline] on the menu:Project Settings[Project setup] page to create a new GitHub App pipeline.
 
 === How do I prevent duplicate builds?
-Original file line number
+Diff line change
@@ Expand Up @@
     +
     [NOTE]
     ====
-    Your CircleCI organization ID is only needed for the initial setup. You can find it by navigating to menu:Organization Settings[Overview] in the link:https://app.circleci.com/[CircleCI web app].
+    Your CircleCI organization ID is only needed for the initial setup. You can find it by navigating to menu:Org[Overview] in the link:https://app.circleci.com/[CircleCI web app].
     This integration authenticates via xref:permissions-authentication:openid-connect-tokens.adoc[OpenID Connect] (OIDC). By default, the organization ID provided is used for audience validation, but this can be modified, or more can be added.
     ====
@@ Expand Down @@