# Structure & Terms ### Workspaces Within our Property Management System (PMS), a **workspace** serves as the central hub where users manage multiple buildings. It's the primary interface for: * Daily operational tasks associated with building management. * Configuring integrations with third-party systems, including but not limited to, DocuSign, Airbnb, and Stripe. For detailed insights into authentication and access control related to workspaces, please refer to the [auth](https://docs.lavanda.app/concepts/auth "mention"). Many customers often manage multiple workspaces. It's also a common practice for customers to dedicate a single building to each workspace. ### Buildings A **building** comprises: * **Rooms or Units**: These are spaces reserved for guests or residents. * **Facilities**: Non-residential areas such as offices, meeting rooms, gyms, pools, etc. Every building is: * Associated with a unique set of data points. Explore the **building queries** for specific details. * Aligned with a single workspace and cannot be linked to multiple workspaces. ### Unit Types A building encompasses various **unit types**, which define the layout or style of rooms. Think of a unit type as a template for rooms, e.g., "2 Bedroom Deluxe with terrace." However, the definition of a unit type is flexible: * It's determined by the customer setting up the inventory. * One might define a unit type for each floor, while another could categorize inventory based on the duration of stay (short-term vs. long-term). ### Units A **unit** represents a specific instance of a unit type. For instance, using the "2 Bedroom Deluxe" type as an example, there might be five units named "2 Bedroom Deluxe - Room 3A", "2 Bedroom Deluxe - Room 3B", and so on. Each unit features: * A unique calendar. * Distinct availability parameters. ### --- # Agent Instructions: 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.lavanda.app/concepts/structure-and-terms.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.