Project Security - Secure at the model, not over all Project

[JulienDFO]

Hi Guys,

since support is very slow in terms of replying (due to time difference).I was wondering if this would be faster.
we've recently start to set-up Sparx and some clients want users / groups security. However, seems like the project security is per Project, not per model within a project.

Am i wrong or do i simply not know how to manage the user access?

[qwerty]

Locking is per model (repository). So once you turn it on, access is only possible via EA's "security". I guess you can have read-only access set up easily via EALite. EA's security is for hindering people to accidentally delete things or to limit access to reference data.

q.

[Eamonn John Casey]

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.

[qwerty]

Hmm. Are you a bot?

q.