How to share an Attio list

What Attio can and cannot do here

Attio’s help centre is direct about it. Restricting a member to a single list needs their Pro plan, and even then the person “would still be able to see all records across your workspace”. So the two native options are a seat that shows more than you meant, or an export that is wrong by Thursday. The comparison, with prices and their words, is on the Attio seats view.

1. Connect the workspace

Sign up and connect Attio over OAuth. We read the lists and objects your Attio account can see, which means a view can never contain something you could not already open yourself.

One thing to know at this screen: a single registered Attio app has one fixed scope set, so the consent screen asks for write access even if every view you ever publish is read-only. We enforce read-only in our own layer instead, and the connect screen says this in the same words.

2. Pick the source

Either an Attio list, or an object with a filter. A filter is the better choice when the audience is one client: filter the deals object to that client’s records rather than maintaining a list by hand. Membership follows the filter, so a record that starts matching appears on the view at the next check and a record that stops matching comes off it.

Watch the negated operators. In Attio, is not also matches records where the field is empty, so “stage is not Lost” publishes every record with no stage set. The filter builder says so next to the operator, and the record count under it is the fastest way to notice.

3. Choose the attributes

This is the part that matters. Every attribute starts hidden. On the same first step, tick the ones the viewer should see; everything you leave unticked stays on our side and is never sent to the browser. To drag them into the order you want, or rename any whose internal label is not the one you would use with a client, open Order, rename and editable fields. arr_2026_committed becomes Committed.

The layout is not a question yet. A view publishes as a table, and once it is live the editor’s Look row switches it to a board for a pipeline somebody reads, or a single record at a time. All three are on every plan.

If you want the viewer to be able to change something, mark that attribute editable on the same page you reorder them on. By default their change waits for your approval before it reaches Attio. You can instead set the view to apply changes without approval: only a viewer who has verified their email address can then edit, and each change is still recorded with the value it replaced. Keep the list short, and think hard before making an amount field editable.

4. Decide who can open it

Pick one way in, then add an expiry on top if you want one:

• Unlisted link. An unguessable URL and nothing else. Fine for a public directory, thin for anything confidential, because a link that reaches one person reaches anyone they forward it to.
• Password. Set per view. On every plan, including free. A view has a password or an allowlist, not both.
• Email or domain allowlist. Named addresses, or everyone at a company without listing them. By default a viewer only has to type a listed address. Switch on email verification and they have to open a confirmation link, so the address is verified rather than typed.
• Expiry. On a date, after a number of opens, or both. Right for anything that goes into a board pack or a diligence process.

Not all of these are on every plan. The unlisted link and the password are on the free plan; the email or domain allowlist and expiry begin on a paid one, and per-viewer row scoping is higher again. A lock your plan does not carry is shown disabled with the plan it starts on named beside it, rather than hidden, and the pricing page has the full split.

One consequence to understand before you switch on viewer edits, because it runs the opposite way to how it sounds. A viewer’s edit is attributed to a person, so an editable view needs the email or domain allowlist. An allowlist challenges everyone, including on a link you meant to leave open to anyone holding it. There is no setting that asks for an address only from the people who want to edit. Publishing a view has the rest of it.

5. Read the exposure preview as your client

Publishing shows you the view itself, rendered the way your viewer will get it, with your real records and only the attributes you chose. Read it as the person you are about to send it to, not as the person who configured it. It also lists the attributes we hold and never display, such as one used to sort the view, so nothing about the arrangement is a surprise.

Then publish and copy the link. Send it once. There is no account for your viewer to create.

Afterwards

• Freshness. The view carries the time it last updated. 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. Sync now forces a check on any plan.
• Edits. By default, anything a viewer changes waits in your dashboard beside the current Attio value, and approving it writes it. On a view set to apply edits without approval, it is written straight away and recorded with the value it replaced. Either way, we re-read the attribute first and refuse to write over a value that moved.
• Turning it off. Pause or unpublish and the view stops resolving on the next request, with every open viewer session signed out in the same transaction. Your configuration is kept, so you can publish it again. Why that is instant rather than eventual is on the security page.