User groups can have any number of users, and you can assign users to any number of groups. User groups are the basis for access control and are nonhierarchical, which means the access available to one group does not imply access for any other. You can use user groups with notifications and approvals. For example, a user can belong to the Development group in Project A and the Testing group in Project B.
You can use user groups in the following areas:
Grants user groups permission to perform a particular action on an object. For example, specific users might be in a group named Developer, which has permission to check out and check in items, delete versions, and promote packages.
Notifies specific users or all members of one or more user groups of certain events in the lifecycle. Notifications can be sent manually or automatically. For example, a notify process can alert the QA user group that a package has successfully been promoted from Development to QA.
Specifies that certain users or user groups must give their approval before a package can progress from one state to another through the lifecycle.
CA Harvest SCM has the following predefined user groups with special meaning:
Public—All users implicitly belong to the Public group. If the Public group is added to the access list of a method, everyone can execute that method.
Administrator—Any user belonging to an Administrator group is exempt from security checks. As a security measure, only members of the Administrator group can grant Administrator rights to other users.
Important! Take extreme care to verify that at least one member of the Administrator group always exists.
Note: You can define other groups.
|
Copyright © 2013 CA.
All rights reserved.
|
|