Before you begin
Invite Staff Rater to a server you own or manage. The bot needs permission to create and manage the channels used by the workflows you enable. Keep its role above any role it needs to assign, and avoid granting permissions the server does not use.
After signing in, the dashboard only lists servers you own where Staff Rater is already installed. Other Discord servers from your account are intentionally hidden.
Set up staff ratings
- Choose a channel where members should submit ratings.
- Register each staff member who should have a Staff Rater profile.
- Post the persistent rating panel in the chosen channel.
- Choose a separate results channel if you want approved rating activity to appear publicly.
/setratingchannel→/addadmin→/postratinguiMembers can rate a registered staff member from one to five and add context. A member keeps one current rating for each staff member instead of creating unlimited duplicate ratings.
How Staff Rater keeps scores useful
A rating is feedback, not an automatic moderation decision. Staff Rater reduces the effect of common abuse patterns while leaving final judgment with the people running the server.
- Repeated edits are paced. A short correction window handles mistakes; later changes have a cooldown.
- Extreme patterns can be held. When one account repeatedly gives nearly everyone the same extreme score, those ratings can be removed from public averages until a manager reviews them.
- Small samples are weighted. A profile with one review is not treated as equally certain as a profile with a meaningful history.
- Moderation is auditable. Managers can review held ratings instead of silently deleting uncomfortable feedback.
Use /ratingqueue to inspect held ratings and /moderaterating to approve or reject one.
Set up support tickets
Connect a ticket category, the role responsible for support, and a private log channel. Then post the open-ticket panel where members can find it.
/setticketconfig→/postticketbuttonTicket channels are private to the requester and the configured staff role. Staff can claim responsibility, close the ticket and record a reason. The persistent controls are restored when the bot restarts.
Keep the experience clear
Name the public channel for the action members understand—such as Get support—and keep staff logs in a separate channel. Test opening, claiming and closing one ticket before announcing the system.
Set up applications
Create an application, add the questions your team genuinely needs, and post the application panel. Staff can review pending responses and record an accept or reject decision.
/app_create→/app_addq→/postappuiAvoid collecting passwords or unnecessary sensitive information. Ask questions that help reviewers make the decision, and tell applicants how their answers will be used.
Troubleshooting
A dashboard server is missing
Confirm that you own the Discord server and that Staff Rater is still installed there. Sign out and back in if your Discord ownership recently changed.
A panel button stopped responding
First verify the bot is online and can view the channel. Persistent rating and ticket controls should return after a restart; repost the panel only if the original message was deleted or permissions changed.
An action says “owner only”
Older diagnostic wording referred to the Staff Rater developers, not a Discord server owner. Use the public server commands and dashboard for server management.
You still need help
Join the Staff Rater support server and include the command or page, what you expected and what happened. Never share your Discord password or bot token.
