PublicViews

PublicViews

Share the view - Keep the workspace

Overview

Share the view. Keep the workspace.

PublicViews is how you get information out of Attio and in front of someone who is not in your workspace: a client, an investor, a candidate, a partner, a contractor. You choose a list or an object, narrow it to the records that person should see, switch on the attributes they should see, and publish the result as a web page at its own address. You send one link. They open it. There is no account for them to create, no invitation to accept, and no Attio seat to pay for.

Attio has no way to show a list to someone outside your workspace. The alternatives are a CSV that is wrong by Thursday, a paid seat so one person can read eight records, or rebuilding the whole thing somewhere else and maintaining it twice. This is the fourth option.

The product is built around what a viewer cannot reach. A new page starts with every attribute hidden, so nothing is exposed until you expose it, and an attribute you did not switch on is not sent to the browser at all. The link carries its own locks, and they stack rather than replace one another: an unlisted address, a password, an email or domain allowlist, and an expiry by date or by number of opens. Row scoping goes further and shows each viewer only the records matched to the address they confirmed, so one link can serve every client their own rows.

A viewer can change nothing you have not marked editable, and a new page marks nothing. Where you have allowed it, a viewer proposes a value and you decide how it lands. It can wait in your dashboard beside the value Attio holds now until you approve it, which is the default and how every page starts, or it can apply on its own. Both require the viewer to confirm their email address first, and either way the change is recorded with the value it replaced, so you can see what happened and put it back.

PublicViews is built by Dialed Technologies. It is an independent app and is not an official Attio product.

How it works

PublicViews syncs the following data from Attio, and nothing else.

Attribute schemas, for the objects and lists you choose to publish from: attribute names, types and select options. This is what lets you choose columns and build filters.

Record values, for the records your filter matches, and only for the attributes you have made visible. An attribute you leave hidden is not stored and is not sent to a browser. Stored beside each row are the Attio record identifier, the list entry identifier where the source is a list, and the parent object slug.

Workspace members, as a directory: member identifier, display name, email address and avatar URL. It is refreshed at most once a day and exists so that an attribute holding a workspace member renders a name rather than an identifier. A member's email address reaches a viewer only if you made that attribute visible.

PublicViews reads through your own Attio account, so it can never reach a record you could not open yourself.

It writes one thing back: a change a viewer made to an attribute you marked editable, either after you approve it or, if you chose that mode, on its own. Each one is recorded with the value it replaced. Nothing else is ever written to Attio.

How the sync runs

A published page is served from this stored copy rather than from a call to Attio, so viewer traffic never touches your Attio rate limit. PublicViews re-reads Attio on a schedule set by your plan and the size of the source. Every published page carries the time it last updated, and you can start a sync yourself before a call. Pausing a page is one click and its address stops resolving. Deleting your PublicViews workspace deletes the stored copy with it.

Configure

You do not need a paid plan to use this app. The PublicViews free plan covers one published page, does not expire and does not ask for a card. Paid plans raise the number of pages, the size of a source and how often it re-reads Attio.

You do need an Attio account that can already see the records you want to publish. PublicViews reads through your own account and can never reach more than you can.

  1. Create a PublicViews account

Sign up at publicviews.app/sign-up.

  1. Connect your Attio workspace

Open Settings, then Attio, and start the connection. Approve Attio's consent screen and you are returned with the workspace connected.

Expect that screen to ask for write access, and do not read anything into it. Attio fixes an app's scopes at registration and offers no way to narrow them per install, so every publisher consents to the same set whether or not any page they build is ever editable. What decides whether PublicViews writes is PublicViews: viewer edits are off on a new page, and turning them on takes several deliberate steps the app shows you as a checklist.

  1. Create a page

Choose New view and pick the list or object it reads from. Setting up a draft is three steps: Data, Access, Publish. Each step saves before the next one opens, and nothing is public until the last one.

Data. Choose which records the page covers: everything in the list or object, one of your Attio saved views, or conditions you build yourself. Then choose the columns. Every attribute starts hidden, and you cannot leave this step with all of them hidden.

Access. Choose between an unlisted link, a password, an email or domain allowlist, and an expiry, and combine as many as the situation deserves. Row scoping is optional and shows each viewer only the records matched to the address they confirmed. Viewer edits are set here: a new page allows none, and you can let changes wait for your approval or apply on their own.

Publish. The last step shows the page as your viewer will get it, beside a manifest of what is shared, what is sensitive and what is withheld. Publishing is gated: the app lists every reason it will not publish, with a code and the control that clears it. There is no publish anyway.

  1. After it is published

The same address opens an editor with five rows, each expanding in place: Rows, Columns, Access, Look and Activity. Proposed edits and visit counts are under Activity. Approving an edit writes it to Attio; rejecting it changes nothing there.