Model Access

[Amy_N]

Our model now has a large number of users from across various areas of the business. I have had a request to restrict who can view certain diagrams. I know you can easily 'lock' packages so only certain users can edit them. However can you actually 'hide' diagrams and package contents?

I fully understand that if objects used in the 'hidden' packages are used elsewhere then users could still analyse links etc. I also understand that this could cause problems of duplicate objects etc.

[PeterHeintz]

From my knowledge this is not possible.
What you could do, is using a version control tool like subversion and restrict your content within the version control system.

[qwerty]

I would rather talk to those people who want that restriction and find out the reason. For a model there is first hand no reason for restrictions as this will simply disable a collaborative work. If there are confidentiality reasons then you need to split the model into reasonable chunks.

q.

[Glassboy]

Hi there.  My approach to activities like major business process re-engineering is to replicate the repository and let only the people working on the project have access.  This may seem extreme but when process reengineering may result in redundancies it is very problematic letting anyone know of ideas being explored.  Once decision have been made you can update the main repository and drop the "what if" repository completely.

[Helmut Ortmann]

Hi,

I don' think that's easily possible. You have a repository with all information in it and no intrinsic means to hide something (except diagramlinks as far as I know).

As PeterHeintz remarked you may use Version Control.

Be aware:
- You may have to do something around Version Control to get it running (try it first)
- Private repository with Version Control (the rights are in Version Control) may work
- Version Control and EA is no such easy thing you just have to install and run without caring about
  (see threads in this forum)

Helmut

[Amy_N]

Thanks for the replies everyone. Sorry I should have explained: our team have a company wide model and this is to provide to (sometimes competing) vendors.

As I thought there doesn't appear to be a way to do this. I think we will probably go with a master model and then have cut down versions (without the sensitive content) going out to the vendors and then hopefully 'seamlessly' integrate it back into he master.....

[RoyC]

In that scenario, you are correct - very briefly, export and import the cut-down 'public' models as xmi files to and from the vendor's versions of the project. You can compare baselines of the model in your project with the models in the vendors' projects to see what they have changed, and roll in the changes you want to add to your model.