Require 2FA for your team: passkeys, audit log

Turn on two-factor and passkeys, require them for everyone with the Organisation security policy, and see who changed what in the audit log.

On this page
  1. How Brevily keeps an organisation secure
  2. Turn on two-factor for your account
  3. Add a passkey or sign in with Google, GitHub or Microsoft
  4. See where you're signed in
  5. Require 2FA for your team with the Organisation security policy
  6. See who changed what in the audit log
  7. Common questions
  8. Next steps

To require 2FA for your team in Brevily, you turn on two-factor for your own account, then switch on Require two-factor in the Organisation security policy. From their next page, anyone without an authenticator app or a passkey is asked to add one before anything else opens.

A short link is only as safe as the accounts that can change where it goes. Two-factor keeps a leaked password from redirecting your printed QR codes, and the audit log shows who changed what.

Before you start: setting rules for everyone needs the Security Edit permission, which admins hold; see team roles and permissions. The policy and the audit log depend on your plan.

How Brevily keeps an organisation secure

  • Each person's sign-in: an authenticator app, recovery codes, passkeys, and sign-in with Google, GitHub or Microsoft under Your account › Sign-in methods, and the password under Your account › Password. Every change asks for the current password and is confirmed by email.
  • The organisation's rules: the Organisation security policy, which applies to every member, and the audit log, which records what they do.

Turn on two-factor for your account

  1. Open Your account › Sign-in methods and choose Turn on two-factor.
  2. Enter your current password and choose Continue.
  3. Scan the code with any authenticator app that shows six-digit codes.
  4. Type the current code into Six-digit code and choose Turn on two-factor.
  5. Save the recovery codes shown next. They're shown once.

From then on, sign-in asks for a code after your password. Each recovery code stands in for one code, for days when your phone isn't to hand; Make new codes replaces the whole set.

Add a passkey or sign in with Google, GitHub or Microsoft

A passkey signs you in with Face ID, Touch ID, Windows Hello or a security key, with no password or code. It counts as two-factor on its own.

  1. On Sign-in methods, choose Add passkey.
  2. Give it a Name you'll recognise, such as "MacBook Touch ID", and enter your current password.
  3. Choose Continue, and your browser asks for your face, fingerprint or key.

Remove stops a passkey at once. Under Linked sign-ins, Link Google, Link GitHub or Link Microsoft lets you sign in through that account; two-factor is still asked after it.

[screenshot: Your account › Sign-in methods with two-factor on and two passkeys]

See where you're signed in

Your account › Sessions lists every browser signed in to your account, with its device, city and country, and when it was last used. Sign out ends one, such as a laptop left at a conference; Sign out everywhere else ends all but This device.

Brevily emails you about each new sign-in and each change to how you sign in, and these emails can't be turned off. Admins see how many sessions each person has on their page under Access › People, with Sign out everywhere.

Require 2FA for your team with the Organisation security policy

The Organisation security policy lets you require two-factor or a passkey for every member, set how long a sign-in lasts and when an idle console locks, and choose which email domains may be invited. It depends on your plan; see pricing.

  1. To switch on Require two-factor, add two-factor or a passkey to your own account first; the save is refused until you do.
  2. Open Settings › Access & security and find Sign-in rules.
  3. Set the rules you want (below).
  4. Choose Save rules.
  • Require two-factor: someone without two-factor or a passkey sees Add two-factor or a passkey to continue at their next page, and their personal API keys stop working until they add one.
  • Sign-ins last at most: after this long, everyone signs in again, and a shorter limit ends longer sessions already open.
  • Lock the console after: how long without a click, key or scroll before the console locks. Their password or a passkey opens it again, on the same page. Until you choose, Brevily's default applies.
  • Invite only addresses at: invitations go only to the domains you list, such as example.com, and their subdomains, checked again when one is accepted.

[screenshot: Settings › Access & security, the Sign-in rules with Require two-factor on]

The People page shows how many people have two-factor on. Single sign-on through your identity provider is set up on Settings › Access & security, on plans that include it.

See who changed what in the audit log

Safety › Audit log records every change in your organisation: people, groups, keys, links, domains and settings, with who made it and when. Select an entry to see what it changed. How far back it goes depends on your plan.

  • Narrow it down by person or API key, action, record and dates, or search for a word.
  • Export CSV downloads what the filters select, for a security review or a client's questionnaire.

Reading the log needs Security View, and exporting it Security Export; people see the entries for the folders they can open.

Common questions

What if a team member loses their phone and recovery codes?

An admin chooses Reset two-factor on their page under Access › People, which clears both and signs them out; passkeys stay.

Does a passkey count as two-factor in Brevily?

Yes. A passkey is both factors in one, so it meets Require two-factor on its own.

Can I turn off the idle console lock?

Yes, in the Organisation security policy, which depends on your plan: choose Never under Lock the console after.

Whose security rules apply across two Brevily organisations?

Each organisation's own, when you enter it.

Next steps

All how-to guides

Brevily is invite-only, for now

Say what you would use it for and a person replies. Already invited? Sign in.