Pictures and initials on the card
The card has no header, so there is no obvious place for a customer's picture. It sits beside one field's value instead, and a project administrator chooses which field that is.
Only one field on a card ever carries the picture, and a field holding several values gets one picture rather than one per value.
#Where the picture sits
The picture is anchored to a row. That is a position on the card, so it depends on that row being there.
Anchor the picture to a field you are not showing and no picture appears anywhere If the field the picture is anchored to is not one of the fields chosen for display, the card shows no picture at all rather than moving it somewhere else. A position that is not on the card is nowhere. Clearing the nominated picture attribute also clears which row it sat beside, so nominating one again means choosing the row again.
#Coloured initials
Where a record has no picture, a coloured circle of up to two initials is drawn instead, so the rows still line up.
The colour is derived from the initials themselves, so the same initials always get the same colour, and two records with the same initials share one.
Initials are the first letter of each of the first two words: "Jane Roe" gives JR, and "Acme" gives a single A rather than an invented second letter.
Leading punctuation, such as a quotation mark or a bracket at the start of a record's name, is skipped.
A record with nothing in the nominated attribute still gets a circle, so it keeps the same indent as its colleagues. A circle is omitted entirely only where the object nominates no picture attribute at all.
Every picture and initials circle on the card is hidden from screen readers, because it always sits immediately beside the name it belongs to and announcing it would only repeat that name.
#There is never a spinner and never a broken image
While a picture is being fetched the initials are shown; when the bytes arrive the picture replaces them in the same box, so nothing moves and nothing is ever visibly waiting. A picture that is missing, blocked, dead, too large or not actually an image falls back to those same initials. The card cannot show a broken-image glyph or somebody else's error graphic, and a picture that fails once is not tried again for as long as the issue stays open.
#Where pictures come from
Record pictures are not loaded straight from whatever host your Attio enrichment happens to use. They are fetched through Capable's own image service, which is one origin and which applies a size limit and a file-type check before serving anything. The service asks browsers to keep a picture for an hour, so a second look at the same ticket costs nothing.
#A picture address held in a text field
An attribute holding a picture address shows the address, not the picture Attio has no image attribute type: its own picture fields are text attributes holding a web address. A text value that is a web address arrives at the card as a link, so putting that attribute on the card gives you the full address as a clickable link wrapped across several lines, with no thumbnail. The way to show the picture without the address is to nominate that attribute as the record's picture and leave it out of the fields the card shows.
That is also why only text attributes can be nominated as a record's picture, and why a nominated attribute does not have to appear on the card at all.
#A few things worth knowing
Two customers with the same initials get the same circle in the same colour. The colour is derived from the letters, so it is decoration and never an identity check.
A missing picture and a picture that would not load are indistinguishable. There is no icon, no tooltip and no message for either: both are initials, which is the ordinary case rather than a fault worth reporting.
A single-word record name gets a single letter. "Acme" shows as one A, not as AC, so a column of one-letter circles is expected on a company object.
#Related
If in doubt, it draws the letters.
