Skip to main content
Resignation is a formal departure process. Unlike simply setting someone to Inactive, resignation captures why people leave — giving you data to improve retention. Every resignation goes through admin approval, so no one disappears without someone knowing. Resignation requests list showing pending requests with date, member name, local group, and status When to use resignation vs other options:
  • Resignation — Member wants to leave formally. You want to know why and have a record.
  • Status → Inactive — Member is lapsing or taking a break. No formal process needed.
  • Status → Suspended — Admin needs to block someone immediately. No member input.
  • Account Deletion — Member wants their data removed (GDPR). If resignation is enabled, they must resign first.

​
How to enable

Go to Settings → Users & Profiles → Configuration → enable Resignations. Once enabled, members see a Resign button on their Close account page, and admins see Resignation Requests in the sidebar.

​
What the member sees

Members reach the resignation form through Profile → Settings & Privacy → Close account → Resign. Member resignation form showing reason field, feedback field, and close account toggle When a member clicks Resign on the Close account page, the resignation form appears inline. It contains a mandatory Resignation reason text area, an optional What would determine you to continue as member? feedback field, and a Close my account toggle (off by default — if enabled, the account is also deactivated upon approval). At the bottom, Submit sends the request for admin review and Cancel returns to the Close account page without submitting. After submitting, the member sees a confirmation. Their account continues to work normally until an admin processes the request.

​
What admins see

Navigate to Resignation Requests in the sidebar to see all submissions.

​
Processing a resignation

1

Review the request

Click View on a pending request. Read the resignation reason and feedback carefully.
2

Consider reaching out

If the member mentioned something fixable, or they’re a key contributor, contact them before processing. The feedback field often reveals retention opportunities.
3

Approve or delete

  • Approve: Processes the resignation. If the member checked “Close my account”, their status changes to Inactive. An email notification is sent to the member.
  • Delete: Removes the request entirely. The member is not notified. Only Admin Tenant can do this.

​
Who can do what

​
Resignation + account deletion

When both features are enabled, they work as a pipeline:
  1. Member must resign first and get approved
  2. Only after resignation is processed can they delete their account
  3. Deletion permanently removes their data
This gives you a two-step safeguard: you see why they’re leaving (resignation) before any data is lost (deletion). If only deletion is enabled (resignation is off), members can delete their accounts directly without any admin oversight.
Enable resignation even if you also enable account deletion. The resignation reason data alone is worth it — it tells you what’s driving people away before their data disappears.

​
Using resignation data

The resignation reasons you collect are a retention goldmine. Look for patterns:
  • Are multiple people citing the same issue? That’s a systemic problem worth fixing.
  • Are departures clustered in a specific local center? That center may have leadership or culture issues.
  • Are people leaving at a particular time of year? You may have a seasonal engagement problem.
  • Is the feedback field showing fixable issues? “I’d stay if there were events near me” is actionable.

​
Common scenarios

If the request is still Pending, an Admin Tenant can Delete the request. The member keeps their account as-is. If it was already Approved, you’ll need to manually change their status back to Active (Profile → Edit → Permissions tab → Status → Active).
This means the member didn’t toggle “Close my account” when they resigned. The resignation is on record, but they chose to keep their profile active. This is normal — some members resign from formal membership but want to stay connected.
If you’re processing many resignations at once, check if there’s a pattern in the reasons. High volume often signals an organizational issue worth addressing. For the processing itself, work through the list — there’s no bulk approve option, as each resignation should be reviewed individually.
Delete is for removing invalid or test requests. Don’t use it to prevent a member from leaving — that creates a bad experience. If a member genuinely wants to leave, approve the resignation. If they submitted by mistake, reach out and confirm before deleting.

​
Requests that sit waiting

Every resignation needs an administrator to approve it, which means a request can sit pending indefinitely if nobody is watching the queue. Members experience that as being ignored at the moment they have already decided to leave, and they tend to escalate by emailing whoever they can find. Two habits prevent it:
  • Check the pending queue on a schedule rather than when someone chases
  • Assign the queue to a named person, not to “the admins”
A member who says the resignation flow did not work has often submitted a request that is still pending, rather than hit an error. Check the queue before treating it as a fault. If there is genuinely no request there, take their email as the notice, record the resignation on their behalf, and report the failure.

​
Resignation and data deletion are different requests

Resigning ends membership. It does not erase anything, and it should not: you keep the record, the history, and the reason they left. A member asking for their data to be deleted is making a separate request under the right to erasure. Handle it through account deletion, not by resigning them and assuming that covers it. Someone who asked to be erased and later discovers their profile still exists has a legitimate complaint, and in the EU it is a regulatory one rather than a service one.
  • Account Deletion — Permanent data removal (can require resignation first)
  • User Statuses — Alternative: set to Inactive without the formal process
  • Adhesion — The opposite flow: joining the organization