Skip to main content

Automating Access by Membership Status

Role sync lifecyclePayBru keeps mapped Discord roles aligned with membership access.

When a member joins, renews, upgrades, downgrades, cancels, or loses access, PayBru updates the mapped Discord role so the server reflects the membership state.

Active roleSyncingPast Due graceRole removed

Once a tier is linked to a Discord role, PayBru handles the role changes for you.

Lifecycle Events

EventMembership statusWhat PayBru does in Discord
New subscriptionActiveAssigns the mapped Discord role.
Tier upgradeActiveSwaps the member to the mapped role for the new tier.
Tier downgradeActiveSwaps the member to the mapped role for the new tier.
Renewal succeedsActiveKeeps the mapped role in place.
Payment failurePast DueKeeps the role during the 6-day grace period. If payment is not recovered, removes the role when membership moves to Ended.
Voluntary cancellationCanceled, then EndedKeeps the role until the paid period finishes, then removes it when access ends.
RefundEndedRemoves the mapped role at the next role check.

How the Sync Works

Membership status changes

A member joins, renews, changes tier, cancels, or loses access after the grace period.

PayBru checks the tier mapping

PayBru looks for the mapped role connected to that tier and Discord server.

The PayBru bot updates the member

If the member linked Discord and joined the server, the bot adds or removes the mapped role.

Discord channel access follows the role

Channels controlled by that role become visible or hidden according to your Discord permissions.

The first update usually happens quickly. Larger servers can take longer when Discord slows down role changes.

If the member is not in your server yet, or has not linked Discord to their PayBru profile, PayBru keeps the expected role state and applies it when those gaps are closed.

When Access Ends

When a membership ends:

  • Roles connected to that membership tier are removed.
  • The member loses access to any Discord channels restricted to those roles.
  • The member is not kicked from the server. They stay as a regular server member unless you remove or ban them in Discord.
Canceled is not the same as ended

A canceled paid membership can still have access until the paid period finishes. The Discord role is removed when the membership becomes Ended, not at the moment the member schedules cancellation.

Automatic Checks

PayBru checks Discord regularly so roles stay aligned even if one update was delayed.

CheckRoughly how oftenPurpose
Role syncEvery few minutesChecks active members against their expected mapped roles and corrects mismatches.
Member presenceEvery few minutesDetects when a linked member joins the server and grants pending roles.
Ban syncEvery few minutesKeeps Discord bans aligned when your community uses Discord ban syncing.
Permission health checkEvery half hourConfirms the PayBru bot still has the permissions and role position it needs.
Membership expiry checkHourlyRemoves roles after the 6-day grace period ends, or when a canceled paid period ends.

Manual Refresh

If a role still looks wrong after the next sync:

  1. Open Settings > Integrations and refresh or reconnect Discord.
  2. Open Members and confirm the member's current membership status and tier.
  3. Open Tiers and re-check the Discord step on that tier.
  4. Ask the member to confirm Discord is still linked in Resources > My Profile > Security > Connected Accounts.
  5. Ask the member to confirm they are still in the creator's Discord server.

If PayBru detects a bot permission problem, the community owner is notified after a short delay so brief Discord role housekeeping does not create unnecessary noise.

Status Examples

Member stateActive + linked + in server

PayBru assigns the mapped role and keeps it in sync.

Member stateActive + not linked

PayBru cannot match the PayBru member to a Discord account yet.

Member stateActive + not in server

PayBru waits until the linked Discord account joins the creator's server.

Server statePermission error

The bot cannot manage the mapped role until permissions or role hierarchy are fixed.

See Also