> For the complete documentation index, see [llms.txt](https://docs.terrakube.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.terrakube.io/2.33.0/user-guide/projects/team-access.md).
# Team Access
Project-level team access lets you grant a team a specific role that applies to all workspaces within the project. This avoids having to configure permissions on each workspace individually.
### Permission Hierarchy
Permissions are additive across a three-tier hierarchy — a grant at any level unlocks that access, and no level can take a permission away that a higher level already granted:
1. **Organization** — organization-level team permissions, see [Team Management](/2.33.0/user-guide/organizations/team-management.md)
2. **Project** — project-level role assigned on this Teams tab
3. **Workspace** — workspace-level role assigned on a workspace's own [Team Access](/2.33.0/user-guide/workspaces/team-access.md) tab
{% hint style="info" %}
Workspaces that are not assigned to any project remain visible to all members of the organization (backward-compatible behavior).
{% endhint %}
### Project Roles
| Role | Manage Project | Manage Workspace | Create Workspace | Plan Job | Approve Job |
| ----- | :------------: | :--------------: | :--------------: | :------: | :---------: |
| Admin | ✅ | ✅ | ✅ | ✅ | ✅ |
| Write | ❌ | ✅ | ✅ | ✅ | ✅ |
| Plan | ❌ | ❌ | ❌ | ✅ | ❌ |
| Read | ❌ | ❌ | ❌ | ❌ | ❌ |
### Adding a Team
Open the project and click the **Teams** tab.
Select a team from the dropdown, choose a role, and click **Add Team**.
The team will appear in the access table and the selected role will be applied to all workspaces in the project.
### Changing a Team's Role
In the Team Access table, click the **Change** button on the row of the team you want to update. Select the new role from the dropdown.
{% hint style="info" %}
Hover over a role tag in the table to see a description of what the role allows.
{% endhint %}
### Removing a Team
Click the **Remove** button on the team's row in the Team Access table to revoke the team's access to the project.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.terrakube.io/2.33.0/user-guide/projects/team-access.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
