> 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/data-organization-in-inspector-5.md).
# Data Organization in Inspector 5
The system is structured as below:
#### Workspace → Asset → Inspection → Flight
Each level has a specific role in organizing inspection data.
### 1. Workspace (Main Environment)
A workspace is the highest level of organization.
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 datasets (for example: different clients or sites)
* It acts as the main container for all assets
In simple terms:
A workspace is the “project environment” where all inspection work lives.
### 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** 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
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 is the top level of Inspector 5. It usually 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 see the current Organization in the Organization selector (Top left corner) and switch Organizations if they have access to more than one.
**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/data-organization-in-inspector-5.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.