Pipeline access roles allow you to assign different levels of access permissions (or roles) to different users on each individual pipeline. This means some users can edit boxes whereas other users may only have view access. This is helpful if you'd like only a small subset of your Team to have access to a specific pipeline.

Note: Pipeline permissions are separate from Team permissions. 

To change permission levels on an individual pipeline, open the pipeline view and select the share icon:

Streak has six pipeline user roles built in. These are:

Limited access roles (3 through 6 above) have additional restrictions that should be considered before assigning the role to another user. They:

The Pro and Pro+ plans include the six permission sets above. Our Enterprise plan allows you to create custom permissions. A complete comparison of versions can be found on our pricing page.

Streak supports individually and highly granular permission levels as part of the Enterprise plan level. Individual features can be granted 'View' access and 'edit' access:

Custom permissions are created on a per-pipeline basis. There is no limit to the number of custom permissions you may add to a pipeline.

How do I add someone to a pipeline?

Open the pipeline and click the Share button in the top-right corner. From there you can:

• Share with your entire team at once using the Team Access setting.

• Add specific individuals by searching their name in the search bar.

• Invite someone not yet on your team by typing their email address directly.

Someone joined our team, but I'd like to keep this pipeline private. What should I do?

By default, pipelines are shared with your whole team. To prevent new team members from automatically gaining access, open the pipeline's Share menu and set the Team Access default to No Access. After that, you can grant access to individuals one by one using the role dropdown.

This change only affects new members going forward. Anyone who has already been shared on the pipeline retains their existing access until you change it manually.

What role does a user get when I first share a pipeline with them?

New users are given the Editor role by default when you share a pipeline. This lets them view, edit, create, and modify boxes and columns.

You can change the role when you invite them, or update it afterward from the sharing list using the role dropdown next to their name.

What’s the difference between an Admin and Editor?

Pipeline Admins have all Editor permissions plus three exclusive capabilities:

• Delete entire columns from the pipeline (Editors can only modify columns)

• Delete the entire pipeline

• Promote other users to Admin

The original pipeline creator is automatically an Admin. You can transfer or share Admin status — helpful if the original creator leaves the team.

What’s the difference between Creator and Assignee?

The key difference is whether the user can see all boxes or only their assigned ones.

A Creator can view every box in the pipeline (same as an Editor), but can only edit boxes they've been assigned to. They can also create new boxes. Good for a team member who needs to see the full pipeline but should only act on their own work.

An Assignee can only see and edit boxes they've been assigned to — nothing else in the pipeline is visible to them. Good for someone who should be narrowly focused on their own deals and nothing else.

What’s the difference between Viewer and Observer?

Both are read-only roles, but they differ in scope:

A Viewer has read-only access to every box in the pipeline — useful for stakeholders like finance or leadership who need to see everything but shouldn't change anything.

An Observer has read-only access only to boxes they've been assigned to — useful when someone needs to monitor a specific deal or ticket without seeing the full pipeline.