Lock Root Node

[jdavid]

We have all of our models in one repository with multiple root nodes (one for each of our clients) We would like to give access to our clients via the EA Viewer, but I would like to restrict access to only the root node that pertains to them. I have tried to lock these, but it seems that a user could still browse another clients models. Is there a solution for this?

Thanks.

[Eve]

http://www.sparxsystems.com/enterprise_architect_user_guide/14.0/model_repository/visibility_levels.html

[Paolo F Cantoni]

http://www.sparxsystems.com/enterprise_architect_user_guide/14.0/model_repository/visibility_levels.html

Hi Simon,

I know you've probably touched on this before, but can you elaborate on the meaning of Security Level.   The definition of "Level" in our Ontological model is: A position on a scale of intensity or amount or quality.  A relative position or degree of value in a graded group
This implies that if you can see records at one level you can see the records in the level(s) below.  However, as  I read the explanation in the link, it may be that the 'levels' (Sparx's quotation marks, not mine) are actually independent.  Thus if you can see records in Level X, you can't see records in any other level.

Which is it?

Paolo

[jdavid]

Simon
Great solution...that is if I had access to ProCloud Server capabilities, but Sparx has taken the direction that small customers like myself don't deserve access to this.

[Eve]

jdavid,

It's not that we have decided that you don't deserve access to any particular solutions.

We have assigned a dollar value. It's up to you to determine how important that solution is to you.

You have the option of charging your clients a value that would allow you to provide that function or to use separate repositories for each client. (Perhaps with controlled packages to provide shared information between them)

[Paolo F Cantoni]

[BUMP]

http://www.sparxsystems.com/enterprise_architect_user_guide/14.0/model_repository/visibility_levels.html

Hi Simon,

I know you've probably touched on this before, but can you elaborate on the meaning of Security Level.   The definition of "Level" in our Ontological model is: A position on a scale of intensity or amount or quality.  A relative position or degree of value in a graded group
This implies that if you can see records at one level you can see the records in the level(s) below.  However, as  I read the explanation in the link, it may be that the 'levels' (Sparx's quotation marks, not mine) are actually independent.  Thus if you can see records in Level X, you can't see records in any other level.

Which is it?

Paolo

[Eve]

but can you elaborate on the meaning of Security Level.

Okay, okay...

I think the word level is just a hangover from an earlier stage of implementation which used levels.

My understanding is that there are 19 filtered views of the model and one complete view. Each element will be in either 1 filtered view or all of them.

[Madhav]

We have all of our models in one repository with multiple root nodes (one for each of our clients) We would like to give access to our clients via the EA Viewer, but I would like to restrict access to only the root node that pertains to them. I have tried to lock these, but it seems that a user could still browse another clients models. Is there a solution for this?

Thanks.

To clarify, the requirement is to give access to one of the root nodes to specific users or user groups and they should not be able to even see other root nodes.

In Sparx PCS/WebEA, you can manage model access using "Visibility levels" feature (Read more at http://sparxsystems.com.au/products/procloudserver/).

There is one more solution that lets you share specific parts of a model with your users. You can choose to share only a specific root node or a package or even a diagram inside a root node with your users and those users will only see what is shared with them and nothing else. And all this will be available in a web browser accessible from anywhere. Check out this video to see how it works - https://www.youtube.com/watch?v=ANbeDzkzQHc

[Paolo F Cantoni]

but can you elaborate on the meaning of Security Level.

Okay, okay...

I think the word level is just a hangover from an earlier stage of implementation which used levels.

My understanding is that there are 19 filtered views of the model and one complete view. Each element will be in either 1 filtered view or all of them.

Did you mean that each element will be in either 1 filtered view or the complete view.
Or did you mean that by default an element is in all views but can be restricted to just one?

Still not clear enough for my pedantry. 

Paolo