I would like to make sure that users for each project only have the appropriate view or view & edit permissions to their own project.
Some of the users might be on only one project, but some might need access to more than one project.
I was thinking about creating two roles for each project one for view only, and one for view and edit. Then if a user needs more than one project I would just add the additional project role whether they need view or view and edit, but I don't know if that is the best way that will require the least work from me going forward. Is there a better way?
@L-Dene Zamora - your approach is sensible! A read-only and read/edit roles are good ways to control access to project data.
To make this truly scalable, ensure each project has at least two project admins, and that these admins understand what roles do. Empowering admins to self-service administrate is the way to go.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.