BetterShield
Appearance

How To Require Two-factor by Role With BetterShield Ultra?

4 min read

Require two-factor for chosen roles with 0 to 90 days to enroll, role-specific grace periods and the shortest applicable deadline.

Use BetterShield Ultra to require authenticator-app two-factor for selected roles. Choose their enrollment periods so people have time to set up their app and store backup codes.

Note: Keep BetterShield Ultra and the free BetterShield plugin installed and active.

What it does

People in selected roles see a dashboard reminder. After their grace period, the next password sign-in goes to ‘Set up two-factor authentication’ before continuing.

Step 1: Open Your Sign-in Rules

Open ‘BetterShield › Ultra › Sign-in rules’.

Two-factor policy with shared days and Days for Editor and Author.
Ultra 1.0.9 local example: Editor uses three days and Author inherits the shared seven. These are example saved choices.

Step 2: Set Roles and Grace Periods

Open ‘BetterShield › Ultra › Sign-in rules’.

Step 2.1. Choose the Covered Roles

Choose ‘Who it applies to’:

  • ‘Only the roles I choose’, the default: include the roles you tick.
  • ‘Every role except the ones I choose’: include every role except the ones you tick.

Read the explanatory line before saving: selecting all roles in the exclusion mode requires two-factor of nobody. New roles are covered by the exclusion mode unless excluded. The ‘Days to set it up’ value may be 0 for the next sign-in; the default is 7 days.

Step 2.2. Set the Enrollment Periods

  • Under ‘People in these roles must have two-factor on’, tick the roles. None are ticked by default.
  • Set ‘Days to set it up’ from 0 to 90. The default is 7. A value of 0 means the very next sign-in.
  • Optionally set ‘Days for’ each covered role. Leave a role field empty to use ‘Days to set it up’. Someone in multiple covered roles gets the shortest applicable period.
  • Select ‘Save Sign-In Rules’.

The three policy cards save together. This Ultra grace period is separate from ‘Protection › Two-Factor’, whose Free policy defaults to 14 days. If both apply, review both deadlines; saving Ultra does not remove the Free requirement.

Step 2.3. Explain the Enrollment Flow

Tell people what to expect. At sign-in, the final ‘Save your backup codes’ page offers ‘Copy Codes’, ‘Download’ and ‘Print’. Store the codes before selecting ‘Turn On Two-Factor’. The free plugin’s ‘Two-Factor’ screen also shows roles covered by the Ultra policy.

With BetterShield 1.1.7 and Ultra 1.0.8 or newer, finishing required setup and storing the backup codes completes that sign-in. The person is not asked to enter the same app code again. Update both plugins together.

Two-factor policy with shared days and Days for Editor and Author.
Ultra 1.0.9 local example: Editor uses three days and Author inherits the shared seven. These are example saved choices.

Our advice:

  • Require administrators first.
  • Give active editorial teams enough time to enroll and store backup codes.
  • Use 0 days only when every affected person is ready.

What it can break and how to undo

After the deadline, a person who cannot complete setup cannot reach the dashboard. An administrator can turn off two-factor for that account, or remove the role from this policy and save.

Recovery safe mode pauses enforcement while somebody gets back in.

On multisite

Each site keeps its own policy. A session started on another site does not bypass this site’s enrollment screen.

Final Outcome

The card shows ‘On’ when at least one covered role is saved. People in those roles see their deadline and enter enrollment at the next password sign-in after it expires.

Two-factor policy with shared days and Days for Editor and Author.
Ultra 1.0.9 local example: Editor uses three days and Author inherits the shared seven. These are example saved choices.

This is how, with the help of BetterShield Ultra’s two-factor policy, you can set enrollment periods for the roles you cover.

Getting Stuck? Feel free to contact our Dedicated Support Team.

Close the open doors today

Install the free plugin. The first audit runs when you activate it, and all but one of the fixes wait for your choice.

Requires WordPress 6.7 or newer and PHP 8.0 or newer.

Get BetterShield