Glossary
Definitions for the terms used across AVUT's documentation.
- AssesseeSkill Track
The person a skill check is recorded against — the one being assessed by an assessor. An assessee can view their own results and the reports their role allows.
See also: Assessor, Skill check
- AssessorSkill Track
The person carrying out a skill check on an assessee. Assessing requires the `skills-assessor` role. One assessor typically records several checks in a single skill check session.
See also: Assessee, Skill check
- D4H
D4H is an external team- and equipment-management platform. Connecting an organisation's D4H access token unlocks read-only D4H Views and lets I3 PPE templates link to D4H equipment. D4H integration is optional — organisations without a token simply don't see D4H-backed data.
See also: PPE template
- Module
A self-contained area of the app — equipment tracking, skill checks, notes, and so on. Each organisation turns on the modules it needs; only enabled modules appear in its sidebar. The Admin module is the one exception: every organisation always has it.
See also: Organisation
- Organisation
The top-level unit of access in AVUT. Every person, team, and record belongs to one organisation, and the modules an organisation has turned on decide what shows up in its sidebar. A user can belong to more than one organisation and switch between them.
- Person
A record representing someone in the organisation — a member, volunteer, or contact. A person record can exist on its own, or be linked to a user account that can sign in.
- PPE templateI3
Describes a standard set of items — for example, a personal protective equipment (PPE) kit — that I3 issues are built from. A template can have variants for different sizes or configurations, and can be linked to D4H equipment so issued items stay in step with the D4H inventory.
See also: D4H
- RoleAdmin
Decides what a signed-in user can do inside an organisation. `owner` and `admin` can manage the organisation itself; `member` has everyday access; `i3-editor`, `skills-assessor`, and `skill-package-author` grant extra rights scoped to one module each.
See also: Organisation, User, Person
- SkillSkill TrackSkill Package Builder
A single assessable capability defined inside a skill package. Skills are organised into skill groups and are what a skill check actually records an outcome against.
See also: Skill group, Skill package, Skill check
- Skill checkSkill Track
A single record that a person was assessed on a skill, with an outcome and a date. Checks done together are grouped into a skill check session. Assessing requires the `skills-assessor` role.
See also: Skill package, Skill check session, Assessor, Assessee
- Skill check sessionSkill Track
Groups the skill checks done together — for example, one assessor working through a group of people on a training day. Reports roll a session's checks up into a matrix so gaps are visible at a glance.
See also: Skill check, Assessor
- Skill groupSkill TrackSkill Package Builder
A named grouping of related skills within a skill package, used to organise a package's skills and structure how reports roll checks up.
See also: Skill, Skill package
- Skill packageSkill TrackSkill Package Builder
A collection of skill groups and skills that defines what can be assessed. Packages are authored in the Skill Package Builder and published into the Skill Track catalogue, where other organisations can adopt them. Packages aren't versioned — the published package always reflects its current state.
See also: Skill package catalogue, Skill, Skill group, Skill check
- Skill package catalogueSkill Track
The set of skill packages available to an organisation's Skill Track module, drawn from packages published by skill package authors.
See also: Skill package
- Team
A grouping of people within an organisation, referenced by other modules — for example, to scope who a skill session or equipment issue applies to.
See also: Person