Glossary

Quick reference for Aptli-specific terms used throughout the platform and this guide.

Data & Records

Versioned model

Records that go through a draft → diff → commit cycle before changes become permanent. Versioned records support offline editing, undo/redo, conflict detection, and a full version history. In Aptli, map features (points, linestrings, polygons, layers, schematics) and tasks use the versioned model.

Contrast with: Real-time model

Real-time model

Records that save immediately to the server with no staging step. Changes are visible to all users instantly. Work orders, reports, validations, transactions, and sites use the real-time model.

Contrast with: Versioned model

Draft

A set of local changes to versioned records that have not yet been committed to the server. Drafts are stored in the browser and persist across page refreshes without network access. A user can have one active draft per version. Drafts can be uploaded to the server for admin review before going live.

Commit

The act of applying a draft's changes permanently to the live dataset. Commits create a new immutable entry in the version history. Only users with the allowCommits admin right can commit.

Version conflict

Occurs when two users have edited the same feature in separate offline drafts. Aptli detects conflicts on commit by comparing the base version each draft was built from against the current live version. Conflicting commits are flagged for admin review and cannot be applied until resolved — no silent overwrites.

Inventory

Resource

A definition of a material, consumable, equipment type, or labor category. Resources define the unit of measure, optional unit conversions, and whether picking up the resource requires a facilitator. Examples: 500 m fiber cable, concrete anchor bolt, installation crew hour.

Stock Item

The current balance of a specific resource at a specific site. Stock items are updated exclusively by transactions — they are never edited directly. A resource can have stock items at multiple sites simultaneously.

Site

A physical or logical location that holds inventory. Sites include warehouses, storage yards, field depots, individual worker "personal sites," and vehicles. Each user can have a personal site that receives inventory from QR pickup scans.

Transaction

An immutable ledger entry recording every inventory movement. Transactions cannot be edited or deleted — corrections are always made by creating a new adjustment transaction. Transaction types:

Pickup Code

A time-limited, tamper-resistant QR code issued when a work order is assigned. Field workers scan the pickup code at a warehouse to authorize and receive their allocated materials. Pickup codes encode the authorized resource quantities, the assignment they belong to, and an expiry time. Only the assigned worker — or a user with the canFacilitatePickups right — can scan them.

Transfer Code

A tamper-resistant QR code that authorizes a peer-to-peer stock transfer between sites. Unlike pickup codes, transfer codes are not tied to a work order. They can be generated for any site-to-site movement and scanned by the recipient to execute the transfer and record the transaction automatically.

Holding Resource

A temporary "staging" designation used when receiving a shipment containing items that don't yet exist in the resource catalog. Field staff accept the shipment into the holding resource so work isn't blocked; office staff later reclassify the stock to a proper resource once it's defined. Prevents the "I can't receive this because it's not in the system" dead-end.

Facilitated Pickup

A pickup performed on a worker's behalf by warehouse staff (typically because the resource is marked as requiring supervision). Staff scan the worker's assignment QR code while the worker is present; the transaction records both parties and which scan method was used. Requires the canFacilitatePickups right.

Work Fulfillment

Task

A geospatially-located unit of planned work with defined resource requirements. Tasks are versioned — they go through draft → commit like map features. A task can be located at a point (a manhole), a linestring (a road segment), a polygon (a subdivision), or left unlocated for office work. Tasks belong to projects and are fulfilled through work orders.

Work Order

An allocation of one or more tasks to a team, with a due date and optional pickup code for materials. Work orders track status (pending → in-progress → completed) in real time. Also referred to as an assignment.

Assignment

Used interchangeably with Work Order throughout Aptli. Some UI surfaces and admin-right names (assignmentsCreate, assignmentsUpdate) use "assignment"; others (workOrdersCreate) use "work order." They refer to the same underlying concept.

Report

A field worker's record of completed work. Reports capture what was done, GPS location, resources actually consumed, and photos. Reports can be submitted against a formal task or ad-hoc for unplanned maintenance. Submitting a report triggers automatic stock deductions and notifies supervisors.

Validation

A supervisor's QA review of a submitted report. Validations record the outcome (pass / fail / needs-revision / approved) and any findings. A failed or needs-revision validation returns the report to the worker; an approved validation can trigger payment release calculations.

Project

A group of related tasks sharing a due date and team assignment. Projects provide a high-level progress view across all their tasks and reports.

Security & Access

Admin Rights

Permissive grants that control what a user can do. Aptli provides granular admin rights covering every create, read, update, and delete action in the system. Examples: workOrdersCreate, reportsDelete, allowCommits, canFacilitatePickups, canRunAiQueries. Admin rights are additive — a user with no rights can only read their own assignments.

Role Restriction

Restrictive field-level filters that control what data a user cannot see. Role restrictions are enforced server-side: unauthorized data is never sent to the client, not merely hidden in the UI. Example: a restriction on assignedTo = currentUser limits a contractor to seeing only their own work orders. Role restrictions and admin rights operate as two independent layers.

Access Request

A pending account created when someone self-registers through the login page. Access requests wait in Admin → Access Requests until an administrator approves or declines them. On approval the account becomes a regular user; on decline the request is soft-deleted.

Single Active Session

Aptli's session model permits one active sign-in per account across all devices at any time. Signing in on a new device ends the previous session; the evicted device sees a one-time notice and is returned to the login page. Two tabs in the same browser profile share a session and do not evict each other.

Hard Lock

An account state that prevents sign-in via any method. Triggered automatically after repeated failed login attempts (default: 10 consecutive failures) or set manually by an administrator. Cleared only by an admin with the usersUpdate right.

Maintenance Mode

An administrator-toggled mode that blocks non-admin writes and shows a banner to all users. Intended for brief windows when a migration or batch job is running and user writes would interleave with operational work. Administrators retain full access.

Audit Log

An append-only record of meaningful actions across the deployment — logins, record creates and edits, file uploads, status transitions, admin-rights grants. Visible per-record in the embedded timeline on detail pages, and globally at Admin → Audit History (requires auditView). Exportable as CSV for external review (requires auditExport).

Archived (soft-deleted)

A record marked deleted but physically retained. Archived records are hidden from normal lists and queries; users with the viewDeleted right can reveal them and undelete if needed. Aptli rarely hard-deletes — archival preserves audit and operational history.

Map & GIS

Layer

A named collection of map features sharing a geometry type (points, linestrings, or polygons) and a visual style (icon, color, line weight). Layers define what a feature is — for example, a "Telephone Poles" layer or a "Duct Routes" layer. Layers are versioned.

Schematic

A relationship diagram that models connections between map features or abstract objects. Schematics use a graph editor (nodes and directed edges) to represent network topology, cable paths, conduit fill, or any other relationship that is difficult to express on a geographic map alone. Schematics are versioned.

Draw Staging

A temporary editing area where geometry is drawn and refined before being committed to permanent map features. Draw staging allows complex edits — freehand drawing, snapping, multi-feature operations — to be reviewed before they go live.