> 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/atomyx-vault/getting-started/what-atomyx-vault-does.md). # What Atomyx Vault Does ## Overview Atomyx Vault serves as the entry point for all Atomyx products, providing a unified system for managing user accounts, workspaces, products, subscriptions, and access control. Atomyx Vault provides identity, workspace, and subscription management for the three core Atomyx products: Atomyx Manage, Atomyx Submit, and Atomyx Prepare. Atomyx Vault is a separate SaaS solution and is not part of any individual Atomyx product. Instead, it provides the shared infrastructure that all Atomyx products rely on for user authentication and authorization. This document provides an overview of Atomyx Vault’s architecture, its core concepts, and how it relates to the broader Atomyx product ecosystem. Atomyx Vault is organized around a hierarchy of concepts. Understanding these concepts and their relationships is essential for configuring and administering the platform.

Concept	Description	Managed In
Account	A personal user identity on the Atomyx platform. Every person who uses any Atomyx product must have an account.	Profile page
Workspace	An organizational container that groups products, users, and billing. Equivalent to a company or team.	Workspaces page
Product	An instance of an Atomyx product type (e.g. Atomyx Manage) added to a workspace.	Products page (within workspace)
Subscription	A billing plan attached to a product, determining pricing tier and usage limits.	Subscription tab (within product)
User (workspace)	A person invited to a workspace, with a workspace-level role (Owner, Admin, Member, Billing).	Users page (within workspace)
Group	A named collection of workspace users, used for organizing access.	Groups page (within workspace)

## Platform Hierarchy The relationship between Vault’s core concepts follows a clear hierarchy. Understanding this hierarchy is important for planning access control and product configuration. ### Account → Workspaces A single Atomyx account (identified by email address) can be a member of multiple workspaces. This allows one person to participate in different organizations. For example, a consultant could be a member of both their own company’s workspace and a client’s workspace. The user’s role can differ across workspaces - they might be an Owner in one workspace and a Member in another. ### Workspace → Products Each workspace can have one or more products added to it. Products are instances of Atomyx product types (such as Atomyx Manage, Atomyx Prepare, Atomyx Submit, or Atomyx Layout). A workspace can have multiple products, including multiple instances of the same product type. Each product instance has its own name, description, short name (used in URLs), subscription, users, groups, and integrations. ### Workspace → Users Users must be invited to a workspace by a workspace admin. Being a member of a workspace does not automatically grant access to all products within it - product access must be explicitly granted. ### Product → Product Users Within each product, workspace users can be given access with a product-level role. The available roles depend on the product type. For Atomyx Manage, this includes an Admin role. Users without product access will not see the product in their interface. --- # 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/atomyx-vault/getting-started/what-atomyx-vault-does.md?ask= ``` 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.