Getting Started
Concepts & glossary
Learn the core words used across Antly: tenants, objects, records, workflows, quick actions, pages, and Iris topics.
Concepts & glossary
Antly uses a small set of platform concepts across objects, modules, automation, portals, and developer APIs. Learning these terms makes the product easier to configure and makes support conversations more precise.
Core terms
| Term | Meaning |
|---|---|
| Tenant | One customer workspace, with its own users, data, settings, apps, domains, and permissions. |
| Workspace | The product environment users sign into. It includes the launchpad, menus, base tools, modules, and settings. |
| Object | A configurable data model created in Antly. Objects have namespaces, form schemas, records, settings, reports, scripts, and workflows. |
| Record | One saved item in an object, such as a customer request, asset, supplier, inspection, or onboarding case. |
| Namespace | The API and permission address for a model or controller, such as objects.Object, objects.Record, or a dynamic object namespace. |
| Pipeline | A set of ordered stages used to track status and movement, commonly on objects, tickets, projects, and candidates. |
| Workflow | A versioned process graph in Workflow Studio. Workflows can be attached to tickets, objects, and other supported entities. |
| Quick action | A record-level action that users run manually, often to update data, invoke a consequence, or start related work. |
| Script | Code attached to an object, workflow node, task, or ticket-enabled model to perform custom logic. |
| Page | A staff, portal, or public surface built with widgets, Page Builder V3, Page Builder V4, or the webpage builder. |
| Topic | An Iris Studio package of a base topic, skills, tools, prompt instructions, and exposure settings. |
How terms connect
Objects and module models are addressed by namespaces. Records belong to objects or module models. Workflows and quick actions operate on those records. Pages and dashboards present them. Roles and permissions decide who can retrieve, create, update, delete, or run actions against them.
When you build a new process, name the object first, then define its records, pipeline, workflow, and pages. When you debug a process, follow the same order: namespace, permissions, record state, workflow state, then UI placement.