Skip to content

App menu name updates#10069

Draft
rosieyohannan wants to merge 5 commits intomainfrom
cursor/DOC-26-app-menu-name-updates-35dc
Draft

App menu name updates#10069
rosieyohannan wants to merge 5 commits intomainfrom
cursor/DOC-26-app-menu-name-updates-35dc

Conversation

@rosieyohannan
Copy link
Contributor

[!NOTE]

You may find that there are errors for the vale/lint job that are unrelated to your change.
Vale checks the whole file when a change is made so if there are existing issues on the page they will be flagged.
You can ignore lint errors outside your changes and the CircleCI docs team will address them for you.
Vale logs are advisory to help all contributors create content that conforms to our style guide. The vale/lint job will not prevent changes from being published.

Description

Updated references to CircleCI app sidebar menu items to reflect recent UI changes.

Reasons

The CircleCI app sidebar menu items have been renamed. This PR updates the documentation to ensure consistency with the current application interface, resolving DOC-26.

Specifically, the following changes were made:

  • Organization HomeHome
  • Chunk TasksTasks
  • Self-Hosted RunnerRunners
  • Organization SettingsOrg

Content checks

Please follow our style when contributing to CircleCI docs. View our style guide or check out our CONTRIBUTING.md for more information.

Preview your changes:

  • View the Vale linter results, select the ci/circleci: lint job at the bottom of your PR. You will be redirected to the vale/lint job output in CircleCI.
  • Preview your changes, select the ci/circleci: build job at the bottom of your PR and you will be redirected to CircleCI. Select the Artifacts tab and select index.html to open a preview version of the docs site built for your latest commit.

Take a moment to check through the following items when submitting your PR (this is just a guide so will not be relevant for all PRs):

Content structure:

  • Break up walls of text by adding paragraph breaks.
  • Consider if the content could benefit from more structure, such as lists or tables, to make it easier to consume.
  • Consider whether the content would benefit from more subsections (h2-h6 headings) to make it easier to consume.
  • Include relevant backlinks to other CircleCI docs/pages.

Formatting:

  • Keep the title between 20 and 70 characters.
  • Check all headings h1-h6 are in sentence case (only first letter is capitalized).

Linear Issue: DOC-26

Open in Web Open in Cursor 

- Changed 'Organization Home' to 'Home'
- Changed 'Chunk Tasks' to 'Tasks'
- Changed 'Self-Hosted Runners' to 'Runners' (menu references)
- Changed 'Organization Settings' to 'Org'

Updated all instances across documentation files including:
- User guides and tutorials
- Configuration and setup instructions
- Security and permissions documentation
- Integration guides
- API and CLI documentation
- Orb documentation

Resolves DOC-26

Co-authored-by: Rosie Yohannan <rosieyohannan@users.noreply.github.com>
@cursor
Copy link

cursor bot commented Mar 12, 2026

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

@linear
Copy link

linear bot commented Mar 12, 2026

DOC-26 App menu updates

Copy link
Contributor Author

@rosieyohannan rosieyohannan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cursoragent changes required

=== Amazon Bedrock authentication error or 401

Your AWS bearer token is invalid or has expired. Regenerate the token in AWS IAM and update it in the `circleci-agents` context in **Organization Settings** > **Contexts**.
Your AWS bearer token is invalid or has expired. Regenerate the token in AWS IAM and update it in the `circleci-agents` context in **Org** > **Contexts**.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Your AWS bearer token is invalid or has expired. Regenerate the token in AWS IAM and update it in the `circleci-agents` context in **Org** > **Contexts**.
Your AWS bearer token is invalid or has expired. Regenerate the token in AWS IAM and update it in the `circleci-agents` context in menu:Org[Contexts].

If organization verification is not possible, you can bypass this requirement by adding an environment variable to your `circleci-agents` context as follows:

. In the CircleCI web app, go to **Organization Settings** > **Contexts**.
. In the CircleCI web app, go to **Org** > **Contexts**.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
. In the CircleCI web app, go to **Org** > **Contexts**.
. In the CircleCI web app, go to menu:Org[Contexts].

. Select **Delete** to delete the environment variable. You will be prompted to confirm the deletion.

NOTE: **CircleCI (Powered by Anthropic) users.** If you are using the CircleCI-managed provider, there is no API key stored in your context. To remove Chunk access, disable the **Allow Chunk tasks** toggle in **Organization Settings** > **Advanced**.
NOTE: **CircleCI (Powered by Anthropic) users.** If you are using the CircleCI-managed provider, there is no API key stored in your context. To remove Chunk access, disable the **Allow Chunk tasks** toggle in **Org** > **Advanced**.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
NOTE: **CircleCI (Powered by Anthropic) users.** If you are using the CircleCI-managed provider, there is no API key stored in your context. To remove Chunk access, disable the **Allow Chunk tasks** toggle in **Org** > **Advanced**.
NOTE: **CircleCI (Powered by Anthropic) users.** If you are using the CircleCI-managed provider, there is no API key stored in your context. To remove Chunk access, disable the **Allow Chunk tasks** toggle in menu:Org[Advanced].

* The CircleCI GitHub App installed in your organization. Check **Organization Settings** > **VCS Connections**. Chunk needs the GitHub App to recommend fixes and open pull requests.
* The **Allow Chunk tasks** option enabled for your organization. Navigate to **Organization Settings** > **Advanced** and toggle on **Allow Chunk tasks**.
* The CircleCI GitHub App installed in your organization. Check **Org** > **VCS Connections**. Chunk needs the GitHub App to recommend fixes and open pull requests.
* The **Allow Chunk tasks** option enabled for your organization. Navigate to **Org** > **Advanced** and toggle on **Allow Chunk tasks**.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* The **Allow Chunk tasks** option enabled for your organization. Navigate to **Org** > **Advanced** and toggle on **Allow Chunk tasks**.
* The **Allow Chunk tasks** option enabled for your organization. Navigate to menu:Org[Advanced] and toggle on **Allow Chunk tasks**.

OpenAI organization verification required. Please verify your organization at https://platform.openai.com/settings/organization/generaland see our community forum for more debugging help.

To fix this issues, head to link:https://platform.openai.com/settings/organization/general[OpenAI Platform, window=_blank], navigate to menu:General[Organization Settings] and select btn:[Verify Organization]. Then follow the steps to get your organization verified.
To fix this issues, head to link:https://platform.openai.com/settings/organization/general[OpenAI Platform, window=_blank], navigate to menu:General[Org Settings] and select btn:[Verify Organization]. Then follow the steps to get your organization verified.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To fix this issues, head to link:https://platform.openai.com/settings/organization/general[OpenAI Platform, window=_blank], navigate to menu:General[Org Settings] and select btn:[Verify Organization]. Then follow the steps to get your organization verified.
To fix this issues, head to link:https://platform.openai.com/settings/organization/general[OpenAI Platform, window=_blank], navigate to menu:General[Organization Settings] and select btn:[Verify Organization]. Then follow the steps to get your organization verified.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This part is talking about openai not circleci

[%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 *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.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Invite teammates to collaborate on your projects. Navigate to *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.
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.

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 *Org > Advanced > Enable resource class brownouts* and toggle the setting off.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Navigate to *Org > Advanced > Enable resource class brownouts* and toggle the setting off.
Navigate to menu:Org[Advanced > Enable resource class brownouts] and toggle the setting off.

== Organization settings

The following organization settings are available by selection "Organization Settings" in the sidebar:
The following organization settings are available by selecting "Org" in the sidebar:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The following organization settings are available by selecting "Org" in the sidebar:
The following organization settings are available by selecting *Org* from the sidebar:

For GitLab integrations, organizations and users are managed independently from your VCS. Organizations and users are considered CircleCI organizations and users, with their own roles and permissions that do not rely on those defined in your VCS.

To manage settings at the organization level, select btn:[Organization Settings] in the CircleCI web app sidebar.
To manage settings at the organization level, select btn:[Org] in the CircleCI web app sidebar.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To manage settings at the organization level, select btn:[Org] in the CircleCI web app sidebar.
To manage settings at the organization level, select *Org* in the CircleCI web app sidebar.

For Bitbucket Data Center integrations, organizations and users are managed independently from your VCS. Organizations and users are considered CircleCI organizations and users, with their own roles and permissions that do not rely on those defined in your VCS.

To manage settings at the organization level, select btn:[Organization Settings] in the CircleCI web app sidebar.
To manage settings at the organization level, select btn:[Org] in the CircleCI web app sidebar.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To manage settings at the organization level, select btn:[Org] in the CircleCI web app sidebar.
To manage settings at the organization level, select *Org* in the CircleCI web app sidebar.

@cursor
Copy link

cursor bot commented Mar 12, 2026

I've addressed all the feedback from the PR review. Here's what was fixed:

Changes Made:

  1. Reverted incorrect OpenAI change - The "Organization Settings" in the OpenAI context was incorrectly changed to "Org Settings". This has been reverted back to "Organization Settings" since it refers to OpenAI's interface, not CircleCI's.

  2. Improved formatting consistency:

    • Updated to use menu:Org[Overview] syntax instead of **Org > Overview** format
    • Changed "click" to "select" for consistency
    • Changed "on the left navigation" to "from the sidebar"
    • Changed https://app.circleci.com/ to link:https://app.circleci.com/ format
    • Replaced btn:[Org] with simple bold *Org* where more appropriate
  3. Updated phrasing to be more consistent with CircleCI docs style guide (e.g., "In the CircleCI web app, select Org from the sidebar")

All changes have been committed and pushed to the branch. The PR should now conform to the CircleCI documentation style guidelines.

Open in Web Open in Cursor 

cursoragent and others added 4 commits March 12, 2026 15:05
- Reverted OpenAI 'Organization Settings' change (was incorrectly changed to 'Org Settings')
- Updated to use menu: syntax for consistency (menu:Org[...])
- Changed 'click' to 'select' and 'go to' to more consistent phrasing
- Changed 'on the left navigation' to 'from the sidebar'
- Changed https:// to link: syntax where appropriate
- Removed btn:[] formatting where simple bold (*) is more appropriate

Co-authored-by: Rosie Yohannan <rosieyohannan@users.noreply.github.com>
The Integrations page in the CircleCI app has been moved to VCS Connections.
Updated all references throughout the documentation to reflect this change.

Changes:
- menu:Org[Integrations] → menu:Org[VCS Connections]
- 'Integrations page under Org' → 'VCS Connections page under Org'
- 'Navigate to **Integrations** within **Org**' → 'Navigate to **VCS Connections** within **Org**'

Co-authored-by: Rosie Yohannan <rosieyohannan@users.noreply.github.com>
Archive files should not be modified as they contain historical documentation.

Co-authored-by: Rosie Yohannan <rosieyohannan@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants