Reading a card
What is behind the chevron on an activated row, and what opening it does.
Opening a card
Section titled “Opening a card”On Dashboard, the paper plane at the end of a row becomes a chevron once somebody is Activated. The chevron opens their card. Rows in any other state have no chevron, because there is nothing behind them to open — Understanding grant states sets out which state is which.
A card also has its own address, which is what an external system points at when it hands somebody a link to a person in the Portal.
What it shows
Section titled “What it shows”Who, and since when. Across the top: the sphere the person belongs to, the email address your workspace knows them by, when they granted your company access, and when they last changed anything.
Their contacts, as they filled them in. The fields of your sphere’s template, under the groups it defines — the owner’s own details first, then the preferred contact, then the backup. A phone is a phone and an address offers to open in Maps.
Fields they added themselves. Anything marked own field is something the person chose to put on the card beyond what your sphere asked for. Your template is the question; it does not limit the answer.
What is true right now. A card is loaded at the moment you open it and never served from a cache. What you see is what the person holds today, not what they entered on the day they were invited.
What it doesn’t
Section titled “What it doesn’t”Anything from before the grant. No history, no previous values, no record of what was corrected. A card is a current state, not a file on somebody.
Anything meant for another company. A person may hold several cards, each answering a different company’s sphere. Yours shows yours.
Anything you can edit. The card is read-only for you, down to an obvious typo. The person maintains it, which is the whole arrangement: if they could not change it without you, it would not be theirs.
Contacts in bulk. Print works from inside one open card, one card at a time, and that is deliberate. The roster export carries who you hold and the state they are in — never a field value from anybody’s card.
A card whose grant has ended. A revoked row will not open, and what comes back says the source was revoked. That is the person having ended something on purpose, not an error to report. The same is true before they have granted: there is nothing behind the row yet.
Printing a card
Section titled “Printing a card”Print this card produces a single sheet carrying the contacts, your company’s name, who printed it and when. It is offered on an activated card only.
It also creates an entry in the compliance trail saying that a card was printed, in which workspace and when. The entry never carries what was on the sheet.
What opening one records
Section titled “What opening one records”Opening a card is a read, and reads are not written to the compliance trail. Nothing is sent to the person either — they are not told that you looked, and the product does not pretend otherwise.
The roster export is recorded as well, with the filters it ran under described but never quoted.