Remove member

What is this?

With the function Remove member you end a person''s membership in your choir. You have two options, depending on how the relationship ended and whether the member wants their data deleted:

1. Set status to "left" — the member stays in the database but is inactive. Singer history, anniversaries and attendance statistics are preserved. Standard case.
2. Completely delete (GDPR request) — all personal data is removed. Used when the member explicitly requests it.

How to remove a member

1. Open your choir and go to Members.
2. Click the member in the list, then "Remove".
3. Choose the variant: "Mark as left" or "Completely delete (GDPR)".
4. Optional: enter a reason for leaving (e.g. "moved away", "illness") — only visible internally.
5. Optional: enable "Notify member" for a short farewell.
6. Confirm the action.

What happens with "left"

• Member loses access to the choir in Chorilo immediately.
• Other members'' singer history keeps the entry (e.g. "former soprano").
• Attendance statistics stay for historical evaluation.
• Birthday and anniversary lists no longer show the member.
• Emails and push notifications are stopped.
• For re-entry you can simply reactivate the member — all data is still there.

What happens with "completely delete"

• All personal base data is deleted (name, email, address, date of birth).
• Profile picture is removed.
• Aggregated statistics stay anonymized (e.g. "2024: 45 members").
• Donation receipts and invoices are kept for legal reasons — retention duty 10 years.
• Confirmation by email to the deleted member.

Permission

You need the permission members.edit. By default the choir director and board have this access. Owners cannot be removed by others — only they themselves can transfer the owner status.

Tips

• The default is "left" — the historical singer history is a piece of choir history that you should only delete on explicit request.
• Enter a reason for leaving — in a year you might want to understand why someone left.
• For the death of a member: use "left" with reason "deceased". That way the member stays in memory and anniversaries are correctly anonymized.
• Document GDPR deletion requests — write down date and request. The confirmation email also serves as proof.