Permissions overview

What is this?

The permissions overview shows you in a compact matrix view which permission group in your choir has which permission. Instead of opening every group individually and checking, you see the complete picture on one page — with check marks per permission per group.

Useful for:

• Audit of the permission structure — are the rights distributed sensibly?
• Setting up new groups — what do predecessor groups have?
• Explanation to new board members — who can do what?
• Comparison between similar groups
• Documentation for club minutes

How to use the overview

1. Open your choir and go to Permissions (permissions overview).
2. Read the table: rows are permission groups, columns are permissions, checks show assignments.
3. Set filters (optional): only show certain modules (e.g. only cashbook permissions).
4. Compare groups column by column — where are gaps or duplications?
5. Switch to "Permission groups" to change permissions.

What you can spot

• Cross-cutting gaps: no group is allowed to e.g. create donation receipts — dangerous if nobody has access.
• Excessive concentration: only one person has all permissions — single point of failure.
• Consistency: similar groups have similar rights — or not (which should be intentional).
• Security issues: too many groups have delete rights, e.g. for members or events.

Permission modules

The overview is grouped by modules:

• Ensemble — choir base data, settings
• Members — members
• Events — events, attendance
• Sheet music — sheet music
• Messages / Chats — communication
• Files — files
• Cashbook — cashbook
• Website — public website

Per module typically view, edit and delete — some modules have additional special permissions (e.g. "send_notification" for events).

Permission

You need the permission ensemble.edit to see the overview. By default the owner and choir director have this access.

Tips

• Do an audit regularly — for example annually. Permissions grow over time, some become superfluous.
• Print the table for the board meeting — especially new board members understand the rights structure much faster when they have the table in front of them.
• Mind the four-eyes principle for critical actions (e.g. delete cashbook) — at least two people should have these rights, but not everyone.
• Document special rights in the description of the permission group so successors also understand why a group has specific rights.