Allow selected Discord roles to manage one server in GuildPilot without granting every staff member the Manage Server permission.
How to give trusted staff GuildPilot dashboard access
GuildPilot normally allows the server owner and members with Administrator or Manage Server to open a server's dashboard. You can also choose trusted Discord roles that receive GuildPilot dashboard access for that server.
Before you start
- GuildPilot must be installed in the server.
- You must already be able to open that server in the dashboard.
- Create or choose the staff roles in Discord before opening GuildPilot.
Warning: A configured GuildPilot admin role can change the server's GuildPilot settings. Select only roles whose members should have that level of control.
Give staff access
1. Open the server settings
From Your Discord servers, open the intended server and select Settings in the sidebar.
2. Find GuildPilot admin roles
In the Roles section, locate GuildPilot admin roles. Search uses the roles currently synced from Discord.
3. Select the trusted roles
Choose each role that should open GuildPilot without Manage Server. Managed integration roles are shown as managed and should not be used as ordinary staff roles.
4. Save the settings
Select Save changes. GuildPilot stores the selected role IDs for this server and checks live Discord membership when someone opens its settings.
Recommended configuration
Use a dedicated administrator or senior moderator role instead of a broad member role. Keep Discord's Manage Server permission limited separately; the GuildPilot role list controls this dashboard only.
Test the setup
- Ask a staff member who has the selected role but not Manage Server to sign in to GuildPilot.
- Have them open Your Discord servers and select this server.
- Confirm that the server settings open successfully.
- Remove the test role from that account afterward if it was assigned only for verification.
What a successful setup looks like
Members with the selected role can open this server's GuildPilot pages. Members without owner status, the required Discord permissions, or a configured admin role receive No access.
Common problems
The role does not appear in the selector
Cause: GuildPilot could not refresh the server's Discord roles or the role was created after the last sync.
Fix: In Settings, use Refresh Discord data, then search again. Confirm that the bot is still installed in the server.
A staff member still sees No access
Cause: Their live Discord role membership does not match a saved GuildPilot admin role.
Fix: Confirm that the member holds the role in the same server, then reopen the dashboard. If the role was replaced, save the new role under GuildPilot admin roles.