Multiple accounts on one PC: what sharing an app really means

Someone asking how to run multiple accounts on one PC and still share apps is usually asking four questions at once. Two people sitting at the same machine is a different problem from one person carrying a work identity and a personal identity. The fix lives in a different place for each, and picking the wrong place is why the second attempt feels no better than the first.

Four different things hide inside the word sharing

Pull the request apart and it separates into login state, the application itself, files, and notifications.

Login state is which identity a service currently sees. It lives in cookies and in the keychain, and it belongs to a browser profile or an operating system account, never to a tab.

The application itself is the binary sitting on disk. The question here is only who can launch it.

Files are documents and exports. Location and permissions decide who reaches them.

Notifications are sounds and badges. The question is whose screen an event lands on.

These four do not move together. Adding a user account to a Mac splits login state, files, and notifications, but leaves one copy of the application in place. Adding a browser profile splits login state and nothing else. Neither operation is wrong. They simply act on different layers, and the layers a given person needs to separate are rarely the same as the layers they end up separating.

One question sorts most cases: should the other person be able to see your documents? If yes, the fix is above the operating system. If no, the fix is at the operating system, and no amount of browser configuration will reach it.

Why the mismatch is expensive

A heavy tool aimed at a light problem does not fail loudly. It works, and then charges rent every day. Separating two Gmail identities with two macOS user accounts is functional. It also means logging out of a full desktop and into another one every time a client emails, several times an hour, forever.

What a macOS user account actually separates

macOS is built for more than one person at a keyboard, and Apple recommends an account per person so settings stay independent. Accounts come in three kinds with different reach: administrator, standard, and sharing only. Installing software is not restricted to the first kind.

Standard users can install apps and change their own settings, but can't add other users or change other users' settings. Source: support.apple.com

What genuinely separates is the environment around the software: desktop, bookmarks, saved sessions, and the home folder. A guest account exists for occasional users and gives them no access to other users' files or settings.

The sharing only type is the one most people never look at, and it fits a common need. That user can reach shared files remotely but cannot log in to the computer or change settings. When a contractor needs a folder and nothing else, this is smaller than handing over a full account.

Automatic login deserves one line of caution. Turning it on means a restart is enough for anyone to land inside that environment, which is why Apple advises against pointing it at an administrator. With FileVault on, automatic login is disabled anyway.

Fast switching is not logging out

macOS offers fast user switching, which moves between accounts while more than one user is logged in at the same time. It can sit in the menu bar or in Control Center, and on a Mac with Touch ID a finger on the sensor is enough to change seats.

The word to notice is simultaneously. Nobody logged out. The previous account keeps its applications open, holding memory and continuing to work. Two browsers loaded with a full day of tabs, both resident, behave the way one browser with twice the tabs behaves.

The second cost is quieter. Notifications from the account nobody is looking at do not appear. For two people sharing a household machine that is the correct behavior. For one person splitting work from personal, it means a message arriving in the half that is currently parked stays invisible until the next switch, which might be hours.

The useful test is who is sitting down. Different people, separate operating system accounts. Same person, different roles, and the separation belongs higher up, because the number of switches per day is what decides whether the method pays for itself.

Installed once, signed in separately

Whether several accounts on one machine can launch the same application, and whose identity that application is signed into, are unrelated questions. The first is about a file on disk. The second is about credentials stored inside each home folder, which do not travel between accounts even when the icon in the Dock looks identical.

Subscriptions follow the same shape. Microsoft states plainly that sharing a household plan does not connect the accounts involved: a Microsoft 365 Family subscription can be shared with up to 5 other people, and the shared accounts are not linked, with email, photos and OneDrive files staying private.

So what gets shared is the right to use something, not its contents. Five people on one plan still have five separate mailboxes. That is not a limitation to work around. It is what correct sharing looks like.

The inverse is where trouble starts. Passing a password around shares the right and the contents together, permanently fused, and there is no later operation that unfuses them. Plenty of people who believe they have an app sharing problem actually have a shared credential problem that has not surfaced yet.

File sharing is a separate setting, not an account favor

Handing over a document does not require handing over an identity, yet shared logins often begin exactly there. macOS keeps file sharing as its own setting, under General and then Sharing in System Settings. For Windows machines on the network, turning on sharing over SMB and selecting which user accounts may connect is the documented path.

What the other side needs is the network address of the Mac plus a user name and password for it. The address appears under the File Sharing indicator once sharing is on. Each Windows person needs a corresponding account on the Mac.

Apple attaches a maintenance note to this route that is easy to skip: because passwords for accounts used in Windows sharing may be stored in a less secure manner, those accounts should be turned off when not in use, and turned off before Windows sharing itself is disabled.

The principle underneath is worth keeping. If the goal is a document, open a document path. If the goal is collaboration inside a service, use the invitation and permission features that service already has. Cases that genuinely require two people to hold one credential are rarer than the search volume suggests.

It is also worth separating the one-off case from the standing case. Sending a contract to an accountant once a quarter does not justify configuring network sharing at all, and a link or an attachment ends the matter. Standing access to a working folder is where the setting earns its complexity, because the alternative is a stream of manual sends that quietly turns into a stream of stale copies. The failure mode of shared credentials is exposure. The failure mode of manual sending is disagreement about which version is current, and it is the more common of the two.

The same split exists on Windows, described in Microsoft's own words

The advice above is not a macOS peculiarity. Microsoft describes the shared machine case in almost the same terms, listing it as one of the ways accounts work next to each other rather than merging: using different accounts on a shared Windows PC lets several people use the same device while each keeps their own sign-in information, files, browser favorites, and desktop settings.

Read that list closely and the same four layers appear. Sign-in information is login state. Files are files. Desktop settings and favorites belong to the environment. What the sentence does not promise is any merging of the identities themselves, and that omission is deliberate: Microsoft says elsewhere on the same page that personal accounts cannot be linked, merged, or combined.

The practical consequence for anyone moving between a Mac and a Windows machine is that the mental model transfers. An operating system account is a boundary around an environment. It is generous with files and settings and silent about identity. Anything that needs identity separated more finely than one environment per person has to be solved by the software running inside that environment, on either platform.

There is one asymmetry worth noting. On a shared Windows PC the second account is usually a second person, so the heavier boundary matches the need. When a single person creates a second Windows account purely to hold a second work identity, the same switching cost described earlier applies, for the same reason: the environment being changed is much larger than the thing that needed to change.

Matching the layer to the setting

Layer to separate	Where the fix lives	What stays merged
Login state	Browser profiles, per app windows	Files, machine settings
The application	Installation and account privileges	Each person's signed-in identity
Files	User accounts, file sharing settings	Where notifications land
Notifications	Per app notification settings, window placement	Billing and permissions

Read the table down and one thing becomes clear: no single action covers all four rows. Read it across and the side effects appear. Reaching for a second user account to split two logins also splits notifications. Reaching for a second browser profile to hide documents does nothing, because the home folder never divided.

Frequency is the other axis. Whatever gets switched twenty times a day belongs on the lightest mechanism available. Whatever gets touched twice a year can afford a heavier, firmer boundary. Putting a twenty-times-a-day action on an operating system account means paying that weight twenty times a day.

When two layers must move for the same person, such as a contractor who needs a folder and a service login, resist doing both in one gesture. Grant the folder through file sharing and the login through the service's own invitation. Two doors can be closed one at a time. One door cannot.

What to change first

Write down, in one line, the layer that is actually bothering you today: login state, application, files, or notifications. If the answer is login state and the same person is doing all the switching, the operating system is the wrong place to fix it, and a browser that gives each service its own window and its own session is the layer that matches. The shape of that approach is described in Features, how roles get bundled is in Workspaces, and the difference in separation model between products in this category is laid out in Compared with Wavebox. If a tool is worth adopting for this, it is SpaceDeck or anything else that separates the exact layer you wrote down, and nothing broader.