8

Additional Project Visibility / Access Options

Basically right now there are two options for Project visibility.  Either users can see all projects or users only see assigned projects.  We are continually running into scenarios where we need more fine grain control.   Below are just a few situations where we need more granular control over Project access.

 

Scenario 1:
In our studio, Producers should be able to see all projects unless that project is an NDA project.  There currently isn't a way I can find to allow for this.

 

Scenario 2:
We are starting to look at using Shotgun as a global asset library interface.  Essentially we'd like all Assets created on projects to be visible in our Global library if a status has been set on the Asset.  This works fine except that users can't see Assets for projects they aren't assigned too.  We can't just open up the permissions due to the NDA project issue and assigning all users to each project doesn't seem feasible.

 

One potential solution to this problem is to turn off "hide unassigned projects" and add an additional field to the Project entity that allows the Project to be visible at the global level.  In our use case, NDA projects would always be set to "invisible" which would only allow visibility to users who are explicitly assigned to them.

 

Definitely open to other ideas on how to manage this but effectively we are looking for a way to allow projects to dictate or override their visibility to users.

7件のコメント

  • 0
    Avatar
    Tony Barbieri

    The formatting looks horrible, are extra line breaks not supported?

  • 0
    Avatar
    Sunil Kapoor

    Hi Tony,

    This is a great idea, and something we've been hoping to get in Shotgun for a while. I've seen some other requests along these lines such as the one below for Project-specific permissions. Visibility/permissions settings on a per-project level would be ideal and hopefully implemented soon. The request below was made in 2009!

    https://support.shotgunsoftware.com/entries/50031-Project-Specific-Permissions

    Sunil

  • 0
    Avatar
    Ben Hadden

    Thanks for adding this Tony! Sounds like there are two ways you want to manage project visibility:

    1) What we have now, which is a user-based system: All Projects are visible to permission roles who don't have the "Only See Assigned Projects" permission, Some Projects are visible to all other users who have been explicitly given access.

    2) What I think you're suggesting (and we don't yet have), which is a project-based system: All Projects are visible to permission roles who don't have some "Can't See Private Projects" permission, Some Projects are invisible to all other users if the project has been marked "private".

    My only concern with us adding another advanced permission to manage project visibility is that it quadruples the number of ways someone can have access to a project (see below). It's making me wonder if there's a way to pull this off without another permissions. Sounds like the difficulty is in adding the right producers to projects each time you get a new NDA project. I wonder if there's an approach that makes that easier? Let's get some discussion going first before we jump on this one.

    Current permissions model with 1 advanced permissions and one field on the project (yes = can see, no = can't see):

      Assigned to Project Not Assigned to Project
    "Only See Assigned Projects" is enabled yes no
    "Only See Assigned Projects is not enabled yes yes

    Proposed permissions model with 2 advanced permissions and two fields on the project:

     

    Assigned to Project

    Project Marked "Private"

    Assigned to Project

    Project Not Marked "Private"

    Not Assigned to Project

    Project Marked "Private"

    Not Assigned to Project

    Project Not Marked "Private"

    "Only See Assigned Projects" is enabled

    "Can't See Private Projects" is enabled

    no yes no no

    "Only See Assigned Projects" is enabled

    "Can't See Private Projects" is not enabled

    yes yes no no

    "Only See Assigned Projects" is not enabled

    "Can't See Private Projects" is enabled

    no yes no yes

    "Only See Assigned Projects" is not enabled

    "Can't See Private Projects" is not enabled

    yes yes yes yes
  • 0
    Avatar
    Tony Barbieri

    Hey Ben,

     

    I totally agree that keeping this simpler is for the best.  This really does boil down to needing to keep certain types of projects hidden but wanting to be able to open up Shotgun a bit more.  This isn't only for producers, it would be for artists as well (wanting to use Shotgun as a Global Asset Manager).

     

    Project-->Role permissions are a whole other thing I'd love to see :).  This situation it's more about being able to open up visibility in Shotgun while ensuring that certain projects are completely locked down without resorting to using a entirely different Shotgun server for NDA projects.

  • 0
    Avatar
    Tram Le-Jones

    +1

    We also have that need as well.  Some NDA policies are super strict and they hit us hard and fast.

  • 0
    Avatar
    Ben Toogood

    +1, we have a use case similar to the asset library situation - we want to use Shotgun for pipeline support tickets, and have all those tickets registered against a specific project (e.g. PipelineProject). This ticket list should be available to all in the company.

    Right now I have to add every existing user to PipelineProject and make sure everyone that might ever make a new user knows to add them to PipelineProject on creation.

    Being able to mark that project as simply 'visible to all' would be great.

  • 0
    Avatar
    Danny Robashkin

    Can there be a simple Private field added to basically every entity? This could solve all the issues. For instance, if I wanted to create a task that only I can see that isn't part of the pipeline I could make it a private task (only people who are assigned to it or who are in the conversation would follow it and be able to see it. Same could apply to any entity or project. 

サインインしてコメントを残してください。