[MC] Sunset 1.1.3

Retire inactive accounts without deleting them.

Features​

Five stages
Sunset sorts each member into one of five stages based on how long they've been gone: Active, Warned, Soft, Hard, and Released. Quiet accounts drift further along over time, and the moment a member comes back they snap straight to Active. Nothing's permanent until that final stage, so what you get is a slow off-ramp rather than an on/off switch.

You set the timing
The stages default to 180, 365, 730, and 1825 days, but those are just starting points. Set your own. Brand-new accounts are left alone for a configurable period so nobody gets a warning in their first week. There's also an optional fast track for members who registered and never posted: give them their own, shorter set of thresholds so they don't sit in the queue as long as someone who actually contributed.

Try before you commit
The simulator runs any set of thresholds against your whole member list and shows you how many members would land on each stage, side by side with your current numbers. Change the days, see the effect, and only then save.

Pick who it leaves alone
The Eligibility page decides who is even a candidate. Exclude staff with a toggle, set a minimum account age, and build your own rules with user criteria and custom user fields, matched on AND or OR. Individual members can also be flagged exempt so they're never touched, no matter how long they've been quiet.

Choose what happens at each stage
Each stage runs whatever actions you assign to it. The built-in ones cover the usual needs:

• Hide the profile from search, leaving every post in place.
• Clear out profile fields like location or signature, after saving a copy first.
• Email the member, an admin, or both when an account reaches a stage.
• Release the username back into the pool for someone else to use.

Most of these reverse cleanly. Releasing a username is the one that doesn't, which is why it only happens at the final stage.

Warn them before they move
Sunset can email quiet members ahead of a stage change rather than after it. Set how many days of warning they get, write your own subject line and body, and it works across multiple languages through phrases. Members who would rather not hear from you can opt out from their own preferences.

Five ways to welcome members back
When a sunsetted member logs back in, you decide what happens, and you can set it per stage. Let them straight back in; let them in but email yourself a heads-up; hold the login for your approval; turn it away with a note to get in touch; or let them in while keeping their personal details hidden until you say otherwise. Early stages wave people through quietly by default. Later ones ask for a review first.

What happens to cleared data
Before any field is cleared, Sunset saves the original, and if the member comes back, it comes back with them. Those saved copies stick around for a set period and are then removed for good. You decide how long that window is.

Username release with a safety net
At the final stage, a username goes back into the pool. Sunset keeps a record of who held it, so you can set a waiting period before it's reusable and stop anyone from grabbing the name to impersonate the previous owner. Prefer to sign off on each one yourself? Strict mode holds releases in a queue on the dashboard until you confirm them.

Approval queues
Held logins land in a reactivation queue for you to approve, reject, or leave sitting. Each entry shows who it is, which stage they're at, when they left, and what would be restored. Under strict mode, pending username releases wait for a separate confirmation on the dashboard. Nothing irreversible happens without you signing off.

Working in bulk
Filter the Admin CP user list by Sunset stage to see exactly who is where, and apply stages through batch update when you need to move a group of accounts at once. Releasing a username stays a deliberate, one-at-a-time action, because it can't be undone.

Reporting
Stage movements, reactivations, releases, and reminders all feed the built-in statistics system, so you can chart what the add-on is actually doing over time. A full activity log records every transition and every action taken, filterable, paged, and exportable to CSV.

API and webhooks
Three REST endpoints, super-user key only: read a member's stage, list members by stage, and trigger a reactivation. Six webhook events cover the full lifecycle, so you can push stage changes out to whatever else you run.

Easy access
Everything lives under Sunset: a dashboard with per-stage counts and recent activity, a grid for assigning actions and welcome-back behaviour to each stage, an approval queue for held logins, and a full activity log you can filter, page through, and export to CSV. There's also a Preview button that shows exactly what the next pass would do before it touches anyone.

Off until you're ready
Nothing runs after install. Set it up, preview a run to see what would happen, then flip the switch when you're comfortable.



Important information:
We include a single copyright line that is shared across all of our add-ons and allow branding removal at no extra cost.