Dashboard
Custom pages are purpose-built screens inside your app that go beyond a plain table: dashboards, work consoles, approval queues, intake forms, self-service portals, and reports. A custom page can read data from your tables and views, show KPIs and charts, and let users create, update, or act on records, for example with Approve or Reject buttons.
Examples from published apps:
- Procurement Overview: KPI cards (requested spend, open commitments, overdue deliveries), filters, and a trend chart
- Requests and Approvals: a queue where approvers act on requests
- Sourcing and Bid Comparison, Receiving and Returns, Supplier Reports
Where custom pages appear
Custom pages are listed in the app sidebar, usually under a Pages section, and on the app’s Overview. They open in a tab like any table. Their web address follows this pattern: apps.erp.ai/apps/<app>/custom-page/<page-name>
Create a custom page
Custom pages are built with Proto, the AI agent. There’s no manual New page option: describe the page you want to Proto (who it’s for, what data it shows, which filters and actions it needs). Proto builds it, and you can keep refining it with follow-up instructions. See Proto AI agent.
A good page request covers: 1. Who uses the page (role) and what job they’re doing 2. Which data: tables, views, and fields 3. Filters and search: for example Supplier, Department, and Date range 4. KPIs and charts: for example open orders, overdue items, trend by month 5. Actions: create, edit, approve, or reject, and what should happen next (for example “start the approval workflow”)
Manage a page
Hover over the page in the sidebar and click ⋯:
| Option | What it does |
|---|---|
| Version history | See earlier versions of the page and restore one |
| Rename | Change the page name |
| Set as main page | Make this page the landing page (for everyone, or for specific roles) |
| Move to section | Move the page to another sidebar section |
| Delete | Move the page to Trash |
Landing pages per role
In App Settings → App Permissions → Landing page, you can choose a default page for each role. For example, Managers can land on an approvals console and View Only users on a dashboard. See App access and permissions.
Page permissions
App roles have four page permissions: View page, Edit page, Delete page, and Create new page.
Tips
- Refresh a page with its Refresh button. Reports and dashboards use the analytics copy of your data, which can lag behind the live data by a few minutes. See Data Health.
- Keep pages focused: one page per job, such as “approve requests” or “track deliveries”.