Understand the main concepts
| Concept | Meaning |
|---|---|
| Realm | A workspace containing map objects, areas, and related data. |
| Object | An entity represented in Hivekit, such as a vehicle, machine, or worker with location data. |
| Person | A tenant-wide directory record. A person can be linked to an object and can have platform access separately. |
| Area | A spatial boundary or geofence on a map. |
| Scheduling location | A named operational place or context. It can be linked to an area, but does not require one. |
| Schedule | A plan containing tracks, tasks, and events, with a defined shift cadence. |
| Track | A row in a schedule timeline. Activity tracks contain tasks and events; other tracks organise or aggregate them. |
| Activity | A reusable definition of a type of work, including its resource requirements and metrics. |
| Task | A specific piece of scheduled work based on an activity. |
| Resource | An object assigned to perform work, such as a person, vehicle, or piece of equipment. |
| Metric | A value or other information recorded for a task, with expected and actual results. |
| Operational role | A person's work role, such as Operator or Supervisor. It does not grant application permissions. |
How a shift fits together
Define an activity and location, create a schedule and tracks, add tasks, assign resources, carry out work, record results, and review progress. Follow the sample shift exercise or the scheduling overview.
People and operational roles are tenant-wide, while map objects belong to a realm. Application permissions and tenant-administrator rights are separate settings. See People & Roles.