Will there ever be a way to migrate legacy roles to new ones? And regardless of that, what will happen to the money we put into them?
Can we have permissions to access moderation tools for certain roles?
The group profile permissions shouldnât include the ability to change the name of the group. Itâs an irreversible action that doesnât (or shouldnât?) need to be done regularly, and thus should be left to group owners.
Additionally, there should be cautionary features added so people donât accidentally change the name of the group when they donât mean to. The original feature under the old group configuration page required that you owned the group and had several steps you had to take to initiate the change (pressing a specific button, clicking the box to accept, entering in the new name in a UI element, Iâm also pretty sure you had to unlock your pin but if not thatâd also be a good feature etc). With the way itâs currently set up, you could accidentally change the groupâs name and not even know it until it was too late. Press the upload button, accidentally press tab and button mash for whatever reason, and if youâre not paying attention your group is getting more than just a new icon
Will we be getting an in-engine API to check for these roles? Being able to give people moderation permissions ingame without assigning them to a publicly visible role would be incredibly useful
This is great! I was wondering if it might be possible to create a separate permission specifically for monitoring bans within the âConfigure This Experienceâ Moderations > Bans page. Our team is currently unsure about the best way to safely grant permissions to an individual who manages bans outside the platform, but needs access to handle them within the platform as well.
it doesnt seem like the asset perms are working correctly, my developers said they cannot upload assets through studio even though i have given them all 3 asset permissionsâŚ
group owned animations refuse to load as well
Following up here after playing around with roles a bit more and looking at them: there are two things Iâd like to check in on.
Add or remove âRoleâ role members: This is a particularly dangerous permission to grant because it allows anyone in the role to assign it to others. Currently collaboration roles donât support hierarchy so ultimately it will still fall on the group owner to manage roles for those ranked below. Being allowed to assign someone else the same permissions as yourself is considerably dangerous and nonstandard in role management systems. I think it could use more restriction.
And as a question: is there a way to set up my configuration so that, for example, I can prevent a higher-ranked member without edit access from kicking or banning a lower-ranked member with edit access? I would like to avoid placing developers at ranks higher than leadership for community purposes though I also donât want to give my leadership team the ability to revoke a developerâs membership in the group. In essence, giving my developers âprotected userâ status.
Pretty good features! Glad that we can have them and hopefully I can get used to them!