> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/account-management/organizations.md).
# Organization & Members
## Access Organization Settings
Click on ":gear: Settings" in the main menu, then on the "Organization" tab.
Or simply click here: Go to Organization page
## Organization Details
Customize the display name of your organization.
Access your Organization ID, a unique identifier generated automatically.
### Default Processing Zone
Set the processing zone used for all models by default.
Most users will want to set the processing zone here rather than at the model level.
## Actions
### Usage Alerts
You can set an alert to receive an email when your [plan](/account-management/plans.md) has reached a certain percentage of use.
## **Team Members**
Each organization may have several members.
Each user ([account](/account-management/plans.md)) may be a member of several organizations.
The **Team Members** section lists all users who belong to your organization, along with their:
* **Name & Email** – displayed for clarity.
* **Role** – "Owner", "Administrator", or "Member"
* **Status** – shows as *Active* for members with access.
### Add New Team Members
Use the "Invite Member" button to add a new user.
Enter their email address and select their role.
They will receive an email allowing them to create an account and join your organization.
{% hint style="info" icon="money-check-dollar-pen" %}
You can only invite members to your organization if you have the the Pro, Business, or Enterprise [Plans and Credits](/account-management/plans.md).
{% endhint %}
### Remove Team Members
Use the ":trash-can:" button to remove a member from your organization.
You must have the "Administrator" or "Owner" role to remove users.
You must have the "Owner" role to remove users with the "Administrator" role.
### Update a Member's Role
Use the "Edit Role" button to change a member's role.
You must have the "Administrator" or "Owner" role to update users.
You must have the "Owner" role to update users with the"Administrator" role.
#### Member Roles
Each organization is governed by a **role system**.
A user must be explicitly added to an organization to access it, except for the **creator**, who is automatically granted the "Owner" role.
Role Name
Permissions Summary
Member
Add and manage models Run Live Tests Manage API keys
{% hint style="info" %}
Only one "Owner" per organization. This owner is set at creation and cannot be transferred.
{% endhint %}
## Danger Zone
### Delete Organization
You can delete your organization and all its associated data.
{% hint style="danger" %}
Deleting your organization is an **irreversible action**, all data will be lost forever!
{% endhint %}
You must always belong to at least one organization.
Deleting an organization will not delete user accounts, this includes your account and any other users belonging to the organization.
When you have a single organization in which you are the sole owner:
* To start with a "fresh" organization: first create the new organization, then delete the old one.
* To delete all your Mindee data: [delete your account](/account-management/account-settings.md#delete-account) instead, the organization will be automatically deleted.
---
# 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.mindee.com/account-management/organizations.md?ask=&goal=
```
`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.