Feature

Choose What Portal Users See First

Pick what loads when someone opens your portal: a page of navigation cards, their own profile, or a specific table.

The first screen decides whether someone understands your portal. Land a contractor on a navigation page and they have to choose; land them on today's jobs and they are already working.

What it does

Each portal opens on one of three things:

  • A navigation page of cards, one per table the person can reach
  • The user's own profile, so they land on their own details
  • A specific table, so they open straight into the work

It is one setting for the portal rather than one per role, and it takes seconds to change.

Why it matters

A portal with three tables does not need a menu, it needs to open on the important one. A portal with ten does need a menu, and dropping someone into an arbitrary table is disorienting.

The choice also sets the tone. Landing on a profile says "this is your account". Landing on a task list says "here is your work". Same portal, different first impression, and it costs one setting.

Pointing at a table some roles cannot see is safe. A role without view permission on that table gets the navigation page instead of an error, so the portal always opens on something the person can actually use.

How it works

Set it on the portal's configuration, then open the portal as a real user and check what they land on. The landing page guide covers the three options and when each fits, and the MCP connector can change it by request.

Who it is for

Single-purpose portals that should skip the menu: maintenance portals opening on today's jobs, sales rep portals opening on the pipeline, and membership portals opening on the member's own record.

Try it on your own base

Connect Airtable, build a portal, and share it. Seven days free, no card needed.