Understanding permissions in Pipelines module
Permission sets allow you to control what users can access and perform within each individual pipeline. These permissions define whether users can view the respective pipelines, create pipeline records, update or delete records, perform bulk actions, link pipeline records, and share pipeline views with others.
Accessing Permission Sets
From the left sidebar, go to Setup > Users and Teams > Permission Sets or Setup > Security > Permission Sets.
BoldSales provides two system defined permission sets:
-
Admin: Full access to all modules and system settings, ideal for admins managing security and overall system configuration.
-
Standard User: Full module access with restricted setup permissions, suitable for users who should not modify system settings.
Note for administrators: You cannot modify the permission set of the built in Standard User. To grant additional permissions, you must create a custom permission set or edit an already created custom permission set.
For more information about system defined permission sets or creating or editing a custom permission set, refer to Managing User Permissions (Permission Set).
Configuring Pipelines module permissions
After selecting or creating a permission set, choose the specific pipeline you want to configure. Access to contacts is enabled by default and cannot be disabled, as contact information must remain accessible to all users.
The sections below explain these permissions in detail.
Access
If access is , click the toggle and confirm the action when prompted to allow users access to that pipeline. The access will indicate as
.
Create pipeline records
Check this option to allow users to create pipeline records. If unchecked, users will not have permission to create pipeline records for this pipeline.
Access Levels
Access levels determine which pipeline records a user can view, edit, or delete based on ownership, team membership, and role hierarchy.
Here is the rewritten table with Pipelines instead of Products, keeping the same access logic and making the wording consistent and clear for end users:
| Access level | View (can see) | Edit (can modify) | Delete (can remove) |
|---|---|---|---|
| All records | All pipeline records, regardless of ownership, team, or role | All pipeline records | All pipeline records |
| Team and role records | Pipeline records owned by the user’s team, child roles, and unassigned | Same scope | Same scope |
| Team records | Pipeline records owned by the user’s team and unassigned | Same scope | Same scope |
| Role records | Pipeline records owned by the user, child roles, and unassigned | Same scope | Same scope |
| Own records | Pipeline records owned by the user and unassigned | Same scope | Same scope |
| No records | Not applicable | Cannot edit any pipeline record | Cannot delete any pipeline record |
Important notes
-
Role records do not include the pipeline records owned by users in the same role level (peer roles). For example, a Team Lead cannot view records owned by other Team Leads.
-
Restricting View access can impact what users are able to Edit or Delete, since users can’t act on records they cannot see.
Actions
Actions section define advanced operations users can perform in addition to basic view, edit, and delete permissions.
-
Bulk delete - Provides permission to delete multiple pipeline records at once directly from the listing page.
-
Bulk update - Allows users to update multiple pipeline records simultaneously from the listing page, based on their view and edit access levels. Bulk update actions include Add Tags, Remove Tags, and Change Owner.
-
Link pipeline record - Allow users to link other pipeline records with a pipeline record.
Record Lock Settings
Record Lock Settings control whether users can lock or unlock pipeline records to prevent unwanted changes.
-
Lock any records and unlock any records - Allows users to lock and unlock all pipeline records, regardless of ownership.
-
Lock any records and unlock my locked records - Allows users to lock any pipeline record but only unlock records they have locked.
View Sharing Permission
This section control how users can share views (saved filter) with others in the organization.
-
Share with everyone - Allows users to share views with all users across the organization.
-
Share with specific users / teams - Allows users to share views only with selected users or teams, maintaining controlled collaboration.
