1. Implementing and Using Journeys
  2. Considerations for Configuring Journey Security

Considerations for Configuring Journey Security

This topic lists the impact of configuring journeys security on various journey template operations:

  • Impact of selecting Enable data security in the Security tab:
    • If you activate Enable data security in your existing templates, but don't enable the profile option ORA_PER_JOURNEY_SECURITY_ENABLED for security, then no security is applied at the template level and at the assigned journey level.
    • If the ORA_PER_JOURNEY_SECURITY_ENABLED profile option is set to Y but you don’t select Enable data security in the Security tab of the journey template, then no security is applied at the template level and at the assigned journey level.
  • Impact on duplicating a journey:
    • If you duplicate a journey that has security configured, the security configuration is copied as well.
    • If you duplicate a journey template and save it as a personal journey, the journey template and view assigned security details won’t be copied. You can still view the personal journey on the Explore tab and take actions such as Assign to Self, Assign to Others, Edit, Delete, and Force Complete of the personal journey.
  • Impact on importing and exporting journey template configuration:
    • Any security configuration you make in a journey template can’t be exported or imported in the Functional Setup and Manager (FSM). However, you can export or import the template and then reconfigure the security configuration.
    • Security configuration isn’t exported or imported when you Export and Import journey templates on the Checklist Template page. However, you can export or import the template and then reconfigure the security.
  • To enforce the security configuration you make, the journey template should be active and the ORA_PER_JOURNEY_SECURITY_ENABLED profile option should be set to Y. Additionally, you need to configure the roles for which access needs to be given for a specific action. If no roles are added here, then all roles will have access if security is enabled.
  • The security configuration is only applicable to the Journeys app and Allocate Checklists quick action, but not to the Onboarding and Checklist Tasks apps.
  • Template level and assigned journey level security configuration isn’t supported in HCM Data Loader.
  • You can’t sync security configuration updates to assigned journeys using the Update Assigned Journey Attributes Based on Modified Journey Template ESS process.
  • You can control who can manage the journey template by configuring security for guided journeys. However, you can’t control access to UI elements in the guided journey page, such as the Guide Me button.