County Control

Docs Step-by-step guides

Choose who can use each command

You know who can run which County Control commands out of the box, and you can let your own staff roles use any command from the dashboard.

5 minutesServer owner

At the end you will know why a staff member sees "You don't have access to this command here." and how to fix it. You can give any role access to any admin command, or limit a command to certain roles.

Before you start

  • You need to be the server owner, or have Manage Server or Administrator, to open the dashboard.
  • County Control has no Discord command for changing permissions. It is done on the dashboard's Permissions page.

Who can use what by default

Who What they can use
Server owner Every command, always. Nobody can lock the owner out.
Administrator Every command, until you set a rule for that command (see below).
Everyone /help, /dashboard, /apply, /priority, /duty, /staff, /ticket, /cad and "Open a ticket about this" (right-click a message, Apps). Some parts of /duty, /staff and /ticket check for staff themselves.
Session role /ssu, /sessions and /players. Set it with /session role.
Staff manager role /promote, /infract, and the manager parts of /staff and /duty. Set it with /staff settings manager_role:.
Ticket support role Claim, close and the staff tools inside tickets of its type.
Application reviewer role The Claim, Accept and Deny buttons on its form.
Priority approver role The Approve and Deny buttons on priority requests, for that role and above.

Everything else, including /ban, /kick, /warn, /timeout, /logs, /mod, /tickettype, /ticketpanel and /apps, starts as Administrator only. Having Manage Server alone is not enough to run these in Discord.

Steps

1. Open the Permissions page

Go to https://cc.pcdev.dev/dashboard/, sign in with Discord, pick your server, then pick Permissions.

You see: "Who can use each command", with a search box and one row per command. Each row shows its default, such as "Admins".

2. Find the command

Type part of its name in Search commands, for example ban.

3. Pick the roles

In that command's row, pick one or more roles, for example @Moderator and @Admin. Press Save.

You see: a message confirming the change, such as "Only @Moderator, @Admin (and the server owner) can use /ban". The row now says Restricted.

Repeat for each command your staff need. For moderators that is usually /warn, /timeout, /untimeout, /kick, /ban, /unban, /logs, /case and /mod.

Heads up
Once a command has roles picked, only those roles and the server owner can use it. Administrators who do not have one of those roles lose it. Add your admin role to the list too.

4. Put a command back to its default

Remove every role from the command's row and press Save.

You see: "/ban is back to its default audience".

Change it later

  • Let non-admins run sessions: /session role role:@Session Host
  • Let non-admins promote and infract: /staff settings manager_role:@Staff Manager
  • Change ticket support roles: /tickettype set label:General Support role:@Support
  • Change application reviewers: /apps settings form:moderator reviewer_role:@Recruitment Team
  • Change who approves priority: /setpriorityrole role:@HR Team

If something goes wrong

  • "You don't have access to this command here. A server admin can change who can use it on the dashboard" The person is not the owner, does not have Administrator, and none of their roles is picked for that command. Add their role in step 3.
  • An admin lost access to a command. That command has roles picked and the admin's roles are not among them. Add their role, or clear the command (step 4).
  • I can't find /duty, /staff or /ticket on the Permissions page. Those are open to everyone and check for staff inside each part, so they are not listed. Use the manager role, support roles and reviewer roles in the table above instead.
  • I can't see my server on the dashboard. You need Manage Server or Administrator in that server, and County Control has to be in it.
  • Someone with Manage Server can't run /ban. Commands need Administrator by default, not Manage Server. Give their role the command in step 3.

Something unclear or out of date? Tell us in the support server.