Technical Anshu
Tutorials Blog
🛟 2FA Lockout Recovery

Tally Two Factor Authentication Lockout Recovery for Admins

Lockouts are not a failure of 2FA - they are a normal Tuesday. A phone is replaced, a number changes, a password is forgotten. Every lockout in this system has a safe admin-side recovery. Here is each one, honestly, including the single password nobody can reset for you.

✍️ Technical Anshu🧾 Admin Recovery Guide⏱️ 5 minute read
🎥 The video covers the setup; keep this page beside it for the day someone gets locked out

The worst response to a lockout is panic: switching 2FA off for the whole office because one person cannot sign in. Resist it. Each piece of this system - the TSplus enrolment, the Tally.NET password, the Tally company user password - has its own recovery path, and they are different paths. Work out which lock the person is stuck at before touching anything.

TSplus Two Factor Administration - Manage Users
User Method Status ------------------- ------- ---------- rajesh App Activated priya SMS Activated suresh App Activated Select the user, then: [ Edit ] change delivery method / phone / e-mail [ Reset ] clear enrolment - new QR code at next login [ Remove ] take the user out of 2FA completely
👆 The three admin actions that solve almost every lockout - Edit, Reset and Remove (panel recreated from the TSplus 2FA administration layout)
1

Lost or Changed Phone - Reset the User

This is the common one, and TSplus documents it directly. In the two factor authentication administration application:

  1. Open the Manage Users tab
  2. Select the activated user and click Reset, then confirm
  3. At the user's next portal login, a new QR code is shown; they scan it into the authenticator app on the new phone and they are back in

The old enrolment stops working from the reset. Verify the person first - in person, or on a number you already know - because a reset hands the next login a fresh enrolment, whoever performs it.

2

SMS Codes Not Arriving - Edit the User

If the user receives codes by SMS and they stop coming, do not reset blindly. Select the user and click Edit: check the phone number on the record (a changed SIM or a typing error is the usual cause) and correct it, or switch the delivery method to EMAIL or the app. Remember SMS delivery runs through a Twilio account - if codes fail for everyone at once, the problem is that sending account or balance, not Tally and not the users' phones.

3

Tally.NET Password Forgotten - the F5 Route

For Tally's own remote access, the recovery is self-service: at the Login As Remote Tally.NET User screen, press F5 - Reset Password. The new password is sent to the registered e-mail address. Two consequences follow. First, the user must still control that mailbox. Second, if they do not, the account administrator has to fix the ID from the Tally account side - there is no way around the mailbox, by design.

4

Tally Company User Password Forgotten - the Owner Resets It

Inside TallyPrime, passwords are never displayed to anyone - not even the administrator. What the administrator can do: sign in as the Owner/Admin, open Alt+K → Users and Passwords, select the user and set a new password. Hand it over privately and let the user change it (the password policy can permit users to change their own password). Any tool or person claiming to "show" you the existing Tally password is not describing how Tally works.

5

The One With No Self-Service Reset - the Administrator Password

Be honest with yourself about the hard case: if the company Administrator (Owner) password itself is lost and no other admin-level user exists, TallyPrime gives you no self-service reset. Recovery then needs help from Tally Solutions or an authorised Tally partner. Prevention is the real fix: the owner keeps the administrator credentials recorded in a proper password safe, and at least the owner plus one trusted senior hold admin-level access, so a single forgotten password never becomes a company emergency. The same warning applies double to a TallyVault password - lose that and the company data stays locked, with no recovery route at all.

6

The Rule That Prevents a Crisis ⭐

Three habits keep lockouts boring:

  1. Reset the one user - never disable 2FA for everyone to fix one person's phone
  2. Verify before you reset - a reset is a new key being cut; confirm whose hand it goes into
  3. Keep one tested admin path - make sure at least one administrator can always reach the server and the 2FA console, and test that login occasionally instead of discovering it is broken during a crisis
🔴 A 2FA reset hands a brand-new enrolment to whoever logs in next. Before you click Reset, be sure the person asking is really your staff member - on a call from a number you already have, or standing in front of you.

🎥 Watch the Full Setup in the Video

The setup video is the other half of this page - watch it so the recovery steps here match the system you actually built.

▶️ Watch Full Video
❓ Common Questions (FAQ)

Can a user reset their own TSplus 2FA enrolment?

No. Enrolment reset is an administrator action in the two factor administration application (Manage Users, then Reset). The user's part starts at the next login, when the fresh QR code appears for their new phone.

After a reset, does the old phone's authenticator entry still work?

No. The reset clears the user's authentication settings, so the old entry no longer produces acceptable codes. The new QR enrolment on the new phone replaces it.

We removed a user from 2FA by mistake. How do we fix it?

Add the user again under Manage Users in the 2FA administration application. They will go through the same first-login QR enrolment as a new user. If the person had left the company, though, treat the mistake as a warning and re-check your leaver list instead of re-adding them.

This guide is based on the Technical Anshu video linked above. If a screen on your system looks different, ask in the video comments - that is where answers come fastest 🙏