Require an authenticator code to approve Confluence pages
To require a code before anyone can approve in a Confluence space, a space administrator turns on Require 2FA to approve on the Security tab of Space Approval Settings. Each approver sets up an authenticator app once for the site, and every approve, reject and comment in that space then asks for a six-digit code.
#Before you start
You need | Why |
|---|---|
Space administrator permission | The requirement is set per space. There is no site-wide switch. |
Approvers with an authenticator app | Any standard app works, such as Google Authenticator, Microsoft Authenticator, 1Password or Authy. |
#Turn it on for a space
In the space, open Space settings, then Capable (Capable Approval if you use the standalone app), to reach Space Approval Settings.
Select the Security tab.
Turn on Require 2FA to approve, then save.
#Each approver, once
Open Authentication in the Approval sidebar. You are also prompted the first time you try to approve in a space that needs a code.
Scan the QR code with your authenticator app.
Type the six-digit code your app shows. You are enrolled for the whole site.
#What changes
Signed responses show a padlock in the approval history.
Slack and Microsoft Teams buttons are not offered in the space, and bulk actions fail there. People answer on the page.
There are no backup codes. A site administrator clears a lost enrolment from Auth tokens in Global settings, on the Approval tab.
Nothing is retroactive. Earlier approvals stay unsigned.
#Related
Every sign-off from here on is provably theirs.
