> For the complete documentation index, see [llms.txt](https://knowledge.flyability.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.flyability.com/software/inspector/inspector-5/common-workflows/inspector-5-data-structure.md).
# Inspector 5 Data Structure
The system is structured as follow:
#### Workspace → Organization → Asset → Inspection → Flight
Each level has a specific role in organizing inspection data.
### 1. Workspace (Main Environment)
A workspace is a storage, or folder, where a selection of data lives. It is independent, i.e. it does not need any other folder to load data.
It represents a complete data environment where all inspection projects are stored.
#### Key points:
* Only one workspace can be opened at a time
* It separates different storages Then the user can decide whether he wants to put different clients or sites on different folders.
* A workspace may contain only a subset of the user's data, depending on what he chose to export to that workspace.
* A same asset can be duplicated in multiple workspaces (backup), or can have its inspections split between multiple workspaces (e.g. by date).
* To move or update data from one workspace to another, the workspace import/export function must be used.
“For example, you can export the latest changes of your local workspace on the workspace of a backup disk. Or you can import older inspections of an asset from another workspace on an old disk. During this process, the newer data are overwriting the older ones.”
In simple terms:
We should think of it like a filing cabinet for documents:
* You can use one or several filing cabinets. If a single cabinet becomes full, you add another one.
* You can organize folders however makes sense for your needs: by client, project, location, year, or any other structure.
* You can duplicate important folders and store them in another cabinet for backup.
A workspace is simply that: a place where information is stored and organized.
### 2. Asset (Project Level)
An asset represents a specific object or location being inspected.
Examples:
* a tank
* a bridge
* a pipeline section
#### Key points:
* Each workspace contains multiple assets
* Each asset groups all inspection activity for one object
* It is the main “project unit” inside Inspector 5
In simple terms:
An asset is what you are inspecting.
### 3. Inspection (Work Session)
An inspection is a structured analysis session performed on an asset.
#### Key points:
* An asset can have multiple inspections
* Each inspection represents a separate survey or time period
* Used to compare multiple attempts
* Supports Comparison Over Time to track asset condition changes ([**Premium**](https://www.flyability.com/premium-software-plan-d33abaec-2f09-4e3f-beae-350f7202ba02) Feature)
* Inspection-Based Reporting ([**Premium**](https://www.flyability.com/premium-software-plan-d33abaec-2f09-4e3f-beae-350f7202ba02) Feature)
In simple terms:
An inspection is one structured check of the asset.
### 4. Flight
A flight is a single drone recording session.
#### Key points:
* It starts at takeoff and ends at landing
* It contains raw visual and sensor data
* Multiple flights can belong to one inspection
* Repeat Inspection (Autonomous Repeat Flight) ([**Premium**](https://www.flyability.com/premium-software-plan-d33abaec-2f09-4e3f-beae-350f7202ba02) Feature)
* Export to Drone ([**Premium**](https://www.flyability.com/premium-software-plan-d33abaec-2f09-4e3f-beae-350f7202ba02) Feature)
In simple terms:
A flight is the raw data recorded by the drone.
### 5. Full Structure
All levels combined look like this:
Workspace → Assets → Inspections → Flights
Example:
### 6. How to use it (workflow)
A typical workflow in Inspector 5:
1. Select a workspace (choose dataset environment)
2. Open or create an asset (choose inspection target)
3. Start or open an inspection (analysis session)
4. Review flights (raw drone recordings)
5. Add annotations or measurements if needed
### Key idea to remember
Inspector 5 organizes drone inspection data from general environment (workspace) down to raw recordings (flights), making complex inspection data structured and searchable.
####
### Organizations
It typically represents a company, department, or team and contains all related assets, inspections, and flights. The active Organization determines which data is visible in Inspector 5. Users can view the current Organization in the **Organization Selector** (top-left corner) and switch to another Organization if they have access to multiple Organizations.
An "Organization" acts as the master account for your company's data and team permissions. Here is what you need to know about managing them:
* **Creating an Organization:** You can create a new organization by clicking the drop-down menu next to your current organization’s name in the upper left corner and selecting "+ Create organization". It is highly recommended to name it after your company.
* **Managing Roles:** At the organization level, you can assign internal roles to your team members, such as Viewer, Editor, Manager, or Administrator. These internal roles grant access to all the assets housed within that organization.
* **Inspection Limits:** Each organization is tied to a specific subscription plan that limits how many inspections you can upload (for example, the free plan allows up to two inspections).
* **Deletion:** If you ever choose to delete your organization, please note that your subscription and all associated data will be immediately and permanently erased
\
**Examples:**
* A service provider may have one Organization for each customer (e.g., *Refinery A* and *Power Plant B*).
* A large company may have separate Organizations for different business units or regions (e.g., *Europe Operations* and *North America Operations*).
---
# 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://knowledge.flyability.com/software/inspector/inspector-5/common-workflows/inspector-5-data-structure.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.