Announcements

Welcome to ACC Ideas! Please note not all ideas receive a response and top voted ideas will be considered for future development. Click HERE for more information on the feedback process. Thank you for your ideas!

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ACC Shared Parameter Service Permissions Controls

ACC Shared Parameter Service Permissions Controls

Currently, I can see the Shared Parameter Service parameters for any firm that I've ever been invited to work on a project on their hub. In turn, anyone I've invited to a project on my hub, they can see my firm's shared parameters on the Shared Parameter Service. 

 

This should not be allowed, certainly not as a default. There should be a permissions setting that prevent external consultants from viewing company standards unless specifically given permissions to do so.

 

Ideally there could be a Parameter Collection that has a different permission set to allow externally invited consultants to view them (i.e., shared parameters for sheet sorting) but the other shared parameters should always be hidden.

 

This may become a non-issue once everyone bridges projects together, but that is years away, if ever, with how some firms do not embrace that method of linking projects and models.

1 Comment
Ric_Weber
Advisor

I am voting for this idea for the singular issue that admins be able to turn off the sharing of their shared parameters if they want.

 

That said, I have no issues with other firms seeing and/or using my parameters especially firms that we are collaborating with.  Recently, I was able to use this functionality by directing our collaborating engineering firms to open our shared parameters library to insert specific parameters into their project parameters list for use in our sheet index. 

 

I am one to vote for a universal shared parameter collection that everyone could dip into.  Then we would all be using the same shared parameters.  That won't come anytime soon, but if someone needs a new shared parameter that I've already created for instance, let them use it.  There is zero proprietary or secret information embedded in a shared parameter.  To my knowledge, there is no way to use the GUID or any other information to hack anything.  If there is some inherent danger to sharing parameters that I am unaware of, please let me know.  

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea