Introduction
This guide explains how administrators can manage user access to Pipelines within a workspace. By configuring Pipeline Permissions, you can restrict or grant specific users the ability to view, edit, or administer Pipelines, allowing you to better control who has access to critical workflows.
Use Cases
Here are some common scenarios where managing Pipeline permissions is beneficial:
Restricting Pipelines to specific individuals: Only authorized team members can view or interact with certain Pipelines.
Controlling who can perform specific activities: Granular permissions allow you to define who can make changes, approve processes, or simply observe progress within a Pipeline.
Enabling Pipeline Permissions
By default, all users in a workspace have access to every Pipeline. However, you can enable User-Level Access control to manage permissions more precisely.
Follow these steps to enable Pipeline Permissions:
Navigate to the specific Pipeline you wish to manage.
In the top right corner of the Pipeline page, locate and click the User Access button. This will open the Permissions settings.
Once you enable Permission Management for the Pipeline, all users will lose access by default until you explicitly assign them roles.
Select the users you wish to grant access to from the Permissions page. Assign them a role based on the level of access they need (e.g., Admin, Editor, View Only).
If you are a Global Admin, you will be able to manage access to any Pipeline
If you are a Global Admin, you will be able to manage access to any Pipeline
Pipeline Roles
What are Pipeline Roles?
Pipeline Roles define what a user can do within a specific Pipeline. These roles are separate from the global roles assigned at the workspace or admin level, which control access across all workspaces and Pipelines.
Available Pipeline Roles:
Admin: Users with full control over the Pipeline. They can add and remove users, modify the Pipeline configuration, and perform all actions within the Pipeline. For example, Admins can control access to the Pipeline, configure the Pipeline Stages, Opportunity Custom Fields, and Scoring Templates, etc.
Editor: Users who can modify opportunities within the Pipeline Only.
View Only: Users who can view the Pipeline and monitor its progress but cannot make any changes.
If a user is not assigned any role for a Pipeline, they will not have access to it. You must assign at least one of the above roles for them to interact with the Pipeline.