Permissions
One admin permission gates the entire AdminCP surface. Two moderator permissions control who can handle reactivation requests and who sees the staff-only tier indicator on member profiles.
Admin permission
AdminCP > Admins > Admin permissions > (edit an admin).
| Permission | Default | Effect |
|---|---|---|
| Manage Sunset (inactive user lifecycle) | Allow (super admin only) | Required to see the AdminCP > Users > Sunset navigation entry and every page beneath it (Dashboard, Policies, Reactivation requests, Audit log, per-user state). |
Moderator permissions
AdminCP > Groups & permissions > Permissions > General moderator permissions, or per-user under AdminCP > Users > Moderators.
| Permission | Default | Effect |
|---|---|---|
| Handle sunset reactivation requests | Deny | Required to see reactivation requests in the moderation approval queue and to approve or reject them. AdminCP-route approvals are gated by the admin permission, not this one. |
| View Sunset tier | Deny | When granted, a small tier chip appears next to the member's name on their profile page (visible only to staff). The chip shows the tier name and the date the member entered it. |
Revoking access for a single group
To remove the staff tier indicator from one moderator group while leaving others unaffected:
- AdminCP > Groups & permissions > Permissions, then edit the group.
- Set View Sunset tier to Never.
The chip stops rendering for that group. Other moderator groups are unaffected.
How permissions interact with the master switch
When Enable evaluator is Off, the cron jobs and lockout listener do nothing, but the AdminCP pages, the Policies page, the per-user state page, and the CLI commands all remain available to anyone holding Manage Sunset. Use that combination to seed configuration on a fresh install without firing anything live.