Document Folders: Granular Permissions

* Original + Attribution:

Horizon House (Connor) is looking to have a folder that is just for Drawing Packages that is only available to Andersen/ASI/OX but no one else.

cpeck@andersen-const.com

What problem are we solving?

Allowing drawings or specs or documents to be shared on mercury to specific roles in the project.

Who are we solving it for?

All projects and users who use the documents tool. Likely more capital projects than SPD.

What should happen?

Under the Projects in the Directory>Roles area (example from the sand castle (https://mercurybuild.com/app/devcustomer/project/sandcastle/directory/roles), I suggest we add a layer to our existing permissions UI by removing Documents from the General tab and instead have Documents as it's own tab. Then under the Documents tab have the Current Set and Public folders there by default. It would look and work just like the Templates tab. Then instead of Add Tool Override like in the Templates tab, have a button called "Add Folder Override". That button brings up a model window with a list of folders under either Public or Current Set for that project. Again matching functionality of the Templates tab (template tab example from sand castle (https://mercurybuild.com/app/devcustomer/project/sandcastle/editRole/cokln9e4infk1luykpu73ce8) that is looking to that project for folders and sub-folders to choose to add overrides of Admin, Create, Edit, View, Recycle.

The repeat all of that at the customer level so that standard roles will come with permissions for the Documents.

Here's a sketch of what that description could look like:

How will we know it’s done?

Open up a test project, and create a role that can view all folders except one or two by editing that role to remove "view" from a specific folder.

Article(s) to Publish

notes / constraints:

Assumed this will fit into cycle 7.