[FEATURE]: Per custom field: what members may see and change #669

Closed
opened 2026-11-13 12:03:22 +01:00 by simon · 0 comments
Owner

Description

Clubs store very different things in custom fields: a phone number the member should maintain, a "photo consent" the member should see and change, an internal "paper application" flag or a reduction reason the member should not see. Today members see all custom fields of their record and (before #664) could change all of them.

Proposal

  • Each custom field gets a member access setting: hidden / visible / editable. Default for existing fields: visible (read-only), so nothing new becomes editable or disappears without the club deciding.
  • The member's own page and edit form respect the setting; the board sees everything as today.
  • The setting is shown in the data fields settings next to "show in join form".

Acceptance criteria

  • Hidden fields are neither shown nor accepted for members; visible fields are shown read-only; editable fields can be changed by the member.
  • Forged params for hidden or visible fields are rejected (test sends them).
  • Existing installations: all fields visible, none editable after migration.
  • Board/admin views unchanged.

Dependencies

## Description Clubs store very different things in custom fields: a phone number the member should maintain, a "photo consent" the member should see and change, an internal "paper application" flag or a reduction reason the member should not see. Today members see all custom fields of their record and (before #664) could change all of them. ## Proposal - Each custom field gets a member access setting: hidden / visible / editable. Default for existing fields: visible (read-only), so nothing new becomes editable or disappears without the club deciding. - The member's own page and edit form respect the setting; the board sees everything as today. - The setting is shown in the data fields settings next to "show in join form". ## Acceptance criteria - [ ] Hidden fields are neither shown nor accepted for members; visible fields are shown read-only; editable fields can be changed by the member. - [ ] Forged params for hidden or visible fields are rejected (test sends them). - [ ] Existing installations: all fields visible, none editable after migration. - [ ] Board/admin views unchanged. ## Dependencies - After #664.
simon closed this issue 2026-11-19 13:48:28 +01:00
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#669
No description provided.