PublicViewsEverything you can control before you press publish.
PublicViews sits between your Attio workspace and the person you are sharing with. Here is every decision that layer lets you make.
Records
Start from a list, or from a filter
Point a view at an Attio list, or at an object with a filter, and PublicViews takes it from there. We snapshot the matching records into a cache and re-check on a schedule.On a paid plan we check Attio every 5 minutes up to 500 records, every 15 minutes up to 5,000, and hourly up to 50,000. Free views check every hour. Change the filter and membership follows on the next check. Records that leave the view come off the page, and records that join it appear.
Layouts
Table, board, or record
Table. Columns you choose, with search and sort inside the published attributes.
Board. Group by a status or select attribute for a pipeline anyone can read.
Record. One record per page, for a profile, a brief, or a per-client status page.
All three layouts are on every plan, including free.
Attribute control
Per-attribute, not per-record
Show or hide each attribute. Reorder them. Rename them, so mrr_net_2026 reads as “Monthly value”. Mark specific ones editable and leave the rest read-only.
We render the Attio types you use: text, number, currency, date, select and status, multi-select, checkbox, URL, email, phone, rating, location, and record references shown as their display name rather than an ID.
A view shows a list’s records and their direct attributes. Following relationships several objects deep is not in this version.
Everything renders. Not everything is editable yet. Text, number, date, checkbox, and single-select and status attributes can be marked editable in this version. Multi-select, linked records, locations, currency, and ratings are read-only for now.
Access
Who can open it
Unlisted link. An unguessable URL and nothing else.
Password. Set per view.
Email allowlist. Named addresses, with an optional magic-link confirmation.
Domain allowlist. Everyone at a company, without listing them.
Expiry. On a date, after a number of opens, or both. An open means someone opening the link. Link previews and scanners do not count against it.
Stack any of them. A proposed edit is attributed to a person, so a view with viewer edits on needs the email or domain allowlist, and that allowlist asks every reader for an address. Pause a view and the page stops resolving straight away.
Editing
Edits you approve before they reach the record
A viewer changes an editable attribute and it becomes a pending edit in your dashboard. You see the proposed value beside the value currently in Attio, and you approve or you do not. Nothing reaches your CRM until you do.
We check the value against the attribute type before it queues, so a viewer cannot stage something the field would reject. We re-read the field at approval time and tell you if it changed in Attio since the edit was proposed, rather than writing over it. Every edit is logged with the viewer’s identity where the view is gated. Write endpoints are rate-limited per view and per session.
Approval is how editing works in this version. There is no mode where a viewer’s change goes straight into Attio.
Branding
It should look like your page
Logo, colours, page title, favicon. The “made with PublicViews” badge comes off on every paid plan.
A published view is served from a publicviews.app link. Custom domains are not available yet, on any plan. The roadmap says where that sits.
Analytics
Whether anyone opened it
Page views on every plan, including free. Paid plans add unique viewers, a timeseries, referrers, and edit counts. Business adds a per-viewer access log you can export, which is the artefact you want when someone asks who saw what and when.