Iris AI
Iris overview
Understand Iris across chat, Page Builder, table filters, record agents, knowledge base, workflows, and scripts.
Iris overview
Iris overview covers Antly’s AI layer across Ask Iris, Iris Studio topics, Page Builder V4, table AI search, workflow agent nodes, scripts, and knowledge support. Use this page when you are configuring the live product surface, planning a rollout, or checking why users see different data from what an administrator sees.
What this surface is
- Primary purpose: Antly’s AI layer across Ask Iris, Iris Studio topics, Page Builder V4, table AI search, workflow agent nodes, scripts, and knowledge support.
- Where staff start: Users open the full Iris page at
/iris; admins configure topics from/settings/iris-studio/agents. - Where admins configure it: Topic creation and editing live at
/settings/iris-studio/agents/createand/settings/iris-studio/agents/:agentId/view. - Runtime/detail surface: Iris appears in the header, page builder runtime chat, page generation, table filtering, record helpers, workflow Agent nodes, and script assistance.
- Platform connections: Iris uses tenant credits, model/provider selection, topic skills, tool permissions, and per-surface runtime context.
Common workflows
| Workflow | What happens | Where to check |
|---|---|---|
| Decide which | Decide which Iris surface you are enabling: general Ask Iris, page building, workflow automation, knowledge support, or object development | Confirm in the product route above before publishing. |
| Review credit | Review credit balance and tenant settings before opening Iris to a large audience | Confirm in the product route above before publishing. |
| Create or | Create or edit Iris Studio topics with a clear purpose, skills, tools, extra prompt, and exposure surface | Confirm in the product route above before publishing. |
| Use built-in | Use built-in topic capabilities for page-builder charts, dynamic objects, reports, Iris chat, or object development when relevant | Confirm in the product route above before publishing. |
Configure it
- Decide which Iris surface you are enabling: general Ask Iris, page building, workflow automation, knowledge support, or object development.
- Review credit balance and tenant settings before opening Iris to a large audience.
- Create or edit Iris Studio topics with a clear purpose, skills, tools, extra prompt, and exposure surface.
- Use built-in topic capabilities for page-builder charts, dynamic objects, reports, Iris chat, or object development when relevant.
- Test the topic with safe prompts and confirm it refuses actions outside its allowed surface.
- For workflows, configure the Iris Agent node with explicit input data and expected output shape.
- For Page Builder V4, iterate in preview and save only after reviewing generated components and data hooks.
- Monitor usage, failed runs, and user feedback after launch.
Configuration options
| Option | Use when | Notes |
|---|---|---|
| Ask Iris | Users need workspace help or answers | Route: /iris and header Ask Iris. |
| Iris Studio topic | Admins need a reusable AI capability | Route: /settings/iris-studio/agents. |
| Page Builder V4 | Builders need generated pages or refinements | Use Page Builder V4 surfaces. |
| Workflow Agent node | A process needs model reasoning | Configure in Workflow Studio. |
| Table AI search | Users need natural-language filters | Available in supported table surfaces. |
| KB/Support agent | Customers or agents need article-backed answers | Pair with Knowledge Base. |
Operating notes
- Iris should have a narrow task and explicit context; broad prompts produce weaker operational results.
- Do not give a topic tools unless the user story requires it.
- Generated pages and scripts must still be reviewed by a configurator or developer.
- Credit usage depends on prompt size, attachments, selected model, and response length.
- For workflows, log the prompt inputs and output so failed runs can be diagnosed.
- Use Iris for drafting and reasoning, not as the only approval authority for regulated actions.
- If Iris says it cannot update a page, use the Page Agent or builder flow for saved page changes.
- Disable or restrict topics that expose sensitive data to the wrong audience.
- Document the intended owner for each topic so stale prompts can be removed.
- Review Iris answers after source data or object schema changes.
For developers
Use the developer and reference pages when this configuration is read or changed by code, scripts, widgets, embeds, API clients, or webhooks.
- /developer/iris-authoring-contracts
- /developer/runtime-overview
- /developer/scripts-api
- /reference/iris