RoControl Documentation
RoControl is a control room for Roblox teams. It gives a workspace one place to manage Roblox games, Live Config, scheduled Jobs, icon automation, team permissions, account setup, and runtime integrations.
This documentation is written for operators first. Each guide explains what the feature does, when to use it, and the exact flow to follow in the dashboard.
Start fast
Connect Roblox, create a workspace, add a game, then enable the modules that game needs.
Run live operations
Publish config, schedule updates, trigger webhooks, and automate event icons.
Control access
Invite teammates and grant module actions through workspace permission groups.
What is documented
| Area | Use it for |
|---|---|
| Getting Started | First sign-in, workspace setup, adding games, and enabling modules |
| Core Concepts | Workspaces, games, environments, modules, scopes, visibility, and runtime keys |
| Dashboard | Workspace overview, sidebar navigation, settings, account panels, and search |
| Modules | Live Config, Jobs, and Icon Automation |
| Team | Members, permission groups, collaboration presence, and common access patterns |
| Reference | Runtime API examples, environment variables, module routes, and troubleshooting |
| Deployment | Docker services, Caddy routing, and the docs subdomain |
Recommended path
- Read Getting Started if this is the first setup.
- Read Core Concepts to understand how RoControl models Roblox operations.
- Use Live Config and Jobs together for liveops.
- Use Team Permissions before inviting non-owner operators.
- Use Runtime API when wiring Roblox server code.
Current active modules
RoControl currently ships these active game modules:
| Module | Dashboard route | Roblox permission |
|---|---|---|
| Live Config | /games/[gameId]/modules/configurations | No Roblox scope required |
| Jobs | /games/[gameId]/modules/jobs | No Roblox scope required for current job types |
| Icon Automation | /games/[gameId]/modules/iconAutomation | Requires legacy-universe:manage to apply icons or names |
Example: a typical event workflow
- Add the Roblox universe to the workspace.
- Enable Live Config for the game.
- Create a
Defaultprofile for Production. - Add event variables like
event.enabled,event.name, andevent.endsAt. - Publish the profile.
- Create a scheduled Job that turns the event off at the end time.
- Enable Icon Automation and set the event start time.
- Let RoControl apply the countdown icon stages.
{
"event": {
"enabled": true,
"name": "Double XP",
"endsAt": "2026-05-05T21:00:00.000Z"
},
"economy": {
"xpMultiplier": 2
}
}Production URLs
| Surface | URL |
|---|---|
| Dashboard | https://rocontrol.duckdns.org |
| API | https://api-rocontrol.duckdns.org |
| Documentation | https://docs.rocontrol.duckdns.org |