local-it/mitgliederverwaltung
2
3
Fork 0
Code Issues 51 Pull requests 13 Projects 1 Releases Packages 1 Activity Actions

associate each user with a member #119

New issue
Closed
opened 2025-07-24 12:53:16 +02:00 by moritz · 7 comments
moritz commented 2025-07-24 12:53:16 +02:00
Owner
Copy link

Each user should be able to edit it's member details independent of the user roles and permissions

Replaced by the following issues:
#164 [FEATURE]: create logical link between users and members
#167 [FEATURE]: Sync member.email from user.email if linked
#168 [FEATURE]: Allow user-member association in edit/create views
#169 [FEATURE]: Allow combined creation of Users/Members
#170 [FEATURE]: Show Userdata when hitting "profile" button
#171 [FEATURE]: Ensure correct handling of Password login vs oidc login

planning happened here:
https://pad.local-it.org/AlGmz-_1Qh-OvfyzgD4p7w?both

Each user should be able to edit it's member details independent of the user roles and permissions Replaced by the following issues: #164 [FEATURE]: create logical link between users and members #167 [FEATURE]: Sync member.email from user.email if linked #168 [FEATURE]: Allow user-member association in edit/create views #169 [FEATURE]: Allow combined creation of Users/Members #170 [FEATURE]: Show Userdata when hitting "profile" button #171 [FEATURE]: Ensure correct handling of Password login vs oidc login planning happened here: https://pad.local-it.org/AlGmz-_1Qh-OvfyzgD4p7w?both
moritz added this to the Accounts & Logins milestone 2025-07-24 12:53:16 +02:00
moritz self-assigned this 2025-07-24 12:53:17 +02:00
moritz added this to the Sprint 4 - 09.07 - 30.07 project 2025-07-24 12:53:17 +02:00
moritz commented 2025-07-24 17:55:17 +02:00
Author
Owner
Copy link

  1. User -> Member Relationship

    • Each user is associated with exactly one member.
    • A member can be (optionally) associated with a user.
    • The relationship is 1:1.

  2. User View

    • The user overview displays which member the user is associated with.

  3. Profile View

    • An logged-in user can edit their own member data via "Profile".
    • The view corresponds to the member editing view, but is limited to the user's own member.

  4. User Registration

    • When registering a user, a new member is automatically created and associated.

  5. Admin: Create User

    • Admin can choose when creating a user:
      • Linking to an existing, unassociated member.
      • Creating a new member for the user.

  6. Delete User

    • When deleting a user, the associated member remains intact.
1. **User -> Member Relationship** - Each user is associated with exactly one member. - A member can be (optionally) associated with a user. - The relationship is 1:1. 2. **User View** - The user overview displays which member the user is associated with. 3. **Profile View** - An logged-in user can edit their own member data via "Profile". - The view corresponds to the member editing view, but is limited to the user's own member. 4. **User Registration** - When registering a user, a new member is automatically created and associated. 5. **Admin: Create User** - Admin can choose when creating a user: - Linking to an existing, unassociated member. - Creating a new member for the user. 6. **Delete User** - When deleting a user, the associated member remains intact.
carla modified the project from Sprint 4 - 09.07 - 30.07 to Sprint 5 - 31.07. - 11.09. 2025-07-31 14:06:29 +02:00
simon commented 2025-08-15 12:37:32 +02:00
Owner
Copy link

Do we allow technical users?

e.g. should we integrate with Kollicloud/Authentik OIDC, we might have "akadmin" Users who are no actual members

Do we allow technical users? e.g. should we integrate with Kollicloud/Authentik OIDC, we might have "akadmin" Users who are no actual members
moritz commented 2025-08-19 21:21:24 +02:00
Author
Owner
Copy link

Actually no. Each user must be associated to a member. But it could be a "technical" member.

Actually no. Each user must be associated to a member. But it could be a "technical" member.
simon commented 2025-08-20 11:21:03 +02:00
Owner
Copy link

then we need to make sure to be able to exclude it from fee calculations, total member count etc.

then we need to make sure to be able to exclude it from fee calculations, total member count etc.
simon commented 2025-08-21 11:53:12 +02:00
Owner
Copy link

Meeting Notes weekly:
New approach User <-> Member

  • User müssen nicht unbedingt einen Member haben (Technischer Support Admin)
  • User sind auch in der UI ein getrenntes Konzept von Members
  • Mail-Adressen werden trotzdem nach Mo's Ansatz gesynct
    • Wenn Member + User existent, dann für Member auch Usermail verwenden
  • User brauchen nicht unbedingt Zugriff auf Memberlist - ggf. nur ihre eigenen Daten bearbeiten
  • Aufschreiben: Welche UX-Flows gibt es, sollten wir supporten?
Meeting Notes weekly: New approach User <-> Member - User müssen nicht unbedingt einen Member haben (Technischer Support Admin) - User sind auch in der UI ein getrenntes Konzept von Members - Mail-Adressen werden trotzdem nach Mo's Ansatz gesynct - Wenn Member + User existent, dann für Member auch Usermail verwenden - User brauchen nicht unbedingt Zugriff auf Memberlist - ggf. nur ihre eigenen Daten bearbeiten - Aufschreiben: Welche UX-Flows gibt es, sollten wir supporten?
carla commented 2025-09-04 12:50:59 +02:00
Owner
Copy link

@simon magst du den issue nochmal splitten in Konzept / Architektur / Datenmodell etc...so dass du vielleicht einen Teil übernehmen kannst, aber di codearbeit Mo macht wenn er wieder da ist? :)

@simon magst du den issue nochmal splitten in Konzept / Architektur / Datenmodell etc...so dass du vielleicht einen Teil übernehmen kannst, aber di codearbeit Mo macht wenn er wieder da ist? :)
carla modified the project from Sprint 5 - 31.07. - 11.09. to Sprint 6 - 11.09 - 02.10. 2025-09-11 10:12:36 +02:00
moritz commented 2025-09-26 13:37:18 +02:00
Author
Owner
Copy link

replaced by: #164

replaced by: https://git.local-it.org/local-it/mitgliederverwaltung/issues/164
simon removed this from the Sprint 6 - 11.09 - 02.10. project 2025-09-26 15:11:23 +02:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
renovate/renovate-renovate-42.x
renovate/mix-dependencies
perform-migration-on-startup
feature/196_search_custom_fields
feature/220_ui_issues_2
sidebar
renovate/major-postgres
feature/223_member_checkbox
renovate/major-mix-dependencies
renovate/postgres
renovate/ghcr.io-sebadob-rauthy-0.x
persist-sort-order
docs/210_payment-concept
feature/151_roles_permissions_docs
manual_renovate_update
feature/#158-polish-README
feature/128_playwright_a11y_test
feature/119_member_user_relation_refactor
feature/119_user_as_member
feature/backpex-migration
feature/backpex_translation
feature/39_account_ressource
feature/74_memberfields
validation
feature/36_add_primerlive
No results found.
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
high priority

   
invalid

Something is wrong

  
L

5 h

  
low priority

   
M

3 h

  
medium priority

   
needs refinement

   
question

More information is needed

  
S

1 h

  
UX research

   
wontfix

This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
question
S
UX research
wontfix
Milestone
Clear milestone
No items
No milestone
Accounts & Logins
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
moritz
3 participants
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#119
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?