Design Collaboration - improve package sharing control

[JA4EK]

The package control sharing needs improvement. Imagine the following scenario where you want control (highly-restricted) content.  Say you want to share it with your design team but not in the default ‘shared’ folder. This would allow the design team access to all the information to allow progression of the design, while restricting certain views for security reasons. At the moment all published views are being shared – regardless if you add it to the package or not.

Below a detailed steps explaining the issue

1. Enabled BIM360 (Restricted) set in Publish settings
   1. Views as on screenshot
2. Enabled BIM360 (Highly Restricted) set in Publish settings
   1. contains additional views 04- Fire, 06-Security only

1. Synchronised and published
2. Go to Design Collaboration and create a new package
   1. Select only BIM360 (Restricted) set
      1.       the BIM360 (Highly-Restricted) package is not selected
   2. Save and share package

1. Now I expect to see:
   1. In …\Project Files\01-M3-WES (Elec) – I expect to see all views/sets
   2. In …\Project Files\Shared\01-M3-WES (Elec) – I expect to see only the restricted set
      1.       What I see instead is all views – both sets restricted and highly-restricted – even though I didn’t share the highly-restricted

Now all people with access to shared folders have visibility to the content which was not shared with them. What I am saying is that during the creation of the package the selection of sets does not work.

Although the response from Autodesk hep is:

…’This is working "as designed". Currently, all views are extracted from the model and are available in docs. The selection of the view sets is only respected inside Design Collaboration. Hence publishing only selected views is the only option. Please let me know if you have more questions for me on this. ‘…

[Ramolla.Marco]

Hi @JA4EK  , thank you for sharing the feedback.

1. Can you share more details about the purpose to share a reduced set of information? What are the downstream workflows? What is the difference in the workflow to use specific sets (restricted vs. highly restricted)?
2. Let's assume the selected set is shared with the models only and only the shared set views and sheets are accessible via Docs and Design Collaboration. What are subsequent workflows in Design Collaboration, Docs and Revit? What is the expected behavior in Revit? Do you expect the Revit content is also removed/reduced in the the model?

Thank you in advance.

Best Regards Marco Ramolla // Lead PM Design Collaboration

[JA4EK]

Hi Ramolla

1. The purpose

Suppose I am working on a secure project where I need to partition parts of project views/models and make them available to some but not all people. Unfortunately, the system does not allow me to do so at the moment.

For example, a separate security model has been 'published', and a package created – how do I control who can consume this information? Imagine I have rights to see the security model, so I consume and link with mine – for coordination. If I publish the view, I will break security – unless I can control who sees this view/package

1. I need to be able to create a package say (Restricted) which I am happy to 'share'; thus, people with access to the Shared folder (highlighted green) can access it
2. I need the ability to create another package (Highly Restricted) and share it with individual Design team members only (area highlighted red) – It cant be available in 'shared.'
   1. If you cant make it controllable who can consume it, then at least prevent the information to be shown in 'shared' otherwise, the Shared does not allow for:
      1.        control of work in progress (and that is another side issue) and
      2.       security reasons

1. Docs Module

Different people would have access to different folders in 'Shared' so I can manage security

The Design Team will have access to models (area highlighted red) where I can also manage access, but the control is 'broken' when a package I do not want to be consumed is allowed to be consumed.

In Design Collaboration, once I create a Package, I need control over whom I am sharing it with.

Each package needs independent control. At the moment, people with Collaborate Licence can see all models in Design Collaboration and consume even if they do not have access to all of them in Docs

I hope it makes sense?

[Ramolla.Marco]

Hi @JA4EK thanks for sharing the details. 

That makes sense. In summary, you need more control about with whom to share packages and not shared it with everybody (as today) and you need more granular control what is available for other teams for view and link into Revit purposes. Correct?

Does this requirement affects the same Revit model or do you want to differ in restricted and unrestricted Revit models? 

Let's assume the case where you published a restricted set and shared it with a selection of teams (not all). After an update of the same model and a publish with unrestricted set you shared it the standard way (all teams). How do you want to differ between restricted and unrestricted Revit content (elements, objects, families...) in the same model?  What do you expect in Revit when a team links in a restricted versus an unrestricted version?

Thank you.

Best Regards Marco Ramolla // Lead PM Design Collaboration

[JA4EK]

Hi @Ramolla.Marco 

Yes, I need more granular control of the packages (whom to share with).

As to the Revit environment, the security control is easy – I keep the secure information as a separate model and only share it on a need-to-know basis.

The problem is that when I link my standard model with the secure model and if the standard model includes a view showing the linked secure information (combined view).

When such combined view is then published ACC, the separation is compromised as both standard and secure information is combined with no control over the access.

[Ramolla.Marco]

@JA4EK  Thank you for sharing the details.

Best Regards Marco Ramolla // Lead PM Design Collaboration