Team invite preview

What changed

When someone invites a teammate to a HumanKey workspace, the invitee now sees who invited them and the role they will hold before accepting. Acceptance is an explicit step — a deliberate click — not an action triggered by simply following the invite link.

The visible result for invitees is a moment of context: the name of the person who invited them, the role they would hold, and a clear acceptance step they choose to take.

Why we surface context before action

This change reflects a discipline we apply across the surfaces a customer touches: when an action carries trust implications, we surface the relevant context before the action is committed. An invitation acceptance is one of those surfaces — the invitee is making a decision about a workspace and a role.

Our DPIA records the basis for this disclosure as Account-holder collaboration: when an account holder invites another person to join their workspace, identifying context about the inviter (such as their display name where available) may be shown to the invitee for identity verification, on the basis of Art. 6(1)(f) — the invitee's legitimate interest in knowing the source of an access offer, balanced against the inviter's reduced expectation of privacy in the act of inviting. Direct contact identifiers of the inviter are not exposed to the invitee.

What this is part of

This work sits alongside the rest of our public compliance posture. The Data Processing Agreement, Privacy Impact Assessment, and Sub-Processor list are public — start with whichever is most relevant to your evaluation.

For a free trial, no credit card required.