> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/getting-started/introductory-concepts.md). # Introductory Concepts **myMove** is built around three core entities — **Organizations**, **Seats**, and **Projects**. Understanding how they relate to each other is the foundation for managing access and getting the most out of the platform. *** ### Organization An **Organization** is the entity that represents your company in myMove. All billing is handled at the organization level. When Move creates your organization during onboarding, it also provides a dedicated set of credentials (username and password) — the **organization account**. This account has full admin rights over the organization itself and over all projects created within it. {% hint style="warning" %} The organization account is a full-admin account. Avoid sharing it broadly. Once you have set up at least one **Organization Admin** personal account, daily operations no longer require using the organization account. {% endhint %} *** ### Seat A **Seat** represents a licensed slot for a personal user account within an organization. The base license includes only the organization account — additional personal accounts require purchased seats. A few key rules apply: * A user connected to multiple projects within the **same organization** counts as **one seat**. * A user connected to projects across **two different organizations** counts as one seat in each. * **Viewer** users do not consume a seat. To invite personal accounts to your organization, you must have at least as many available seats as the users you plan to add. *** ### Project A **Project** represents a monitored structure. Projects are always created inside an organization — a project cannot span multiple organizations or exist without one. Users are connected to projects individually, each with a specific role. The same user can hold different roles across projects, even within the same organization. Inside a project, users can add sensors, analyze data, and use the platform's tools. --- # 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://move-solutions.gitbook.io/untitled/getting-started/introductory-concepts.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.