Due to the highly regulated nature of my industry - we need to be pretty rigid on standards, access, structures etc.
We’ve broken our root structure into individual projects. Each project adheres to a strict folder structure.
At present there are hundreds. That’s fine. It will grow as we scale and that’s also fine.
My sticking point is on permissions.
I’ve no idea how to structure this at scale.
Role based access is the best bet going forward. But certain roles only need to see the projects of the clients they’re assigned.
Other roles only need certain subfolders in each project. Some roles need very little and some need a lot but only some of the time.
For example in a project build, only certain roles should see. One it goes live, that access is removed and other roles can come in with certain access etc etc until it’s closed and archived.
Multiply this by a few hundred with different clients having different needs and I’m stumped how to do this.
My first instinct is perhaps a group per project? Is there a logical limit to how many Box groups can be created on a tenant? Moreover is there a limit to how many groups a user can be added to?
The way I see it is potentially we could automate a group creation once a project gets created and this could be managed easier during the project life cycle.
Has anyone done something similar?
Moreover…. is there any way to nest groups in Box?? I can’t see a logical way to do it and it would be EXTREMELY useful to be able to put a group PMs into a group for a specific project
