Teams and pipeline ownership

Set up your team

1. Open the Teams workspace as an authorized organization admin.
2. Invite or add team members through the current product flow.
3. Assign an appropriate role and the pipelines they need.
4. Enable only the stage, lead and task permissions needed for their job.
5. Test a team member's view to ensure they can see their own leads but not unauthorized organization records.

Understand ownership

Lead routing, connected sender identity and pipeline permissions interact. An employee's access to a pipeline does not automatically connect a new WhatsApp number. Similarly, a device-synchronized call can match an existing lead that the employee may not otherwise be permitted to edit.

Common access problems

• Agent cannot open a lead: pipeline is not assigned.
• Bulk move blocked: permission may be required on both source and target pipelines.
• New call-created lead fails: employee may lack an active assigned destination pipeline.
• Admin-only integration hidden: the user's role is not authorized to manage external provider credentials.

Best practices

Review permissions when employees move teams, revoke inactive users promptly and avoid sharing one account login between team members.

Permissions · CRM routing.