Skip to content

Conversation

@boazpoolman
Copy link

What does it do?

Created documentation for RBAC from plugins.

Why is it needed?

To give a good overview of how you can use the RBAC feature from within your plugin.

@vercel
Copy link

vercel bot commented Oct 29, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
documentation Ready Ready Preview Comment Oct 30, 2025 2:37pm

@pwizla pwizla added the flag: merge pending release Pending Strapi Release label Oct 30, 2025
@pwizla pwizla changed the title docs: add documentation about using rbac from plugins Add a guide about using RBAC from plugins Oct 30, 2025
Copy link
Collaborator

@pwizla pwizla left a comment

Choose a reason for hiding this comment

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

Looks great, @boazpoolman, thank you!
I simply added a few changes to suggest to improve formatting and headings consistency. I applied them directly.

Also, since you're not part of the Strapi org on GitHub apparently, I can't edit your PR directly it seems.

But, to cross-link your guide from the main RBAC docs, could you please add the following after line 174 of the /cms/features/rbac.md file?

:::tip
To create admin permissions for your custom plugin, please refer to our [dedicated guide](/cms/plugins-development/guides/admin-permissions-for-plugins).
:::

Screenshot for context:

Image

@pwizla pwizla self-assigned this Oct 30, 2025
@pwizla pwizla added pr: new content PRs for new product features or new documentation sections source: CMS labels Oct 30, 2025
@pwizla pwizla added this to the 6.11.0 milestone Oct 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

flag: merge pending release Pending Strapi Release pr: new content PRs for new product features or new documentation sections source: CMS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants