[FEATURE]: Define implementation plan for roles and permissions

carla commented

2025-09-04 13:29:12 +02:00

Owner

Copy link

Description

As devs we want to have a clear plan of how to implement the roles concepts and check if anything is missing. The UI will be part of the "Admin settings" part.

Acceptance criteria

We know that the data model fits the requirements regarding the roles
We have a clear overview of the roles and permissions
We know which ressources / domains we need in Ash
We know the default role
We know the relations between the Ash ressources
No actual coding happens in this issue
We have a fitting technical approach that fulfills our theoretical requirements from the planning

## Description As devs we want to have a clear plan of how to implement the roles concepts and check if anything is missing. The UI will be part of the "Admin settings" part. ## Acceptance criteria - [x] We know that the data model fits the requirements regarding the roles - [x] We have a clear overview of the roles and permissions - [ ] We know which ressources / domains we need in Ash - [x] We know the default role - [ ] We know the relations between the Ash ressources - [ ] No actual coding happens in this issue - [ ] We have a fitting technical approach that fulfills our theoretical requirements from the [planning](https://pad.local-it.org/rzPwyKBnQLqn7lc2D3IJEA?both)

carla added this to the We have different roles and permissions milestone 2025-09-04 13:29:12 +02:00

carla added the

medium priority

labels 2025-09-04 13:29:12 +02:00

carla referenced this issue

2025-09-04 15:19:06 +02:00

[FEATURE]: Implement Role and Permission data model #105

carla self-assigned this 2025-11-03 14:21:37 +01:00

carla referenced this issue from a pull request that will close it,

2025-11-03 14:33:18 +01:00

Added Roles and Permissions concept to docs closes #151 #189

carla changed reference from ~~main~~ to feature/151_roles_permissions_docs

2025-11-03 14:33:42 +01:00

carla commented

2025-11-03 14:49:48 +01:00

Author

Owner

Copy link

These two aspects are handled in other issues:

We know which ressources / domains we need in Ash
We know the relations between the Ash ressources

Permission Implementation: #190
Role Implementation: #191

These two aspects are handled in other issues: - [ ] We know which ressources / domains we need in Ash - [ ] We know the relations between the Ash ressources Permission Implementation: https://git.local-it.org/local-it/mitgliederverwaltung/issues/190 Role Implementation: https://git.local-it.org/local-it/mitgliederverwaltung/issues/191

carla referenced this issue

2025-11-03 14:49:55 +01:00

[FEATURE]: Implement Role and Permission data model #105

simon commented

2025-11-06 12:53:31 +01:00

Owner

Copy link

@moritz and I had a talk on the concept again and added some notes to the hededoc (linked in OP now)

Concept on meta level seems fine, technical implementation still unclear. Permission model needs to added on top of ash resources. Afterwards we can think of vertical cuts: handle permissions for members, custom fields etc. and for different permission sets and roles in different issues.

Our conclusion on the next step is now:

Develop different technical concepts with support of cursor and check in with team again

Afterwards we want to start implementing on a fine-granular approach without creating too big "implement everything" issues

@moritz and I had a talk on the concept again and added some notes to the hededoc (linked in OP now) > Concept on meta level seems fine, technical implementation still unclear. Permission model needs to added on top of ash resources. Afterwards we can think of vertical cuts: handle permissions for members, custom fields etc. and for different permission sets and roles in different issues. Our conclusion on the next step is now: - [ ] Develop different technical concepts with support of cursor and check in with team again Afterwards we want to start implementing on a fine-granular approach without creating too big "implement everything" issues

👍 1