# Multi-factor authentication

Multi-factor authentication (MFA) increases the security of browser logins. MFA is not enabled by default.

## Enable multi-factor authentication

To enable MFA, follow these steps:

- Open the
  [Weaviate Cloud console](/go/console?utm_content=cloud).

- Click on the `Account` dropdown menu in the lower left corner
  of the console (1).

- Select `Account Settings` (2).

- Click on `Enable MFA` button (3
  ).

![Multi-factor authentication page](/assets/docs/cloud/img/weaviate-cloud-enable-mfa.png)

Open the Multi-factor authentication page and find the
`Enable MFA` button.

- Open your authenticator application and scan the QR code (
  4\).

- Enter the one-time code from your application (
  5\).

![Enable MFA](/assets/docs/cloud/img/weaviate-cloud-mfa.png)

Set up Multi-factor authentication.

After you configure MFA, Weaviate Cloud prompts you to supply the one-time authentication code each time you log in.

## Disable MFA

To disable MFA, [contact support](https://support.weaviate.io).

## MFA and applications

If you use a JavaScript/TypeScript client to connect a browser hosted application to Weaviate, do not enable MFA for that client's account.

There is no way to pass the one-time authentication code to the application, so the application cannot connect to Weaviate Cloud.

Use API keys to connect browser based client applications to Weaviate Cloud.

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