Glossary
Admin right: permission for an action across the application, such as managing users. Shown under the name the application checks, such as usersManage.
Asset: one thing you own, such as a vehicle or a pole, or a count of many of one class, such as 40 mats. Any asset can hold other assets.
Asset class: what an asset is: its units, its stock levels, its lifecycle defaults and how it draws on the map.
Authorization: permission to take up to an amount of stock from one holder, given in answer to a request. People pick up against it.
Basemap: the map underneath your layers, such as streets or satellite imagery.
Charge: one amount a person owes: a bylaw notice, a municipal ticket, a fee or a deposit.
Connection: a link between Aptli and an outside system, in either direction.
Contact: a person or organisation assets can be assigned to, with or without an account.
Demand: the list of requests other areas have asked of yours, behind the Supply · Demand switch.
Draft: a shape drawn on the map that belongs to no layer yet.
Feature: one point, line or area on a layer, with its fields.
Fee schedule: the amounts and terms for one kind of charge.
Form: a set of questions written once and asked wherever it is needed.
Guest link: a private web address that lets someone without an account act on one record.
Help request: a question or problem raised on the record it is about, sent to the roles that can answer it.
Holder: a site or asset that holds other assets.
Included rule: a rule that comes with Aptli. You turn it on or off.
Investigation: a case that gathers the charges it turns up.
Layer: a set of features of one kind, points, lines or areas, with its own fields and style.
Material line: what a work order needs from stock: a class, an amount and when it is needed by.
Overlay: anything the map draws beside your own layers: a tile service, an imported file or an outside map service.
Permit: one application under a permit type, from applied to issued, refused, expired or revoked.
Portal: a public site where people send requests to your organization.
Printout: a page designed for one kind of record, which its records print on.
Publish: an approver puts a version's changes into the live map.
Report: the record of work done on a work order.
Request: one area asking another for something: stock, work, a charge or a permit. Also, a submission sent through a portal.
Restriction: a line in a role that blocks actions on the records it matches.
Role: a set of restrictions and tags, held by people.
Rule: something that acts on its own: when an event happens and conditions hold, it does what it says.
Save: writes the record on screen. On the map, Save sends your edits to your version.
Seat: a licensed staff account. Guest links and portal accounts use none.
Site: a place that holds assets, such as a depot or a yard.
Submit for approval: sends your version to an approver.
Tag: a word attached to records. Tags group records and can limit a role's reach.
Validation: a reviewer's verdict on a report.
Version: a set of map changes kept apart from the live map until an approver publishes it.
Work order: one unit of work sent to named people, with a due date, its activities, the materials it needs and the asset it is on. A planned work order is maintenance not yet scheduled.