Working on a shared model using security option

[EA2412]

Hello everybody,

I´m working on a shared model with 10 users. As the administrator I would like to manage the security option to this model. At the moment I have added some users with defined password and it works. But now I would like to define permissions to the several users as administrator. I did that at the security option. The problem is that every user can set their own permissions while having a password for working on the shared model. How do I can suppress that? I mean I deselect all permissions for one user he locks on and sets all permissions to himself...

Another problem is locking packages or diagrams.  As the administrator I have locked on to the current modell and I want to make some changes on a defined modell. So I use the option "Lock/Unlock" packages to lock this package. Another user with no permissions uses the security option "Manage Locks" and unlocks all. I think that is not the way it should work like.

Do anybody can help me on these problems?

Thanks a lot

[Luis J. Lobo]

You have to deploy a "security plan" like this:

GROUPS:
ADMIN_PERMISSIONS: group with ALL the permissions checked
USER_PERMISSIONS: group with ALL the permissions checked except those related to "Security - ...", "Manage locks", "Administer Database"...
ANALYSTS: group with no permissions (used only for establish locks)
DEVELOPERS: group with no permissions (used only for establish locks)
TESTERS: group with no permissions (used only for establish locks)

USERS:
Tom --> assigned to groups: ADMIN_PERMISSIONS, ANALYSTS, DEVELOPERS and TESTERS.
Peter --> assigned to groups: USER_PERMISSIONS, ANALYSTS.
Marge --> assigned to groups: USER_PERMISSIONS, DEVELOPERS
Ian --> assigned to groups: USER_PERMISSIONS, TESTERS.

Each user, inherits the functional permissions by pertenence to ADMIN_PERMISSIONS or USER_PERMISSIONS group. Peter, Marge and Ian can't establish lock to packages or assign permissions to himself.

LOCKS:
Tom (the administrator) is the responsable of set the locks to the packages: Logical views, are locked for ANALYSTS group, Design classes packages, are locked for DEVELOPERS group. Test Cases packages are locked for TESTERS group.

Now, Peter only can do WHAT USER_PERMISSIONS say WHERE the locks allows (Peter only can work in Logical views packages).

Marge only can work in Design class packages, with the same permissions than Peter.

Ian only can work in Test Cases packages, with the same permissions than Peter and Marge.

This is only an example of how permissions groups, users and locks can be managed. Other possible ways is to lock a entire project for a group (as ANALYSTS, DEVELOPERS groups... but with PROJECT 1, PROJECT 2 names)

Ufff!!! sorry for my spanglish

[EA2412]

Hello Luis,

thanks a lot for your help. I think the main problem at my model was using single permissions instead of group permissions. No everything works in the correct way

Thanks