👤 Authentication
Authentication confirms the requester, on plans with Authentication required switched on. The member confirms the access request through a method that only they can reach, so a request can never be started by someone who merely knows a password.
How it works
When the request is made, the requester gets a confirmation request through the plan's authentication method. They confirm it there, and only then does the request move on.
No confirmation, no reveal. A stolen laptop or leaked browser session cannot get past a check that lives on another device or in another inbox.
Methods
| Method | How the requester confirms |
|---|---|
| SafeKey Mobile | The request arrives in SafeKey Mobile on their own phone, where they confirm it, signed in with their SafeID |
| Link via email | They click a one-time link sent to their email address |
A plan can use one method or several. If a plan uses several, the requester completes one of them, or all of them when the plan requires all. Your organisation can switch methods off, or require that every plan uses authentication.
When it applies
| Plan configuration | Authentication |
|---|---|
| Direct access | Always on: it is the gate that keeps direct plans personal |
| Private | Always on |
| Business Continuity | Always on |
| Moderated Data Backup plan | Your choice per plan |
This is why phishing gets nowhere: an attacker can copy an email and fake a voice, but they cannot confirm a request on a phone or in an inbox they do not hold.