> For the complete documentation index, see [llms.txt](https://docs.flashback.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flashback.tech/flashgate-platform/organization/teams.md).

# Teams

The **Teams** section helps you control who can access your organization, and what each member can do.

## Team management capabilities

In Teams, you can:

* view all organization members,
* invite/add new members,
* remove members,
* update member role and access scope,
* control workspace-level access,
* control private chat eligibility based on permissions.

## Typical role model

Flashgate uses role-based access control. Common role levels include:

* **USER**: basic usage
* **BILLING**: billing/subscription operations
* **WORKSPACES**: workspace and team operations
* **ADMINISTRATOR**: administrative settings and user management
* **OWNER**: full control

## Workspace and private chat access

For production setups, team governance should include:

* explicit workspace assignment,
* least-privilege role configuration,
* periodic review of access to repositories and private chat environments.

## Operational recommendations

* Add members with the minimum role needed.
* Use ADMINISTRATOR/OWNER roles sparingly.
* Remove inactive users quickly.
* Re-check permissions after org restructures.

## API mapping

* `GET /organization/users`
* `POST /organization/users`
* `GET /organization/users/{userId}`
* `PUT /organization/users/{userId}`
* `DELETE /organization/users/{userId}`
* `POST /organization/users/{userId}/activate`

See: [Organization Management API](/support-reference/platform-api-reference/organization.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://docs.flashback.tech/flashgate-platform/organization/teams.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.