# 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.

:::info
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

<Stepper>

1. Open **Projects** in the dashboard.
2. Select the project.
3. Open the project members or access section.
4. Add the team members who should access the project.
5. Save the changes.

</Stepper>

## 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](/platform/teams/team-members) - Manage team roles
- [Team API tokens](/platform/teams/api-tokens) - Create automation credentials
- [Projects and routes](/platform/projects-and-routes/introduction) - Understand the hierarchy