Add roles and groups (Local Chapters)

[jandix]

Currently, we do not have defined any roles and groups. I would propose to add these asap because we need them in the next steps to be integrated with projects and organisations. I propose the following steps/tasks:

• Add separate table for user_roles to normalize the schema
• Introduce roles: Workspace Admin, Group Coordinator, Group Member
• Add group table

[jandix]

@KonradUdoHannes @DatenBergwerker could you please add your thoughts and requirements?

[KonradUdoHannes]

I'm thinking of roughly the following.

• Member: Can see and edit projects they are invited to. Use case are project team members helping documenting the respective project.
• Group Coordinator: Can view, create and edit projects for a specific group and can invite Members. Use case are LC core teams managing local projects.
• Chief Coordinator: Can view, create and edit projects irrespective of their group. Can invite Members. Can invite Group Coordinators. Can create Groups. Use case are is the core team that supports projects in potentially any group.
• Tech Admin: Can do everything a Chief Coordinator can do and can additionally bypass normel project lifecycle restrictions to fix issues etc. Use case is tech support and dealing with unexpected issues.

I'm still not sure whether we need a Group Member, i.e. a low permission account associated with a group, in addition to a Member, i.e. a low permission account associated with one or multiple projects. Right now I cannot think of a good use case and it seems to me that working on one group project should not give access to other group projects by default, which in my view favors Member as opposed to Group Member.

[jandix]

@KonradUdoHannes Thank you for the detailed descriptions. We can also start without the Group Member and see later in the meeting with the Project Team if the role is needed at all.