EA Standard Security - Corporate version

[Chris Tatem]

Is there a way to manage the creation of a root node using the permissions and security model in standard mode?

I can manage packages simply by having an "admin" user set a group lock on packages, and adding users to that group giving them access to that package (and all of its children).  I think that requires Manage Elements permission (which the group has) which I also think gives you the permission to create Root Nodes - which I don't want...

I have set up a number of root nodes myself - checked out to admin only so that I can partition the model "appropriately," and want to manage those - managing existing ones is easy, not allowing new ones seems tougher.

Any ideas?

cwt

[Geert Bellekens]

Chris,

I think EA doesn't allow creation of new root nodes if not at least one of the root nodes is writable.
There might be a loophole however when importing an xmi file. Sometimes you get the question to "create as root node", when importing. I think EA allows this without caring for locks on any of the existing root nodes.

Geert

[Chris Tatem]

Thanks Geert... I think I have this working now.  Based on some experimentation and your comments, I locked the root nodes that I had, all of them and it appears one can't create new ones - unless you are of the group that I checked those out to.  Which suits me fine.

I hadn't thought about the import, but will tackle that if/when I get sophisticated enough users and provide guidance on where I'd like their models to go.

Ultimately I don't want to be too autocratic, and we are a small group.  Just trying to help organize!

thanks - cwt