I know there are a lot of existing requests around different permission levels for project members, and possibly some work underway. On that note, I wondered whether it might be possible to have different permission grouping templates that each project can choose from?
For instance, maybe Project A assigns permanent lines to their trappers and the existing permissions framework works well for them, but Project B instead wants all trappers to see all traps and be able to enter records, with only approved trappers able to make edits to existing records and installations, and partner organisations being able to view data and run all reports but not make edits. (As we all know, the existing workaround of making everyone in a big project managers/admins as soon as they join, simply for them to be able to view traps, is… not so great!)
If there was a toggle system on the project page where projects could select the permissions template that best suited their project, maybe this would be easier than trying to get a single permissions framework that suits everyone?
Here are some links to similar posts that I found, to try and keep the various discussions connected:
Assign Roles: Trap check only on app - Feature Requests - TRAP.NZ Forums
Adjusted features for Organisations - General discussion - TRAP.NZ Forums
What Level of Membership is Needed to Run All Reports and Download Data? - General discussion - TRAP.NZ Forums
Add “Spectator” as a membership option - Feature Requests - TRAP.NZ Forums
If I’ve missed any (especially any feature requests that people may want to vote on), please do add links in the comments!