[Update] April 9, 2026
[Update] March 31, 2026
Hi Creators,
We’re excited to announce a massive upgrade to how you manage your communities on Roblox: Multiple Roles per Member is now live! Until today, each member of a Community held a single role. You no longer have to choose whether someone is a “Moderator” or a “VIP”. A single member can now hold several roles at once, unlocking a new level of flexibility for your community.
This is a foundational update that helps mirror real-world responsibilities, recognize members for their unique contributions, and safely delegate community management to your most trusted members.
Oh, and one more thing: We’ve removed the 25 Robux fee for creating new roles!
How Permissions Stack Up
Moving forward, a community member will always have a base member role, plus any other roles you choose to assign them.
-
Combined Permissions: Role permissions add together. If a user has the “Developer” role (can edit experiences) and the “Community Manager” role (create announcements), they automatically have the permissions for both.
- Role Hierarchy: With multiple roles, permissions like “Manage lower-ranked member ranks” will always look at the user’s highest-ranked role to determine who they can assign, kick, or ban.
-
Backwards Compatibility: We’ll continue to expose the highest‑ranked role in most legacy interfaces so nothing breaks. You can view a user’s full list of roles right now in the Configure Community > Members tab.
The New “Base Member” Role
To ensure this system works seamlessly, every Community now has a “base member" role at rank 1. Here’s how this impacts your community:
-
Existing Communities (created before March 16th): No changes to your current roles. We’ll simply add a new base member role with no permissions to your community that you can fully customize at any time. When new users join, they will receive your current default role plus this new blank base role.
-
New Communities (created after March 16th): These will automatically generate a base member role mirroring today’s standard Member permissions. As the owner, you can fully customize this to fit your needs.
API Updates
If your experience relies on roles for in-game logic, here’s what you need to know about the current APIs:
-
Reading Roles: The current GET ListGroupMemberships endpoint continues to work exactly as it does today, returning the member’s highest ranked role.
-
Writing Roles - The legacy endpoint: PATCH Update Group Membership will overwrite a user’s profile. It removes all current roles and sets them only to the single role you specify in the request.
What’s Next
Multiple Roles is just the foundation. Over the coming months, we’re rolling out several improvements on top of this:
-
In‑Experience Role Automation: New Open Cloud endpoints to automatically unassign or grant roles for hitting level milestones, completing quests, or winning events. Learn more here.
-
Bulk Assignment: Select multiple members in the Roles tab and assign them to a new role all at once.
-
Role Reordering: Drag-and-drop reordering of role hierarchy instead of manually editing ranks.
-
Full API Support: We will update the GET ListGroupMemberships response to return an array of all roles associated with a member.
We can’t wait to see how you use these new tools to better organize and build more rewarding communities. For more information, please visit our Help Center and be sure to let us know what you think below!
FAQs
Why do I need a base member role?
- It guarantees every Community member has a default role with predictable permissions. This gives you a stable foundation for your hierarchy, APIs, and scripts as you add or change other roles.
Do I have to adopt Multiple Roles right away?
- No, your existing single-role setup will continue to work as-is. You can start assigning multiple roles per member whenever you’re ready, giving you time to plan and test your new community structure before rolling it out.
Does assigning multiple roles change my Creator Hub setup?
- No. Assigning multiple roles to a user in your Community does not change how Creator Hub permissions work. You will still manage your developer access (like creating experience events and viewing experience analytics) directly through Creator Hub.
How will the “Manage lower-ranked member ranks”, “Kick lower-ranked members”, and “Ban lower-ranked members” permissions work now?
- If the acting user has one of those permissions on any of their roles, they will be able to perform the associated action on any target user whose highest-ranked role is lower than the acting user’s highest-ranked role.
In existing Communities, why do new members sometimes look like they’re getting a second “Member” role?
-
In existing Communities, when someone joins they always get:
- the hidden base member role at rank 1, and
- the auto-assigned role, which is the lowest ranked role above the base member role (often your existing “Member” role).
The base member role is required, applied to everyone, and doesn’t show on the Members page or in APIs, so you’ll only see the auto-assigned role even though both are present. We’re actively exploring ways to give you more control over which role is auto-assigned so this behavior is clearer and easier to customize.
What happens to my “internal-only” Creator Hub roles once roles are unified?
- Today, Creator Hub and Community roles are separate, so you can still use Creator Hub roles purely for permissions (testers, per-experience devs, etc.). We’re planning to merge Creator Hub and Community roles and permissions into a single, streamlined system. At that point, Creator Hub roles will show up as normal group roles and be returned by Groups endpoints. We also know some creators want truly internal/hidden roles, so we’re exploring visibility options for the unified system.