Customize permissions for each pipeline

Customize permissions for each pipeline

Greetings,

In Bigin, each user's access to any given pipeline is controlled by profile permissions that grant either full access or none at all. While this simplifies access management, it doesn't enable admins to fine-tune access to specific pipeline components flexibly.

To make Team Pipelines better-suited to your specific requirements, you can customize permission settings for each pipeline instead of applying them broadly at the module level. This means you have more granular control over the permissions for specific pipelines.

We've added a new section to the pipeline creation tab: Pipeline Permissions.

 
 In this section, you will find six different access levels:
  • Organizer: Organizers can manage the whole team pipeline with full access to actions such as adding users, customizing stages or fields within the pipeline, and configuring workflow automations.
  • Manager: Managers have comprehensive access to all records within the pipeline, including the ability to create, edit, and delete records. However, they do not have permissions to organize or customize the pipeline, nor can they add or remove users in their respective team pipelines.
  • Member: Members can view all records in the pipeline, but can only edit or delete the records they own. If the Enable Role Hierarchy option is turned on for this pipeline, they can also modify/delete records owned by their subordinates.
  • Participant: Participants can only view, edit, or delete the records they own.
  • Viewer: Viewers have view-only access to all records in the pipeline; they can't edit or delete any records in the pipeline.
  • Requester: Requesters are typically users outside a team pipeline who can contribute add records to a pipeline and track their statuses, but cannot edit or delete records they've created. The Requester permission is designed to address a unique use case in organizations. For example, let's say an organization uses Bigin to manage work between multiple teams like sales, support, HR, and so on. In this case, members of each respective team have access to their respective pipelines and not to other pipelines. But let's say a sales rep needs to report an issue his prospect is facing to the support team. In this case, the sales rep can be added as a requester to the support pipeline, where they can create a ticket and track its progress.

Additionally, you can change the permission levels for Profiles and Users.

The permissions levels required for each action are outlined below for each role.


 
To learn more about pipeline permissions, please refer to this help document.

That's all for this enhancement. We sincerely hope you find these improvements useful. Please give them a try and leave your feedback in the comments section below. Watch this space for future announcements.


Thanks and have a good day!