Overview
What Ro-Link manages
Ro-Link is not just a bot invite. It is a control surface that connects your Discord staff workflow, your dashboard configuration, and your live Roblox servers into one operational path.
Live server visibility
See active servers, inspect player rosters, and target individual jobs instead of moderating blind.
Moderation control
Issue moderation and utility actions from the dashboard or API without joining the experience manually.
Operational logging
Track what was sent, by whom, and when, so your staff team has an audit trail for reviews and reports.
Staff workflow
Keep Discord staff, Roblox runtime, and dashboard configuration aligned around the same server record.
Rollout
Recommended rollout order
The cleanest setup sequence is to establish ownership and keys first, install the Ro-Link Studio plugin second, and only then test live commands. That prevents false negatives caused by missing runtime or permission gaps.
Connect the Discord side
Invite Ro-Link, sign into the dashboard, and confirm you are operating on the correct Discord server before editing any configuration.
Collect Roblox identifiers
Gather the Place ID, Universe ID, and the correct owner-scoped Open Cloud key for the experience you are linking.
Run the installer plugin
Install the RoLink installer plugin in Roblox Studio, paste in your dashboard security key, and let it configure the bridge for you.
Run a controlled live test
Test a low-risk command or lookup first, confirm logging is correct, then move into day-to-day moderation use.
Requirements
Before you begin
The fastest way to lose time during setup is to start without the correct ownership scope or without a live server available for testing. Make sure the basics below are settled before you continue.
- A Discord server where Ro-Link is installed and where you have permission to configure it.
- A Roblox experience that you own directly, or a group-owned experience where you can create owner-scoped credentials.
- Access to Roblox Studio so you can run the installer plugin and publish a fresh build.
- At least one runtime server you can start for live delivery testing after installation.
- A plan for which staff roles should have moderation access before the dashboard goes live.
- A release version you want staff and users to see on the landing page when update posts are published.
Navigation
Where work happens
Ro-Link operations are split across a few surfaces. Treat each surface as a dedicated job area rather than trying to do everything from one screen.
Dashboard
Configure servers, inspect live activity, publish updates, and manage settings.
Update Posts
Review published release notes and verify that public versioning matches the latest rollout.
Creator Dashboard
Use Roblox Creator Dashboard to collect identifiers and create the correct Open Cloud key.