Community Ownership Is Now Managed at the Community Level
Key Takeaways
Community ownership is now managed at the Community level, not through the legacy rank-255 Owner role. The legacy role no longer represents ownership or carries owner permissions.
Find the owner through the Owner label across Community surfaces and settings.
Hi Creators,
Today, we’re updating how ownership works in Communities on Roblox. Community ownership will belong to the Community itself, not to the legacy rank 255 Owner role. Going forward, Owner will no longer be a roleset at all: it will only exist as a property of the Community.
This aligns the system with how ownership has always worked. The Owner roleset was never a standard role: it could only be held by one person, it had unique behavior, and creators didn’t manage it like other roles. Community owners will still automatically have all permissions, so a separate Owner roleset is no longer needed.
What’s Changing
Today, many Communities show the Owner role at rank 255 as if it were a standard configurable role. That creates confusion because ownership is unique and shouldn’t be assigned, removed, or managed like a regular role.
With this update:
• The legacy Owner role will not be renamed, but will no longer have any permissions.
• Rank 255 will no longer be a reserved rank value.
• The legacy Owner role will behave like a regular managed role, meaning it can be adapted for your own use, repurposed, or deleted if you no longer need it.
• The actual Community owner will still be shown as Owner through an ownership label next to their username.
• Communities created on or after June 16, 2026 will no longer get a default Owner role at rank 255.
Where You’ll See the Difference
The Legacy Owner Role
The legacy Owner role at rank 255 will stay in your Roles list, but it will no longer have any special owner permissions. It will behave like a regular role, and you can reassign it, remove it, repurpose it, or delete it.
U…