Modules : Entries

This is not critical to understand to use AirOS, however, it will help to understand the data structure of platform.

Modules

A module is a section within AirOS that meets a certain requirement.
Modules are customisable at an organisational level which means status', field definitions, permissions, cross references and actions may differ from one organisation to another.

A module either provides a specific feature, such as Roster Management, or provides a segregated database for management of entries.


Tables

For segregated databases, a Table provide tools to filter, sort and search for specific entries.
  • Search Field
  • Provides global search over any detail within the entries. Search terms can include Wildcards (*)

  • Show Revision (children)
  • Shows the related children of the entries within the module (such as revisions of master documents)
  • Status
  • Filter by status
  • Draft
  • Released
  • Cancelled
  • Tags
  • Filter by tags


Insights

A dashboard is available for each module, providing quick insight into the number of entries within the module and their status.

Entries

An entry is a record within a module. For instance, a document within the Document Management Module or a task in a Project Module.
Some modules may allow sub entries in a parent:child relationship. For example, a Master Document may have a Revision within the Document Management Module.


flowchart LR
subgraph Module
dmm@{ shape: processes, label: "Document Management Module" }
end
subgraph parent
md1(EASA AD 2025-0001)
md2(ASB EC135-00A-001)
end
subgraph child
md1.1(rev 1)
md1.2(rev 2)
md2.1(rev 1)
end

dmm-->md1-->md1.1
md1-->md1.2
dmm-->md2
md2-->md2.1
There is no limit to the number of child objects some modules - such as projects and tasks - can contain.