Skip to main content

Data model overview

Purpose​

Explain how InspectAssets organises information so teams understand what they are selecting and why it matters for reporting and insights.

Core concepts​

Tenant​

A tenant is an organisation workspace. Tenants isolate:

  • users and roles
  • sites and assets
  • inspection history, reports, and insights

Users, roles, and permissions​

Users are assigned roles. Roles include permissions that control:

  • which menus appear
  • which pages can be opened
  • which actions can be performed

Sites​

Sites represent operational locations. Inspections are scheduled against sites and reporting frequently groups by site.

Assets​

Assets represent equipment or items inspected and tracked over time. Assets are usually linked to a site.

Templates​

Templates define what an inspection collects. Templates are essential for consistency across inspectors and time periods.

Inspections and visits​

Inspections are scheduled/assigned items of work. Each completed run becomes an inspection record (a “visit”) that forms part of the history.

Reports and insights​

Reports and insights are derived from inspection history. The reliability of reporting depends on consistent site, asset, and template usage.

Why structure matters​

A well-maintained structure reduces:

  • duplicate assets
  • misclassified inspection history
  • noisy trends and inconsistent reporting

Need step-by-step instructions? If you already have access to the app, open the Role Guides in the private documentation area (requires login).