OpenMake Meister

Managing Dependency Directory Privilege

 

For Project Dependency Directories, the "top level" privilege is at the Project Level.  If a Group is assigned write access to the Project Dependency Directories at the Project Level, the Group will have write access to all Dependency Directories for that Project.  If a new Dependency Directory is added, the Group will automatically have write access to the new Dependency Directory.

 

Alternatively, a Group could be assigned write access to a particular Dependency Directory and could have read access to the other Dependency Directories.  In this situation, if a new Dependency Directory were added, the Administrator would have to update the Group's access for the Project Dependency Directory in order to provide the Group with "Write" access to the new Dependency Directory. Table GU-2 provides some suggestions for assigning Group Privileges for Dependency Directories:

 

 

Table GU-2 Dependency Directory Privileges Scenarios

Scenario

Group Access

You want to limit the number of Projects the end User can view and you don't want the Developers to have update privileges for the Project Dependency Directories.

Create Groups based on the Development Teams.  Assign each Group Read-only access for any Projects they should view when they bring up the Meister Client.  Remove each of the Developers from the default Users Group so that they do not have the "default" privileges. Add the Users to the new Groups based on the Project.

You want to allow certain Developers to have Write access to the Development Dependency Directory of their Project.  You want them to be able to view all of the other Projects and Dependency Directories, but not to have Write access to the other Projects and Dependency Directories.

Create a Group that has Write access to the Development Dependency Directory for the Project. Add the Users who should have write access to the Dependency Directories to the Group.  Do not remove the Users from the default Users Group.

You want certain Developers on a development team to have the ability to create new Dependency Directories or update any existing Dependency Directory.  All of the other developers on the team should have Read Only access to their Project's Dependency Directories. Every User should only be able to view those Projects and Dependency Directories to which he has been given access.

Create two Groups, one a "Development" Group for the Project and the other a "Team Lead" Group for the Project.  For the Development Group, assign Read access at the Project level.  To the Development Group, Add all Users who should have read only access.  Create the Team Lead Group and assign "Read", "Add", "Write", and "Delete" access at the Project level for Dependency Directory Privilege.  Then add the Users who should be part of the "Team Lead" Group.  Remove all Users from the default User Group.  Since you want the Users to have fewer privileges than the default User Group provides, you must remove the Users from the default User Group.