Windows account privacy
Sharing a Windows Travel Laptop? Use Separate Accounts
Prepare separate Windows accounts, browser sessions and file access before handing a travel laptop to another person.

Agree what the other person needs
Sharing a travel laptop often begins with a small request: print a ticket, join a call or finish a booking. Before handing over the keyboard, agree whether the other person needs a short browser session or their own working space for several days. That decision helps you choose the account and avoid exposing a personal desktop simply because the Wi-Fi is convenient.
A VPN connection does not decide which person can open an email app or see a document already on the screen. Plan the local handover separately from the network connection. For a borrowed employer-managed computer, ask the responsible administrator which sharing arrangement is allowed. Do not add another person or change organisation settings on your own.
Create a separate Windows account
On a personally owned Windows laptop, the owner can review Settings > Accounts > Other users and add the intended user. Follow Microsoft's Windows account management instructions for the available Microsoft-account or local-account route. Let the person enter their own sign-in information privately. Avoid putting a shared password into a travel group chat.
Use a standard account for ordinary activities unless there is a specific, understood need for administrative access. Microsoft explains that administrators can change settings, install software and access all files. Separate accounts therefore do not make sensitive material inaccessible to the device administrator. If that level of trust is unsuitable, use a different device rather than promising isolation the laptop cannot provide.
Try the agreed task from the new account while the owner is available. Check that the required app opens and that the user knows where to save their own work. A missing app is a question for the owner or publisher; it is not a reason to hand over the owner's Windows credentials.
Check the browser and the files separately
Microsoft's Edge profile guidance describes separate browser settings, bookmarks and extensions. Treat that as a browser feature, distinct from choosing the Windows user. Confirm the active browser profile and signed-in website account before opening personal services. A familiar profile picture can otherwise conceal a mistaken assumption about whose session is active.
The incognito, cookies and VPN guide explains the limits of a private browsing window. Choose a suitable Windows account first, then the browser arrangement for the task. Closing one browser window does not explain what happened to a file saved elsewhere or an app left running on the desktop.
Share only the document needed for the journey or appointment. Review the cloud file-sharing permissions checklist before sending a link. Agree who may open it and which copy should be edited. Avoid sharing a whole folder merely to make one ticket or meeting note easier to find.
Finish your own session before the handover
Microsoft distinguishes locking, signing out and switching Windows users. Locking keeps the current apps open; switching users also leaves the earlier session running. Signing out closes its apps, so save work first. Choose deliberately instead of assuming those actions produce the same result.
For a longer handover, finish outstanding work and sign out of your own Windows session before the other person signs in. For a brief interruption when you remain the user, locking may suit the situation. Keep each person's sign-in method private and make sure the owner can return to their own account without depending on the visitor.
Use the Windows clipboard privacy checklist to review information you copied during your own work. This is a separate preparation step, not a claim that clipboard contents necessarily cross Windows accounts. If the next task includes presenting a call, the screen-sharing privacy guide helps choose the intended window and check what participants can see.
Review the connection in the new session
After the intended user signs in, check their actual connectivity and the VPN publisher's current instructions. Do not assume that changing Windows users creates a separate VPN entitlement, resets a connection or gives each person a different network route. The scope of an installation and its settings must come from the supported configuration, not the colour of the account picture.
Keep work and personal VPN instructions separate. A visitor should not inherit permission to use an employer's resources simply because the laptop can reach them. If the task needs organisational access, ask the responsible team for the approved arrangement. Avoid saving someone else's activation details in a general handover note.
Close the sharing arrangement carefully
At the end, let the visitor collect their own documents through the agreed route and sign out of services they used. Confirm that an important file is available where they expect before discussing account removal. Microsoft's account guidance notes that removing a Windows user removes that user's sign-in information and data from the device; it does not delete their Microsoft account.
Have the owner handle that decision after the visitor confirms the handover. Keep the useful outcome note short: which account was used, which document was delivered and whether any access still needs attention. Separate accounts, a deliberate session change and a checked file handover each answer a practical question. A connected VPN indicator cannot replace those local checks.
