Teams & Permissions
User roles
Each user in a company has a role:
| Owner | The company creator. Can manage all company settings, delete the company, and remove members. Always has full access to all pipelines and stages |
| Admin | A promoted member. Can create and update items, pipelines, stages, and teams, and add members |
| Member | The default role. Can view items, contacts, and tasks within the pipelines and stages they have been granted access to |
You can promote a member to Admin from Settings → Company Settings → Users.
Teams
Group your users into teams for easier permission management. A user can belong to multiple teams.
Go to Settings → Company Settings → Teams to create a team and add members. Each team member has a role within the team:
| Manager | Can manage the team and its members |
| Member | Standard team member |
Pipeline and stage permissions
For granular control, you can assign permissions to teams or individual users at the pipeline or stage level:
| Read | View items in the pipeline or stage |
| Write | Create and edit items |
| Manage | Full control, including managing assignees and tasks within the pipeline or stage |
Owners always have full access to all pipelines and stages and bypass these permissions.
How permissions are resolved
- If a user level permission exists for the pipeline or stage, it takes priority
- Otherwise, team permissions are checked across all teams the user belongs to
- If no permission rules exist for a pipeline or stage, access is unrestricted by default
Example: Pipeline-level access
A company has two pipelines: Sales and Support. The Sales team only has access to the Sales pipeline, and the Support team only has access to the Support pipeline. Neither team can see the other's pipeline.
Example: Stage-level access
Within a Recruitment pipeline, the HR team has access to the "Applied", "Screening", and "Interview" stages, while the Finance team only has access to the "Offer" and "Hired" stages. Items move through the full pipeline, but each team works within their own stages without seeing each other's.
When to use permissions
- Different teams work on different pipelines
- Sensitive stages (e.g., salary negotiation) should be restricted to specific users
- Multiple teams share a pipeline but each team only needs to see certain stages
- Members should only see the pipelines relevant to their role
- You need a combination of user level and team level control on the same pipeline