Skip to content

Understanding grant states

Every person in your workspace sits in exactly one state, shown at the end of their row on Dashboard. The state is about one thing: whether that person has given your company access to their contacts, and whether they still have.

You never set it. It is derived from what has happened — an invitation sent, a consent given, a consent ended — and the filter above the list narrows by it.

The row exists and the invitation has not gone out.

Adding somebody and inviting them are two actions, not one, so this is where everyone lands the moment you add them — the invitation waits until you send it. It is also where a person stays if a send fails: a failed invitation is never silent, and the row not moving is how you see it. Either way there is nothing behind the row — an empty card waiting for its owner.

Send, or fix the email address first and then send. Invitations covers both.

The invitation has been delivered, and nothing has come back yet.

The link in it is good for seven days. The person has not filled anything in, or has not finished, and there is still nothing for you to read. Silence here is an answer in itself, and resending is the only lever you have — not a reason to add somebody a second time.

The person filled in their details and granted your company access. Their card is readable, and the Contacts column stops being a zero.

What you see is theirs and stays theirs. They can change a number tonight and your card carries the new one tomorrow; they can end your access at any point without asking you. Reading a card covers what is behind the row while this lasts.

The person ended your company’s access.

The row stays in the list, keeps its seat and keeps its state on show. The card behind it closes, and opening it says the source was revoked. Nothing is retained from it on your side.

Getting the details again means asking for them again. Re-invite the person and the row returns to Invited: they are given an editable card and have to grant afresh. Nothing is served in between, and no previous consent is resumed.

Reading a card. Opening one changes nothing and tells the person nothing.

Anything you do in the Portal. You cannot mark somebody activated by hand, and there is no state that means “asked twice” or “declined”.

A token. Whether somebody carries a token is independent of their state here, and it stays independent: a person who has ended your access still has a working token, because a token answers to them and to whoever scans it, not to your workspace.

Seats. Only archiving frees one. A revoked person is still somebody your workspace holds a row for.