Skip to content

User registration and types#10070

Draft
rosieyohannan wants to merge 1 commit intomainfrom
cursor/DOC-23-user-registration-and-types-0b78
Draft

User registration and types#10070
rosieyohannan wants to merge 1 commit intomainfrom
cursor/DOC-23-user-registration-and-types-0b78

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

  • Created a new documentation page: user-types-and-registration.adoc in the plans-pricing section.
  • This page defines Registered, Active, and Unregistered users, provides instructions on how to register, and offers guidance for organization administrators.
  • Updated nav.adoc to include the new page.
  • Added cross-references to the new page from prevent-unregistered-users-from-spending-credits.adoc, billing-faq-snip.adoc, plan-free.adoc, and plan-performance.adoc.

Reasons

This PR resolves Linear issue DOC-23 by:

  • Providing clear documentation on how to register within CircleCI.
  • Defining the terms "Registered User," "Active User," and "Unregistered User."
  • Addressing urgent customer concerns and the upcoming billing changes for unregistered users (effective December 1st) by explaining their implications and providing solutions.
  • Empowering users to become registered and active, and guiding admins on managing user types.

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-23

Open in Web Open in Cursor 

- Create new user-types-and-registration.adoc page explaining registered users, active users, and unregistered users
- Add detailed instructions on how to register for a CircleCI account
- Explain the billing implications of unregistered users
- Add guidance for organization admins on ensuring team members are registered
- Update navigation to include the new page in plans-pricing section
- Add cross-references from prevent-unregistered-users, billing FAQ, and plan pages
- Resolves DOC-23: Address customer concerns about unregistered user billing

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

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