docs/guides/rbac.md (1)

83-83:Consider simplifying "all of the" to "all the".

The phrase can be made more concise as suggested by the static analysis tool.

-This displays a table of all of the CodeRabbit **Admin** and **Member** accounts associated with the selected+This displays a table of all the CodeRabbit **Admin** and **Member** accounts associated with the selected

🧰 Tools

🪛 LanguageTool

[style] ~83-~83: Consider removing “of” to be more concise
Context: ...bscription**. This displays a table of all of the CodeRabbitAdmin andMember acc...

(ALL_OF_THE)

docs/guides/rbac.md (3)

117-117:⚠️ Potential issue

Fix the typo in "administative".

There's a spelling error that should be corrected (same typo appears twice in the document).

-The following table lists the CodeRabbit administative functionality+The following table lists the CodeRabbit administrative functionality

📝 Committable suggestion

‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

The following table lists the CodeRabbit administrative functionality

🤖 Prompt for AI Agents

In docs/guides/rbac.md at line 117 and elsewhere in the document, correct thespelling of "administative" to "administrative" to fix the typo. Search theentire document for this misspelling and replace all instances with the correctspelling.

---

37-37:⚠️ Potential issue

Fix the typo in "platorm".

There's a spelling error that should be corrected.

-effect on that account's role or permissions in your organization's Git platorm.+effect on that account's role or permissions in your organization's Git platform.

📝 Committable suggestion

‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

effect on that account's role or permissions in your organization's Git platform.

🤖 Prompt for AI Agents

In docs/guides/rbac.md at line 37, correct the typo "platorm" to "platform" tofix the spelling error.

---

46-46:⚠️ Potential issue

Fix the typo in "administative".

There's a spelling error that should be corrected.

-CodeRabbit RBAC roles affect only access to administative features. Roles have no effect on using CodeRabbit developer features, such as automated code reviews.+CodeRabbit RBAC roles affect only access to administrative features. Roles have no effect on using CodeRabbit developer features, such as automated code reviews.

📝 Committable suggestion

‼️IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

CodeRabbit RBAC roles affect only access to administrative features. Roles have no effect on using CodeRabbit developer features, such as automated code reviews.

🤖 Prompt for AI Agents

In docs/guides/rbac.md at line 46, correct the typo "administative" to"administrative" to fix the spelling error.

docs/guides/rbac.md (8)

1-4:Add concise frontmatter metadata
Consider adding asidebar_label (for a shorter menu title) orsidebar_position to the frontmatter so this guide integrates smoothly into the sidebar navigation.

---

2-4:Rephrase description for conciseness
Rewrite the description as:
“Using CodeRabbit’s role-based access control (RBAC) feature”
to streamline and use the possessive form.

---

6-9:Clarify introductory sentence
Break or reword for readability, e.g.:
“Use CodeRabbit’s role-based access control (RBAC) to manage which administrative features your users can access.”

---

22-27:Refine the Billing Admin bullet for readability
The current phrasing is a bit awkward. Consider:
“Billing Admin: allows read/write access to subscription and billing management features, plus limited access to other administrative functions.”

---

79-82:Standardize ordered list numbering
You’re using1. on each step (which Docusaurus will auto-increment). Alternatively, you can explicitly number them1.,2.,3.—pick one style and apply it consistently.

---

83-83:Remove redundant “of”
Change “table of all of the CodeRabbit Admin and Member accounts” to “table of all the CodeRabbit Admin and Member accounts.”

🧰 Tools

🪛 LanguageTool

[style] ~83-~83: Consider removing “of” to be more concise
Context: ...bscription**. This displays a table of all of the CodeRabbitAdmin andMember acc...

(ALL_OF_THE)

---

115-132:Polish the permissions table formatting
Ensure pipes and separators line up consistently, and verify uniform capitalization/hyphenation (e.g., “Read-only” vs “No access”). You might also bold the column headers to improve readability.

---

135-136:Add trailing newline
Include a blank line at the end of the file to satisfy POSIX newline conventions.

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

docs/guides/roles.md (3)

1-9:Clarify RBAC acronym and usage in frontmatter and introduction

The description and intro don’t explicitly define “RBAC” or use the acronym, even though this guide addresses role-based access control. Consider updating the frontmatter and intro copy to introduce “Role-Based Access Control (RBAC)” for consistency with the PR title and to help readers recognize the acronym.

--- a/docs/guides/roles.md+++ b/docs/guides/roles.md@@ title: Control administrative access-description: Using the role-based authorization features of CodeRabbit+description: Using the role-based access control (RBAC) features of CodeRabbit@@-You can control which CodeRabbit-administrative features are available to your organization's user accounts by-assigning and updating account roles.+Role-Based Access Control (RBAC) in CodeRabbit lets you control which administrative features+are available to your organization's user accounts by assigning and updating roles.

---

22-27:Fix minor grammar in the Billing Admin definition

Remove the stray article “a” before “subscription and billing management” for smoother reading.

-**Billing Admin**: allows read/write access to features specific-  to a subscription and billing management, and limited access to other administrative features.+**Billing Admin**: allows read/write access to features specific+  to subscription and billing management, and limited access to other administrative features.

---

83-83:Streamline wording: drop unnecessary “of”

Per the static analysis hint, shorten the phrase “table of all of the CodeRabbit Admin and Member accounts” to “table of all CodeRabbit Admin and Member accounts”.

-This displays a table of all of the CodeRabbit **Admin** and **Member** accounts associated with the selected organization.+This displays a table of all CodeRabbit **Admin** and **Member** accounts associated with the selected organization.

🧰 Tools

🪛 LanguageTool

[style] ~83-~83: Consider removing “of” to be more concise
Context: ...bscription**. This displays a table of all of the CodeRabbitAdmin andMember acc...

(ALL_OF_THE)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

docs/guides/roles.md (2)

6-9:Nit: simplify introductory phrasing.

Consider rewriting to an imperative style for conciseness and consistency. For example:

“Control which administrative features are available to user accounts in your organization by assigning and updating account roles.”

---

83-85:Style: remove redundant “of”.

Change:

This displays a table of all of the CodeRabbit**Admin** and**Member** accounts…

to:

This displays a table of all CodeRabbit**Admin** and**Member** accounts…

for greater conciseness.

🧰 Tools

🪛 LanguageTool

[style] ~83-~83: Consider removing “of” to be more concise
Context: ...bscription**. This displays a table of all of the CodeRabbitAdmin andMember acc...

(ALL_OF_THE)

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro