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

# Accounts

An Atomyx account is a personal user identity.

Every person who uses Atomyx has their own account, identified by their email address.

### What an account is for

An account allows a user to:

* sign in to Atomyx Vault
* manage their personal profile
* belong to one or more workspaces
* access products they have permission to use
* work across different organisations or environments with the same identity

### Important distinction

An account is **not** the same thing as a workspace.

An account is personal.

A workspace is the organisational container the account can belong to.

### One account, multiple workspaces

A single Atomyx account can be a member of multiple workspaces.

For example, the same person might:

* belong to a development workspace
* belong to a production workspace
* belong to both their own organisation and a client workspace

Their role can differ in each workspace.

### Practical advice

Treat accounts as individual identities, not shared team logins.

This improves security, traceability, and access control across the platform.

### Related pages

* **Workspaces**
* **Roles and Access**
* **Create an Account**


---

# 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:

```
GET https://docs.atomyx.io/getting-started/shared-concepts/accounts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.