View users, roles, and privileges for requests

You can view the current role assignments for a Dimensions CM request, and the users who have that request in their inboxes. You can also view a user's privileges for the request.

Note: This functionality is not available for external requests.

PRIVILEGES: View Other User's Privileges for the product that owns the request.

To view the users and roles for a Dimensions CM request:

  1. In the desktop client, select a Dimensions CM request in a request list.

  2. Select Request > Show User Roles and Privileges.

  3. To view which users have this request in their inbox, select the Users with Object in Their Inbox tab. The following details are displayed:

    Field Description
    User Name The user ID for whom the request is pending.
    Role The user's role.


    Displays whether the user has the Primary (P), Secondary (S), or Leader (L) role capability for the request.

    You can set up these responsibilities in the Administration Console. For details, see Set up the process model.

    Full Name The user's name.
    Site The user's location.
    Department The user's department.
    Telephone The user's telephone number.
  4. To view which users are assigned to a particular role for this request, click the Role Assignments tab.

  5. To view which privileges are enabled, click the Privileges tab.

  6. If you have the privilege View other User's Privileges, you can select another user whose privileges you want to view from the User list.

  7. To view deployment privileges that apply to a specific stage or area, select a stage from the Stage list, and optionally, select an area from the Area list.

    Note: The warning icon unresolved_privilege.gif next to a privilege indicates that the user’s permission cannot be resolved. Select a Stage and Area above to determine whether the user has that privilege.

  8. To view the rule that applies to a privilege, select the privilege.

    The details are displayed in the Rule(s) Applied text box.

  9. Click Close.

Back to top

See also: