Skip to main content

Merging Project Setting Team and Project Access

Feature requests ProductionCommunity

Wild thought: Doesnt it make more sense to merge both of these pages together? Both of them define user access rights, one group based and one individual based. What are the benefits of not merging both functionalities on one? I've had producers get lost because they were overlooking Project Access because they went straight for Team, and the other way around, because they were looking for just “Assigned Users” functionality but split over two different pages.

Posted by Dieuwer Feldbrugge
1 comment

Log in to comment and vote

Comments1

  • CS Team

    Team

    I quite like the idea even thought I was more thinking about merging Permissions and Access Groups together with their attributes…but could also work for future Teams which arent still fully developed atm.

    The idea behind is very much the same, first picking a project on the left, picking any user in the middle and assign him to any Access group available and finally been able to select the group itself and be able to tweak permissions on a project level (as overrides)…