# Core concepts Before you touch an endpoint, it helps to know the **core concepts** that make up Hiboo and that appear throughout the API and Application. ## Fleet Administration Manage the assets you own and the metadata around them. * **Organization** – It is composed of all your machines, users, zones. It is the logical receptacle of all your data in Hiboo. One user belongs to only one organization. * **Workspace** – It belongs to an Organization, it is a group of machines, users and zones that you could map to a Business Unit, a Job type or any sub division that makes sense for your enterprise * **Equipment** – Single machine uniquely identified by an Hiboo ID. * **Custom Field** – User‑defined metadata that you attach to equipment (e.g., Cost Code, Site). * **Document** – Any file linked to equipment such as an inspection report, spec sheet or photo. ## Mixed‑Fleet Data Query harmonized telematics metrics no matter the source. * **Data Source** – the upstream system supplying raw data (e.g., Caterpillar, Komatsu, Samsara). Managed under **Catalog** in the Hiboo App. * **Integrations** - Your Organization + A Data Source + Your credentials = an Integration. Managed under **Integrations** in the Hiboo App * **Data Kind** – a normalized datapoint such as operating hours, fuel %, GPS location or fault code. ## Hiboo Connect (e.g. Data Sharing) Securely grant partners or customers scoped access to your fleet data. * **Connect Share** – a time‑bound way that exposes a chosen subset of fleet data to a third party. * **Scope** – the filters that limit what a share can see (Machine, metrics, date range). Configured when you create or edit a share. --- # 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.hiboo.io/guides/core-concepts.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.