Requiring two-factor authentication for your organisation

Last Updated: 17/11/2026     Tags: two-factor authentication, 2FA, security, organisation settings, content deploy
  • Switch Version
  • V5
  • V4

Administrators can require two-factor authentication (2FA) for their organisation. You can apply the requirement to all users, or restrict protected permissions for users who have not enabled 2FA.

This article covers:

Before you begin

You must be an administrator with 2FA enabled or single sign-on (SSO) configured on your account to change these settings.

Before enabling a requirement, let affected users know and ask them to set up 2FA. User accounts configured for SSO satisfy these Taguchi security requirements without needing a separate Taguchi authenticator setup.

Choose a security option

The Security section in Settings has two two-factor authentication options:

Option Effect
Require two-factor authentication for all users Users without 2FA or SSO cannot access the organisation.
Require two-factor authentication for content deploy and database users Users without 2FA or SSO lose access to protected permissions. Their other assigned permissions remain available.

Both options are off by default.

If both options are selected, users without 2FA or SSO cannot access the organisation, because the requirement for all users still applies.

Despite its name, the second option covers more than content deployment and subscriber data. It restricts:

  • Content deployment.
  • Lifecycle deployment.
  • Editing, activating and reviewing Genichi agents.
  • Reading, managing and exporting subscriber data.
  • Power user and administrator permissions.

Enable the requirement

  1. Open the organisation you want to configure.
  2. Select Settings.
  3. Select Security.
  4. Select the requirement you want to apply:
    • Require two-factor authentication for content deploy and database users to protect the permissions listed above.
    • Require two-factor authentication for all users to require 2FA or SSO for everyone accessing the organisation.
  5. Select Save.

To remove a requirement, clear its checkbox and select Save. If the other requirement remains selected, it continues to apply.

What changes for users

When Require two-factor authentication for content deploy and database users is enabled, Taguchi restricts protected permissions for users without 2FA or SSO. For example, a user with content editing and deployment permissions can retain content editing access but lose deployment access.

The user's assigned roles are preserved. After the user enables 2FA, their protected permissions become available again without an administrator needing to reassign those roles.

This option does not set up 2FA for users. Each affected user needs to complete their own 2FA setup, or use an account configured for SSO.

Troubleshooting

I cannot change the security settings

Check that you have administrator access and have enabled 2FA or configured SSO on your account. Taguchi displays “You do not have enough privileges to modify the security settings of this organisation.” when your account does not meet these requirements.

A user can sign in but cannot deploy or access subscriber data

Check whether Require two-factor authentication for content deploy and database users is enabled. If the user has the necessary roles but has not enabled 2FA or configured SSO, ask them to enable 2FA.

A user cannot access the organisation

If Require two-factor authentication for all users is enabled, the user needs 2FA or SSO before they can access the organisation. See Two-Factor Authentication for account setup instructions, including how to reach account details when organisation access requires 2FA.

If you need help with your organisation's 2FA requirements, contact Taguchi Support.