# Authentication

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

### Create an API key

If you don't have an existing API key, you'll need to create one. Follow these steps to find the API keys section and create a new key if necessary:

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

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

1. Open the [Weaviate Cloud console](/go/console?utm_content=cloud) and [select your cluster](status.md#select-a-cluster).
2. Navigate to the `API Keys` section, found in the `Cluster details` panel.
3. If you need a new API key, click the `New key` button.
4. In the `Create API Key` form, provide a descriptive name for your key.
5. Choose the role for this API key. You can either select an existing role like `admin` or `viewer`, or [create a new role](authorization.md) with specific permissions.
6. Click the `Create key` button.
7. **Important:** This is the only time your API key will be displayed. Make sure to copy it or download it and store it in a secure location immediately after creation. You will not be able to retrieve the full key again.
:::

### Rotate an API key

Rotating an API key allows you to generate a new key while invalidating the old one, enhancing security.

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

:::accordion{title="Steps to rotate an API key"}
To rotate an API key, 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 `API Keys` section.
3. Locate the API key you want to rotate and click the `Rotate` button next to it.
4. A confirmation dialog will appear, explaining that the old key will be invalidated. Click `Rotate key` to proceed.
5. **Important:** This is the only time your API key will be displayed. Make sure to copy it or download it and store it in a secure location immediately after creation. You will not be able to retrieve the full key again.
:::

### Edit an API key

Editing an API key allows you to modify its assigned roles. To edit an API key for a cluster:

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

:::accordion{title="Steps to rotate an API key"}
To edit an API key's roles and permissions, 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 `API Keys` section.
3. Locate the API key you want to edit and click the `Edit` button next to it.
4. In the `Edit API key` form, you can modify the key's description/name.
5. You can also update the roles associated with this API key. Choose from the existing roles or [assign different roles](authorization.md).
6. Click the `Save` button to apply your changes.
:::

### Delete an API key

To delete an API key, follow these steps:

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

:::accordion{title="Steps to delete an API key"}
To delete an API key, 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 `API Keys` section.
3. Locate the API key you want to delete and click the `Trash can` button next to it.
4. A confirmation dialog will appear. Enter the necessary text (usually the API key name or a confirmation phrase) to confirm the deletion.
5. Click on the `Delete key` button.
:::

## Further resources

- [Manage authorization in WCD](authorization.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`.
