OpenMake Meister

Managing Build Service Privilege

 

Access privileges for Build Services work very similarly to the access privileges for Project Dependency Directories.  The "top level" access for Build Services is at the Operating System Level.  If a group is assigned "Write" access to the Operating System, the Group will be able to update the Build Services associated with the Operating System.  If a new Build Service is added to the Operating System, the Group will also immediately have the ability to update the new Build Service.  Table GU-3 provides sample scenarios for defining access privileges to Build Services:

 

 

Table GU-3  Build Services Privileges Scenarios

Scenario

Group Access

You want one team to have "Read" and "Write" access to Build Services belonging to a certain Operating System.  They should have "Read" only access to all other Build Services.

Create a Group and give them Read and Write access to the specific Build Services. Do not remove them from the default "User" Group.

You want to define a Group to manage all of the Build Services, including the creation of new Build Services.

Create a Group and give them "Read", "Write", "Delete", and "Add" privileges to all Operating Systems.

You want to limit the Build Services that Developers can see without having to create a special Group.

Update the default "User" Group and de-select the "Read" check box for those Operating System or Build Services that you do not want the Developers to see.