> For the complete documentation index, see [llms.txt](https://docs.idlayr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idlayr.com/get-started/concepts/workspaces.md). # Workspaces A workspace is the top-level container for everything an organisation has on IDlayr. It groups projects, credentials, billing, and access control. Most customers have one workspace. Organisations with separately-governed business units may have more than one — for example, when a payments arm and an identity arm have different procurement, compliance, or commercial relationships with IDlayr. ## What a workspace contains * One or more **projects**. Each project is a use case (for direct customers) or a customer-and-use-case bundle (for channel partners). See [Projects](/get-started/concepts/projects.md). * **Workspace-level configuration:** account contact, billing entity, data residency choice. * **User access control:** who in your organisation can view or modify workspace resources, managed via the Enterprise Portal. ## Identifiers Workspaces are identified by a `workspace_id` (UUID). You'll see this in the Enterprise Portal and in some API responses. Most API operations are scoped through a project's credentials rather than a `workspace_id`, so you rarely need to reference the workspace ID directly in code. ## Onboarding A workspace is created when you sign your first commercial agreement with IDlayr. Subsequent projects, credentials, and configuration are managed inside the workspace by your IDlayr administrator. --- # 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://docs.idlayr.com/get-started/concepts/workspaces.md?ask=&goal= ``` `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.