Getting Started
What is Antly
Understand Antly as a configurable ERP workspace for data, work, pages, portals, modules, and AI.
Antly is a Work Operating System and ERP. Every tenant gets a Base workspace you configure (objects, work, automation, pages, Iris, admin), optional Launchpad modules (HCM, Finance, Inventory, …), and public/customer-facing surfaces (portal, forms, pay links, careers, shop).
This support site is organised the same way:
| Area | For | Start here |
|---|---|---|
| Guides | Configurators | Platform core |
| Modules | Configurators | ERP apps |
| Developer | Developers | Scripts, runtime, webhooks |
| API Reference | Developers | JQL contract |
Platform map
| Layer | What it is |
|---|---|
| Tenant / workspace | Isolated organisation with users, roles, domains, branding, enabled apps |
| Base | Objects & records, tasks & tickets, Workflow Studio, Sites/pages, reports, channels, Iris, global settings |
| Modules | Launchpad apps (HCM, ATS, Attendance, Payroll, Finance, Billing, Sales, Procurement, Inventory, Assets, Shop, Documents, Bookings, Projects, Learning, KB, Forum, Omnichannel, …) |
| Customer portal | Signed-in external users: tickets, billing, forum, object views, custom pages |
| Public surfaces | Anonymous forms (/form/<code>), careers, storefront, payment links, webchat |
| Iris | AI across chat, Page Builder, table filter, record agent, KB, workflow agent nodes, script helper |
Core ideas
- Objects are your tenant-defined data models. Records are instances. Pipelines, quick actions, scripts, workflows, and reports hang off objects.
- Work is first-class: tasks, approvals, schedules, tickets, and projects — not bolted-on afterthoughts.
- Automation is visual (Workflow Studio) plus an event/job engine for ops visibility.
- Pages present experiences to staff, portal users, or the public (Page Builder V3 visual or V4 AI+code).
- One API — JQL — for integrations, scripts, and page runtime data.
First path for configurators
- Navigate the product (launchpad, menus, global settings).
- Build your first object (schema → record → quick action → page).
- Add a workflow when the process repeats.
- Enable the modules your organisation actually uses.
- Expose the right pieces via portal or public forms.
First path for developers
- Developer overview — API, scripts, or page code.
- Quickstart: first API call.
- Learn authentication and API keys.
- Use runtime when building Page Builder code.