Projects & Routes
Project members
Project member access lets owners restrict which team members can view and manage a project. Use it when projects represent separate apps, customers, or environments.
Owners can access every project. Members can access all projects when no restrictions are configured, or only explicitly assigned projects when project access is restricted.
Configure access
- Open Projects in the dashboard.
- Select the project.
- Open the project members or access section.
- Add the team members who should access the project.
- Save the changes.
When to restrict project access
- Production and staging environments should be managed by different people.
- Customer-specific projects should only be visible to the responsible team.
- Support staff need message visibility for one product but not another.
- Finance or compliance teams need clearer project ownership.
Team API access
Team API project-member endpoints require a Team API token with write:members. Request read:projects as well when an integration needs to list projects before updating membership.
Next steps
- Team members - Manage team roles
- Team API tokens - Create automation credentials
- Projects and routes - Understand the hierarchy
Last modified on