Will we still have the option to hide roles from public view? I kind of liked being able to have roles for my developers have an internal hierarchy (senior devs having more mpermissions than the juniors), and not have that exposed to the group.
no way, LESS MONETIZATION ON ROBLOX?? IN THIS ERA???

however still a LONG way to go buddy: such as removing the premium necessity on classic clothing, etc etc..
Thanks for the feedback. We are working on it - more updates to come, stay tuned.
- you cant ban people anymore you can only remove them
- youre given an option in studio to select the default member role and let them playtest or edit, or publish, but an error just pops up when you attempt to save
Can you give some more details for these two issues you’re seeing? I am unable to reproduce them; banning users and setting the base role to have different collaboration permissions in Studio both seem to work in my testing.
You can do so via the API for the time being
- first issue either its horrible design to the point where i cannot find the ban button to ban a user from the group, or its just completely missing
- second issue regarding studio now doesnt even exist because in studio where you “Manage Collaborators”, theres 2 sections, 1 for group roles and 1 for the newer collaborators roles. the new default member USED to appear under the group roles section, and when i attempted to give the role any permission such as playtest it would error out (i do not have the error saved), but now that the option is completely gone this technically isnt a bug anymore however,
- you cant give the default member role in the NEWER collaborator roles section in the “Manage Collaborators” ANY permission because when you try to, and click save, it just defaults back to “No Access”
please answer these
- why are you unable to delete roles with members inside them? if youre going to mess up roles in the group, why not let us at least delete the role? are we expected to go through hundreds if not thousands of members and remove them from said role just to delete it?
- there is no way to auto assign roles or bulk assign roles, because of this im unable to give a lot of people a certain role in order to give them say certain permission such as playtesting when managing collaborators
Why is this new system giving all new members a role? I have a role at rank 10, i want new members to just be, members. Nothing else. Just members, but now its ranking them to the next highest automatically when accepted to the group. Why does it do this! You literally said there is a base members role for a reason! Why does it use it???
Why are there duplicate Member roles now?? With no ability to delete one of the two, that seems like a huge oversight
Great update. But… seems a bit silly to release it without any engine API or at least a cloud api, the only way to actually check if someone has multiple roles (from what i can tell) is through a proxy and on an account which has access to change member roles. Nonetheless, a really cool feature and hope the api’s to make this easier for us come swiftly
EDIT: Nevermind! I found out the https://apis.roblox.com/cloud/v2/groups/{groupId}/memberships returns all users roles in a seperate endpoint! Truly is a beautiful update, cant wait for the EngineAPI (if there will be one)
Hi Creators,
We’re sharing some updates on our APIs:
-
Reading Roles: GET
ListGroupMembershipsstill returns the member’s highest ranked role, plus a list of their assigned rolesets (excluding the base member role, which every member has by default). -
Open Cloud API endpoints
- The new Open Cloud endpoints for role automation are now live, so you can assign or unassign Community roles directly from your experience.
- Use them to:
- assign roles when players hit level milestones, complete quests, or win events
- unassign time‑limited roles when events or seasons end
-
Documentation:
HI - thanks for the feedback and we acknowledge the issues you’re experiencing.
-
We are working on removing friction for deleting roles and understand your concern. That update will be shared here when available, but it’s coming soon.
-
There are a couple things I want to answer here:
- Studio / playtester access: Studio does not currently support changing permissions for the base member role. For existing groups created before Multi-Roles launched on March 16, new members are auto-assigned to both the base member role and your legacy member role (the lowest ranked role above base member). If new members are landing in that legacy member role, you can grant Playtest (or other permissions) to that role in Studio, and everyone in it will get access with no changes to the base member role required.
- Bulk / auto-assignment in Communities: Right now there’s no bulk assignment in the Community UI, so you do need to assign Community roles one at a time. We’ve launched new Open Cloud endpoints that let you assign or unassign Community roles in-experience, so you can automate role assignment over time. We know bulk actions are important for large groups and are actively exploring better bulk-assignment tools in Communities (separate from how Studio collaborators work).
We are working on adding back that functionality and will update here when available.
I noticed you can use the same access level number for multiple roles, but if you accept a new user into the community, it will just give a random one instead of the bottom most in the hierarchy. Is this something that can be changes?
A second part to this is it would also be nice to be able to adjust where the role is, and if it goes above its current assigned number you could have either it assign the next one up above the role, or say “change the permission level first” or smth. When I was editing, lets say we have 5 roles, if I wanted roles 3, 4 and 5 to be assigned level 50 if I assign 5 first and 3 last its going to put 3 above 5.
Also this feels a little clunky, like how to change the roles, could you not adopt the same design concept as guilded? You go to a list of members, and it shows a card fly out with a guided/discord style roles management toggle, instead of a tiny list with a minus button.
Overall this is a great update, but the UX/UI needs to be improved a bit.
I am having an issue with this in regards to giving members with separate roles separate access to different testing places. I have 2 tester roles and 2 testing places for different games under my group and each role is supposed to be required to join either one, but regardless of permissions I set anyone with either role is able to join either game.
Example: those with the blue rank are able to join the place only those with the green rank are supposed to be able to join.
This happens for any privacy setting (Public, Community Members, Private) and leads me to believe this system just isn’t working correctly and does not stop anyone from being unable to access a place as there is no other role anyone has that is granting any other permissions.
Update: I’ve got this to work but it just takes awhile to update with the places set to Private. It would be a lot less confusing if this were not the case and places set to Community Members had this behavior too, but all this would really change is if the place is visible on the group or not
Could you file a separate bug report on this with more details on what happened and the places/groups involved (by ID)? We can definitely take a look at it that way.
Hi Creators,
We’re sharing two more improvements now available as part of our Multiple Roles update:
-
Role colors: You can now assign colors to your custom roles. From the Roles section, navigate to the Settings tab and choose from 16 color options.
- Note that the default Guest and Member roles cannot be color-customized.
-
Simpler role deletion: You can now delete roles without needing to unassign them from current members. To Delete a role, navigate to its Settings tab > Delete Role.
- Members will always be represented as their highest-ranked role. All members will still have the default Member role.
Amazing work!! You guys have been doing so good recently with communities
I’m hoping engine APIs are next so I don’t have to make web requests to fetch players multiple roles every time
This seems like a very botched release, I had 2 duplicate member roles, one of them I was unable to delete and the other I could delete, so I did. Doing so made it so members were assigned the “Creator Games” role automatically on join instead of “Member”, and additionally removed the member role from 38,000 of my communities members.
I cannot remove the “Member” role without it just defaulting to the aforementioned “Creator Games” role, and 38,000 of my members are also just straight up role less.
Not sure if this is planned, but can we get a feature to hide forums from non-community members much like the group wall had?




