# Authorization

[Weaviate Cloud (WCD)](/go/console?utm_content=cloud) uses [RBAC (Role-Based Access Control)](../authorization-and-authentication/weaviate-configuration-rbac.md) to manage authorization. Below, you can find guides on how to create, edit and delete user roles and manage their permissions.

## Create a role

Custom roles allow you to define specific permissions for different users or applications accessing your Weaviate cluster. You can control access to collections, tenants, and specific operations.

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

:::accordion{title="Steps to create a new role"}
To create a new role, follow these steps:

1. Open the [Weaviate Cloud console](/go/console?utm_content=cloud).
2. [Select your cluster](status.md#select-a-cluster) and navigate to the `Roles` section.
3. Click on the `New role` button.
4. Enter a descriptive name for your role in the `Role name` field.
5. In the sections below, configure the permissions:
   - Select which resources the permission applies to (for example, to which collections the role has access to)
   - Choose the appropriate permissions (create, read, update, etc.)
6. Click the `Create` button to save your new role.
:::

:::callout{intent="info"}
To find out more about RBAC and available permissions, check out the [RBAC documentation](../authorization-and-authentication/weaviate-configuration-rbac.md).
:::

## Edit a role

You can modify the permissions and settings of existing custom roles at any time.

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

:::accordion{title="Steps to edit a role"}
To edit a role, follow these steps:

1. From the roles management page, locate the role you want to edit.
2. Click the `Pencil` button next to the role you want to modify.
3. In the role editing interface, you can:
   - Update collection permissions by checking or unchecking the appropriate boxes for Create, Read, Update, and Delete operations
   - Add or remove additional constraints from the role's scope using the dropdown menus (e.g. which collections the permissions apply to)
4. After making your changes, click the `Update` button to save the modifications.
5. Changes to role permissions take effect immediately for all API keys assigned to that role.
:::

## Delete a role

When you no longer need a custom role, you can delete it. This action will affect all API keys currently assigned to this role.

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

:::accordion{title="Steps to delete a role"}
To delete a role, follow these steps:

1. From the roles management page, locate the role you want to delete.
2. Click the `Trash can` button next to the role you want to remove.
3. In the confirmation dialog, type the exact role name to confirm the deletion. This prevents accidental deletions.
4. Click `Confirm and delete` to permanently remove the role.
:::

Deleting a role is permanent and cannot be undone. This action will:

- Remove the role and all its associated permissions
- Affect any API keys that were assigned to this role
- Potentially break applications that rely on the permissions granted by this role

Make sure to update or reassign any affected API keys before deleting a role.

:::callout{intent="info"}
You cannot delete the built-in admin and viewer roles, as these are system-defined roles required for basic cluster operations.
:::

## Further resources

- [Manage API keys in WCD](authentication.md)
- [RBAC documentation](../authorization-and-authentication/weaviate-configuration-rbac.md)

## 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`.
