Skip to content

docs: clarify custom roles require Enterprise plan#7078

Merged
jakehulberg merged 1 commit into
mainfrom
devin/1782767575-docs-rbac-custom-roles-enterprise
Jun 29, 2026
Merged

docs: clarify custom roles require Enterprise plan#7078
jakehulberg merged 1 commit into
mainfrom
devin/1782767575-docs-rbac-custom-roles-enterprise

Conversation

@devin-ai-integration

Copy link
Copy Markdown
Contributor

Context

The RBAC docs page describes custom roles without mentioning they require an Enterprise license. This causes confusion for free self-hosted users who see RBAC marked with a red X in Usage & Billing but read the docs as if custom roles are available to everyone.

Adds an <Info> callout to the "Creating custom roles" section clarifying that custom roles require the Enterprise plan, while built-in roles (Admin, Member, Viewer, No Access) are available on all plans including free self-hosted.

Steps to verify the change

  1. Visit https://infisical.com/docs/documentation/platform/access-controls/role-based-access-controls
  2. Confirm the Info callout appears above the "Creating custom roles" content

Type

  • Fix
  • Feature
  • Improvement
  • Breaking
  • Docs
  • Chore

Checklist

  • Title follows the conventional commit format: type(scope): short description (scope is optional, e.g., fix: prevent crash on sync or fix(api): handle null response).
  • Tested locally
  • Updated docs (if needed)
  • Updated CLAUDE.md files (if needed)
  • Read the contributing guide

Link to Devin session: https://app.devin.ai/sessions/3443e277cf1d4ea6be2c05ad63c127aa

Co-Authored-By: jake <jake@infisical.com>
@devin-ai-integration

Copy link
Copy Markdown
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment, CI, and merge conflict monitoring

@mintlify

mintlify Bot commented Jun 29, 2026

Copy link
Copy Markdown

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
infisical 🟢 Ready View Preview Jun 29, 2026, 9:18 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

@greptile-apps

greptile-apps Bot commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR adds a single <Info> callout to the RBAC documentation page to clarify that custom roles are an Enterprise-only feature, addressing confusion for free self-hosted users.

  • Inserts an <Info> block directly above the "Creating custom roles" section content, clearly stating that built-in roles (Admin, Member, Viewer, No Access) remain available on all plans including free self-hosted.

Confidence Score: 5/5

This is a docs-only change with no code impact; it is safe to merge.

The change is a single four-line addition to an MDX documentation file. The callout is placed accurately, the text is factually consistent with the rest of the RBAC docs, and no code paths are affected.

No files require special attention.

Important Files Changed

Filename Overview
docs/documentation/platform/access-controls/role-based-access-controls.mdx Adds an callout before the "Creating custom roles" section clarifying that custom roles require the Enterprise plan while built-in roles remain available on all plans.

Reviews (1): Last reviewed commit: "docs: clarify custom roles require Enter..." | Re-trigger Greptile

@scott-ray-wilson scott-ray-wilson left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@jakehulberg jakehulberg merged commit 358c5d5 into main Jun 29, 2026
9 checks passed
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