Shared folder permissions in BIM 360

[ChrisGamble]

I know this is the Revit Forum, and this is a BIM 360 question. My comments are urgent and the BIM 360 forum is pretty delayed.

In order for a consultants to be able to share packages of their work to their teams sub folder in the shared folder, they need view+upload+download permissions to the shared folder.

By default, they inherit those same permissions to every sub folder in that folder.

It seems they really only should have view+download permissions to the root sub folder and then you can upgrade their permissions for their individual teams sub folder in the shared folder to view+download+upload. That way they can share their work with everyone, and only link in other teams work, and not open and modify it. 

I know they aren't able to create and share packages of other teams work unless they are added to that team (see link), so it seem those inherited permissions to the other sub folders are pointless??

Do I have that correct?

[RDAOU]

@ChrisGamble 

Refer to my reply on the hierarchy and responsibility matrix of your post https://forums.autodesk.com/t5/revit-architecture-forum/folder-permissions-in-bim-360/td-p/9283288

With regards to this question, consultants are team members and can be assigned any privileges as deemed suitable to do what is required/expected from them to do. Hence, there is no specific rule which applies to all. It all depends on the Account Administrator, it is his baby and he should  manage it the way he sees fit.

In collaboration, you should be able to trust others and give more access to team members (delegation is the key to success) otherwise. The less permissions you give, the more you have to do as an Account Admin. If you want my personal opinion... "View/Download/Upload/Edit" is the way to go

                       Unless the flow of data/info is unilateral on your projects, I would say that they are your consultants

                      and one of the main stakeholders, it should be part of their role to review, edit and publish markups. 

[ChrisGamble]

Understood, but my question is more trying to understand permission levels for sharing packages.

When you give teams certain permission to the shared folder, they inherit those permissions for every other team folder in the shared folder.

They cant create and share packages from those other teams except for the ones that they are added to themselves.

So, for example, MEP having "upload" permission in the Shared Architectural folder is pointless it seems.

So I guess my question is, is there any back drops or issues with giving all teams view+download permissions to the root shared folder, and then in the team sub folders in the shared folder, upgrade the permissions for each individual, relative to their own team folder, to view+download+upload?

[RDAOU]

@ChrisGamble 

Ok there are 2 scenarios and which you adopt depends on many factors one of which is trusting that your counter part at the consultants is capable...

Scenario 1:

You are doing all the coordination + Editing and Publishing markups => MEP Consultant would be grantaed:

• View + Download (to all disciplines' folders)
• View + Download + Upload to the MEP folder

Pros: Fail safe scenario 

Cons: More work for you will be the solo champion, do all the review/editing and publishing of markups, manage teams...etc

Scenario 2:

Your consultants are envolved in coordinating their works with other trades ie: they need to Publish Markups => MEP Consultant would be granted:

• View + Download + Upload + Edit to their folders
• Or you assign the Consultants as Team Admins ie: Folder Controllers each of their folder and let/allow them to manage their folder and their team  (that's why they are called Team Admins) <- my preference 

Pros: less work for you In the end, as an account admin you have full access to monitor them, they do the work which you oversee what they are doing...so if they screw up you can always suspend their permissions 

Cons: I don't know lol someone could mess up something in the other trades? that's what you are worried about I guess?