Check which QuickBooks app and environment the service uses, and which connections need attention.
Operator consoleAvailable
Customers connect a company's QuickBooks on the dashboard. The connection is kept on the service, never in the app, and the service is the only thing that talks to QuickBooks. QuickBooks shows how that is set up. Use it when a customer cannot connect a company, or a connection stopped working.
Everything here is read only. A client ID is only ever its last four characters.
The page is read only. It never shows a secret, a company's name, a company number or a connection itself. A client ID, which names a QuickBooks app, is shown as its last four characters.
Two words to know
App. To talk to QuickBooks, Haruno uses an app registered with Intuit, the company behind QuickBooks. The service has one. An organization can register one of its own.
Environment.sandbox is a test world with invented money. production is the customer's real books. An app belongs to one of the two.
This deployment's app
The first section shows the app the service uses by default:
App is its client ID, or Not configured in red.
Environment is sandbox or production.
Sandbox only says whether production is allowed. When it is Yes, production is allowed only for the organizations listed under Production organizations. Test environments run this way.
Redirect URL is where QuickBooks sends the person back after they sign in.
Organization apps
Organizations that registered their own app are listed with its client ID and environment. On this deployment says Allowed, or Blocked here when this environment does not let that organization use its app in that environment.
Portfolio companies and personal connections
The next two tables count connections, grouped by the app that made them, the environment, the status and whether the app is still labelled with the same environment as the company. Portfolio companies are companies an organization or person connected into their portfolio. Personal connections are single-person ones.
The App column says whose app made the connection: this deployment's, an organization's, one that is no longer set up, or Not recorded.
A red Needs reconnect note appears when connections sit under an app that is now labelled with the other environment than the company. This can happen when an app is saved again under a different environment, or the environment of the service changes.
Portfolio connections like this are not renewed, and none are revoked here. Putting the label back before the next renewal is enough. After that, a reconnect works once the app is of the company's environment.
Personal connections are never renewed by the service. For them the note only means that disconnecting will not revoke the connection at Intuit.
Disconnecting a company for a customer
Nothing on this page can be changed. A super admin can still disconnect a company on a customer's behalf, for example when the customer asks and cannot do it themselves. The console has no button for it.
It does the same as the customer pressing Disconnect on the dashboard. Haruno's access to the company ends. The service also asks QuickBooks to end the access. If QuickBooks does not confirm, the company is still disconnected in Haruno, and the customer can remove Haruno from inside QuickBooks. The disconnect is recorded, with whether QuickBooks confirmed it.
Who can use it
Every operator can read it. Nothing on it can be changed.
What a person in support can ask an operator
"This firm cannot connect their QuickBooks. Is their app allowed here?" Look at Organization apps for Blocked here.
"A company stopped syncing and asks to reconnect." Look for needs_reconnect and Needs reconnect in the tables.
"Is the service in test mode?" Read Sandbox only and Environment.
"Please disconnect this company for us." A super admin can do it. Check first that the person asking is an admin of the customer's organization.