
Should a Rust moderator have access to one world or all of them?
Give a helper access where they work. A Friday moderator on your weekly world and an owner who covers emergencies on both worlds have different jobs. Verify the scope on both worlds before relying on the setup.
Write the smallest useful scope
Name the person, the world and a specific action. For example, Mina handles reports on Juniper Weekly. Lee is on call for Weekly and Monthly.
| Job | Give access to | Verify |
|---|---|---|
| Read incoming reports | The relevant Discord channel or management view | Mina can open a Weekly report and cannot open Monthly's private staff queue. |
| Use an in-game plugin action | The relevant game's supported permission | Mina can use the named helper action on Weekly and cannot use it on Monthly. |
| Carry out a server-wide emergency action | Both worlds for the named on-call responder | Lee can reach both worlds under Lee's own login. Test the read path first and rehearse any disruptive action on a spare world. |
Check each place that can grant the action
Review access in the management tool, hosting panel, Discord and game separately. Oxide permissions can come from a direct grant or a group. A Discord role controls Discord permissions unless you have deliberately set up a connection that changes game access. Note any shared group or automated role mapping before changing a single server's grants.
On a spare setup, have the helper try the same harmless read or staff command on both worlds. Use the helper's own accounts. If the other world unexpectedly allows the action, check its direct grants, groups and shared tooling. Keep existing world owners in place while you verify.
Tell the helper who covers the gap
Leave a line in the rota that names the worlds and who to contact for the other one. If the moderator later moves worlds, revisit the allowed action and its denial on the old world together. A read-only ordinary action gives you a fresh check without disrupting play.