Add Pages to Your Portal, Including Several Views of One Table

A table in Airtable often serves more than one job. The same Jobs table is a board when you are moving work along and a calendar when you are planning the week. Your portal can now show it both ways, on two pages, each in the sidebar under its own name.

What it does

A portal is a list of pages, and every page shows one table's records. You can:

• Add a page, on any table, including one that already has a page
• Filter a page to part of its table, so one Jobs table can be an Open jobs page and a Closed jobs page
• Delete a page you no longer need
• Drag the pages into the order you want in the sidebar
• Name each page and give it a short description, instead of showing the Airtable table name
• Give each page a readable address, like /acme/jobs instead of /acme/tblXk2p9QrsT4
• Open the portal on any page, including a table's second one
• Pick any icon for a page's sidebar link, instead of the one for its view type
• Add an embed page: a sidebar page that shows another website inside the portal, either one address for everyone or each user's own address from their profile

Embed pages

Not everything your portal users need lives in Airtable. A booking calendar, a dashboard you built in another tool, a calculator, a report. An embed page puts it in the sidebar beside your tables, under your portal's header, so people use it without leaving the portal.

Point it at one address and everyone sees the same thing. Point it at a field on your user table and each person sees their own: a per-client dashboard, for example, with each client's link stored on their row. The embed pages guide covers both, and which sites allow themselves to be shown this way.

Why it matters

Until now a portal had one page per table. Different roles could see it in different layouts, but anyone who needed both a board and a calendar of the same records had to make do with one.

Two pages of one table fix that without duplicating anything. They read the same Airtable records, so there is nothing to keep in step.

That split is deliberate. No page can quietly show someone records their role cannot see, because every page of a table reads the same access settings. It also means a page filter decides what a page lists, not who can open a record: to keep records from a role, use the record filter on the table's Access tab.

How it works

Press Add page in the portal admin, pick the table, and type a name. The address fills in from the name as you type. Set the page up on its Display, Fields and Labels tabs, then save. The portal pages guide covers each step, choosing which page is a table's main page, and what deleting a page removes. Page addresses covers the addresses you can and cannot use.

Who it is for

Any portal where the same people need one table laid out more than one way: maintenance portals with a job board and a schedule, event scheduling portals with a calendar and a sortable list, and project management portals with a kanban of tasks alongside a table of the same tasks sorted by due date.