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

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

New issue
Closed
opened 2025-07-17 21:00:28 +02:00 by moritz · 1 comment
moritz commented 2025-07-17 21:00:28 +02:00
Owner
Copy link

Description

The role and permission data model defined in #151 will be implemented in Ash. Each user has a default role. Changing the role will be part of implementing the settings.

Acceptance criteria

  • Ash domain is implemented
  • Ash ressources is implemented
  • relationships are implemented
  • Each user has a default role
  • Tests are implemented to ensure that users can just access parts of the application as designed
## Description The role and permission data model defined in #151 will be implemented in Ash. Each user has a default role. Changing the role will be part of implementing the settings. ## Acceptance criteria - [ ] Ash domain is implemented - [ ] Ash ressources is implemented - [ ] relationships are implemented - [ ] Each user has a default role - [ ] Tests are implemented to ensure that users can just access parts of the application as designed
moritz added this to the We have different roles and permissions milestone 2025-07-17 21:00:28 +02:00
moritz added this to the Sprint 4 - 09.07 - 30.07 project 2025-07-17 21:00:28 +02:00
carla modified the project from Sprint 4 - 09.07 - 30.07 to Sprint 5 - 31.07. - 11.09. 2025-07-31 14:05:31 +02:00
carla changed title from create default role concept to [FEATURE]: Implement role concept 2025-09-04 15:09:52 +02:00
carla changed title from [FEATURE]: Implement role concept to [FEATURE]: Implement Role and Permission data model 2025-09-04 15:10:25 +02:00
carla added the
medium priority
M
 labels 2025-09-04 15:19:18 +02:00
simon modified the project from Sprint 5 - 31.07. - 11.09. to Sprint 6 - 11.09 - 02.10. 2025-09-11 10:12:49 +02:00
carla added the
needs refinement
 label 2025-10-02 12:16:31 +02:00
carla removed this from the Sprint 6 - 11.09 - 02.10. project 2025-10-02 12:16:58 +02:00
carla commented 2025-11-03 14:49:55 +01:00
Owner
Copy link

@moritz I just realised you created that already: I split that issue in two see my comment in: #151 (comment)
Maybe we can close this here?

@moritz I just realised you created that already: I split that issue in two see my comment in: https://git.local-it.org/local-it/mitgliederverwaltung/issues/151#issuecomment-14583 Maybe we can close this here?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
renovate/mix-dependencies
renovate/renovate-renovate-42.x
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
We have different roles and permissions
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 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#105
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?