> For the complete documentation index, see [llms.txt](https://docs.canhav.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.canhav.com/accounts/clerk-accounts.md).

# Clerk accounts

**In development.** CanHav accounts use **Clerk**. Studio is wired for Clerk in the product codebase. Do not assume production keys and sign-in are configured for every environment yet.

## What requires an account

* Creating and editing Project and Token design drafts in studio (`/studio`)
* Publishing and unpublishing those drafts
* Linking a project to a token design
* Markdown export and MCP access for design documents, once those ship (see [AI and IDE](/ai-and-ide/export-and-mcp.md))

## What does not require an account

* Reading research on [canhav.com](https://canhav.com)
* Reading published docs on [docs.canhav.com](https://docs.canhav.com)
* Using Token Launch with a **wallet** on testnet (`/launch`): create, explore, and on-chain actions stay wallet-based
* Reading public project and token pages (`/p/...`, `/t/...`)

Wallet connection for Token Launch is separate from Clerk account sign-in.

## What data is stored

| Data                                                  | Purpose                                           |
| ----------------------------------------------------- | ------------------------------------------------- |
| Account identity (via Clerk)                          | Authenticate studio owners (`owner_id` on drafts) |
| Draft project / token design documents                | Autosave and edit                                 |
| Publish snapshots and slugs                           | Public pages (insert-only snapshots)              |
| Optional link rows between project and token design   | Cross-links                                       |
| Optional attach of deployed token address to a design | Connect design to on-chain launch                 |

CanHav does not need your private keys for studio. Do not paste seed phrases into any CanHav form.

Exact retention and deletion controls will be documented when account management is production-ready.

## Cost

Accounts and the studio surfaces described here are **free**. There is no paid tier documented for these features.

## Related

* [Public pages](/public-pages/public-pages.md)
* [AI and IDE](/ai-and-ide/export-and-mcp.md)
* [The two ideation tracks](/getting-started/two-tracks.md)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.canhav.com/accounts/clerk-accounts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.