[FEATURE]: Retention for join request data #671

Open
opened 2026-11-13 12:05:36 +01:00 by simon · 0 comments
Owner

Description

Decided join requests keep all applicant data, including bank-related custom fields, forever and cannot be deleted (no destroy policy). Expired unconfirmed requests are only cleaned by a mix task that never runs in production.

Proposal

  • Club setting (off by default): clear the applicant data of decided requests after N months (suggested 6). A protocol always stays: received, decision, decided by, decided at, admission/rejection mail sent at.
  • Rejected requests can be deleted by the board (protocol stays unless deleted explicitly).
  • The cleanup of expired unconfirmed requests and the retention run in production on a schedule (minimal recurring process; no general job framework in this issue).

Acceptance criteria

  • With retention on, applicant data of requests decided more than N months ago is cleared; the protocol remains.
  • With retention off, nothing is cleared.
  • Rejected requests can be deleted by the board; members and other roles cannot (forged event test).
  • Expired unconfirmed requests are removed without manual action.

Dependencies

  • None.
  • The recurring cleanup must be idempotent or take a lock: with several replicas (#267) it runs on each node.
## Description Decided join requests keep all applicant data, including bank-related custom fields, forever and cannot be deleted (no destroy policy). Expired unconfirmed requests are only cleaned by a mix task that never runs in production. ## Proposal - Club setting (off by default): clear the applicant data of decided requests after N months (suggested 6). A protocol always stays: received, decision, decided by, decided at, admission/rejection mail sent at. - Rejected requests can be deleted by the board (protocol stays unless deleted explicitly). - The cleanup of expired unconfirmed requests and the retention run in production on a schedule (minimal recurring process; no general job framework in this issue). ## Acceptance criteria - [ ] With retention on, applicant data of requests decided more than N months ago is cleared; the protocol remains. - [ ] With retention off, nothing is cleared. - [ ] Rejected requests can be deleted by the board; members and other roles cannot (forged event test). - [ ] Expired unconfirmed requests are removed without manual action. ## Dependencies - None. - The recurring cleanup must be idempotent or take a lock: with several replicas (#267) it runs on each node.
Sign in to join this conversation.
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
local-it/mitgliederverwaltung#671
No description provided.