Comparison
When a Discord member becomes inactive, you do not have to jump straight to removal. For many communities, an inactive role is the safer first step.
| Decision | Inactive role | Kick |
|---|---|---|
| Best for | Reversible cleanup, role hygiene, staff review | Final cleanup after clear policy and review |
| Member impact | Lower | Higher |
| Reversible | Yes | Only if they rejoin |
| Drama risk | Lower if explained | Higher if unexpected |
| Best CleanerBot flow | Warning to inactive role to review | Review to optional removal |
Use an inactive role when the server has many roles, members may return later, staff should review before removal, paid supporters or volunteers need a softer process, or RP, guild, clan, education, and product communities need context.
A kick may make sense when the policy was clearly published, the member crossed the final threshold, staff reviewed edge cases, the member had a chance to return, and the server has a real roster reason.
1. Warning 2. Inactive role 3. Staff review 4. Optional removal
Keep auto-kick off until the team understands the thresholds and trusts the process.
CleanerBot lets you configure warning threshold, inactive role threshold, kick review threshold, manual kick review channel, exempt roles, slower decay for selected roles, pre-kick DMs, optional reinvite URL, and optional auto-kick guardrails.
Role behavior depends on your configured inactivity role mode. Review your settings before publishing a policy or enabling stronger actions.
Gaming and RP: keep rosters clean without erasing returning players too quickly.
Creator communities: keep quiet supporters from being treated like abandoned accounts.
Education: use early warnings and private review.
SaaS communities: use Ghost Mode and staff-only review.
NGOs: use long thresholds and staff review for seasonal volunteers.
It should not be framed as punishment. It is a status signal that activity has faded and staff may need to review access.
Only if your server intentionally configures that behavior and understands the consequences.
Not during initial setup. Use manual review first. Auto-kick is optional and should only be enabled with guardrails and a clearly published policy.
Yes. If they participate again, their Decay Score can drop or reset based on your configuration.
Use warnings, inactive roles, and review before final removal.