Quick Answer: If you are finding iManage down and not able to login, first verify the global iManage server status via the official Trust Center. If their cloud servers are online (green), the issue is likely local. Fix this by completely closing the iManage Work Agent in your system tray, clearing your browser/WebView2 cache, and ensuring your corporate VPN or Single Sign-On (Okta/Azure AD) session has not expired.
For law firms, accounting agencies, and enterprise businesses, iManage Work 10 is the central nervous system for document and email management. When you suddenly cannot log in, the inability to file emails or access critical contracts brings productivity to a screeching halt. Because iManage relies on a complex web of cloud architecture, local network security, and desktop agents, pinpointing the exact cause of a login failure requires a structured approach.
Let’s break down how to determine if the outage is on iManage’s end or your IT department’s end, and the fastest ways to regain access to your documents.
Why is iManage Not Letting You Log In?
Login failures in the iManage ecosystem generally fall into three categories: global cloud outages, localized network/VPN blocks, and desktop client desynchronization. Knowing which error you are facing saves you hours of pointless troubleshooting.
| Symptom / Error Message | Likely Root Cause | Recommended Action |
|---|---|---|
| “Cannot connect to server” (Timeout) | iManage Cloud outage or corporate firewall blocking access. | Check iManage Trust page; Verify VPN connection. |
| Infinite loading loop on SSO screen | Stale Azure AD/Okta tokens or WebView2 cache issue. | Clear browser cache; Restart iManage Work Agent. |
| “Invalid Username or Password” | Active Directory sync delay or expired local network password. | Reset Windows network password; Contact IT Helpdesk. |
How to Check the Official iManage Server Status
Before you alter any settings on your computer, you must verify if the iManage Cloud itself is experiencing degradation. iManage maintains detailed, regional status dashboards for all of their data centers (US, UK, EU, AP).
To check real-time uptime, visit the iManage Trust Center Status Page. Look for your specific region (e.g., US Cloud, UK Cloud). If you see a yellow “Degraded Performance” or red “Service Interruption” indicator next to Work 10, the issue is on their end. You will simply need to wait for their engineers to resolve it.
Immediate Fixes for Local iManage Login Issues
If the Trust Center shows all systems are operational, the login block is happening locally on your machine or within your firm’s network infrastructure. Follow these troubleshooting steps to force a fresh connection:
- Restart the iManage Work Agent: Do not just close Microsoft Word or Outlook. Go to your Windows system tray (bottom right corner), right-click the iManage logo (the blue ‘i’), and select Exit. Then, relaunch it from your Start menu.
- Verify Your Corporate VPN/SSO: iManage is strictly gated by Single Sign-On. If your firm requires a VPN (like Cisco AnyConnect or GlobalProtect) to access cloud services, ensure it is connected and authenticated. If you frequently face authentication loops, review our guide on fixing corporate VPN and SSO token errors.
- Clear Browser and WebView2 Cache: The iManage login prompt relies on Microsoft Edge WebView2. If the cache gets corrupted, the login window will go blank. Clearing your default browser’s cache (Edge or Chrome) often resolves this.
- Disconnect from “Offline Mode”: Sometimes, iManage will intentionally block login attempts if the local client is stuck in Offline Mode. Check the Work Agent status to ensure it says “Connected” rather than “Working Offline.”
TL;DR: Solving iManage Login Failures
- Check Trust Center First: Always verify the iManage status page to rule out a global data center outage.
- Kill the Background App: Exiting the iManage Work Agent from the system tray and restarting it fixes most minor desyncs.
- Check Your Tokens: Ensure your network password hasn’t expired and your Okta/Azure AD connection is active.
- Call IT for Blank Screens: If the login window is completely white, your IT department may need to reset your WebView2 registry keys.
