Two controls put more than one person into the same QuickBooks company file. On the computer that stores the file, open File > Utilities > Host Multi-User Access. Then, with the company file open, choose File > Switch to Multi-user Mode. Everything else in this article exists because one of those two steps failed, or because your situation needs something other than local multi-user access.
Those two menu items look interchangeable. They are not, and confusing them is the reason most setups stall.
Jump to what you need: licenses and seat limits · hardware and network requirements · server setup · workstation setup · creating users · troubleshooting · remote and multi-location access · single-user-only tasks · Mac and QuickBooks Online · performance and maintenance · FAQ
Hosting is a property of a computer. It decides whether that machine’s QuickBooks database service will hand the company file out to other machines on the network. Intuit is explicit that hosting mode “is set for each version of QuickBooks Desktop and for each computer. It isn’t set for the company file or the QuickBooks Desktop installation.” Install two version years on one PC and each carries its own independent hosting state.
Multi-user mode is a property of an open company file. It decides whether the file you are looking at right now accepts concurrent logins.
| Host Multi-User Access | Switch to Multi-user Mode | |
|---|---|---|
| Applies to | One computer, per QuickBooks version year | One company file, in the current session |
| Where you set it | File > Utilities | File menu |
| What it changes | How the QuickBooks database service runs on that machine | Whether the open file accepts other signed-in users |
| Where it belongs | On the machine holding the file, and nowhere else | On any workstation, once hosting is correct |
.nd descriptor stay on one machine. That machine runs the database service; every other machine connects to it. Hosting is on in exactly one place.One mechanic catches almost everyone: the menu label states the opposite of the current state. If File > Utilities reads “Host Multi-User Access,” hosting is currently off and clicking turns it on. If it reads “Stop Hosting Multi-User Access,” hosting is already on. Reading that line backward is how workstations end up hosting alongside the server, the condition Intuit’s own remediation tells you to remove whenever an H-code appears.
It gives several people concurrent access to one company file stored on one computer on one local network. Each person works in their own QuickBooks session, sees the others’ saved entries, and is blocked only when two of them reach for the same record.
It does not create extra licenses, it does not copy the file, and it does not extend access beyond the local network. If your bookkeeper works from home, multi-user mode alone will not reach them. The four options that do reach them are covered further down. And if you only want to move a file that already runs fine between the two modes, switching between single-user and multi-user mode is a two-click job that does not need any of the configuration below.
More failed setups die here than anywhere else. The Windows work is wasted if the license was never going to permit it.
Section 4.1 of Intuit’s End User License Agreement is the governing document. It is a legal instrument rather than a marketing page, and as published in August 2026 it sets these ceilings:
| Edition | Maximum concurrent users | Still sold to new U.S. subscribers |
|---|---|---|
| QuickBooks Desktop Pro Plus | 3 | No, as of Sept. 30, 2024 |
| QuickBooks Desktop Premier Plus | 5 | No, as of Sept. 30, 2024 |
| QuickBooks Accountant Desktop (subscription) | 5 | No, as of Sept. 30, 2024 |
| QuickBooks Accountant Enterprise | 30 | Yes |
| QuickBooks Desktop Enterprise | Up to 40, depending on the subscription | Yes |
| QuickBooks Desktop Mac Plus | Not published; sold in 1-, 2- and 3-user licenses | No, as of Sept. 30, 2024 |
Those first two rows are where most small businesses sit: Pro 2024 covers up to three simultaneous users, and Premier 2024 raises that ceiling to five. Intuit contradicts itself on the Enterprise figure, and it is worth knowing which number you are reading. Its support article on adding a user license says Enterprise supports “up to 30 simultaneous users.” Its Enterprise 24.0 subscription tiers say Gold and Platinum allow up to 30, and Diamond adds 10 more for a maximum of 40. The tier-specific figures are the current ones; the flat 30 in the support article appears not to have been revised for Diamond. Intuit’s own Enterprise pricing page sells licenses in increments of 1 to 10, then 20, 30 and 40, and offers the 40-user tier on a monthly payment plan only.
For Mac, Intuit publishes no maximum anywhere: not in the EULA table, not in the Mac multiuser article, not in the 2024 Mac user’s guide. The 1-, 2- and 3-user tiers above come from how the product is sold, not from a published ceiling. Check your own count in QuickBooks > About QuickBooks 20XX.
Every simultaneous user needs their own license seat. Three people in the file at once means three seats, whatever the edition.
The EULA goes further than the phrase “concurrent user” suggests. Section 3.1.4 grants access “solely for the number of specific persons corresponding to the number of user Subscription licenses you purchased, with no substitution of such users except as expressly permitted by this Section.” Seats attach to named individuals. They are not a floating pool you rotate through as people come and go.
One seat does stretch across two machines, but only for the same human being: Section 3.1.3 permits installation “for access and use solely by one specific person on (i) one primary computer, and (ii) one additional computer (e.g., a laptop or a home computer).” A bookkeeper with a desktop and a laptop is covered. Two colleagues sharing one license are not, and in practice they will find themselves confined to single-user mode.
To see what you actually hold, press F2 in QuickBooks and read the User Licenses figure in the Product Information window. Repeat on each workstation. To add seats, use Help > Manage My License > Buy Additional User License, then Help > Manage My License > Sync License Data Online. In Enterprise, each new user requires a purchased license.
This is license law, not advice. Section 3.1.4 states that “All users in a multi-user environment must be using licensed copies of the same version year of the Software.”
Release level is a softer rule with the same practical effect. Intuit’s support staff instruct that when the application is updated, “you need to update and upgrade the new version on all workstations, and server for all users,” and warn that “once a company file is being updated to a higher version, you can no longer open it in the older version.” That guidance appears in support answers rather than in the update documentation itself, so treat it as Intuit’s recommendation rather than a contractual term. Even so, plan to update every workstation to the same release in one pass anyway, because a mixed environment produces connection failures that look like network faults.
The same compatibility page settles two edition questions. Pro and Premier of the same year read each other’s files without altering data, so a Pro user and a Premier user can share a file, though the host installation’s seat ceiling still governs how many people fit. Enterprise runs the other way: the upgrade from Pro or Premier is one-way, and “you cannot open ES company files in Pro or Premier.” If your team has outgrown five seats, moving a Pro file up to Enterprise is a conversion, not a setting.
Lockouts that read alike come from three separate mechanisms, and conflating them sends people looking for the wrong fix.
Activation lock. The message “QuickBooks has reached the maximum number of unregistered uses,” which older builds word as “unregistered hours,” appears when a license has gone unregistered for more than 30 days. Despite the word “users,” it has nothing to do with seat count. Clear it through Help > Activate QuickBooks Desktop and confirm the license shows as active in Intuit’s account management portal. The full sequence is covered on the page for the maximum number of unregistered users message.
Seat exhaustion. You have three seats and a fourth person tries to sign in. QuickBooks refuses the fourth login specifically.
Lapsed subscription. When a Plus subscription expires, Intuit grants read-only access for one year; renewing restores full access.
Intuit stopped selling QuickBooks Desktop Pro Plus, Premier Plus, Mac Plus and Desktop Enhanced Payroll to new U.S. subscribers after Sept. 30, 2024. The date is worth stating carefully, because most of the web repeats July 31, 2024, the originally announced deadline that Intuit later extended. The July date survives partly because it is still embedded in the URL of Intuit’s own help article, whose body text says September 30.
Existing subscribers were not affected: they renew normally, keep updates, and, as Intuit support staff have confirmed, can still add seats up to their edition’s ceiling. Pushing past three seats on Pro or five on Premier still requires Enterprise, which Intuit continues to sell.
There is also no QuickBooks Desktop 2025 or 2026. Intuit moved off annual version releases; a member of the QuickBooks team confirmed in February 2026 that the company “did not release them as separate new versions” and instead shifted to “maintaining and updating the current QuickBooks Desktop 2024.” Release notes for 2024 run through R21, released in June 2026. Intuit has also dropped the three-year sunset for version 24.0, which now receives ongoing security patches and compliance updates rather than a scheduled discontinuation. Version 23.0 and its 2023 siblings reached the end of service after May 31, 2026; Intuit has published no discontinuation date for 24.0, and any date you see quoted for it is not Intuit’s.
Intuit recognizes three topologies. In a client-server setup, a dedicated machine stores the file and runs the database service while nobody works on it directly. In peer-to-peer, the fastest workstation does both jobs. In remote hosting, a terminal server or a hosting provider runs QuickBooks and the file together, and workstations connect to that session.
| Peer-to-peer | Dedicated server | |
|---|---|---|
| What holds the file | The fastest workstation, which somebody also works on | A machine nobody signs into |
| Cost | None beyond what you already own | A PC or server, plus its Windows license |
| When the host reboots | Everybody stops | Nobody notices, if it is scheduled |
| Effect of heavy work on the host | Reports and batch jobs on that PC slow every other user | Isolated from user workloads |
| Backup window | Constrained by whoever is using that PC | Any time the file is closed |
| Sensible ceiling | Two or three concurrent users | Any size, and effectively required past five |
Intuit’s own guidance is not perfectly consistent here. Its Enterprise installation guide states that “a dedicated computer must run the QuickBooks Desktop Enterprise Database Server Manager and store the company file,” while its current install article presents the combined machine, QuickBooks plus the file on one PC, as the recommended choice. For two or three users, the combined machine is fine. Intuit does not publish a threshold for moving to a dedicated machine. In our own client work the line falls around five concurrent users, past which a machine nobody logs into is the difference between a file that stays responsive and one that stalls whenever somebody runs a large report.
Intuit’s published requirements for QuickBooks Desktop 2024 scale server memory with headcount:
| Concurrent users | Server RAM |
|---|---|
| 1 to 5 | 8 GB |
| 10 | 12 GB |
| 15 | 16 GB |
| 20 or more | 20 GB and above |
Workstations need 8 GB minimum and 16 GB recommended, a 2.4 GHz x86 processor from Intel or AMD, and 2.5 GB of disk plus room for the data files. Solid-state storage is recommended. ARM processors are not supported. Supported servers are Windows Server 2022, 2019 and 2016 in Standard and Essentials editions, plus 64-bit Windows 11 installed natively. Intuit states plainly that the software “requires you to use Windows natively. Linux, Windows 10 S Mode, emulators, and virtual environments are not supported.” Windows 10 reached end of support on Oct. 14, 2025, so a Windows 10 host is now an unpatched host. The per-edition detail lives on the page covering published system requirements for each Desktop edition.
Intuit reduces file access to three requirements, and it is worth memorizing them because they map exactly onto the diagnostic method later in this article:
Miss any one and the file will not open, no matter how correct the other two are. They also assume the file itself is already in a usable state, so if you are building this alongside a fresh installation, complete the initial company file configuration before you start sharing anything.
Not on a USB drive. An Intuit moderator states it directly: “QuickBooks doesn’t have an option to host QuickBooks company file from a USB drive. Instead, you’ll need to use the hosting service providers so you can run your QuickBooks and store your data files on a service provider’s servers.”
Not on a NAS appliance. Intuit’s error H202 documentation carries the line that “the QuickBooks Database Server Manager doesn’t support devices like Network Attached Storage (NAS).” The architectural reason is straightforward: the database service is a Windows service that must run on the machine holding the file. A Synology or QNAP box serves files over SMB but cannot run that service, so workstations find the .QBW and nothing to talk to.
Not inside a Dropbox, Google Drive or OneDrive sync folder. Intuit publishes no statement on this, and any article that quotes one is inventing it. The reason is the same architecture: multi-user access assumes exactly one authoritative copy, opened by one database service, with a .nd descriptor pointing at that machine’s address. A sync client replicating a file mid-write produces divergent copies with no arbiter, which is how conflicted copies and unrecoverable damage appear. Sync the backup, never the live file.
Mapped drives on the server side. Two separate Intuit sources say the Database Server Manager “can’t monitor mapped drives” and that mapped drives “are not displayed and cannot be monitored.” The server must therefore reference the file by its local path, while workstations reach it through the share. Intuit does not publish a blanket instruction to prefer UNC paths over mapped drives, and this monitoring limitation is the specific, documented constraint, not a general prohibition.
Linux, in current versions. Intuit did support Linux file servers for Enterprise through version 22.0, running Samba 2.2.12 or later on Fedora, openSUSE Leap or RHEL. Enterprise 23.0 ended it. Note that Intuit’s 2024 system requirements say Linux is unsupported while its install article still links to Linux server instructions. The requirements page is describing the QuickBooks client, the install article is describing a database server option that no longer applies to current versions.
Work through these six steps in order on the computer that will hold the company file. Do not skip ahead to the hosting toggle; it is step five for a reason.
When the installer asks for an install type, choose Custom or Network options and select Next. Do not choose Express. Intuit’s instruction is explicit on this point, because Express installs a single-machine configuration with no database server component.
Three choices follow:
If you host more than one version year on the same machine, install the oldest year first and finish with the newest.
QuickBooks Database Server Manager is the component that actually shares the file. Its job is narrow and specific: Intuit describes it as the tool that “shares your company files with other computers over your network,” and elsewhere notes that it “exists to create .ND files.”
That .nd file is the whole point. It is a small text file sitting beside the company file, named yourcompany.qbw.nd, and it holds the information a workstation needs to reach the server: the IP address and the port. Until the folder is scanned, no .nd exists and no workstation can find its way in. Intuit’s Enterprise guide states the rule flatly: “All company files stored on the server must be scanned once to allow access to other QuickBooks users.”
Open the tool from the Windows Start menu and work through its tabs:
.qbw files, then Start Scan. Scanned folders appear under “QuickBooks company files found.”The full walkthrough, including how to restart the service, is on the page for installing and scanning with Database Server Manager.
QuickBooks creates a dedicated Windows user for each version year of the database manager, such as QBDataServiceUser33 for 2023 and QBDataServiceUser34 for 2024, and that account is what actually reads and writes the file. It needs explicit permission.
Open the company file folder’s Properties, go to Security, then Advanced, select the QBDataServiceUserXX account, and allow all nine of these:
Intuit also accepts Full Control as a simplification. The same account needs these permissions on several system folders, not just the company file folder: the Entitlement Client folders under C:\ProgramData\Intuit, the version folder under C:\ProgramData\Intuit, C:\ProgramData\COMMON FILES\INTUIT and its QuickBooks subfolder, and the QuickBooks folders under C:\Users\Public\Public Documents\Intuit.
Then share the folder itself: Properties > Sharing > Share, add the user, and set the permission level to Full Control. Intuit’s File Doctor documentation states the requirement as full control including view, open and modify. Getting this wrong produces the folder permission errors on the shared directory that surface as vague “insufficient permissions” messages.
Intuit publishes this port table, and the placeholders in it are real:
| QuickBooks Desktop year | Ports |
|---|---|
| 2020 and later | 8019, XXXXX |
| 2019 | 8019, XXXXX |
| 2018 | 8019, 56728, 55378–55382 |
| 2017 | 8019, 56727, 55373–55377 |
“XXXXX” is Intuit’s own notation, not a redaction on our part. From 2019 onward QuickBooks assigns a dynamic port at installation. In Intuit’s words: “These are specific firewall ports (not a range) assigned during installation. This ensures QuickBooks Desktop gets exclusive use of a given port.” Any article quoting a fixed port number for QuickBooks 2019 or later invented it. Read your actual number from Database Server Manager > Port Monitor, find your version, and note the port. If you change it with Renew, available only for 2019 and later, go back to the Scan Folders tab and select Scan Now to reset firewall permissions.
Then create the program exceptions. In Windows Defender Firewall with Advanced Security, open Inbound Rules, select New Rule, choose Program, browse to the executable, allow the connection, apply it to all profiles, and name it. Repeat under Outbound Rules. Fourteen executables need both:
| Executable | Location |
|---|---|
AutoBackupExe.exe | C:\Program Files\Intuit\QUICKBOOKS YEAR |
Dbmlsync.exe | C:\Program Files\Intuit\QUICKBOOKS YEAR |
DBManagerExe.exe | C:\Program Files\Intuit\QUICKBOOKS YEAR |
FileManagement.exe | C:\Program Files\Intuit\QUICKBOOKS YEAR |
FileMovementExe.exe | C:\Program Files\Intuit\QUICKBOOKS YEAR |
QuickBooksMessaging.exe | C:\Program Files\Intuit\QUICKBOOKS YEAR |
QBW32.exe | C:\Program Files\Intuit\QUICKBOOKS YEAR |
QBDBMgrN.exe | C:\Program Files\Intuit\QUICKBOOKS YEAR |
QBServerUtilityMgr.exe | C:\Program Files\Common Files\Intuit\QuickBooks |
QBCFMonitorService.exe | C:\Program Files\Common Files\Intuit\QuickBooks |
QBLaunch.exe | C:\Program Files\Common Files\Intuit\QuickBooks |
QBUpdate.exe | C:\Program Files\Common Files\Intuit\QuickBooks\QBUpdate |
IntuitSyncManager.exe | C:\Program Files\Common Files\Intuit\Sync |
OnlineBackup.exe | C:\Program Files\QuickBooks Online Backup |
Antivirus deserves the same treatment. Real-time scanners that inspect the company file while the database service writes to it cause intermittent, hard-to-reproduce disconnections; adding QuickBooks as an antivirus scanning exclusion removes a class of faults that otherwise looks like network instability. If the workstations also use QuickBooks features that reach Intuit’s servers, whitelisting Intuit domains in your browser firewall settings prevents a second class of intermittent failures.
Now, and only now:
Re-open File > Utilities and confirm the entry now reads Stop Hosting Multi-User Access. That is what “on” looks like.
Hosting itself has three states, and knowing which one you are in explains a great deal:
| Hosting state | How the database service runs | Multi-user support |
|---|---|---|
| Not hosting | As a normal process under the signed-in Windows user, using shared memory | None — only the local user reaches the file |
| Hosting local files only | As a Windows service, QuickBooksDBXX, running whenever the machine is on | Yes, over TCP/IP, for files stored on that machine |
| Hosting local and remote files | As a normal process that starts at Windows login and stops at logout | Yes, over TCP/IP, including files opened from other machines |
A fresh QuickBooks installation starts in “not hosting,” which is why a file that has never been shared opens fine for one person and refuses everybody else. “Hosting local files only” is what a dedicated server should be in. Note the practical trap in the third state: because the process is tied to a Windows login session, logging out of the host drops everyone.
Three checks, all on the server:
services.msc, and confirm QuickBooksDBXX is running with startup type Automatic. If it is stopped, right-click it, select Properties, set Startup type to Automatic, then select Start. The number is the version year plus 10, a rule Intuit states as “XX notes your version of QuickBooks plus 10. Example: QuickBooks 2023 is QuickBooksDB33.” So 2022 is QuickBooksDB32 and 2024 is QuickBooksDB34. Intuit names 2022, 2023 and 2024 explicitly in its hosting article; the remaining rows below follow from the rule rather than from a published list, and are marked as such. Worth knowing before you go looking: Intuit’s own hosting article states the 2022, 2023 and 2024 names at the top and then, further down, describes the service as “QuickBooksDBXX (where XX is a number from 25 to 28),” a block written for QuickBooks 2015 through 2018 and never revised. The table below applies the rule Intuit publishes rather than reproducing the stale list.QBCFMonitorService is also running. It listens on port 8019 and multi-user access fails without it.yourcompany.qbw.nd now sits beside the company file. If it does not, the folder scan in step 2 did not complete.One preventive step belongs here rather than in troubleshooting. Give the host a fixed address, either by assigning a static IP or by reserving its address in the router’s DHCP table. The .nd file every workstation reads carries the server’s IP address, and it is only refreshed when the folder is rescanned. A host that picks up a new lease after a power cut leaves every workstation pointed at an address nobody answers.
| Version year | Service name | Source |
|---|---|---|
| 2018 | QuickBooksDB28 | Rule-derived |
| 2019 | QuickBooksDB29 | Rule-derived |
| 2020 | QuickBooksDB30 | Rule-derived |
| 2021 | QuickBooksDB31 | Rule-derived |
| 2022 | QuickBooksDB32 | Named by Intuit |
| 2023 | QuickBooksDB33 | Named by Intuit |
| 2024 | QuickBooksDB34 | Named by Intuit |
The server is the hard part. Workstations take minutes, and the only real hazard is the one covered first.
1. Install the same version year, at the same release. Use the workstation install option, “I’ll be using QuickBooks Desktop on this computer.” Then update every machine, including the server, to the same release before anyone opens the file.
2. Confirm hosting is off. Open QuickBooks without opening a company file, go to File > Utilities, and look at the label. If it reads “Stop Hosting Multi-User Access,” this workstation is hosting and must be stopped. Hosting belongs in exactly one place. Intuit’s remediation for H505 is precisely this: turn hosting off everywhere except the server.
3. Turn on network discovery. On the server and every workstation, open Control Panel > Network and Sharing Center > Change advanced sharing settings, expand the current profile, turn on network discovery, turn off password-protected sharing, and save.
That last instruction is Intuit’s own, and it has a consequence Intuit does not state: with password-protected sharing off, any device on the local network can reach the shared folder without credentials. On a network carrying guest Wi-Fi or unmanaged devices, share the folder to named accounts instead and let the NTFS permissions from server step 3 do the controlling. The folder holds your general ledger; treat it accordingly.
4. Map or browse to the file. Intuit’s prerequisite is that you “map Server or Host computer as a network drive.” If mapping by computer name misbehaves, Intuit suggests using the server’s IP address instead. Workstations that cannot see the share at all are covered on the page for workstations that cannot see the mapped drive.
5. Open the company file. Go to File > Open or Restore Company, select Open a company file, then Next. Browse to the mapped drive or share, select the .qbw file, and select Open. Sign in when prompted.
6. Switch to multi-user mode. Go to File > Switch to Multi-user Mode. If the “Multi-user hosting setup required” window appears, select Yes, then OK on the information window that follows. That prompt is telling you QuickBooks will run QBDBMgrN.exe as a background service on the hosting machine. That service keeps running whether or not QuickBooks is open there, which is exactly what you want.
Repeat steps 1 through 6 on each workstation. When the last one is in, open Database Server Manager on the server and check the Database Server tab; everyone should be listed.
Then put three checks on a monthly calendar reminder, because multi-user environments fail quietly between the day they are built and the day somebody complains: confirm both Windows services are still running and still set to Automatic, confirm every machine is on the same release after the last update wave, and confirm a backup has actually completed rather than being blocked by somebody leaving the file open overnight.
A working multi-user file with one shared Admin login is a compliance problem waiting to happen. Intuit’s third condition, that every user needs their own QuickBooks login, is also the only way the audit trail can attribute anything.
A note on the menu label: Intuit’s own article writes it as “Set Up Users and Password” in two procedures and “Setup Users and Passwords” in a third. The on-screen label is what you should follow.
What is actually restrictable deserves care. Intuit currently names only two areas in its documentation: Sensitive Accounting Activities, and sensitive financial reporting such as the Balance Sheet and Profit and Loss. The nine-item area list that circulates widely is not published by Intuit anywhere; it comes from third-party articles and older printed manuals. Build permissions from what you see in the dialog rather than from a list you found online.
To hide account balances from a specific user: Company > Set Up Users and Passwords > Set Up Users, highlight the user, select Edit User, choose “Selected areas of QuickBooks,” select Next until you reach Sensitive Accounting Activities, set it to No Access, then Next through to Finish. Broader role design, including how to change and remove roles later, is covered under assigning administrator rights and editing user roles.
Enterprise replaces per-user checkboxes with roles, and asks for the admin password first.
Custom roles follow the same first three steps, then the Role List tab, New, a name and description, and an Area and Activities section where each area is set to None, Full or Partial. Enterprise ships up to 14 predefined roles. To audit what a role actually permits before assigning it, use Role List > View Permissions > select roles > Display.
Enterprise behaves differently in two ways that matter operationally. First, Enterprise is the only edition that can create a view-only user. Second, changing a role changes it for everyone holding it, so when one person needs different access, duplicate the role, assign the duplicate to that person, and edit the duplicate. If you need finer control over who can reach financial data without crippling their day-to-day work, the approaches under restricting what each person can open without limiting their work are worth reading alongside this.
Enterprise also offers Intuit Account User Management under Company > Users, where you add a user by name and email, assign a role, and send an invitation.
Certain actions are reserved for exactly two identities.
The Admin is the only user who can sign another user out of the company file, and the only one who can disable QuickBooks Messenger.
The External Accountant is the user type your accountant should have. Intuit recommends it explicitly: it “lets your accountant access your company file without the need to sign in as Admin,” grants access to all areas except customer credit card numbers, and, in the part that matters most for control, “your audit trail will track changes made by the External Accountant user.” Setting one up links it to the accountant’s Intuit account through an emailed invitation they accept before signing in. Intuit’s own help page for creating one currently renders its numbered steps inside a collapsed block that does not load, so follow the in-product wizard rather than a transcription of it. If you are simply bringing a firm into the file for the first time, the sequence for inviting your accountant into the file covers the surrounding decisions.
Everyone else hits a specific wall. Even with full access and even in single-user mode, a non-Admin, non-External-Accountant user opening Payroll Setup gets: “Only the QuickBooks administrator or an External Accountant can perform this action. You must reopen the company file and login as the Admin or External Accountant to do this.” Intuit confirms this is by design. Such users can still change payment and filing methods from the Payroll Center.
Intuit publishes no statement on whether the Admin consumes one of your licensed seats. Rather than guess, check it directly: sign everyone in, press F2, and compare the User Licenses figure against how many people are actually working.
To see who is signed in at any moment, use Company > Users > View Users. Signing somebody out is an Admin-only action, and the workflow for it sits with the single-user tasks that require it further down this page.
Multi-user failures feel random because the symptom rarely names the cause. They are not random. Every failure sits in one of the three layers Intuit’s own conditions describe, and each layer has a decisive test.
| Layer | What it governs | Typical symptoms | Decisive test | Usual fix |
|---|---|---|---|---|
| License | Whether QuickBooks will permit another session | Fourth user refused; activation prompts; version mismatch messages | F2 on each machine — compare User Licenses and the version and release number | Add seats; bring every machine to the same version year and release; activate the license |
| Windows | Whether the database service can open the file | H-code errors; “insufficient permissions”; service not running | Windows Services — is QuickBooksDBXX running? Does QBDataServiceUserXX hold all nine permissions on the folder? | Start the service, set it to Automatic, reapply permissions, rescan the folder |
| Network | Whether workstations can reach the server | Intermittent drops; “unable to communicate with the company file”; workstation sees the share but not the file | Ping the server by name from a workstation; confirm yourcompany.qbw.nd exists beside the .qbw | Open the ports, add the executables to the firewall, rename and regenerate the .nd |
Run them in that order. Layer one takes two minutes and rules out the problem that no amount of network work will fix.
Intuit’s position is unambiguous and worth quoting, because the internet’s position is not: “Error codes H202 and H505 (as well as H101 and H303) occur when something blocks the multi-user connection to your server computer.”
One cause, four codes. The neat per-code explanations you will find elsewhere — H101 means the workstation cannot find the server, H303 means missing configuration, H505 means wrong hosting — are field convention accumulated by technicians, not Intuit doctrine. They are often useful as a starting hypothesis and should never be treated as a diagnosis.
Intuit’s documented remediation splits along one line. For H202, work the server: run Database Server Manager and File Doctor from the Tool Hub, confirm both services are running, add the services to the Windows admin group, check the firewall, and ping the server from a workstation. For H505, H101 and H303, work the workstations: turn off Host Multi-User Access everywhere except the server. Site pages exist for each: error H202 raised by hosting and network configuration, error H505 on a workstation configured as a second host, the H101 remediation sequence and the workstation-side steps for H303. Each carries the full sequence for that code.
.nd file worksThis is the loop almost nobody closes, and closing it makes half of multi-user troubleshooting obvious.
Intuit documents the connection sequence in three steps. QuickBooks looks for the .nd file beside the company file. It reads the server contact information inside: the IP address and the port. It checks whether the .qbw is already in use, then tries to reach the server at that address. Success opens the file; failure produces an error describing what to fix.
.nd and rescanning rebuilds step two from current state.So a stale .nd sends the workstation to an address that is no longer right, whether after the server’s IP changed, after a port was renewed, after the file moved. The file is not corrupt in any interesting sense; it is simply out of date. Deleting or renaming it to .ndold and rescanning the folder in Database Server Manager regenerates it from current state. Intuit lists .nd alongside the transaction log and data source name files as the QuickBooks support files that can become damaged. The step-by-step for renaming the .ND and .TLG files to force a clean rebuild covers both.
Related service failures have their own pages: the QBDBMgrN service that will not start on the server and QBCFMonitorService failing to run.
Most cases come down to one of two patterns. If the host is in “hosting local and remote files” mode, the database process is tied to a Windows login session and ends when that user logs out or the machine sleeps, and everyone drops. And if a workstation is also hosting, the two database services compete for the same file and QuickBooks resolves it by collapsing to single-user. Check the hosting state on every machine before looking anywhere else. Recurring instability after a period of working fine is covered under multi-user mode that stops working after it was running fine.
These are not errors. QuickBooks Desktop uses pessimistic locking: it blocks the second person before they start, rather than letting them work and discarding it later. Intuit documents four message strings:
Intuit’s explanation is that “another user is doing a QuickBooks task that’s limited to one user at a time, even in multi-user mode.”
The practical version of the question is what happens to work already in progress. Because the block lands before the save rather than after it, a half-finished transaction stays on screen; you are prevented from committing it, not stripped of it. That is the meaningful difference from the browser version, where the second person completes the work and is then told it was discarded. When the message names someone, ask them to close and reopen QuickBooks, then confirm through Company > Users > View Users that they are gone. When it names nobody and nobody is signed in, the file has a stale lock: see a file reported as already in use when nobody is signed in. Messages that terminate the session rather than delay it belong to a different family, covered under abort messages that appear only in multi-user sessions.
When the layer is genuinely unclear, repairing company file and network faults with File Doctor tests hosting state, folder permissions, firewall ports and DNS resolution in one pass and tells you which one failed.
Say this plainly before anything else: local multi-user mode does not work across locations. It is not a remote-access feature. It shares one file over one local network, and there is no configuration of it that safely reaches a home office, a branch, or a laptop in a coffee shop. Opening the company file across the public internet through a file share, or through a sync folder, does not work reliably and does not fail cleanly.
Four options do work, and they are genuinely different products with different economics. One qualifier before the table: everything in this section describes QuickBooks Desktop for Windows. Intuit’s position on the Mac version is a flat no, “all workstations must be on the same network,” so Mac shops choose between hosting, migration, or moving the file to Windows, as the Mac section below sets out.
| Local multi-user | Remote Desktop Services | Intuit-authorized hosting | QuickBooks Online | |
|---|---|---|---|---|
| Works across locations | No | Yes | Yes | Yes |
| Concurrent users | Up to your edition’s seat limit | Up to 30, per Intuit’s 2014 RDS guide | Matches your QuickBooks seat count | 1 to 25, by plan |
| You still need QuickBooks licenses | Yes | Yes | Yes | No — the subscription is the license |
| Cost model | One-off hardware plus licenses | Server, Windows CALs, RDS CALs, licenses | Per user per month on top of licenses | Per month, all-in |
| Network requirement | Local network, ideally wired gigabit | 40 Mbps or higher, per Intuit | Broadband; latency to the host’s data center matters | Broadband |
| Who owns backup and restore | You | You | The host, within its stated retention | Intuit |
| Who supports it | You or your IT provider | You or your IT provider | The host for infrastructure, Intuit for QuickBooks | Intuit |
| Main limitation | Same network only | You build and maintain the server | Local printing, scanning and app compatibility | Feature differences from Desktop |
The table shows what the options are. Four questions eliminate three of them.
Does anyone actually need to work outside the office? If the answer is only “occasionally, and only the accountant,” stay on local multi-user and grant temporary access for that one case. Rebuilding the environment for an occasional visitor is the most common overcorrection on this topic.
Do you have in-house or contracted Windows administration? Remote Desktop Services is a server you build, patch and back up. Without someone who owns that job, it becomes the least reliable option rather than the cheapest, and authorized hosting exists precisely to buy that role.
Is Desktop-specific functionality load-bearing? Inventory assemblies, job costing, the Enterprise list capacities further down this page. If none of it is, QuickBooks Online removes an entire cost layer, because the subscription is the license rather than an addition to it. If any of it is, the browser version is a downgrade dressed as a solution.
Where does the arithmetic cross over? Hosting is a monthly per-user fee stacked on top of licenses you still pay for. RDS is a capital purchase plus Windows and RDS client access licenses, amortized over three to five years. Intuit publishes no crossover point, and neither does anyone else honestly. In our experience small teams with no IT tend to land on hosting, while teams above roughly ten users that already own server infrastructure tend to land on RDS. Price both against your own seat count rather than against a general rule.
This is Intuit’s own documented answer, and the one most small firms end up on. Users connect to a Windows server running QuickBooks; the application and the file both stay on the server and only screen output travels. Intuit’s guide puts it directly: RDS “allows QuickBooks users to work anywhere: in the office, on the road, from a satellite office, or from home,” supports up to 30 concurrent users depending on licenses purchased, and keeps QuickBooks data from ever being “directly transmitted outside the server.”
Intuit’s current install article treats a terminal server as a first-class scenario, and its published bandwidth requirement is concrete: “Your network requires a bandwidth of 40 Mbps or higher.” It even gives the measurement method: copy a file of at least 150 MB from the shared folder and calculate file size in MB × 8 ÷ seconds. Intuit’s RDS guide sizes the server for the fact that it carries the QuickBooks sessions as well as the database service. Its figures are 8 GB for 1 to 5 users, 12 GB at 10, 16 to 24 GB at 10 to 15, and 16 to 32 GB at 15 to 30. The first two bands match the general system requirements in the table above; the upper bands run higher, which is the right way round for a machine running everybody’s sessions. They come from a 2014 Intuit publication, so treat them as a floor rather than a current specification. Remote Desktop Services client access licenses are sold separately from QuickBooks. If the requirement is narrower, such as one accountant working occasionally, granting your accountant temporary remote access is a smaller solution than standing up a terminal server, and remote access in Enterprise 24.0 covers the current version’s specifics. Larger Enterprise deployments have their own considerations, set out under building a multi-user environment in Enterprise 24.0.
Intuit runs an authorized hosting program covering Pro, Premier, Accountant Desktop and Enterprise, described as letting you “run your QuickBooks Desktop and store your data files on a service provider’s servers.” As of August 2026 it lists 21 providers: AbacusNext, Ace Cloud Hosting, Apps4Rent, CloudVara, Coaxis, Infinitely Virtual, Itopia, MyVao, Nerds Support, Netgain, Network Alliance, Productive Computing, ProSource, Proxios, Rightworks, SKYLINE Cloud, Summit Hosting, Swizznet, Tandem CloudTop, Virtual Systems and XenWingo.
Read Intuit’s disclaimer before you read any vendor’s marketing: “Intuit doesn’t endorse, certify, sponsor, or guarantee the hosts’ services.” Support splits too: the host handles infrastructure and setup, Intuit handles QuickBooks itself, sometimes for a fee.
Intuit’s own hosted offering is powered by Rightworks. Your Rightworks user count must match your QuickBooks user count, and each person needs their own credentials. Two limitations are worth knowing before you commit: transfers go through the Rightworks File Manager, and users cannot reach local drives or local QuickBooks files from inside the hosted session. Backup retention is stated inconsistently by Intuit. One help article says 90 days across multiple locations, while the Enterprise hosting page says the last 45 days and up to 100 GB. Ask your provider which applies to your plan rather than assuming.
The trade-offs vendor pages rarely mention are real: the monthly per-user fee sits on top of your QuickBooks license rather than replacing it, printing and scanning to local devices needs configuration and sometimes does not work cleanly, third-party integrations must be compatible with the hosted environment, and you should understand how you get your data out before you put it in. If you later decide the model is not for you, leaving Enterprise cloud hosting without losing your data is a process, not a cancellation.
The browser version removes the problem rather than solving it: no hosting, no server, no ports. It is not feature-equivalent to Desktop, and for inventory-heavy or job-costing workflows the gaps matter. If your team has outgrown a single office rather than a single edition, weighing Pro Plus against Premier, Enterprise or the browser version is the decision worth making before the technical one.
Honesty is owed on two gaps, because filling them with invented authority is what most articles on this topic do.
VPN. Intuit publishes no position on running multi-user mode over a VPN, neither endorsement nor prohibition. Its documented answers for off-network access consistently route to terminal services or hosting instead. The practical objection is latency: a company file is a network file, not a client-server database, and the protocol is chatty enough that a VPN link with tens of milliseconds of round-trip delay produces performance that, in our experience, teams abandon quickly.
Consumer cloud sync. Likewise, there is no Intuit statement warning against Dropbox, Google Drive or OneDrive. The architectural objection stands on its own and is covered above. The one adjacent thing Intuit does say is about USB drives, and its answer there is to use a hosting provider.
Some operations rewrite structures the file cannot safely hold open, so QuickBooks reserves them for single-user mode. Intuit groups them like this:
| Category | Tasks that require single-user mode |
|---|---|
| Company file | Create portable company file; Rebuild Data; Condense Data; copy the company file for QuickBooks Online |
| Lists | Merging list entries |
| Import and export | Advanced Import; import timer activities; export lists to IIF; export timer lists |
| Workflow | Set closing date; manage fixed assets; assess finance charges for the first time; the 1099 wizard; change bank feeds mode; scheduled reports |
| Accountant | Create, save and send an Accountant’s Copy; send the company file to an accountant; batch delete or void transactions |
| Payroll | Manual payroll setup |
| Preferences | The Company Preferences tab — in multi-user mode, users can change My Preferences only |
Deleting individual list items is not on Intuit’s list, despite frequently appearing on other people’s. Merging entries is.
The switch itself is one click, File > Switch to Single-user Mode, but it will refuse while anyone else is in the file. The sequence that works:
Since Rebuild Data, Condense Data and the Accountant’s Copy all change the file structurally, take a fresh backup before you start. The scheduling options under backing up the company file on a schedule are worth setting up once for a shared environment, because a backup can only run when the file is not in use.
Readers land here from three adjacent situations often enough that all three are worth resolving.
Mac multiuser mode, which Intuit spells without the hyphen on Mac, is a different architecture, not a Mac-flavored version of the same one. There is no Database Server Manager. Instead, Intuit ships a separate macOS application called QuickBooks Server, described as letting you “share your company file with other users on the same network” without running QuickBooks itself on that machine.
Setup on the host runs through System Preferences rather than Windows dialogs: Sharing > File Sharing, add the company file’s folder under Shared Folders, and set Everyone to Read and Write. Then Security & Privacy > Firewall > Firewall Options > Allow Incoming Connections, on the host and on every workstation. Create a QuickBooks username and password for each person. Finally, sign in as admin on the host and choose File > Enable Multiuser Mode. Workstations then reach the file from the No Company Open window or the Shared Files section.
Mac toggles the mode differently, and this trips up people who administer both platforms. Windows swaps between two menu strings; Mac shows a checkmark beside a single Enable Multiuser Mode item, and selecting it again removes the checkmark and returns to single-user. Mac also has a mode Windows does not: File > Enable Multiuser Admin Mode disconnects everyone else so the admin can change preferences.
The restriction that matters most is Intuit’s own sentence: “You can’t share the company file with other remote workstations. All workstations must be on the same network to access the company file.” For Mac, remote multiuser access is not a configuration problem.
Mac and Windows users cannot work in the same live file at once either. Intuit never states this as a prohibition, but its documented workflow makes it unavoidable: moving a file between platforms requires an export and conversion, and Intuit’s round-tripping instructions tell the client not to enter anything while the accountant has the file. That is sequential custody, not concurrent access.
There is no hosting step and no mode toggle in QuickBooks Online. Concurrency is inherent to the browser architecture, and the only limit is how many seats your plan includes. Intuit’s user-management documentation contains no reference to single-user mode, multi-user mode or hosting at all.
| Plan | Billable users | Accountant firm users | Free roles |
|---|---|---|---|
| Simple Start | 1 | 2 | None |
| Essentials | 3 | 2 | Unlimited time-tracking-only |
| Plus | 5 | 2 | Unlimited time-tracking-only and reports-only |
| Advanced | 25 | 3 | Unlimited time-tracking-only and reports-only |
That Plus figure is worth stating twice, because at least one page currently ranking for these queries publishes 25 billable users for Plus. Intuit’s usage-limits documentation says 5. Advanced is the plan with 25. Check your own position under Settings > Account and settings > Usage. The wider picture of what the browser version offers in 2025 covers the feature differences that usually matter more than seat counts, and moving a Desktop file into the browser version covers what survives the trip.
The two products also handle collision in opposite ways, which is worth knowing if your team works across both:
| QuickBooks Desktop | QuickBooks Online | |
|---|---|---|
| Approach | Pessimistic locking | Last write wins |
| What the second user experiences | Blocked before starting, told to wait | Works normally, then loses the work at save |
| Message | “Another QuickBooks user is currently performing a task which must finish before you can continue.” | “You and another user were working on this at the same time. Another user finished before you did, so your work was not saved.” |
Multi-user mode is several people in one company file. Multiple companies is one person across several company files, and none of the configuration in this article applies to it. Pro and Premier open one company at a time; Enterprise and Accountant can open two simultaneously. Where the two topics genuinely overlap is payroll, and running payroll for two companies with separate EINs has rules of its own that catch people who assumed one subscription covers both.
Intuit’s position is exact and frequently misquoted: “QuickBooks’ performance decreases as the size of the company file increases,” and “there aren’t any limits on the size of your company data file.” The 150 MB threshold for Pro and Premier and the 1 GB threshold for Enterprise that circulate widely are not Intuit figures. They are folklore. Do not plan a migration around them.
What Intuit does publish is a list of levers, and they are the ones worth working through when a shared file slows down:
.tlg file that sits beside the company file and grows with every change since the last backupList capacity, not file size, is what most growing companies hit first:
| List | Pro and Premier | Enterprise |
|---|---|---|
| Chart of accounts | 10,000 | 100,000 |
| Combined names (customers, vendors, employees, other) | 14,500 | More than 100,000 |
| Items, including inventory | 14,500 | More than 100,000 |
| Items in assemblies | 100 | 500 |
| Classes | 10,000 | 100,000 |
| Price levels | 100 | 750 |
| Memorized transactions | 10,000 | 50,000 |
| Custom fields | 20 | 45 |
On Mac, the chart of accounts holds 10,000 and combined names, items, memorized reports and memorized transactions hold 14,500 each.
File > Utilities > Condense Data is single-user only and cannot be undone. Intuit is candid that it may or may not reduce file size, and it will not be offered at all if no significant change is expected. It does not remove open transactions, unpaid sales tax, undeposited funds payments, estimates linked to invoices, or improperly linked documents. It does damage reporting: item-based reports go blank for the condensed period, cash-basis reports become inaccurate, and class-filtered reports show unclassified amounts.
Treat it as a last resort, after a verified backup, and know how to restore from a backup when a shared file goes wrong before you run it. Where the real problem is years of accumulated mess rather than volume, cleaning up a company file that has grown unwieldy addresses the cause instead of the symptom.
When the server itself needs replacing, the sequence for moving QuickBooks to a new server machine matters more than usual in a multi-user environment, because every workstation’s .nd file points at the old address until the folder is rescanned on the new one.
Can I still buy a multi-user QuickBooks Desktop license in the United States in 2026?
Only Enterprise. Pro Plus, Premier Plus and Mac Plus closed to new U.S. subscribers after Sept. 30, 2024. The stop-sell is U.S.-only, and it closed new subscriptions rather than existing ones, so an inherited or acquired subscription is worth confirming as active before you plan seats around it.
Is there a QuickBooks Desktop 2025 or 2026 version?
No. Intuit stopped releasing numbered annual versions after 2024. The practical consequence is that “upgrade to the latest version” no longer means buying anything: you take the current release through Help > Update QuickBooks Desktop, and the version year on your title bar stays 2024 indefinitely. Vendors still advertising a 2025 or 2026 edition are relabelling 24.0.
Do all users need the same version and release of QuickBooks?
Same version year, yes, by license. Same release, in practice. The failure mode is worth knowing because it is silent: the first machine to open the file after an update writes the newer structure, and every machine still on the older release then fails to open it, usually with an error that names the network rather than the release. Update the server and all workstations in one sitting rather than as people notice prompts.
Can a Pro user and a Premier user open the same company file at the same time?
Yes, if both are the same version year. Two licenses do not add up, though: a 3-user Pro license and a 5-user Premier license give you whatever the host installation permits, not eight seats. Intuit also confirms that a file created in one industry edition opens in any other without affecting the data, so a Contractor Edition user and a Retail Edition user share a file without converting anything.
Can two people install QuickBooks with one license and both work at once?
No, and the arrangement people most often try is the one the agreement names: one license, two desks, “we never use it at the same time.” Section 3.1.4 permits no substitution of users, so sequential sharing is no more licensed than simultaneous sharing. What it does permit is the same person on two machines, which is why a bookkeeper with a laptop and a desktop needs one seat, not two.
Do I need a dedicated server, or can the file live on someone’s desktop PC?
A desktop PC works for two or three people. Before you spend on a server, check the cheaper fix first. In our own client work, complaints about a peer-to-peer setup usually trace to the host PC sleeping, being rebooted mid-afternoon, or running a heavy report rather than to the hardware itself. Disabling sleep on the host and scheduling its restarts solves more slowdowns than new hardware does.
Can I keep the company file on a NAS drive?
No, and the workaround people reach for does not work either. Pointing a Windows PC at a NAS folder and hosting from there fails for the same reason: Database Server Manager cannot monitor a mapped drive, so the folder never gets scanned and no .nd file is created. The working arrangement is the live file on the Windows machine’s local disk, with the NAS holding backups.
Can I put the company file in Dropbox, Google Drive or OneDrive?
Not the live file. There is a safe pattern, though, and it is worth setting up: back up to a local folder on the host, then let the sync client replicate the .qbb backup. You get off-site copies without ever asking a sync engine to arbitrate between two machines writing to the same open database.
Does the Admin user take up one of my licensed seats?
Intuit publishes no answer, and anyone stating one confidently is guessing. Test it rather than reasoning about it: have everyone sign in, press F2 on any workstation, and compare the User Licenses figure with the number of people actually working. Do the test before you buy seats, not after, because the difference between a 3-user and a 5-user environment can turn on this single question.
Why does QuickBooks keep dropping back into single-user mode?
Two causes, and one check separates them. Walk to each workstation, open File > Utilities without opening a company file, and read the label. If any machine other than the server offers to stop hosting, that is your answer. If they are all clean, the host is in “hosting local and remote files,” where the database process dies with the Windows session. Sessions that drop rather than change mode are a different fault, covered under connection to the company file being lost mid-session.
What happens if two of us open the same transaction at the same time?
QuickBooks Desktop stops the second person before the save, so nothing on screen is lost. The message names the other user, which is the part worth acting on: it tells you who to go and ask rather than leaving you to guess. Note that the block is not limited to transactions. Some tasks are single-user-only even in multi-user mode, so the person you have been waiting on may be running a report or a payroll step rather than editing your invoice.
How do I find out who is signed in and get them out?
Company > Users > View Users lists them. If the list looks wrong, cross-check it against the Database Server tab in Database Server Manager on the server, which reads live connections rather than QuickBooks’ own session record. A machine that crashed rather than closing cleanly often shows in one and not the other. Only the Admin can sign another user out.
Can QuickBooks Desktop multi-user mode work over a VPN?
Intuit publishes no position, and its own remote-access guidance routes to terminal services or an authorized host instead. Measure before you commit rather than trusting either opinion: ping the host across the link, then run Intuit’s own test: copy a file of at least 150 MB from the shared folder, multiply its size in megabytes by 8, and divide by the seconds it took. Intuit asks 40 Mbps of a terminal server, and a company file over the network is heavier than a terminal session.
How many users does each QuickBooks Online plan include?
Simple Start 1, Essentials 3, Plus 5, Advanced 25, plus two accountant firm users on every plan except Advanced, which allows three. The seat count is not usually what forces the upgrade. The 250-account chart of accounts limit on Simple Start, Essentials and Plus, and the 40 combined classes and locations on Plus, catch growing companies first. Check both under Settings > Account and settings > Usage.
How big can a QuickBooks company file get before multi-user performance suffers?
Intuit publishes no threshold and states there are no limits on company file size. Watch the numbers that do have published ceilings instead, since combined names and items cap at 14,500 in Pro and Premier. Treat the first symptom as diagnostic rather than the file size: reports slowing for everyone points at the host, while one workstation slowing points at that machine.
The setup itself comes down to three decisions and one rule. Decide which machine holds the file and let only that machine host. Confirm your edition allows the number of people you actually need before configuring anything. Give the QBDataServiceUser account real permissions on the folder, and scan it so the .nd file exists. The rule is that hosting lives in exactly one place, and most multi-user failures are a second machine quietly claiming the job.
If your people are not in the same building, none of that is your answer, and the honest choice is between a terminal server you maintain, an authorized host you pay monthly, or the browser version. If you would rather have someone configure and verify the environment with you, dedicated help with multi-user mode is available, and broader server and network faults in QuickBooks Desktop are documented separately for the problems that outlive a single fix.
Every figure, port, service name, menu string and seat count above was checked against Intuit’s published documentation and product pages during August 2026. The licensing quotations come from Intuit’s QuickBooks Desktop and Payroll End User License Agreement, United States, 2024 edition, retrieved on Aug. 27, 2026; because a license agreement can be revised without notice, verify any clause you intend to rely on against the current version.
Four things on this page have a shelf life and are worth re-checking before you act on them: which editions are still sold to new subscribers, the roster of authorized hosting providers, the current release number for version 24.0, and service discontinuation dates. Everything else, meaning the architecture, the permissions and the diagnostic method, changes only when Intuit changes the product.
Published by eBetterBooks. Last reviewed Aug. 27, 2026. Where Intuit’s own documentation contradicts itself, this page shows both readings rather than choosing one silently, and where Intuit publishes nothing it says so instead of filling the gap.