Connect Roblox
RoControl starts with Roblox identity. The account connection identifies the operator and lets RoControl attach workspaces and permissions to the right user.
Module-specific Roblox permissions are requested later, only when a feature actually needs them.
Why permissions are requested later
Jobs run inside RoControl, and Event Automation uses an Open Cloud API key that
you set in the module, so neither needs a Roblox OAuth permission. Icon
Automation does write to Roblox icons and localized game names, so that module
requires a Roblox connection with legacy-universe:manage when it applies
changes. Live Config publishes to Roblox experience configs with either an Open
Cloud API key or a Roblox connection with universe:read and universe:write,
chosen in the module.
Flow
- Open RoControl.
- Click Connect Roblox.
- Complete the Roblox authorization flow.
- Return to the dashboard.
- Enable module permissions only when prompted by a module.
Permission example
When Icon Automation needs Roblox access, RoControl shows a permission prompt with the missing scope and the resource that needs authorization.
| Field | Meaning |
|---|---|
| Scope | Roblox permission required by the module |
| Resource | The universe or place the permission applies to |
| Reason | Why RoControl is asking for it |
Troubleshooting
If the browser returns to the dashboard but the account still looks disconnected, check that the API domain is reachable and that cookies are allowed for the RoControl domains.