How to assign Automatic Roles with GuildPilot

Automatic Roles gives each new human member the saved safe member roles. Standard servers can actively grant the first two ordered roles. Premium removes GuildPilot's quota; Discord's role, permission and hierarchy limits still apply.

Before you start

• GuildPilot needs Manage Roles, and its active bot role must be above every role you select.
• Only ordinary member roles are accepted. GuildPilot rejects managed roles, @everyone, and roles with administrator, moderation, audit-log, member-management, server, channel, message, thread or webhook management powers.
• Bot accounts are never targeted.

Warning: Update guild member roles now changes roles for every eligible current human member. Review the ordered list before confirming it.

Configure Automatic Roles

1. Open Automatic Roles

Choose Moderation, then Automatic Roles. The page reports whether GuildPilot can manage roles and shows saved roles even if Discord later deletes them or makes them unsafe.

2. Add and order safe roles

Search for a role, add it, then use the up and down controls to set grant order. The selector prevents duplicate roles. Removing a row from this configuration does not remove that role from existing members.

3. Review the active quota

On Standard, roles one and two are active. Additional roles saved while Premium was active remain visible but paused after Premium ends; they reactivate in the same order if Premium returns. GuildPilot does not remove roles that members already hold during a downgrade.

4. Save the setup

Select Save Automatic Roles. Automatic assignment is enabled whenever at least one role remains configured. New human members then receive only safe, manageable, missing active roles.

5. Update existing members when needed

Select Update guild member roles now, review the confirmation, then start the job. The operation is additive: it adds missing active roles and never removes any other role. Keep the page open or return later to review queued, running, retry, completed or failed progress.

Remove and disable the setup

Use Remove automatic roles from all members only when you want to stop future automatic assignment and remove the configured roles from current human members. GuildPilot snapshots every configured Automatic Role, including paused roles, clears the configuration, and processes removal in the background. Unrelated guild roles are never touched.

Test the setup

1. Join with a designated human test account that does not already hold the configured roles.
2. Confirm it receives only the active safe roles, in accordance with the current Standard or Premium quota.
3. Start Update guild member roles now and confirm the finished counters without changing any unrelated role on the test account.
4. If you test removal, review the destructive confirmation first and verify the setup is disabled after the snapshotted roles are removed.

What a successful setup looks like

A new human member receives each active safe role they do not already hold. An existing-member update completes with processed, changed, already-correct, skipped and failed counts, while unrelated member roles remain unchanged.

Common problems

A saved role is paused or unsafe

Cause: The server is above its current plan quota, the role moved above GuildPilot, Discord deleted it, or its permissions became privileged.

Fix: Restore Premium for paused quota rows, or replace the unavailable or unsafe role with an ordinary member role below GuildPilot.

Some members were skipped or failed

Cause: Members who leave during processing are skipped. Discord permission, authentication, or hierarchy denials are reported as failed.

Fix: Open the progress details and correct GuildPilot's Manage Roles permission or hierarchy. Start a new additive update, or select Retry saved removal if a confirmed removal failed; the same role snapshot is resumed without restoring automatic assignment.