1
Automation Interface, Add-Ins and Tools / Re: Project Security - Secure at the model, not over all Project
« on: April 10, 2019, 11:50:44 pm »
The entire Repository (Model) i viewable by everyone who has access. To stop other people changing things the package must locked to a user or group. But it will still be visible for all.
In our solution we offer two options:
1. Get your own Repository. This way you can develop stuff without making it public.
2. Groups are created. Assigned to Packages in the same Repository. The Package is Group Locked to that Group. Individual Users are then added to the Group. Everyone can still see the content but only members of that Group get to change it.
One problem with option 2 is that connectors do not obey the rule.
In our solution we offer two options:
1. Get your own Repository. This way you can develop stuff without making it public.
2. Groups are created. Assigned to Packages in the same Repository. The Package is Group Locked to that Group. Individual Users are then added to the Group. Everyone can still see the content but only members of that Group get to change it.
One problem with option 2 is that connectors do not obey the rule.