This documentation supports the 22.1 version of Action Request System.
To view an earlier version, select the version from the Product version menu.

User and group access

Users are assigned to groups according to their need to access information. For example, you might create a group called Employee Services Staff whose members are permitted to view and change only certain fields in an Employee Information form. You might have another group called Employee Services Managers whose members are permitted to view and change all fields in the Employee Information form, including salary information. You can also configure a hierarchical relationship between groups to allow the parent group to inherit the permissions of the child group.

Access control groups are collections of AR System  users. A user gains access to an object, a field, or a request if a group the user is in has access, or a role mapped to such a group has access. Notifications also can use groups. For example, you can designate an entire group to be notified in a filter action. 

AR System  includes a Public group and eight other special groups that are essential for access control within the system. You can define additional groups based on a common profile and assign access accordingly. For example, you might create a Sales group and allow members to view the status of a request but not to change it. A group can also be a general category, such as Browsers. For information about adding groups, see Creating and managing access control groups.

See User and group access overview for descriptions of user and group access and of explicit and implicit groups.

For more information, see:

Was this page helpful? Yes No Submitting... Thank you