# Users and organizations

Accounts in [Weaviate Cloud (WCD)](/go/console?utm_content=cloud) are based on organizations. There is an organization for each user account. Users can belong to more than one organization, and each user has a role that controls what they can see and change.

## User accounts

User accounts are identified by email addresses. Each user account has its own default [organization](#organizations).

- To create a user account, follow [these steps](create-account.md).
- To delete a user account, follow [these steps](create-account.md#delete-user-account).

## Organizations

Organizations group user accounts together. An organization owns its clusters and billing, and each member's access is determined by their [role](#user-roles):

- Cluster management
- User management
- Organization management
- Billing configuration

Be cautious when granting elevated roles (`Owner`, `Admin`) in production. Those users can modify the organization, its clusters, and its billing.

## Manage organizations

### Create a new organization

[Embedded content embed](https://app.guideflow.com/embed/zklx9q4iok)

Weaviate Cloud automatically switches the console view to the new organization.

### Switch organizations

To switch between organizations, select an organization name in the organization dropdown menu in the upper left corner of the Weaviate Cloud console.

### Organization settings

The **Organization settings** page is where _Owners_ and _Admins_ can rename the organization, leave it, or delete it. The walkthrough below covers all three:

[Embedded content embed](https://app.guideflow.com/embed/3r3e7mwsnk)

:::callout{intent="warning"}
You cannot delete an organization that still has clusters. Delete all clusters first.
:::

## Manage organization members

### User roles

Each member of an organization has one role that controls console access and management permissions:

| Role       | Features & resources | User management | Billing | Add Owners | Delete organization |
| ---------- | -------------------- | --------------- | ------- | ---------- | ------------------- |
| **Owner**  | Full access          | Yes             | Yes     | Yes        | Yes                 |
| **Admin**  | Full access          | Yes             | Yes     | No         | No                  |
| **Editor** | Full access          | No              | No      | No         | No                  |
| **Viewer** | Read-only            | No              | No      | No         | No                  |

Only _Owners_ and _Admins_ can add or remove users and change their roles.

### Add a user

A Weaviate Cloud user can be a member of more than one organization. Even if a user doesn't have an account in Weaviate Cloud, you can add that user to your organization, and they can create the account afterward.

To add a user, follow these steps:

[Embedded content embed](https://app.guideflow.com/embed/6kw5gowuzk)

### Remove a user

To remove a user, follow these steps:

1. Open the [Organization settings](#organization-settings) page.
2. Find the user's email address in the `Users and Roles` section.
3. Click the trashcan icon to delete the user.
4. Enter the email of the user and click `Confirm and remove`.

Clusters created by the removed user remain available to the organization.

## Billing

[Billing](billing.md) is configured at the organization level by _Owners_ and _Admins_.

Once a billing account is configured, _Owners_, _Admins_, and _Editors_ can create new clusters or modify existing ones. _Viewers_ have read-only access.

The account gets an invoice for each cluster. Clusters are billed on the 1st day of each month.

## Support

If you use **Weaviate Cloud** (Database cluster(s) or Weaviate product in the cloud) or have a self-hosted support package, open a ticket in the [Support Portal](https://support.weaviate.io) or email [Weaviate support](mailto\:support@weaviate.io) directly. To add a [support plan](https://weaviate.io/support-plans), contact [Weaviate sales](https://weaviate.io/pricing#contact-sales).

Use the **Support Portal** for direct help from the Weaviate team: open and track tickets, and we'll respond in line with your support plan. The **Community Forum** is open to everyone, and a great place to ask questions, get help with your cluster, and connect with other developers. For all the ways to get help, see the [Support overview](../support/overview.md).

::::card-grid
:::card{title="Weaviate Support Portal" href="https://support.weaviate.io" icon="headset"}
Direct help from the Weaviate team for Weaviate Cloud. Open and track tickets in the **Support Portal**.
:::

:::card{title="Weaviate Community Forum" href="https://forum.weaviate.io/c/support" icon="messages-square"}
Ask questions, share ideas, and connect with other developers on our **Community forum**.
:::
::::

## Related pages

- [Agents](./agents-index.md)
- [AI-assisted Weaviate code generation](./ai-assisted-vibe-coding-index.md)
- [APIs](./apis-index.md)
- [Authorization and authentication](./authorization-and-authentication-index.md)
- [Benchmarks](./benchmarks-index.md)
- [Best practices](./best-practices-index.md)
- [Client libraries](./clients-index.md)
- [Client Libraries / SDKs](./client-libraries-index.md)
- [Cloud](./cloud-index.md)
- [Cloud account management](./cloud-account-management-index.md)

# Agent Instructions

This portal answers questions programmatically. To receive a synthesized,
source-cited answer instead of crawling page by page, append the `?ask=`
query parameter to any page URL on this site:

    /guides/quickstart?ask=how+do+I+authenticate

Optional parameters:

- `&goal=<what-you-are-trying-to-do>` steers the answer toward your
  objective (e.g. `&goal=write+a+python+client`).
- `&version=<label>` scopes the answer to a mounted version when the
  portal publishes more than one.

The response is `text/markdown`: the answer followed by a `# Sources` list
of the portal pages it was grounded in. Status codes are the contract:

- `200` — the answer; `402` — the portal owner’s plan or answer credits are
  exhausted (surface this to your operator; do NOT retry); `429` — you are
  rate-limited; back off for the `Retry-After` seconds; `503` — the answer
  lane is temporarily unavailable; fall back to crawling the `.md` pages.

For the full corpus map read `llms.txt` at the site root; for the tool
surface (search + page fetch as MCP tools) see `/mcp`.
