> For the complete documentation index, see [llms.txt](https://developers.epiqai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.epiqai.com/working-with-more-than-one-account.md).

# Working with more than one account

If you only have one Epiq AI account, you can skip this — everything just works.

If you belong to several accounts:

* **By default**, Claude uses the account you last had open in the Epiq AI web app.
* To **see your options**, ask *"Which Epiq AI accounts do I have access to?"*
* To **switch**, tell Claude which one (for example, *"Use my Litigation account for this"*) and Claude can pass that account on the following Epiq AI tool calls in the conversation.
* Tool results include the Epiq AI account used. Ask Claude to show the account if you want explicit confirmation.

You will always only see the projects and documents you have permission to see, exactly as in the web app. Claude can't reach another account's data unless you're a member of it.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.epiqai.com/working-with-more-than-one-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.