Skip to main content
Deleting an account in Orgo strips the member’s contact identifiers, cuts their access permanently, and removes them from every list and search. It does not delete the underlying record, and it does not remove their name, their history or their payments. That distinction matters if you answer erasure requests, so this page states it field by field. Read the tables before you promise a member anything. Built for honouring a member’s request to be removed from the community. Replaces an “archive” flag that leaves the person searchable. The Close account card in a member's settings, offering Close account, Suspend account, Resign and Delete account, each with its explanation

​
Where it lives

Profile → Settings → Account and security → Close account card, then Delete account. A member reaches it from the Settings button on their own profile. For someone else’s account, add ?tab=settings to the profile address (/user/{id}?tab=settings); there is no button for it on another member’s profile. A confirmation dialog appears (“Are you sure you want to completely delete the account? This action cannot be undone!”) and confirming applies the change immediately. There is no module to enable and no setting that turns deletion on or off. The same card also offers Close account (sets Inactive, reversible) and, for admins, Suspend account and Reactivate account. Those are the reversible options; see User statuses and Member profile.

​
Who may delete an account

Ordinary members cannot self-delete. An erasure request from a member is something an administrator carries out on their behalf, which is worth building into your privacy procedure rather than pointing members at a button they will not find.

​
What deletion removes

These are cleared or deleted outright on the account:

​
What deletion keeps

These are not touched:
Both tables describe the Delete account action only. A record that was merged away also ends up on the Deleted status, but it is not shaped like a deleted account: its email is prefixed rather than cleared, its phone number and local group are kept, and its roles were transferred to the surviving record rather than deleted. See Merging duplicates.
“Deleted” in Orgo is an anonymisation of contact identifiers plus a permanent access block. It is not erasure. If your organisation has to satisfy a right-to- erasure request in full, treat the built-in action as step one and remove the remaining personal data yourself: the name and profile fields, custom field values, uploaded identity documents and the adhesion record. Retaining payment and invoice records for the statutory period is normally lawful; retaining a profile photo is not.

​
What deletion does not do

  • It does not notify anyone. No email goes to the member and none to your administrators. The Notify Admins on Account Deactivation setting covers a member closing their own account (Inactive), not deletion.
  • It does not write an audit entry. There is no deletion record in the member’s activity log, so if you need a compliance trail, record the request and the action in your own system.
  • It does not free places. Event registrations, attendee lists and waitlist entries are untouched. Cancel those separately if the place should be released.
  • It cannot be undone. There is no restore action, and a deleted account can no longer be edited: an administrator who tries is refused with “User has been deleted”. The one exception is a merge, whose source record is also set to Deleted and is put back on its previous status if the merge is undone within 30 days.

​
What the member experiences

Immediately after deletion:
  • their session ends and they are returned to the login screen;
  • signing in with a password fails, because the sign-in identifier no longer matches;
  • asking for a one-time code returns the neutral “if this email exists, a code has been sent” response and no code is sent;
  • they no longer appear to other members anywhere in the app.
Because the email address was cleared, the same person can register again from scratch with the same address. The new account is a genuinely new member with no history: the old record stays where it is, detached.

​
Automatic clean-up

Two things happen without anyone pressing a button. Unconfirmed registrations. Every night at 05:00 UTC, accounts that have been sitting on Unconfirmed email for more than two months, with no payments and no adhesion, are removed. Where related records prevent the row from being removed, the account is marked Deleted instead and is anonymised in the same way as above. Erasing old inactive or deleted accounts. This one is off until you turn it on: Settings → Modules → Users & Profiles → Configuration → Erase Inactive or Deleted Accounts After, with a window of 6, 12, 24 or 36 months. It runs nightly and is counted from the date an account became Inactive or was deleted. Members who still sign in are never included, and Suspended accounts are never touched.
  • An account with no history (no payments, applications, roles held, events or content) is deleted outright.
  • An account with any history is anonymised: name, contact details, ID documents, custom field answers, staff notes about them and the profile photo are erased, and the record stays so that invoices, votes and offices keep a valid owner. The member shows as an obfuscated user.
  • The first run comes 14 days after you switch it on, so a mistake can still be switched off in time. Erasure cannot be undone.
Unlike the Delete account action, this is a real erasure of the personal data on the account. It only reaches accounts that have already been Inactive or Deleted for the whole window.

​
Common questions

Delete the account from the Close account card of their Settings view (/user/{id}?tab=settings) as an Orgo administrator: the Delete account button is not shown to anyone else. Then decide, against your own retention policy, what to do with the name, profile fields, custom field values, identity documents and adhesion record, which the action leaves in place. Record the request and what you did outside Orgo, because the platform does not log the deletion.
On a member’s own profile it is under Settings → Account and security → Close account, and it is shown only to a guest on their own account and to an Orgo administrator. An ordinary member sees Close account (Inactive, reversible) and, where the Resignation module is on, Resign. An HR administrator on someone else’s profile sees Request delete, which opens a support request.
No. Even setting the status back to Active does not return their email, phone number, local group or roles. They should register again.
Use resignation, or set them to Inactive. Both keep everything and both are reversible.
Payments, invoices and fee history survive untouched, so an unpaid invoice is still an unpaid invoice. Deletion does not cancel debts and does not write anything off.
Expected. Event attendance is not touched. Remove the attendance record from the event if it should not be there.