# What to check when a Rust server moderator leaves

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Players and community](https://rustsc.com/learn/community/index.html.md)

Before someone leaves the moderation team, list the places they used to do the job. Their Rust staff assignment, community chat roles and hosting access each need their own check.

## Keep the team’s work reachable

Ask for open cases and the next step on each. Assign a new contact for each case, and check that the new contact can reach the notes and evidence. If access must end immediately, use the records already available to the owner and assign a new contact as soon as possible.

1. On every game server they helped run, remove their Rust staff role and any staff permissions granted by a plugin, whether given directly or through a framework group.
2. Remove their staff roles and any individual access to restricted community channels.
3. Remove their individual access to the hosting panel, moderation tools and any team records.
4. Replace shared credentials they could still use and update the tools that rely on them.

## Walk through a friendly departure

Say Kai is stepping down from staff on Harbour Trio but will keep playing. Rowan confirms which staff duties end on Sunday. A private case still needs an evidence reply and a named helper must take over the Sunday report check.

| Place to check | Harbour Trio's closeout |
| --- | --- |
| Open case and rota | Rowan assigns Sam the unfinished case and next shift. Sam confirms access to the notes and the next player reply owed. |
| Rust and framework roles | Rowan checks the game staff list and both direct and group-based staff access on every affected world. Kai keeps ordinary player access. |
| Discord and private records | Rowan removes staff roles and any separate channel or shared-document grants. Kai stays in the ordinary community channels. |
| RustSC and hosting tools | Rowan checks memberships and roles in each place Kai used. Where a shared login is being retired, a remaining staff member checks the tools that depend on it after replacement. |

## Verify the remaining access

Use the account lists to check the former moderator’s Rust role and any plugin permissions that still apply. In Discord, check direct channel access as well as roles. Confirm a remaining moderator can handle a test report. If the former moderator is staying as a player, compare their remaining access with what an ordinary player receives.

## Have the new moderator take the next action

Ask Sam to open a practice report and state the next step on the unfinished case. From the owner side, reread the former staff assignments and check for permissions still inherited through a different role. If the team can arrange a cooperative, ordinary-player check, ask Kai only to confirm access they should retain. End the handoff when Sam can do the agreed work and Kai's remaining grants match the ordinary role.

## Sources

- [Facepunch documentation on Rust game staff access](https://wiki.facepunch.com/rust/Creating-a-server)
- [Oxide documentation on direct and inherited plugin permissions](https://docs.oxidemod.com/guides/owners/permissions)
- [Discord documentation on roles and channel permissions](https://support.discord.com/hc/en-us/articles/214836687-Discord-Roles-and-Permissions)

## Related resources

- [How to check a Rust moderator’s access after a role change](https://rustsc.com/learn/community/verify-a-rust-moderator-access-change/index.html.md)
- [Understand workspace roles](https://rustsc.com/support/guides/workspace-roles/index.html.md)
- [How to hand over an open Rust moderation case](https://rustsc.com/learn/community/hand-over-an-open-rust-moderation-case/index.html.md)

---

HTML version: https://rustsc.com/learn/community/remove-rust-server-staff-access-when-someone-leaves/
