Choosing and ordering the fields on the card
The card starts empty, and stays empty until somebody ticks something. The Fields screen says as much where the list of chosen attributes would be: "Nothing yet. The card does not render until at least one attribute is ticked."
Fields are chosen in one place whether you are setting the project up or changing your mind a year later: the Fields step of the six-step wizard, or the Fields tab of the settings page afterwards. Both live in a Jira project under Project settings, Apps, Attio, and both are for project administrators of that project.
#The two lists
Every attribute of the chosen Attio object appears as a row, split into two groups: "On the card", which is in the order the card will render, and "Everything else". Ticking a row adds it to the bottom of the card; unticking takes it off. Attributes archived in Attio are never offered, because an archived attribute can never receive a new value again.
The description above the second group says what it is for: "Every other attribute on this object, with what it holds for the address above. Tick one to add it to the bottom of the card." There is no search box and no filter, and the unchosen group is in Attio's own order, so an object with many attributes has to be scrolled.
Control on a row | What it does |
|---|---|
Tick box | Puts the attribute on the card, at the bottom of the chosen list. Unticking removes it. |
Grip | Drag the row to a new position within "On the card". |
Move up and move down | The same reorder without a mouse. Always available, including from the keyboard. |
Image | Nominates that attribute as the record's picture. Offered on text attributes only, ticked or not. |
Value column | What this attribute holds for the test address typed at the top of the step. |
#Putting them in order
The order of the chosen list is the order of the card, exactly. Drag a row by its grip, or use the move buttons on the row, which work from the keyboard and are always visible rather than appearing on hover. Every completed move is announced with where the row landed, so a screen reader user is told the new position rather than left to count.
The heading above the list keeps the count: "3 attributes, in the order they render. Drag them by the grip, or use the arrows." With a single attribute it reads "1 attribute", and with none it invites you to start: "Tick an attribute below and it moves up here, where you can put it in order."
#Seeing real values before you ship
A "Test email address" box sits at the top of the step. Type an address that exists in your Attio workspace and the value column fills in with that customer's real values. It is your own test address, not a reporter's, and the lookup waits about six tenths of a second after you stop typing so a burst of edits costs one lookup.
Values fill in for every visible attribute, not only the ticked ones, which is the point: you can tell a useful attribute from an empty one before putting it in front of an agent. It costs no extra calls to Attio, because it reads more of the record that was already fetched. Nothing is looked up at all until the first attribute is ticked, and the step says so: "Tick one attribute and every row below fills in, including the ones you have not chosen. Attio is not looked up for a project with an empty card."
When the project matches reporters by company rather than by person, only the part after the @ is used, and the step names the domain it is matching on.
The value column reads | What it means |
|---|---|
"Type an address above to see this value." | No address has been looked up yet. |
A value | What this record holds for that attribute. |
"No value on this record" | The lookup ran and the record is empty for this attribute. |
Nothing at all | The lookup did not cover this attribute, so the step declines to claim it is empty. |
A note above the list explains whatever came back: no matching record, more than one matching record with the values taken from the first, a key Attio has rejected, Attio rate limiting the app, or a lookup that failed. Clearing or refusing an address does not blank the column: the previous answer stays on screen with "Any values below are from the last address that was looked up." added, so nothing is left quietly claiming to be current.
#Attributes of a linked record
A ticked attribute that links to another Attio object gets a chevron. Expanding it shows that object's attributes as the same kind of rows, with their own tick boxes, live values, ordering and Image column, under a heading reading "Shown under" and the attribute's name.
Those choices are stored against the linked object rather than against the row you opened, so setting them once on Companies applies to every attribute on the card that links to Companies. The same panel chooses whether a linked record is drawn inside the card or kept behind its link and shown on hover, and neither costs an extra call to Attio.
Nesting goes one level and stops. Inside an expanded linked record, attributes that link on to a third record are not offered at all.
#Saving
In the wizard, pressing Next is what stores the step. On the finished settings page nothing is stored until you press "Save changes": a bar appears at the foot of the window naming what changed, for example "Unsaved changes to fields.", with "Discard" beside it, and a small indicator near the heading reads "Saving", "Saved" or "Not saved". Only the parts you actually changed are sent, so two administrators working on different tabs do not overwrite each other.
Everyone who passes the gate sees every field There is no per-person hiding of individual attributes. The Permissions step says it plainly: "Everyone who passes this gate sees every attribute you chose on the previous step. Nothing on the card is hidden per person." An attribute that should not be in front of every agent on the project should not be ticked.
#A few things worth knowing
Typing in the Test email address box on the Fields tab saves your pending changes. The lookup runs on the server against the stored configuration, so the page stores whatever is unsaved first, even though the "Save changes" bar is still sitting there.
Toggling a placement discards unsaved field work. Placements are written the moment they are switched, and the page then re-reads the whole configuration from the server, which replaces anything still unsaved on the other tabs. Save first, then touch placements.
Changing the record type, or switching between matching the person and matching their company, clears every chosen field, the order, the nested linked-record choices and the picture settings, because all of them belong to the object. The settings page warns first and names how many fields will go. The wizard clears them with no confirmation at all.
#Related
Tick less than you think. An agent reads a short card and skims a long one.
