Skip to main content

Onboard your first Rust moderator without sharing your login

Start your first moderator with their own account and a clear job. Give them a short role sheet, show them where reports go and practise one together. Keep your owner login with you so adding a volunteer does not mean handing over the whole server.

Copy this role sheet into your staff space

These are example duties for a small community. Replace each name and server, then agree which player actions your moderator can take. The labels describe jobs, not permission settings you can copy into every tool.

Copy this role sheet into your staff space
Job and personCan handlePass to
Owner: Rowan. Harbour Trio.Server changes, staff access and reviews of staff decisions.An agreed backup contact while unavailable.
Moderator: Kai. Harbour Trio.Private player reports, missing evidence and actions named in the staff rules.Rowan for appeals, unclear rules or reports involving Kai’s own team.
Event helper: Erin. Saturday build night.Welcome arrivals, explain the event and post agreed updates.Kai for conduct complaints; Rowan for changes to the game.

Give each person access for their job

Use each tool’s individual membership or staff access where available. Give Kai the private report space and the moderation tools you have agreed to use. Erin may need only the event channels. Neither job needs your sign-in, recovery codes or hosting password.

Discord roles, Rust game staff and a management tool’s roles are separate. A Discord role called Moderator does not by itself make someone game staff. Discord’s Administrator permission grants all permissions and bypasses channel restrictions, so leave it off for a helper who only needs a few channels.

In RustSC, use a separate workspace membership and check the role’s actual permissions. The Moderator role can manage players and bans. A note saying ‘ask me before banning’ does not remove that ability. Use the linked role and access guides to choose what fits your arrangement.

Rehearse a report before the first shift

Use a private practice report for this exercise. Ask the event helper to open the event information from their own account and check that the private report stays out of view.

  1. Put the player rules, private report link and owner contact beside the role sheet. Ask Kai to open them using their own account.
  2. Send a labelled practice report: ‘Four people raided us. Here is a short clip.’ Leave out the server and time.
  3. Have Kai reply: ‘Which server was this on, and what time with time zone? Please send the full clip in this report.’ No real player needs a punishment for the exercise.
  4. Add that one raider is Kai’s teammate. Have Kai pass the report to Rowan with the evidence and the next decision.

Leave a clear end to the shift

Once Kai can reply to the practice report and hand it over from their own account, agree when they will be available and who receives unfinished reports. After the first shift, read one reply together and ask what was difficult to find or decide. Update the same role sheet so the next volunteer starts with the answer.

Agree what the volunteer owns by the end of week one

Rowan and Kai fill in a first-week sheet together. If the role technically lets Kai do more than the sheet says, check whether a narrower supported role fits. The duty agreement tells everyone who decides. The permission check tells you what the account can do.

Agree what the volunteer owns by the end of week one
DutyCheck from Kai's accountOwner at the end of week one
Acknowledge reports on Harbour Trio.Kai opens a private test report and replies using a practice account. Erin cannot see it.Kai during the named shift. Rowan owns the alternate shift.
Pass a proposed ban for review.Kai sends Rowan the rule and the minimum facts in private. Rowan confirms receipt.Rowan decides bans under this first-week agreement.
Ask for a server restart after maintenance.Kai can reach Rowan by the agreed contact. Verify the role's actual restart permissions separately.Rowan makes any restart decision.

Set a review date on the sheet

Record the day you will revisit the roles and one change you expect to consider. On Sunday, Rowan and Kai review a practice reply and discover that Kai knows how to post it but did not know which person covers Rowan's absence. Write the backup's name next to the escalation path. Close the first week by asking Kai to describe their next shift and who owns each decision they cannot make alone.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details