NirmaanOne Help
TroubleshootingReviewed 2026-09-29

Pages refuse to load data: your organization requires two-factor authentication

A red banner says most pages will refuse to load data, dashboard sections fail and every list shows the same message: the organization now requires two-factor authentication and your account has not set it up yet.

Messages this explains

  • “Your organization requires two-factor authentication. Until you set it up, most pages will refuse to load data.”
  • “Your organization requires two-factor authentication. Set it up in My Profile to continue.”
  • “Your organization requires two-factor authentication. Set it up now to regain access to the rest of the app.”
  • “Could not load this section. It will try again when you come back to the page.”
  • “Set up two-factor authentication first”
  • “Enable two-factor authentication on your own account before requiring it for everyone.”
  • “Two-factor authentication is already enabled.”
  • “Start the setup again to get a new secret.”

Pages refuse to load data: your organization requires two-factor authentication

What you see

  • A red banner at the top of every page except My Profile (the app shell): "Your organization requires two-factor authentication. Until you set it up, most pages will refuse to load data." with the link Set up two-factor authentication.
  • Lists, records and forms show the error "Your organization requires two-factor authentication. Set it up in My Profile to continue." instead of their data.
  • On the Dashboard, each section shows "Could not load this section. It will try again when you come back to the page."
  • On My Profile, the Two-factor authentication card shows a red Off badge and the alert "Your organization requires two-factor authentication. Set it up now to regain access to the rest of the app."
  • On Connect an app, the heading "Set up two-factor authentication first".

On Organization settings, when an administrator turns on Require two-factor authentication for all users: "Enable two-factor authentication on your own account before requiring it for everyone." with the link Set up yours in My Profile.

While setting it up on My Profile: "Two-factor authentication is already enabled." or "Start the setup again to get a new secret."

Why it happens

  • The policy is an organization setting. The Security policy card on Organization settings has the switch Require two-factor authentication for all users ("Users without it can still sign in but only to set it up; every other page is blocked until they do."). Once it is on, every request that needs a permission is refused for a user whose account has no two-factor authentication. Signing in, your profile and the two-factor setup itself keep working, so you can always put it right yourself. The card also shows how many users still lack it ("N users, M without two-factor authentication.").
  • Dashboard sections hide the reason. Each widget loads on its own and shows the generic "Could not load this section" whenever its data is refused, including for this policy. The banner above tells you why.
  • An administrator must lead by example. The switch cannot be turned on by someone whose own account lacks two-factor authentication; otherwise the administrator would lock themselves out of every page at the same moment.
  • Setup is a two-step handshake. Set up two-factor authentication creates a secret to scan; Enable confirms it with the first code. "Two-factor authentication is already enabled." means the setup was already completed, usually in another tab or on another device. "Start the setup again to get a new secret." means Enable was pressed without a pending setup (for example after Disable two-factor cleared it), so the app needs a fresh secret before it can check a code.

How to fix it

  1. Open My Profile (the banner link Set up two-factor authentication takes you to the Two-factor authentication card). Anyone can do this for their own account; no permission is needed.
  2. Press Set up two-factor authentication, scan the QR code with an authenticator app (Google Authenticator, Authy or similar), or type the key shown under Or enter this key manually.
  3. Enter the app's code under Enter the 6-digit code to confirm and press Enable.
  4. Save the 10 backup codes the app shows. They are shown only once and each works one time, for days when the authenticator is not at hand.
  5. Go back to the page you needed. The banner disappears and lists load again; if a dashboard section still shows "Could not load this section", leave the page and come back.
  6. Administrator cannot turn the policy on. Complete steps 1 to 4 for your own account first, then return to Organization settings and turn on Require two-factor authentication for all users (the Edit permission on Organization Settings), then confirm Require two-factor in the "Require two-factor for everyone?" dialog, which counts the users who have not set it up yet. Warn users first: from that moment everyone without it sees the banner until they set it up.
  7. "Already enabled". Reload My Profile; the card shows Enabled and no action is needed.
  8. "Start the setup again". Press Set up two-factor authentication once more, scan the new QR code and confirm with a fresh code.

Related

  • My ProfileScreen

    Your own account: see your email, organization and roles, change your name and phone, change your password, turn two-factor authentication on or off, and sign out everywhere.

  • DashboardScreen

    The page you land on after signing in: shortcuts to common jobs, a queue of what is waiting on you, the headline figures and one card each for projects, sales, stock, receivables, construction and the RERA accounts.

  • Sidebar, top bar and notifications bellScreen

    The frame around every page once you are signed in: the sidebar with its groups, the top bar with the notifications bell, the light and dark switch and your account menu, and the banners that ask you to act.

  • OrganizationScreen

    Your organization's profile and policies: name and invitation expiry, the two-factor requirement, the AI connectors switch, the help-assistant recording switch, the project defaults every project inherits (RERA gate, estimate validity, the two chargeable areas, carpet area offered, revenue method and trigger) and the effective-dated rules: the RERA escrow share that splits every sweep of a project's collection account, TDS on sales and booking cancellation.

  • Connect an app (<app> wants to connect to NirmaanOne)Screen

    The consent page an AI assistant sends you to when it asks to work in NirmaanOne on your behalf: see what it will be able to do, then allow or deny it.

  • Two-factor sign-inScreen

    Turn on two-factor authentication with an authenticator app, sign in with a 6-digit code or a backup code, manage your backup codes, and what happens when your organization requires it.

  • Cannot sign in: wrong password, pending invitation, deactivated account or a rejected codeTroubleshooting

    The sign-in form, the two-factor step or a password form refuses you: what each message means, the rule behind it and how to get back in.

  • Connecting an AI app is refused: connectors are off, 2FA is missing or the request is invalidTroubleshooting

    The consent page will not let you allow an AI assistant, an existing connection has stopped working, or the Revoke icon is greyed out: what each message means and who can fix it.