control access and modification of model

[JanK]

Hi Gurus,

I found the following statement on http://www.sparxsystems.com/share.html
User security provides the ability to control the access and modification of model portions based on user login. For the most comprehensive sharing needs.

How can I actually configure EA to define access of model portions to users or groups. I'd like to grant access to create and update a package to users/groups. Other users/groups may not even view the same package. Doing this within one EA project in one database repository, is this possible at all?

Best Regards
Jan Krueger

[«Midnight»]

The way EA security used to work was that if a user (or group) had read (or any) access to any part of the model, then that user (or group) had (at minimum) read access to all parts of that model.

AFAIK this has not changed. Can anyone confirm that?

[HowardB]

Hello Jan,

EA's User Security functionality does not allow you to "hide" parts of the model.

You can grant permissions to users or groups for updating elements, updating diagrams and many other specific operations, but there is no permission that can be revoked to prevent reading or viewing any part of the model.

The locking functionality allows users and groups to apply locks to parts of the model that will exclude other users from editing those parts, but again, this will not prevent anyone from reading and viewing any part of the model.

Midnight is correct in saying this functionality has not changed.  At this time, we have no plans to change this in the future.


Some of our users have been able to achieve what you are trying to do, through the use of version control.  Specifically, they set up a Subversion repository where certain folders within the repository were hidden from certain users.  Users built their models by importing packages (or model sub-trees) from the version control repository, so specific users' models could only contain the parts for which they had (Subversion) permission to access.

I hope this helps.


Best regards,
Howard Britten.

[Michael Schmalzbauer]

OK - I understand that there is no ability to hide some portions of the model.
But what about restricting user access on different model elements.
In the white paper "Deployment of EA" there is a hint to manage multiple projects in one model (page 6). Each Project should be a seperate root node.

Text from the white paper:

Additionally, Enterprise Architect’s security can be used to restrict a user’s access to certain areas (for example root nodes) that they are involved in.

How can I do that?