Skip to main content

⏱️ Auto & Delayed Roles

Auto and delayed roles put role assignment on autopilot. Every new member receives your starter roles the moment they join, and can be granted further roles once they've been in the server for a set time — no admin action required.

Overview​

  • Auto Roles grants a set of roles to every new member immediately on join
  • Delayed Roles grants a role a set time after joining — minutes, hours, or days
  • Delayed rules apply to new members only; existing members are not affected
  • Bots that join the server are skipped
  • Both run as part of the agent's onboarding sequence, after screening and verification

Configuration​

Auto Roles​

  1. Open your project in the Fren One webapp.
  2. Select the Discord server you want to configure.
  3. In the sidebar under Agent Configuration, select Role Manager, then the Auto Roles tab.
OptionDescription
Roles granted on joinMulti-select. Every new member automatically receives these roles when they join.

Delayed Roles​

Switch to the Delayed Roles tab to grant roles once some time has passed since a member joined. Select "Add Delayed Role" to add a rule — each rule grants one role after its own delay.

OptionDescription
RoleThe role to grant. Required. Each role can only have one delay rule.
Grant afterHow long after joining the role is granted. Minimum 1; default 1.
UnitMinutes, Hours, or Days. Default: Days.

Delayed rules only affect members who join after the rule exists — existing members are never granted the role retroactively.

How it works in Discord​

When a member joins, the agent runs its onboarding sequence — blacklist screening, impersonation checks, and verification come first — then grants the auto roles and schedules any delayed-role rules. Bots are skipped.

Delayed grants are one-shot: once the delay elapses and the role is granted, the agent never re-adds it. If you (or the member) remove the role later, it stays removed. Grants that hit a transient failure are retried a few times; grants that permanently fail — the member left, the role was deleted, or the role sits above the agent in the hierarchy — are marked failed. If a member leaves and rejoins, the delay clock restarts from the new join.

Saving your changes​

Both tabs use a batched save — edits stay local until you select Save in the bar that appears at the bottom of the page. Each tab saves independently. Leaving the page with unsaved changes shows a warning first.

Best practices​

Layered access
  • Use auto roles for baseline access every member should have from day one.
  • Use a delayed role to unlock extra channels or perks for members who stick around — the default one-day delay filters out drive-by joins.
  • Keep the agent's role above every role in these lists, or the grants will fail.
  • Remember delayed grants are one-shot: removing the role manually is permanent, which makes them safe to combine with manual moderation.
Troubleshooting

A role isn't being granted?

  • Check the agent's role sits above the target role in your server's role list.
  • Delayed rules only apply to members who joined after the rule was created.
  • If a delayed role was granted once and later removed, the agent won't re-add it — that's by design.
  • If the role was deleted or the member left before the delay elapsed, the grant is marked failed.

A member rejoined and had to wait for the delayed role again?

  • The delay clock restarts when a member rejoins the server.

On this page