Skip to main content
Resignation is a formal departure with a reason attached. A member submits a request, an administrator approves it, and the approval closes out their roles and (usually) sets them to Inactive. Nothing is deleted: the record of who left, when and why stays in the organisation. Built for organisations that want to know why people leave. Replaces someone quietly going Inactive with no explanation and no record. Resignations list with all, pending and processed filter chips and a table of requests showing date, member, requested by, chapter, stay active and status

​
Settings

Resignation is off by default.

​
What the member does

Profile → Settings & Privacy → Close account → Resign. The form opens in place. Resignation form with a resignation reason box, a what would determine you to continue as member box, a Close my account toggle and Submit and Cancel buttons When Automatically Inactivate Accounts After Resignation is on, the toggle is replaced by a line in red: “This account will be closed after resignation is approved.” After Submit, the Close account page shows “Your resignation is pending and it will be processed by administration” with a Cancel resignation button. The account works normally until an admin acts.
A member may have only one pending request at a time. Submitting a second one is refused with “Your current resignation request is pending, we will email you once is processed.”Guest accounts do not see the Resign button at all.
An administrator with HR_LOCAL over the member’s local group sees the same form on that member’s Close account page, headed “Record the resignation of this member”, plus a shortcut with that label on the member’s Permissions tab. Use it when somebody resigns by email or in person.

​
What administrators do

The queue is Resignation requests in the sidebar under MANAGEMENT, visible to HR_LOCAL and above once the module is on. The screen is titled Resignations: 30 requests per page, newest first, chips for All, Pending and Processed, and columns for date requested, member, requested by, chapter, StayActive and status. StayActive is hidden when automatic inactivation is on, because the answer never varies. Opening a row shows the reason, the retention answer and an Exit conclusion box for the reviewer’s note. The exit conclusion is hidden from the resigning member and read-only once approved. Approve processes the resignation; Delete removes the request entirely and is only offered in the queue to ADMIN_TENANT. Resignation request detail showing status, date, member, requested by, stay active, resignation reason, retention answer, exit conclusion box and Approve and Delete buttons HR_TENANT and ADMIN_TENANT cover every local group.

​
What approval actually changes

Approval, in one step:
  • stamps the request as approved, with the approving admin and the date;
  • sets the member Inactive if automatic inactivation is on, otherwise Inactive or Active according to their “Close my account” choice;
  • sets the member’s user type to the configured Guest User Type;
  • clears the member’s adhesion link, if the Adhesion module is on and a guest user type is configured;
  • end-dates every open role the member holds, as of the resignation date;
  • emails the member the resignation-approved notice.
The user type is reassigned on every approval. If your organisation has no Guest User Type configured (Settings → Users & Profiles → Configuration → User Types & Roles), approving a resignation leaves the member with no user type at all. Set a guest user type before you turn the module on if user type drives anything in your setup.
Nothing is deleted: the profile, the payment history, the event attendance and the ended roles all remain.

​
Emails

Both are governed by Resignation Notifications under System Emails. A member asking for their data to be removed is making a different request: handle that through account deletion, and read that page first so you can tell them what survives. The two are independent: deletion does not require a resignation, and resigning does not start a deletion.

​
Common questions

While it is pending, the member withdraws it with Cancel resignation on their Close account page, or an ADMIN_TENANT deletes it from the queue. After approval, set their status back to Active on the Permissions tab and reassign the roles the approval end-dated.
The member left “Close my account” off and your organisation does not force automatic inactivation. The resignation is on record and the roles are closed, but the account still works. That is a supported outcome.
Nothing expires or auto-approves a request. A member who says the form “did not work” has usually submitted one that is still sitting there.
No. Approval is one request at a time, from the detail view.
Delete is for invalid or test entries. It notifies nobody, so the member is left thinking they resigned when nothing was recorded.