The QuickBooks user lacks permission
The connection works, but QuickBooks refused one particular action because the QuickBooks user the connection signs in as is not allowed to do it.
What you see
Section titled “What you see”The app shows:
QuickBooks Desktop did not give this connection permission for this. Ask your QuickBooks Admin to update the permissions.
The app’s support team may see the QuickBooks status code 3260, which QuickBooks describes as an insufficient permission level, or 3261, which means the app may not access personal data.
Often only some actions fail. For example, the app can read customers but cannot create invoices or see payroll.
Why it happens
Section titled “Why it happens”During setup, someone chose a QuickBooks user under Login as. The connection does everything as that user, so QuickBooks applies that user’s permissions. The error appears when:
- the user’s role does not cover the area the app works in, such as sales, purchases, banking or reports
- the user can view an area but not create or change records in it
- the app touches sensitive areas, such as payroll or closed periods, that need extra permission
- someone changed the user’s role after setup
Personal data (status 3261)
Section titled “Personal data (status 3261)”Some information is protected separately from user roles: payroll reports, Social Security numbers and full credit card numbers. The connection does not ask for this access during setup, so it stays off until the QuickBooks Admin turns it on. Until then, these requests fail even for the Admin user.
To allow it, the QuickBooks Admin:
- Signs in to QuickBooks as Admin and opens the company file in single-user mode if QuickBooks asks for it.
- Chooses Edit › Preferences › Integrated Applications, then the Company Preferences tab.
- Selects the app and clicks Properties.
- Turns on the option that allows the app to access personal data, such as Social Security numbers and customer credit card information, then clicks OK.
Only allow this if the app needs payroll or other personal data. Then try the action in the app again.
How to fix it
Section titled “How to fix it”These steps cover status 3260, the QuickBooks user’s role. You need the QuickBooks Admin for them.
- Find out which user the connection uses. In QuickBooks, signed in as Admin, choose Edit › Preferences › Integrated Applications, open the Company Preferences tab, select the app and click Properties. The user is shown under Login as.
- Give that user the access the app needs. In QuickBooks Pro and Premier, choose Company › Set Up Users and Passwords › Set Up Users, select the user and click Edit User. In Enterprise, choose Company › Users › Set Up Users and Roles, then edit the user’s roles.
- Grant access to the areas the app works in. If you are not sure which areas those are, ask the app’s support team. Granting full access to every area also works, at the cost of a broader permission.
- Save the changes, then try the action in the app again.
Another option is to switch the connection to a different user that already has the right access, such as Admin. See Change the QuickBooks user the connection uses. A dedicated QuickBooks user for the connection keeps its permissions separate from any person’s.
How to check it worked
Section titled “How to check it worked”Repeat the action that failed in the app. It goes through without the permission message.
When to contact the app’s support
Section titled “When to contact the app’s support”Contact them if you are unsure which permissions the app needs, or if the error continues after the user has full access. Send the time, the exact message, the action you tried in the app, and the QuickBooks user name shown under Login as.
Related pages
Section titled “Related pages”For developers, see QBD_INSUFFICIENT_PERMISSION.