User Guide
Glossary
These are the terms the Alloy Navigator guides use, in alphabetical order. Where one word carries two meanings in the product, the entry gives both.
| Term | Definition |
|---|---|
| Access scope | The narrowing applied on top of a security role, by organization and by workspace. |
| Account | The credential-bearing record joined to a person. A person is not an account. See Accounts. |
| Action | A workflow item a technician invokes. Not to be confused with the action bar that presents it, or with the numeric administrative right of the same name in the permission space. |
| Action bar | The component that presents the workflow actions available on a record. |
| AI provider / AI Action | The configured language-model connection, and the authored unit that uses it. |
| Analytics | A saved query with a chart attached. |
| API application | The registered caller identity an API request carries. See API Applications. |
| Approval | A record that gates a ticket's progress, with its own object class and lifecycle. See Approvals. |
| Audit conflict | A disagreement between audited and stored values, resolved by a shared rule store. |
| Automation Server | The Windows service that runs background jobs. |
| Component | Two different things share this name: a reusable part a workflow item points to (a form, data template, function, icon, notification, macro, parameter, or lookup filter), and an installed package, executable, or installer feature placed on disk. |
| Condition | The evaluated test that decides whether a workflow item or a branch proceeds. |
| Configuration item (CI) / CMDB | A record managed in the configuration management database (CMDB). CIs include computers and hardware, as well as people, locations, organizations, and other classes. See Configuration Items. |
| Dashboard / widget | The frame that carries reports and analytics, and the individual pane inside it. |
| Default Workflow | The default configuration shipped with the product and applied to a database. See Default Workflow Configuration. |
| Directory synchronization | The scheduled import that creates and updates person records from a directory, and the identifier that lets a re-import recognize a person. See Person Matching Reference. |
| Edition / deployment | The product edition, and whether the installation is on-premises or Cloud. The two are decided by different mechanisms. |
| Entitlement / allocation | What a license permits, and the link that assigns it to a device or a person. |
| Field | A column of an object's table or view. |
| Form | Two different things share this name: a workflow component that collects input, and the screen layout a record is presented on. |
| Function | The stored program a workflow item runs. |
| Impersonation | Acting as another user on an API call. |
| Integration | One of three different things: shipped product code, supplied configuration, or published instructions. |
| Job / schedule / job history | What the Automation Server runs, when it runs it, and the record the run leaves behind. |
| Knowledge Base article | A knowledge record with a category tree and its own portal visibility rules. |
| License compliance | The computed comparison of a license's entitlement against its use. See License Compliance. |
| License module | A licensed capability that gates features and, in places, whole object classes. |
| Lookup | An administered reference list whose values are data. |
| Macro / workflow parameter | Text expanded at run time rather than linked; the two differ only in where the value comes from. See Macros Reference. |
| Mail Connector | The component that processes incoming e-mail. Outgoing e-mail is handled separately through the notification queue. |
| Notification | An authored message the product sends by e-mail or push. See Notifications Overview. |
| Object class | A registered kind of business object with its own table, views, forms, and permissions. |
| Operation | One step of a function's program. See Operations Reference. |
| Permission | A right to view or change records, perform an operation, or manage settings. See Permissions Reference. |
| Person | The organization-side record for a human being, which may or may not carry an account. |
| Printable report | The file-based, parameterized report system. |
| Process | Two different things share this name: a grouping label for workflow items, and an operating-system process running a job. |
| Purchase order / product catalog | The procurement records and the catalog of purchasable products behind them. |
| Relationship | A modeled and constrained link between two objects, not a free association. |
| Schema version | The database's own version stamp, which drives the upgrade path and the version checks each component makes. |
| Security role | The grantable bundle of permissions an account holds. |
| Service | A cataloged offering a ticket can be raised against, and the anchor a service level agreement attaches to. See Services and SLAs. The same word also names a Windows service, such as the Automation Server. |
| Service action | A workflow item a background component invokes on the product's behalf, with a declared field mapping. |
| Service catalog | The end-user-facing set of request offerings, distinct from the services that back them. See Service Catalog. |
| Shell | The frame an application presents around its content: sidebar, header, and navigation. |
| Single sign-on (SSO) | Provider-based sign-in and how it is set up. Directory import is a different thing. See Authentication Methods. |
| SLA / SLA clock | The commitment attached to a ticket, and the elapsed-time measurement that tracks it against a work calendar. |
| Task | Depending on context, either a Project Task record or a scheduled task run by the Automation Server. |
| Template | Two different things share this name: a workflow data template, and a notification wrapper template. |
| Ticket | An incident, problem, change request, service request, or work order. See Tickets. |
| Trigger | A workflow item the engine invokes on a schedule or in response to a record being created, changed, or deleted. |
| Upgrade ladder | The configuration changes applied to an existing database during an upgrade. |
| User-defined field (UDF) | A customer-added field on a class that permits them. |
| View (saved) | A saved choice of columns, filters, sorting, and grouping for a Web App list. A view can be personal or shared. See Customize a View. |
| Work calendar | The definition of working hours that an SLA clock counts against. See Work Calendars. |
| Workflow item | Any authored unit of workflow, such as an action, a trigger, or a service action, taken as one group. See Workflow Overview. |
| Workspace | An access-scope partition a security role may be restricted to. |
| Wrapper template / section | The two-layer model that shapes an HTML notification body. |