Reference
Attribute type support
Every type but one renders. Not everything is editable. This is the exact split, and the reason behind every No in it.
| 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 | Yes | Renders with the currency Attio holds. A viewer edits the amount; the currency is set on the attribute in Attio and no edit here can change it. |
| 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 a pill. Attio's API does not expose an option's colour, so the colour is ours, assigned from the option's own label and stable for it. |
| 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 | Yes | Whole stars, 0 to 5, the range Attio itself uses. |
| 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 view. |
| 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 | No | No | The one type that does not come through. Attio treats it as read-only and so do we, but this version also has no published-view rendering for it: switch the column on and the cells are empty. Leave it off. |
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, currency, date, rating, checkbox, single-select or status. Everything else is read-only in this version. The shorter list is chosen so that no single approved edit can quietly change more than the record you were looking at, and marking an attribute editable is not what decides whether a viewer’s value reaches Attio: by default it waits for your approval, and it goes straight through only on a view you have set to apply changes without one.
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 view 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 view, 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: support@publicviews.app.