Core Concepts
RoControl is easier to operate when the main objects are clear.
Object model
| Concept | What it means |
|---|---|
| Workspace | Team container for members, games, permission groups, and settings |
| Game | A Roblox universe managed by the workspace |
| Environment | Runtime target such as Studio or Production |
| Module | A feature installed on a game, such as Live Config or Jobs |
| Profile | A named Live Config branch inside one environment |
| Draft | Editable config data that is not published yet |
| Publish | Immutable version served by runtime endpoints |
| Runtime key | Secret used by server visibility requests |
How data moves
- An operator edits a module in the dashboard.
- RoControl saves the draft or settings in the backend.
- When the operator publishes or runs an action, RoControl records the result.
- Roblox servers fetch the latest published runtime data through the API.
What is safe to change live
Use Live Config for values that your Roblox code can handle without a deploy.
Good examples:
- Feature flags
- Event names and dates
- Shop prices
- Spawn weights
- Reward multipliers
- Message copy
Avoid using Live Config as the only source of truth for permanent player data, inventory ownership, or anything that must be transactionally secure.