This guide walks you through the essential concepts you need to start working with the IoT Cloud. No prior database knowledge required.
The IoT Cloud organizes data in a hierarchy:
Instance (your database)
└── Project (a workspace)
├── Object Structures (table definitions)
│ └── Objects (rows — machines, sensors, sites…)
│ └── Data (measurements, time-series)
└── Data Tables (define data column structure)
Instance — your dedicated database. You log in and see the projects you have access to.
Project — a workspace grouping related structures and data. Think of it as a department or site.
Object Structure (OT) — defines what an object looks like (which columns it has). Example: a "Sensor" structure with columns name, location, type.
Object — an actual sensor, machine, or entity. Created according to its structure. Objects can nest (parent/child) and reference each other.
Data Table (DT) — defines what measurement data looks like. Attached to an object structure. Example: time, temperature, humidity.
Data — the actual measurements belonging to a specific object. Typically time-series rows.
When you log in, the menu shows:
Objects start from "root" and expand into children. Two views:
Click an object to see its detail — children, data, history, and access settings.
If an object has a data table assigned, you'll see its data tab. Features:
Tip: The GUI is for inspection and small fixes. For bulk operations, use the JSON-RPC API or automated services.
Profile → API Keys — create keys for:
Each key can optionally restrict permissions below your full level.
| I need to… | Required permission |
|---|---|
| View data | DATA_ANALYST |
| Insert new data | DATA_SOURCE |
| Edit/delete data | DATA_MANAGER |
| Manage objects | OBJECT_MANAGER |
| Design structures | ARCHITECT |
| Manage users in project | ROLE_MODERATOR |
See Permissions for the full breakdown.