Give Discord roles an expiry time

Temporary Roles is an opt-in Pro module. Choose a manager role, an optional log channel, a maximum grant duration and whether members receive a DM when their role expires.

What you get

Example commands

Full command list and configuration options in the Temporary Roles documentation.

Worked example: give a member two hours of event access

1. Prepare a dedicated role. Create an ordinary Discord role named Event Guest and configure the event channel’s permissions for it. Keep it out of automatic or self-role lists used by other modules. Choose a test member who does not already hold it. Can you put an existing permanent role on a timer? No: Temporary Roles refuses that grant and leaves the existing role alone.

2. Enable Temporary Roles on a Pro bot, then regenerate it and start it. Open Modules → Temporary Roles → Settings and select your server. Choose an optional manager role and log channel, set the maximum duration (1–365 days, default 30) and choose whether to send expiry DMs. Save the settings.

3. Check the hierarchy. Give the bot Manage Roles and place its highest role above Event Guest. The person running the commands needs Manage Roles or the configured manager role and must also be above Event Guest; the server owner is exempt from that manager hierarchy check. Integration-managed roles and @everyone cannot be granted.

4. Grant two hours. Use /temprole add @user @role 2h, selecting your test member and Event Guest in Discord’s user and role fields and entering 2h in duration. The two hours start when you submit the grant, not when an event starts. Read the private response: it confirms a grant and expiry or says the operation is queued. Verify that the member actually receives the role and can access the intended channel.

5. Inspect the grant. Run /temprole list @user for that member, or /temprole list for the server. The private list shows the first 15 grants with expiry times and active or pending status. After two hours, the running bot attempts to remove Event Guest. Confirm both that the role is gone and that the intended channel access has ended; other roles or channel overrides may still allow access.

6. End access early if needed. Use /temprole remove @user @role with the same member and Event Guest. It only removes a tracked grant, never an unrelated permanent role. If the response says queued, restore the bot’s access and check again. To change a tracked duration, remove the grant first, confirm removal, then add a new grant.

7. Allow for downtime and retries. Expiry times persist, but an offline bot cannot remove Discord roles. Overdue grants reconcile after restart when the module is enabled and the bot can reach Discord with the required permissions. Failed removals retry; interrupted work may wait up to two minutes for its claim to expire. Optional log messages and expiry DMs are best effort.

For an Events & RSVP gathering, an authorised organiser grants Event Guest manually. RSVPs do not trigger Temporary Roles, and this module does not bill for paid memberships. Use a dedicated role so another automatic role workflow does not restore access after expiry.

What does it cost?

Temporary Roles is included in Pro — Start free. Pro is $9.99/month.

Frequently asked questions

Related modules