Book a Demo

Author Topic: Package level security  (Read 3384 times)

andykennelly

  • EA User
  • **
  • Posts: 54
  • Karma: +0/-0
    • View Profile
Package level security
« on: December 06, 2012, 10:39:32 pm »
Help!! I've got a problem that must have been encountered, and solved, in the big wide world. There's probably something on the forum somewhere, but I can't see for looking. Here goes:-

I have a model on which I have enabled security. I have 2 users (U1 and U2). I have enabled security on the model but I want to implement security at the package level, i.e. I want to let only U1 be able to lock/edit P1 (and, of course, its underlying diagrams and elements) - U2 I want to only be able to view P1 elements. And vice versa for P2, i.e. only U2 can lock/edit P2 while U1 can only view.

Any ideas????

Makulik

  • EA User
  • **
  • Posts: 400
  • Karma: +0/-0
    • View Profile
Re: Package level security
« Reply #1 on: December 07, 2012, 12:05:23 am »
I'm afraid this isn't really possible. See this recent thread about this topic: http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1352796528

HTH
Günther


Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Package level security
« Reply #2 on: December 07, 2012, 12:29:40 am »
Can't you just have U1 lock P1 and U2 lock P2 all the time.
That way the packages are already locked and they can't be locked by the wrong user.

If that doesn't work for you I would try out group locking

And if all else fails you can still use an external version control system, and use the user security in that system to define who gets checkout rights on which package.

Geert

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Package level security
« Reply #3 on: December 07, 2012, 04:13:19 am »
Geert is right. But honestly, why are so many keen to lock modelers from doing something. It's much easier to TALK. Hey, U1, don't modify U2's stuff and vice versa. If they don't listen, it's a good idea to kick them out of the project.

q.