how is possible ?, did u asked to roblox support?
It would be great if you could rank certain players via a script in the game without a need of 3rd party scripts.
2 Likes
We still lack the ability to fully “ban” members from groups.
Currently, the only option is to “kick” them, which allows disruptive users to repeatedly rejoin, requiring manual intervention each time they break the rules.
We need a feature that enables us to fully ban users from the group, with banned members being logged in a separate “banned members” list. This would greatly improve group management and help maintain a safe and organized environment for all members.
3 Likes
Hello @arumyx, we are investigating the issue with your group Yummy studio!! - Roblox and will get back to you shortly.
Hello @arumyx I believe this group’s ownership has been fixed. Are you able to confirm if you’re able to access group owner settings now?
1 Like
Everything is now working perfectly
thank you.
Heyo Roblox Devs,
Thank you for the wonderful improvements to group roles within Creator Hub! The new roles and permissions system has certainly streamlined many aspects of group management, and it’s clear that a lot of thought went into making collaboration more accessible for creators.
I wanted to share a couple of observations and suggestions based on how my team interacts with the new roles:
- Feedback and Observations:
- It appears that the roles system may have lost some of its hierarchical flexibility. For instance, our QA Manager, who is responsible for overseeing QA members, can’t currently promote team members to a role with different permissions directly.
- This means we would have to give QA Members broader permissions than we’re comfortable with, as they would need the ability to rank up others to their role, which might pose a security risk.
- Impacts and Challenges:
- To work around this, we have our QA Manager temporarily promote members to his own rank during testing sessions and demote them afterward. While this approach works, it’s not ideal for our setup and adds an extra step to an otherwise simple process.
- Without a more flexible permission setup, we may need to create an in-game access management system that uses legacy roles to maintain structure, which adds complexity.
- Suggestion for Improvement:
- It would be incredibly helpful if management roles, like the QA Manager, could have a setting allowing promotion within a restricted set of ranks. This would provide more control without broadening permissions across the team, thus ensuring a secure workflow. That way my QA manager can promote people to a QA role to test the game, without giving QA tester role the ability to promote anyone to the role
Thank you again for your time, effort, and openness to feedback. I’m looking forward to more updates and am excited to see this feature evolve! ( Used AI to make the formatting for the message more clear )
1 Like
Hey - thanks for the feedback and thoughtful suggestions! I am happy to say we’re just about to roll out a new permission that I think should solve this for you - it will be a ‘manage limited roles’ permission, and be perfect for your QA manager.
Keep an eye out 
1 Like
Thanks a ton for the speedy response. Sounds amazing, keep up the amazing work 
1 Like
Please add a feature where we can transfer funds from one group to another. It would be a great feature and it is a must too.
2 Likes
Hello Roblox Devs!
As already said by so many others, thank you for the improvements made to not only group management in general but also the possibilities that now exist with the new roles in the Creator Hub!
Similar to KingFossi’s reply, I also wanted to share a couple of observations and suggestions based on how my team interacts with the new roles:
I was hoping to create a new “Live Access” role with permissions similar to our current Developer legacy role, specifically to allow certain team members to also access the live game studio of our game, rather than just the one under our development group. This would allow us to role them to the rank they actually have within our group, rather than needing to add it to our codebase. However, the current system doesn’t allow us to fully replicate the Developer role’s permissions under this new role.
Our Senior Developers, who are given live game access for testing and publishing updates, are unable to upload development assets (non-clothing items). This limitation affects the efficiency of our workflow, as they often need to make quick updates to live game assets, and relying on the group owner to do this every time is quite cumbersome.
It would be incredibly useful if we could manage these permissions directly within the new roles settings as well, with granular control over upload capabilities. This would allow us to tailor access more accurately, especially given that “upload items” now includes specific permissions for asset types like clothing but doesn’t extend as effectively to other types of development assets.
I hope that is somewhat understandable and not too long 
I was also wondering if there are currently any plans to add a way to check if a player is member of a specific role within a group via the API, similar to the existing GetRankInGroup function? This would allow us to easily verify role-based permissions in-game, improving our ability to control and customize access based on roles as well rather than just ranks.
Thank you again for all the work and for being open to feedback!
3 Likes
I concur with this. I am trying to do something very similar!
1 Like
There is an issue where people that have been invited to my group cannot access studio experience if team create is off. Even if they have all permissions.
1 Like
Only thing missing here is the Rank ID because this is very important for scripting in our experiences.
I feel like the Rank ID should go below the Role Name.
I had the same issue - and only happened after I took the advice for 2FA Authenticator App.
After I eventually logged in a 2nd time with the 2FA code… then decided to select it to remember my login for 30 days - then only does it allow me to log in without a hassle.
Def started after the 2FA request.
Seems it needs the new owner login permission - after portioning the shares.