# Controlling access per project

Roles govern permissions organisation-wide. On top of that, each project lets you control
exactly who is a member and which areas they may access.

## Add a member to a project

1. Open the project and switch to the **Team** tab.
2. Click **Add member** and pick a person from your organisation.
3. Set the access level for each area — tickets, notes, files, chats, documentation, and
   team.

There are three levels: **No access**, **Read only**, and **Read & write**. Removing
someone from the team revokes their access to the project immediately.

## How the permissions combine

Access comes from three layers: account administrators see everything, below them the
role's permissions apply, and project-specific permissions sit on top — they override the
role. Only account administrators and people with write access to the **Team** area can
manage a project's members.

<div class="docs-callout docs-callout--info">
  <div class="docs-callout__title">Access is project-based</div>
  <p>Users only see projects they belong to. That keeps client-facing and internal projects cleanly separated.</p>
</div>

For how to bring people into the organisation in the first place, see
[Inviting team members](https://lalabase.com/docs/en/guides/team/invite-members).