21.6 Mapping Pipelines to Jurisdictions
As an additional layer of security, you can restrict access to pipeline details by jurisdiction, based on your business requirements. Users can only view pipelines and pipeline details which they are not restricted from.
By default, access to pipeline details is controlled based on Pipeline Type
roles assigned to user groups. You can configure an additional layer of access
restriction based on jurisdictions. Pipelines associated with jurisdictions that are not
authorized for the user will be restricted from view in the following features:
- Pipeline Designer
- Jobs
- Threshold Manager
- Importing and Exporting Pipelines
Note:
Importing restricted pipelines is allowed. After importing a restricted pipeline, the pipeline's details will display according to configured restrictions.
Note:
Before you can configure pipeline access, you must create Jurisdictions and then map User Groups to Jurisdictions, with the appropriate Security Mappings as shown in Using Application Security Attributes.To map pipelines to jurisdictions, follow these steps:
Note:
To complete this task, you must have the Pipeline Jurisdiction Mapping Maintainer Role. This role is reserved for Supervisor and Admin users.- In the Navigation Menu
expand Business Processes. - Expand Pipeline Administration, then select Pipeline Jurisdiction Mapping. The Pipeline Jurisdiction Mapping page displays any pipelines which have already been mapped to jurisdictions.
- Click Add a Pipeline
to map an existing pipeline to jurisdictions. - Select a pipeline from the Pipeline Name drop-down list. The Pipeline Type field populates with the type for the selected pipeline.
- Click Add Jurisdiction
. - Select one or more Jurisdictions from the drop-down list. Only Jurisdictions which have been already created and mapped to security attributes will display.
- Click Save . A confirmation message displays.
- You can delete pipeline jurisdiction mappings by clicking Delete. After confirming deletion, click Save to save your changes.