Options overview

All options live at AdminCP > Setup > Options > [MC] Sunset. They are grouped into the tabs below.

Tab	Settings
General	Master switch, branding, evaluator schedule, batch size, excluded groups, member and admin emails, debug logging.
Tiers	Days inactive to enter each tier, plus the scoring weights.
Reactivation	What happens after a rejected reactivation request.
Retention	Snapshot, audit-log, and username-release retention windows.

The per-tier reactivation models and the policy assignments live on a dedicated admin page at AdminCP > Users > Sunset > Policies, not on this options page. See Policies.

General

Setting	Default	What it does
Remove branding	Off	Removes the "Powered by [MC] Sunset" footer text.
Enable evaluator	Off	Master switch. When off, the evaluator and retention enforcer crons return immediately. CLI commands and manual admin actions still work.
Evaluator schedule	Weekly	How often the evaluator runs: Daily or Weekly (weekly runs on Mondays). The cron entry itself fires hourly; this option gates whether the entry queues work.
Maximum members per run	500	Upper bound on candidates evaluated per cron pass. The evaluator paginates by user_id and resumes from the last cursor on the next pass.
Minimum account age	90 days	Members whose register_date is younger than this are never candidates. Stops the evaluator targeting fresh accounts that simply haven't started posting yet.
Excluded user groups	(empty)	Members of any selected group are never candidates. Add staff, moderator, and bot groups here.
Email member when entering warned tier	On	When on, the seeded notify_user policy at the Warned tier sends an email. Turn off if you'd rather not warn members at all.
Admin notification email	(empty)	Recipient for the notify_admin policy. Plain email address. Leave empty to silently disable admin emails.
Verbose debug logging	Off	When on, every policy execution and cron-run summary writes a line to AdminCP > Tools > Logs > Server error log under the source MC\Sunset\DebugLogger.

Tiers

Setting	Default	What it does
Warned tier threshold	180 days	Days since last activity to enter the Warned tier.
Soft sunset threshold	365 days	Days since last activity to enter the Soft sunset tier.
Hard sunset threshold	730 days	Days since last activity to enter the Hard sunset tier.
Username release threshold	1825 days	Days since last activity to enter the Released tier.
Last activity weight	60	Multiplier applied to days-since-last-activity in the composite score. Visible on the per-user state page.
Low post count threshold	5 posts	If message_count is at or below this, the low-post-count signal contributes to the score.
Low post count weight	10	Fixed amount added to the score when the low-post-count signal fires.

Reactivation

Setting	Default	What it does
After a rejected reactivation request	allow	What the lockout page allows after a request is rejected: allow lets the member submit again immediately, block removes the request button entirely, cooldown enforces a waiting period.
Re-request cooldown	30 days	Only applies when After a rejected reactivation request is set to cooldown. Days the member must wait before submitting a fresh request.

The four per-tier reactivation models (Warned, Soft, Hard, Released) are configured on AdminCP > Users > Sunset > Policies, not here. See Reactivation for the meaning of each model.

Retention

Setting	Default	What it does
PII snapshot retention	365 days	How long released-username snapshots are kept before the retention enforcer deletes them. Once gone, the released username can never be restored.
Profile snapshot retention	730 days	How long native and custom profile-field snapshots are kept. Once gone, the original values are unrecoverable.
Audit log retention	2555 days	How long audit rows are kept. Pruned in 1000-row chunks per retention-enforcer pass.
Hard to released window	730 days	How long a member must sit in the Hard sunset tier before the retention enforcer queues the Released transition.
Released username lockout	30 days	How long after release the username is blocked from re-registration. Enforced via xf_mc_sun_released_username, which survives user delete.
Confirm username releases manually	Off	When on, the retention enforcer does not auto-release. Eligible members surface in a confirmation queue on the dashboard, each requiring an explicit admin click to release.