> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/organizations-and-projects/team-management.md).

# Team Management

Invite Teammates, assign roles by scope, and keep access aligned to delivery needs.

### Overview

Team Management controls who can access Transform. It also controls what actions are permitted. Access is scoped to Account, Organization, and Project.

### Key Concepts

* **Teammate**: person record with access at one or more scopes
* **Scope**: what a Teammate can see (Account, Organization, Project)
* **Role**: what a Teammate can do within a scope
* **Least privilege**: grant only the access required for delivery work

### How It’s Used

Use this section during onboarding and governance changes. Use it for regular access reviews and offboarding.

### Benefits

* Reduced risk from over-scoped access
* Cleaner collaboration through consistent role assignment
* Easier audits through predictable access patterns

### Setup Steps

{% stepper %}
{% step %}

### Define access scope

Start by picking scope, then assign a role.

* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
  {% endstep %}

{% step %}

### Invite or update Teammates

* [Add Teammates](/organizations-and-projects/add-teammates.md)
  {% endstep %}

{% step %}

### Standardize roles and permissions

* [User Roles and Permissions](/organizations-and-projects/user-roles-and-permissions.md)
  {% endstep %}
  {% endstepper %}

### Best Practices

* Limit Account Admin and Owner roles to a small set.
* Prefer Project scope for external collaborators.
* Review access monthly and after major delivery milestones.

### Summary

Team Management is the control plane for access and collaboration. Scope controls visibility. Roles control actions.


---

# 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://help.transform.ai/organizations-and-projects/team-management.md?ask=<question>&goal=<user_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.