user-role-cluster #760
@ -9,6 +9,7 @@ Thus, here is the current (October '24) model and the reasoning behind it:
|
||||
- All user-relevant fields are stored in `User`.
|
||||
- `Role` (and its associative table `UserRole`) map current roles the user has. This is used for e.g. permissions (`Vorstand`, `Admin`, `cox`, ... roles) and fee calculation (`Donau Linz`, `scheckbuch`, `Rennjugend`).
|
||||
- `Family` specifies, well, a family. Currently only used for fee calculation.
|
||||
- `cluster` in `Role` groups roles together. There is a db check to only allow for at most 1 role of the same cluster (e.g. either `cox` or `bootsfuehrer`, but not both).
|
||||
|
||||
## Planned rowing adventures :-)
|
||||
![](./planned.svg)
|
||||
|
@ -29,6 +29,7 @@ classDiagram
|
||||
class Role {
|
||||
+int id
|
||||
+string name
|
||||
+string cluster
|
||||
}
|
||||
|
||||
class UserRole {
|
||||
|
Loading…
Reference in New Issue
Block a user