Align
Sign inStart free
Products
UnderwriteUnderwritingPayments
Sell and serveCRMTexting & callsInterfaces
CommunicateMailAutomations
BuildSitesApps
All products
PricingSign inStart free
Part of the CRMRoles enforced on the data pathDrawn for the job, not filtered down

Each role sees its own page,
over the same rows.

A collector sees the route. A funder sees the queue. An intake clerk sees the form. Each is one page over the same rows, and none of them can see or change what the role was not given.

Set it up for my teamOpen the CRM

What a role was not given is not on the page, and not in the API behind it.

Fig. 1 — Three roles, three pages, the same rows underneath: the merchant's upload, the funder's queue, the collector's route. None of them can see what its role was not given.
What is in it

Not a permission on a grid. A page.

A page per roleThe collector's route, the funder's queue, the intake clerk's form. Each is drawn for the job, not filtered down from the grid.
Only the fields the role may touchWhat a role was not given is not on the page and not in the API behind it. Enforced on the data path, not the screen.
Built for the hand that uses itA route for a phone in a van; a queue for two monitors on a desk. The same rows, laid out for where the work happens.
Roles from the workspaceDiscord-shaped: per-project roles, permissions and overwrites. Give a person a role and the page is theirs.
Actions, not just viewsA button on the page runs the automation, moves the stage, sends the text. Interfaces do, as well as show.
In your brandYour name, your mark, your domain. A customer-facing interface never says our name.
How it fits

The grid is for the people who run it. Interfaces are for everyone else.

An operations lead lives in the grid. A collector should never see it — they should see today's route, the next stop, and a button that says arrived. Both write the same row.

  • One data model, every surface
  • Roles enforced on reads and writes, not only in the layout
  • Drawn from the brief, with the team that will use each one
  • Grows into a full app when a role needs more
01Name the rolesWho does what, and what they must never see.
02Draw the pagesOne per role, over the rows the role works.
03Hand them outA role on a person is a page in their hands.
Also in Sell and serve

The record, the phone and the page each role sees.

CRMLive grids over Postgres, a view per role, automations on a cell, the phone and the invoice on the row.built to a briefTexting & callsTexts and calls placed from the row on your own numbers, logged where they happened.in the CRM
All products
Questions
How is this different from an app?
An interface is a page inside the workspace for a signed-in member. An app is a product of its own on your domain, for customers or staff, with its own sign-in. Interfaces grow into apps when a role needs one.
Can a role be changed later?
Yes. Roles, permissions and overwrites are edited in the workspace, and every page follows the change at once.
How is it priced?
As part of the CRM, quoted per team. Seats are free.

Tell us the roles.
We will draw the pages.

A list of who does what is enough to begin.

Set it up for my teamWhen a role needs an app