> For the complete documentation index, see [llms.txt](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces.md). # Organizations & Workspaces DevAlly is organized in three nested layers: 1. **Organization**: your company's home on DevAlly. One per company. Owns billing, members, and the unique URL at `app.devally.com/`. 2. **Workspace**: a team or product area inside an organization (e.g. Growth, Marketing, Platform). Owns its own members and is where products live. 3. **Product**: a site or app you audit. Lives inside exactly one workspace. {% hint style="info" %} You create your first organization and workspace the first time you sign in. After that, you invite teammates to the organization and grant them access to the workspaces they need. {% endhint %} ## Where to start


Set up your organization	The 5-minute first-run lesson.	Set up your organization
Invite members	Bring teammates in. Pick roles and workspace access.	Invite members
Roles and permissions	What admins, members, editors, and viewers can do.	Roles and permissions

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.devally.com/EfyQpV4281edZ3h0g8tY/core-concepts/organizations-and-workspaces.md?ask=&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 `automate deployments from our CI pipeline` 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.