Iris AI
Credits & usage
Manage token accounts, credit purchases, model choices, and per-user access to Iris.
Credits & usage
Credits & usage covers credit allocation, token usage, model access, tenant-level AI enablement, and cost governance for Iris features. Use this page when you are setting up the product surface, reviewing a rollout, or troubleshooting why users see a different result from an administrator.
What this surface is
- Primary purpose: credit allocation, token usage, model access, tenant-level AI enablement, and cost governance for Iris features.
- Where users start: Iris credits live at
/settings/account/iris-credits; Ask Iris opens at/iris. - Where administrators configure it: Iris Studio topics are managed at
/settings/iris-studio/agents; company settings can enable or disable Ask Iris. - Runtime/detail surface: Credit usage applies to Ask Iris, Page Builder V4, Iris chat widgets, workflow Agent nodes, table AI search, and script helpers.
- Platform connections: Iris usage connects tenant credits, provider tokens, model choice, topics, workflow runs, page generation, and usage logs.
Where it lives
| Area | Path or surface | Use it for |
|---|---|---|
| User surface | Iris credits live at /settings/account/iris-credits; Ask Iris opens at /iris. | Day-to-day work and review. |
| Configuration | Iris Studio topics are managed at /settings/iris-studio/agents; company settings can enable or disable Ask Iris. | Setup, permissions, routing, labels, and behaviour. |
| Runtime/detail | Credit usage applies to Ask Iris, Page Builder V4, Iris chat widgets, workflow Agent nodes, table AI search, and script helpers. | Testing the live experience users actually see. |
Configure it
- Confirm the audience for this surface and whether they are staff users, portal users, customers, public visitors, or administrators.
- Open the owning product route: Iris credits live at
/settings/account/iris-credits; Ask Iris opens at/iris. - Review the configuration route and permissions before changing live behaviour: Iris Studio topics are managed at
/settings/iris-studio/agents; company settings can enable or disable Ask Iris. - Define the primary records, fields, statuses, owners, and notifications involved in this workflow.
- Configure Credit balance, Ask Iris, and Iris Studio first because they shape the rest of the rollout.
- Add Page Builder V4 and Workflow Agent node only after the core path works with sample data.
- Test the runtime surface as a restricted user, not only as a superadmin: Credit usage applies to Ask Iris, Page Builder V4, Iris chat widgets, workflow Agent nodes, table AI search, and script helpers.
- Check downstream connections after saving: Iris usage connects tenant credits, provider tokens, model choice, topics, workflow runs, page generation, and usage logs.
- Record the owner, rollout date, and support path for the configuration.
- Review the first week of activity and remove any option that users do not understand or need.
Configuration options
| Option | Use when | Notes |
|---|---|---|
| Credit balance | Admins need available AI capacity | Route: /settings/account/iris-credits. |
| Ask Iris | General workspace AI use | Route: /iris. |
| Iris Studio | Reusable topics need control | Route: /settings/iris-studio/agents. |
| Page Builder V4 | Page generation uses AI | Monitor during build sprints. |
| Workflow Agent node | Automations call AI repeatedly | Estimate run volume. |
| Table AI search | Natural-language filtering uses AI | Train users on efficient prompts. |
Operating notes
- Keep labels aligned with the words users see in the product, especially Credit balance and Ask Iris.
- Permissions still matter even when a menu, page, or link is visible.
- If users see empty data, check role filters, enabled apps, ownership rules, and saved filters before editing records.
- If a change affects customers or public visitors, test from a logged-out or customer account as appropriate.
- Use reports or logs to confirm the change produced the expected operational result.
- Capture configuration decisions in rollout notes so support teams know what changed.
- Do not reuse one option for unrelated processes just because it is already configured.
- Review linked notifications, workflows, dashboards, and reports after changing this surface.
- Prefer narrow changes that can be tested with sample data before a tenant-wide rollout.
- When troubleshooting, start at the route users open, then inspect configuration, permissions, and logs in that order.
- Keep retired settings hidden or archived so users do not choose outdated paths.
- Assign an owner for ongoing review; unattended configuration becomes stale quickly.
For developers
Use these pages when the surface is read or changed by code, scripts, embeds, widgets, API clients, webhooks, or realtime listeners.