Fix Word Presence Indicators Showing Stale User Sessions in Co-author Mode

When you co-author a document in Word, presence indicators show colored flags or profile pictures next to the names of other editors. These indicators are meant to update in real time as people join or leave the document. But sometimes the indicator shows a user who already closed the file hours ago, or it fails to show a new collaborator who is actively editing. This problem happens because Word’s real-time co-authoring service relies on a persistent connection to Microsoft 365, and that connection can become stale when network interruptions, browser caching, or delayed sync events prevent the session list from refreshing. This article explains the root causes of stale presence indicators and provides a set of practical steps to force a clean refresh, clear cached sessions, and restore accurate co-author status.

Why Presence Indicators Show Stale User Sessions

Word’s co-author presence system uses a combination of WebSocket connections and periodic HTTP polling to track who is currently editing a document stored in OneDrive, SharePoint, or Microsoft 365. When a user opens the document, Word sends a join event to the server. The server updates a session list and broadcasts the new presence to all other active clients. When the user closes the document or navigates away, Word sends a leave event. If the leave event is not delivered, the server continues to show that user as active.

Network Interruptions and Unclean Disconnects

The most common cause of stale presence indicators is an unclean disconnect. If a user loses Wi-Fi, closes their laptop lid, or kills the browser tab without waiting for the leave event to transmit, the server never receives the departure signal. Word then continues to display that user’s indicator until the server’s session timeout expires. The default timeout is typically 60 to 120 seconds, but under heavy load or misconfigured network proxies, the timeout can extend to several minutes.

Cached Session Data in the Client

Word desktop and Word for the web both cache session information locally. If the cache is not invalidated after a network change or after another user leaves, the client may continue to render outdated presence data. This is especially common in Word for the web, where the browser’s Service Worker and IndexedDB store presence state across page reloads.

Delayed Sync From the Server

In large SharePoint document libraries or when co-authoring with many users, the server may batch presence updates to reduce load. This batching can cause a delay of up to 30 seconds between a user leaving and the presence indicator disappearing. If the server is under high demand, the delay can be longer, making the indicator appear stale even though the server will eventually correct it.

Steps to Force Refresh Presence Indicators in Word

Use the following methods in order. Start with the simplest refresh and escalate only if the problem persists.

Method 1: Manual Refresh in Word Desktop

1. Press Ctrl+Alt+F5
   This keyboard shortcut sends an immediate request to the server for the latest session list. The presence indicators in the ribbon and in the Share pane will update within a few seconds.
2. Open the File menu and select Info
   Click File > Info. On the Info page, locate the Manage Document section. Click the Refresh button directly above the document thumbnail. This performs the same action as Ctrl+Alt+F5.
3. Close and reopen the document
   If the refresh does not clear the stale indicator, save the document, close Word completely, and reopen the same file. This forces a new connection to the server and discards the local session cache.

Method 2: Refresh in Word for the Web

1. Reload the browser tab
   Press Ctrl+R or F5. This reloads the entire Word for the web application and re-establishes the WebSocket connection. Presence indicators usually update immediately after the reload.
2. Clear browser cache and cookies for the Microsoft 365 domain
   Open your browser’s developer tools (F12), go to the Application tab, and select Clear storage. Check the boxes for Cache storage, Cookies, and IndexedDB. Click Clear site data. Then reload the tab. This removes any stale session state stored by the browser.

Method 3: Force Server-Side Session Cleanup

1. Ask the stale user to close the document properly
   If the user shown in the stale indicator is available, ask them to open the document and then close it using File > Close. This sends a proper leave event to the server.
2. Use SharePoint to remove the user’s session
   If the user is not available, go to the SharePoint library or OneDrive folder that contains the document. Open the document in the browser. In the top-right corner, click the presence indicator of the stale user and select Remove from session. This option is only available to the document owner or a site administrator.

If Presence Indicators Still Show Stale Sessions After the Main Fix

Word for the web shows a ghost user who is no longer editing

If the refresh and cache clear did not work, the stale session may be stuck in the server’s session table. Have the document owner or a SharePoint administrator run the following: Navigate to the document library, select the document, click the ellipsis (…), choose Manage access, and then remove any users who no longer need access. This forces the server to terminate all active sessions for that document. After removing the user, the document owner should add them back if needed. This is a last-resort method because it disrupts co-authoring for all current users.

Presence indicators flicker or show the wrong user name

This is often a browser extension conflict. Disable all extensions that modify page content, such as ad blockers, grammar checkers, or translation tools. Reload the document. If the indicators stabilize, re-enable extensions one by one to identify the culprit. In Word desktop, the same symptom can be caused by a corrupted Normal.dotm template. Rename the template file to Normal.old and restart Word. Word will create a fresh template.

Presence indicators do not appear at all for any user

This indicates a broader connectivity problem. Verify that the document is stored on OneDrive, SharePoint, or Microsoft 365. Local files do not support co-authoring presence. Check that all users have signed in with the same Microsoft 365 tenant account. If the document is stored in a SharePoint site that uses a custom domain, presence may be blocked by the browser’s third-party cookie policy. Add the SharePoint site to the browser’s allow list for cookies.

Word Desktop vs Word for the Web: Presence Refresh Behavior Differences

Item	Word Desktop	Word for the Web
Refresh shortcut	Ctrl+Alt+F5 or File > Info > Refresh	Browser reload (Ctrl+R or F5)
Cache location	Local session cache in AppData	Browser Cache, Cookies, IndexedDB
Server session timeout	60–120 seconds	60–120 seconds
Force session removal	Not available in desktop UI	SharePoint Remove from session option
Effect of network interruption	Indicator may stay until timeout	Indicator may stay until timeout

The core behavior of presence timeout is identical on both platforms. The key difference is how the client-side cache is cleared. Word desktop stores session data in a local file, while Word for the web relies on browser storage. Both platforms require a server-side timeout or manual intervention to remove a truly stuck session.

After applying the steps in this article, you can now identify stale presence indicators, force a refresh using Ctrl+Alt+F5 or a browser reload, and clear cached session data when the refresh is not enough. For persistent ghost sessions, use the SharePoint Remove from session option. As an advanced tip, consider enabling the Co-authoring settings in the Microsoft 365 admin center to reduce the session timeout from 120 seconds to 30 seconds for faster presence cleanup in collaborative environments.