Pages
Pages are real screens in your app: tables, dashboards, detail views, charts, embedded forms, public-intake QR blocks, or chat. They load without calling the AI on every visit, so everyday browsing feels like normal software. Pages pull data through your tools, let people take actions (create, edit, navigate), and can be limited by role so each audience sees the right screens. Link actions can open a phone, SMS, or email URI and still run a background tool afterward (for example dial a client and log the outreach without opening chat). The same pattern works on phone, email, and URL cells in tables and on profile contact links. Ask the builder AI to wireside_effect when you want click-to-call with automatic logging. If only some roles should log (while others can still see the number), say so: the side effect can be limited by role separately from who can see the page.
If a page data source fails in Preview or the portal, the error message should name the real cause (for example missing role access on a table, or invalid tool arguments). Re-test as that role with Preview as, not only as a builder.
Find them under App Blueprint → Pages. Configured pages also appear in project navigation for end users.