Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify admin requirement for CPM #9125

Closed

Conversation

JoeMitchellJones
Copy link
Contributor

Clarifies that users must be org admins to make changes to manage config policies

Description

Adds a line clarifying that users must be org admins to manage config policies

Reasons

Previously, the only way users would know this is by trying and failing, or reading one of our blog posts.
This will reduce confusion about who can manage policies

Content Checklist

Please follow our style when contributing to CircleCI docs. Our style guide is here: https://circleci.com/docs/style/style-guide-overview.

Please 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) 😸:

  • 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.
  • Keep the title between 20 and 70 characters.
  • Consider whether the content would benefit from more subsections (h2-h6 headings) to make it easier to consume.
  • Check all headings h1-h6 are in sentence case (only first letter is capitalized).
  • Is there a "Next steps" section at the end of the page giving the reader a clear path to what to read next?
  • Include relevant backlinks to other CircleCI docs/pages.

Clarifies that users must be org admins to make changes to manage
config policies
@JoeMitchellJones JoeMitchellJones requested review from a team as code owners December 9, 2024 11:48
@rosieyohannan
Copy link
Contributor

Thank you, @JoeMitchellJones! I think I'll combine the two notes together so we don't have two banners at the top of the page

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