Require security keys for everyone on your account

Last verified

A security key is a passkey on a phone or computer, or a hardware key such as a YubiKey. A stolen password, or a code typed into a fake sign-in page, is not enough to get past one. Require security keys makes a key compulsory for everyone on your account: the team, and the people who sign in with their mailbox address.

It is stronger than Require two-factor for all members (see roles and permissions): an authenticator app alone does not satisfy it.

Before you start

  • You need to be the account's Owner or an Administrator.
  • Add a security key to your own sign-in first, on Security with Add passkey (see two-factor sign-in and passkeys). The rule applies to you too.

Switch it on

  1. Open Settings → Team.
  2. Choose Require security keys.
  3. The dialog says who has no key yet. Confirm with Require security keys.

Two-factor sign-in is required for everyone from that moment. Everyone without a key then has a grace period to add one. The Security keys panel on the Team page says how many days.

The Security key column shows where each person stands: Has a key, Needs a key by a date, or Overdue. People who sign in with their mailbox are listed under Mailbox users, with the same column.

To switch the rule off again, choose Make security keys optional. Two-factor sign-in stays required until you switch that off as well.

What each person sees

  • Before their date: every portal page shows Your organisation requires a security key. Add one by the date, with a link to their Security page. They can dismiss it for the page they are on.
  • After their date, without a key: signing in only lets them add a key. Their mailbox stops accepting its password in mail apps, and no new app passwords can be made for them, until they add one.
  • Someone who joins later gets the same grace period, counted from the day they join.

Phones and mail apps

Mail apps such as Apple Mail, Outlook and Thunderbird cannot use a security key. Once someone has a key, or their date has passed, their mailbox no longer accepts its own password in those apps. Each device then signs in with its own app password: the people who use a mailbox make them on their own Security page, under Mail apps, and whoever manages the mailbox can make them with App passwords… in its ⋯ menu on the Email page. See mailbox passwords and devices.

Only for some mailboxes

To protect one mailbox, such as a shared info@, without a rule for the whole account, choose Require security key in that mailbox's ⋯ menu on the Email page. Its own password then stops working in mail apps, and the people who use it open it in webmail and Veldmail only once their own sign-in has a key. See require a security key for one mailbox. Account-wide Require security keys works as before, alongside it.

If someone loses their key

Someone with a key who loses it can still sign in with their password and an emailed code, their authenticator app or a recovery code, and add a new key.

If they have none of those:

Caution: Reset sign-in removes the person's security keys, authenticator app and recovery codes, signs them out everywhere, and signs out the mail apps on their mailbox. It cannot be undone.

  1. Open Settings → Team, or the mailbox on the Email page.
  2. Open the person's ⋯ menu and choose Reset sign-in.
  3. Confirm with Reset sign-in.

Their password stays. At their next sign-in they add a new security key straight away: the grace period does not start again. Set their phone and mail apps up again with new app passwords.

An Administrator cannot reset the Owner's sign-in, or that of anyone whose role holds more than their own.

Stuck? Contact support — replies within one business day.