> 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/account-and-billing/team-and-account-management.md).

# Team and Account Management

Manage Teammate access, roles, and security controls at Account scope.

### Overview

Team and Account Management covers who has access and what actions are permitted. It also covers Account-level controls that affect every Organization and Project.

### Key Concepts

* **Account scope**: top-level access boundary for all Organizations and Projects
* **Organization scope**: access boundary for one Organization and its Projects
* **Project scope**: access boundary for one Project
* **Role**: permission set within a scope

### How It’s Used

Use these guides during onboarding, offboarding, and governance changes. Use them for access reviews and security posture checks.

### Benefits

* Reduced risk from over-scoped access
* Cleaner collaboration through consistent role assignment
* Clearer auditability through stable access patterns

### Setup Steps

{% stepper %}
{% step %}

### Define access scope and roles

* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
* [User Roles and Permissions](/organizations-and-projects/user-roles-and-permissions.md)
  {% endstep %}

{% step %}

### Invite and manage Teammates

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

{% step %}

### Review security controls

* [Security and Compliance](/account-and-billing/security-and-compliance.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 and Account Management standardizes access patterns at Account scope. Scope controls visibility. Roles control actions.

Related:

* [Add Teammates](/organizations-and-projects/add-teammates.md)
* [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
* [User Roles and Permissions](/organizations-and-projects/user-roles-and-permissions.md)
* [Security & Compliance](/account-and-billing/security-and-compliance.md)


---

# 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/account-and-billing/team-and-account-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.