Example of Delegating Access for Journeys and Tasks

Priya Krishnan is a Line Manager who wants to delegate her journeys and tasks access, including notification access to her peer Megan Miller before proceeding on a long leave.

This example assumes that Priya has the delegation-allowed role named Vision_Journeys Manager having the Manage Journey By Manager duty role. After this custom role is delegated to Megan, she will be able to access assigned journeys for Priya's directs.

Delegate the Custom Role to Megan

  1. Go to Me > Roles and Delegations.
  2. In the Role Delegations area, click Add.
  3. Select the Vision_Journeys Manager custom role and the start date.
  4. Select Megan to delegate the custom role and click Save.
Note:
  • Megan can access the journeys and tasks from the Journeys app.
  • Only roles that have the Delegation Allowed check box enabled appear in the list of roles to delegate.
  • Only roles that have been directly assigned to a user can be delegated by the user. A role that is part of another role and not directly assigned to a user can't be delegated, even if the Delegation Allowed check box is enabled for that nested role. For example, the Vision_Journeys Manager role is assigned to the user. The Vision_Document Records Manager role is part of the Vision_Journeys Manager role. In this case, the Vision_Document Records Manager role can't be delegated by the user.
  • The person to whom a role is delegated can't further delegate that role. For example, if Priya has delegated a role to Megan, Megan can't delegate that role.

Delegate the Notifications to Megan

  1. In the Approval Delegations area, click Add.
  2. Enter the rule name Vision Journeys Onboarding Rule and the start date.
  3. Select Journeys for the Category and On Boarding for the Sub category.
  4. Select Megan to delegate the notifications and click Save.
Note:
  • After these steps, Megan will also receive journey or task notifications along with Priya.
  • If the same journey category rule is delegated to more than one person, only the first-person record in the Approval Delegation section is delegated. You can have only one proxy for a specific journey category and subcategory combination.
  • Seeded and user-defined journey subcategories are supported for delegation.
  • These journey subcategories are not supported for delegation:
    • Guided Journey
    • Survey
    • Enterprise Onboarding
  • If an existing journey subcategory is renamed or a new subcategory is created in the Journey Category Security UI, the change is populated in the Approval Delegation section.