QuickBooks "Not Allowed to Log In Automatically" Error When Connecting Third-Party Apps
QuickBooks Desktop blocks external applications from automatic login during integration setup, requiring a manual permissions reset through Integrated Applications preferences.
When a third-party application tries to connect to a QuickBooks Desktop company file, users can hit a wall with a message stating that the application is not allowed to log into the data file automatically. The error typically surfaces during initial integration setup or after changes to the company file environment. QuickBooks Desktop Enterprise and the QBXML SDK are common environments where this surfaces, though the problem is not specific to any one developer tool — it affects any application relying on QuickBooks’ integrated application framework.
What’s Happening Behind the Error
QuickBooks maintains an internal permissions list for external applications that request access to company data. When an application connects, QuickBooks is supposed to prompt the admin user to grant access, after which the application can log in automatically on subsequent attempts. The “not allowed to log in automatically” error means that permission grant has either been corrupted, partially applied, or is being blocked by a stale permission file that QuickBooks uses to track integrated application logins.
The culprit is frequently a file with a .lgb extension stored in the same directory as the company file. This file stores login credentials and permission information for integrated applications. When it becomes outdated or corrupted, QuickBooks may reject automatic logins even though the application was previously granted access — or may never successfully prompt for the initial grant in the first place.
The Resolution Path
The accepted fix walks through a full reset of the integrated application permissions, starting with clearing the stale login data and then re-establishing the connection from scratch.
Step 1: Locate the Company File Directory
Press Ctrl+1 inside QuickBooks to open the Product Information screen. This displays the full file path to the company file. Note the directory location — the folder containing the company file, not the file name itself.
Step 2: Clear the Permissions File
Get every user logged out of QuickBooks completely. Open Windows Explorer and navigate to the company file directory. Look for a file with a .lgb extension — this is the integrated applications login file. Rename or delete it. Removing this file forces QuickBooks to rebuild the permissions tracking from scratch on the next connection attempt.
Step 3: Remove the Existing Application Entry
Open QuickBooks in single-user mode and log in as the Admin user. Navigate to Edit > Preferences, then select Integrated Applications and click the Company Preferences tab. If the third-party application appears in the list, highlight it and click Remove, then confirm with Yes. Click OK to close the preferences window.
This step clears any partially-formed or corrupted permission entry that QuickBooks may be holding for the application.
Step 4: Re-establish the Connection
Switch QuickBooks back to multi-user mode while still logged in as Admin. Open the configuration tool for the third-party application and remove the company from its own list if it appears, then attempt to reconnect. QuickBooks should now present a fresh permission prompt asking the admin to confirm that the application is allowed to access the company file. Approve the prompt.
For QuickBooks Enterprise users, an additional dialog may appear with instructions to create a dedicated custom user account for the integration. When setting up that user, use the exact same password both in QuickBooks and in the third-party application’s configuration to avoid mismatch errors on subsequent automatic logins.
Once the connection is saved in the application’s configuration tool, automatic login should function normally on future launches.
When the Problem Recurs
If the error returns after following these steps, the underlying company file may have deeper structural issues affecting how preference data is stored and retrieved. In those cases, running QuickBooks’ built-in Verify and Rebuild utilities can address data integrity problems that interfere with integrated application permissions. Persistent integration failures on a healthy file may also point to company file corruption that requires more thorough diagnosis than the standard repair tools can provide.
The key takeaway is that this error is rarely caused by the third-party application itself. It is almost always a QuickBooks-side permissions issue, and the .lgb file in the company file directory is the first place to look.