> 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/workspaces/team-access.md).

# Team Access

A workspace's **Team Access** tab grants teams access scoped to that single workspace, on top of whatever they already have from [organization](/2.33.0/user-guide/organizations/team-management.md) or [project](/2.33.0/user-guide/projects/team-access.md) level permissions. Access is always additive — a role granted here can't take away permissions a team already has at the organization or project level.

{% hint style="info" %}
Managing workspace team access requires the **Manage Workspace** permission on that workspace (from any level of the hierarchy).
{% endhint %}

### Roles

| Role       | Description                                                |
| ---------- | ---------------------------------------------------------- |
| **Admin**  | Full control over this workspace                           |
| **Write**  | Can plan, apply runs, and manage this workspace's settings |
| **Plan**   | Can queue plans but cannot apply changes                   |
| **Read**   | Read-only access to this workspace and its runs            |
| **Custom** | Fine-grained permissions, picked individually              |

### Custom permissions

When **Custom** is selected:

| Permission       | Description                                                  |
| ---------------- | ------------------------------------------------------------ |
| Plan Runs        | Queue plan runs on this workspace                            |
| Apply Runs       | Approve/apply runs on this workspace                         |
| Manage Workspace | Administrate this workspace's settings                       |
| Manage State     | View the terraform/tofu state for this workspace from the UI |

### Adding a team

Open the workspace, go to **Settings > Team Access**, select a team and a role, and click **Add**.

<figure><img src="https://3934308512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCtajpHVKO4bym06TrmbV%2Fuploads%2Fgit-blob-8e5697b8c48cc3a574986b51468b4a8e5aa7eded%2Fworkspace-team-access.png?alt=media" alt=""><figcaption><p>Team Access tab, with one team granted the Write role</p></figcaption></figure>

{% hint style="info" %}
This tab can also be managed via the `terrakube_workspace_access` resource in the [Terrakube Terraform provider](https://registry.terraform.io/providers/AzBuilder/terrakube), or the [Workspace Access](/2.33.0/user-guide/terrakube-cli/commands/workspace-access.md) CLI commands.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.terrakube.io/2.33.0/user-guide/workspaces/team-access.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.