Currently, the Verified Badge is only automatically granted to group owners, leaving co-owners and key developers of team-based experiences without recognition. Automated detection of contributors is impractical, and the pause on granting badges to group contributors has been in place for over eight months with no visible progress. This leaves developers who play significant roles in creating or maintaining an experience without a path to verification, especially in teams that use holder accounts.
With this feature request, I propose a manual Verified Badge request system accessible through the experience dashboard for group-owned games. A new Verified Badge Requests tab, visible only to the group holder, would allow them to submit requests for contributors who have studio access and meet eligibility requirements. The eligibility requirements are as follows:
Automatically checkable criteria:
- Contributor has had studio access for at least 1 to 3 months
- Account is at least 1 year old
- Account is ID verified
- Account has no recent or significant negative moderation history
- Experience meets minimum engagement requirements, which could be increased to get access to the manual Verified Badge request system
Manually reviewed criteria:
- Contributor has a significant and ongoing role in live operations, with a short explanation of responsibilities.
Requests would be submitted by the group owner, marked as pending, and reviewed by Roblox staff. Staff would approve or decline requests, possibly providing a reason if declined. This means it is entirely Roblox staff’s discretion whether a request is accepted or not, even if all the criteria are seemingly met. Approved requests would result in the contributor receiving a Verified Badge.
If, after acceptance, a contributor is found to not be fulfilling the role they claimed in a way that the group owner could have reasonably known about, the group owner can be held accountable for abusing the request system.
This system ensures that only actual owners or key developers receive verification, prevents abuse, and integrates naturally into existing workflows while allowing staff oversight.