Set Model 'Read Only' access

[Mamta]

Hi,

  I am using professional build of 7.5 version. We have multiple model added to a project. I am unable to set model to 'Read access',  so as to use it as a reference model.

Can somebody please help me on this.

Thanks

[Jan Holub]

Hi Mamta,
I'm afraid you can only secure the entire project, no matter how many models are in that project included. All included models get the same access (read-only) as parent project.
The solution may be to separate mentioned models into different projects and allow access to SOME project(s) only for users given in SOME groups.
Is that what you've been asking for?
Let me know, Jan.

[Mamta]

Hi Jan,

  If they are in different projects, I cannot use the reference of one model in another.

 One of the model is a reference model, so even if i save the porject, I don't want any cahnge to this model.

Thanks

[Jan Holub]

Mamta, sorry, I am a little bit confused what you mean by "model" and "project". Could you post a picture of your Project browser with description what part you need to lock for Read-only against any referenced model?
Still I advise you working with sorting users into groups and managing permission of theese groups (package lock).

[Paolo F Cantoni]

Mamta, sorry, I am a little bit confused what you mean by "model" and "project". Could you post a picture of your Project browser with description what part you need to lock for Read-only against any referenced model?
Still I advise you working with sorting users into groups and managing permission of these groups (package lock).

This is caused, in part, by EA's conflicting nomenclature.  Different parts of EA call different parts "project" etc.  (Sometimes the word project means the entire repository, sometimes it means the hierarchy from a specific project root...)
I have taken the view that the entire repository should be called a Repository and each root be called a Subject.  That way you can be clear about what you are talking about.

HTH,
Paolo