Guild's permission logic can be summed up in one sentence: you set conditions, Guild automatically assigns roles, and automatically revokes them when conditions are no longer met. It does not require you to manually approve each person, nor does it require you to write scripts to sync Discord roles. The core mechanism is built on three things: Requirements, Roles, and Rewards. The real effort lies in understanding when "condition failure" triggers revocation, and which actions can cause existing members to instantly lose permissions.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Conditions: AND, OR, and Exclusion Rules
After creating a role in Guild's Editor, click "Add requirements" to add conditions. Condition types cover on-chain activity (holding specific tokens or NFTs, interacting with a certain contract), social proof (following X, holding a Discord role, verified email), internal Guild activity (reaching a certain point value, holding another Guild role), and time conditions (holding a Discord role before a certain date, having transactions on Base in the last 7 days).
There are three logical relationships between conditions: Meet all (AND), Meet any one (OR), Meet X of them. The default is usually AND. If you want "holding a token OR following X" both to grant the role, switch to "Should meet 1".
There is also an easily overlooked toggle: "Should not satisfy". Its purpose is to exclude people who meet a certain condition. For example, if you want to give roles to active users but don't want bots or alt accounts to sneak in, you can add "Should not satisfy: holding an NFT from a known bot address". This exclusion rule stacks with normal conditions, it is not an either/or choice.
Once conditions are set, members click Verify on the Guild page, and Guild checks if they satisfy them. Most conditions are continuously synced, not a one-time check. This means if your condition involves "interacted in the last 30 days", and a member has no new interaction on day 31, the role will be automatically revoked.
Syncing: Automatic Assignment, Automatic Revocation, But With Delays
Guild's design goal is "no manual management". When members meet conditions, the corresponding Guild role takes effect automatically, and associated rewards (like Discord roles, points) are distributed accordingly. When members no longer meet conditions, roles and rewards are automatically revoked.
Discord role syncing is not instant. Official documentation states that role assignment is automatic, but due to Discord's rate limits, it may take 1–2 minutes, and during busy periods members will see an estimated timer. If many members verify simultaneously during an event in your community, the delay will be more noticeable. This is not a Guild issue, but a constraint of the Discord API.
Discord role syncing has a prerequisite that must be met: the Guild bot must be in your Discord server and have the "Manage Roles" permission. Additionally, the bot's own role position must be higher than the roles it needs to assign. If you drag the Guild bot's role below member roles, it will not have permission to give anyone roles, and syncing will fail silently. This is the most common configuration error during setup.
Revocation: Condition Failure and Manual Removal Are Two Different Paths
Automatic revocation occurs when conditions are no longer met. For example, if your condition is "hold 500 tokens", and a member sells down to 499, the role and Discord role will be revoked. Guild documentation does not give a specific number of seconds for sync frequency, but the statement "most requirements are continuously synced" implies that revocation is not waiting for a fixed cycle, but rather takes effect when a member next triggers verification or during a background check. If your community has high requirements for permission timeliness (such as paid subscriptions), you need to consider both "Guild's sync delay" and "Discord's assignment delay" together.
Manual removal is a different path, and its effect is more thorough. On Guild's Members page, admins can remove members from the Guild. After removal, the member's roles are revoked and they disappear from the member list. Note that this is removal at the Guild level, which severs all associations between that member and your Guild, not just one role. If you only want to revoke a specific role's reward, you should do so by modifying or deleting that role's reward, not by removing the member.
Here is an operational reminder: Do not add new conditions to existing roles. Guild documentation explicitly warns that if you add new requirements to a role that members already hold, existing members likely will not satisfy the new requirements and will all lose that role. The correct approach is to create a new role, set conditions, and have members re-verify, or notify members before making changes.
Our Take
If you are setting up Guild for the first time, starting with 2–5 basic roles is enough. Put "Join Discord" and "Follow X" on the homepage as entry-level roles, then create roles for token holders or active contributors on separate pages. Preview the verification flow using "View page as a visitor" first to confirm condition logic works as expected before publishing.
If you are doing paid subscriptions or token gating, pay special attention to the Discord bot's role hierarchy. Drag the Guild bot above all member roles that need to be assigned before configuring rewards. Otherwise, you will see "setup successful" but members won't get roles, which wastes a lot of time troubleshooting.
If you are worried about accidental revocation, set wider time windows in conditions, or use "Should meet 1" to give members multiple paths to satisfy conditions. The stricter the conditions, the higher the probability of accidentally hurting legitimate members, and Guild's automatic revocation will not give you a chance to "confirm before revoking".
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
References
- Guild Docs·How Guild works, page published or updated: 2025-09-22; verified: 2026-10-21.
- Guild Docs·How to setup requirements, page published or updated: 2025-06-15; verified: 2026-10-21.
- Guild Docs·Add Guild roles, page published or updated: 2025-08-12; verified: 2026-10-21.
- Guild Docs·Discord role, page published or updated: no date indicated; verified: 2026-10-21.
- Guild.Host·Elevate Your Community | Members, page published or updated: no date indicated; verified: 2026-10-21.
