Reference

Attribute type support

Everything renders. Not everything is editable. This is the exact split, and the reason behind every No in the third column.

The renderer set covers every attribute type the product models, so a view will not meet a field it cannot draw. What a viewer may change is a much shorter list, chosen so that no single approved edit can quietly change more than the record you were looking at.

Attio attribute type	Renders	Can be editable	Notes
Text	Yes	Yes	Long text wraps in the record layout and truncates in a table cell.
Number	Yes	Yes	Rendered with your Attio number formatting.
Currency	Yes	No	Renders with the currency Attio holds. Editing waits for a write-shape test.
Date	Yes	Yes	Absolute, with a relative form in the record layout.
Timestamp	Yes	No	Read-only. A timestamp is usually something the system set, not something a viewer should move.
Checkbox	Yes	Yes
Select	Yes	Yes	Single-select only. Rendered as the pill Attio shows, in Attio's own colour.
Status	Yes	Yes	Same. This is the attribute a board layout can group by.
Multi-select	Yes	No	Renders every value. Not editable: Attio's write semantics for multi-select are not settled enough to trust with a client's record.
Rating	Yes	No	One line away from editable once a write-shape test exists.
Record reference	Yes	No	Shown as the linked record's display name rather than an id. Not editable: writing one silently changes a second record through the paired relationship.
Actor reference	Yes	No	A workspace member, shown by name. Never editable from a published page.
Email address	Yes	No	Renders as a mailto link. Worth a second look in the exposure preview before you publish a directory of people.
Phone number	Yes	No
Domain	Yes	No	Attio has no URL type. Domains render as links, and a full URL kept in a text attribute can be marked as a link.
Location	Yes	No	Rendered as the parts Attio holds.
Personal name	Yes	No	First, last and full name as Attio structures them.
Interaction	Yes	No	Read-only in Attio itself, so read-only here.

The editable rule, stated once

An attribute can be marked editable when all three of these are true: Attio reports it as writable, it is not multi-select, and its type is text, number, date, checkbox, single-select or status. Everything else is read-only in this version. Marking an attribute editable never means a viewer writes to Attio: it means they can propose a value that waits for your approval.

Four things the table does not cover

Clearing a value is not supported. A viewer can propose a different value, not an empty one. Whether an empty write clears an Attio attribute or is rejected is not documented, and we are not going to find out on a customer’s record.
Creating records is not in this version. A view publishes the records a list or filter already matches. There is no form mode.
Relationships are one hop. A view shows a list’s records and their direct attributes. Following a reference into another object and publishing that object’s attributes is not in this version.
An attribute deleted in Attio is dropped, not guessed. If an attribute you published disappears from the source, the column comes off the page and the dashboard tells you which one it was. Nothing else about the view changes.

Which of these end up on our servers

Only the attributes your views need: the ones you switched on, plus any used to sort the page, group a board, label a linked record, or decide which viewer sees which rows. The security page has the full table, including the two kinds we hold and never display.

If your workspace has something odd in it

Connect a workspace and preview a view before paying anything. That takes less time than reading a compatibility table, and it answers the question against your own attributes rather than against ours. If something renders wrong, send us the type and we will fix it: help@publicviews.app.