Working in Clio

OneDrive not connecting to Clio?

Most connections that never complete fail for one of three reasons: Clio's Microsoft document source connects OneDrive for Business and not a personal account, connecting one is an administrator action inside Clio, and some Microsoft 365 tenants require an administrator to consent to third-party apps before anyone can authorize them. Past that, this guide works the other symptoms firms report — folders that come back duplicated after a rename, files that never sync because of a character in the name, slowness at firm scale, and the gap between Microsoft 365 permissions and Clio matter access. Confirm any vendor menu path in Clio's or Microsoft's help center, since both move.

By Lucas Barnes, Founder · Last updated July 24, 2026

Why it breaks the way it does

A mirror between two clouds

Nearly every OneDrive-and-Clio problem gets easier once you accept one sentence: Clio's Microsoft document source is a server-to-server mirror between Clio and OneDrive for Business, not a sync client running on your computer. Nobody's laptop is involved. An administrator authorizes the connection once, Clio creates a root folder in OneDrive with per-client and per-matter subfolders underneath it, and from then on the two clouds keep that structure aligned between themselves.

That matters because there are usually three separate layers in play, and people report all three as "OneDrive isn't working with Clio". Layer one is the cloud-to-cloud mirror described above. Layer two is the OneDrive sync app in your system tray, which copies your Microsoft 365 files down to the machine you're sitting at — it knows nothing about Clio. Layer three is Clio Drive, Clio's own desktop client, which mounts Clio's storage and has nothing to do with Microsoft at all; its failure modes are covered separately in the Clio Drive guide. Work out which layer is actually broken before you change anything. A fix aimed at the wrong layer is wasted at best and destructive at worst.

Figure A · Two things called "OneDrive sync"

One runs between clouds, one runs on your desk

The same complaint — "OneDrive isn't syncing" — points at two unrelated systems. Deciding which one before you touch anything saves most of the wasted troubleshooting.

The Clio document source

Cloud to cloud, authorized once

What it connects: Clio Manage and a OneDrive for Business account, server to server, with no software on any workstation.
Breaks when: Authorization lapses or is revoked, the wrong account type is used, or somebody reorganizes the folders Clio created.
Where you check it: Clio's app settings, as an administrator — and the folder tree Clio built in OneDrive.

The OneDrive sync app

Microsoft cloud to this computer

What it connects: Your Microsoft 365 storage and the local folder on the machine you're sitting at. It has never heard of Clio.
Breaks when: The machine is offline or paused, the account is signed out, item counts get large, or a filename is unusable.
Where you check it: The OneDrive icon in the Windows system tray or the macOS menu bar, on that specific machine.

If the file is missing in the Clio web app, the mirror is the suspect. If it's missing only on one computer, the mirror is fine and the sync app isn't.

A third system, Clio Drive, mounts Clio's own storage on the desktop and involves Microsoft not at all — it belongs to a different troubleshooting guide entirely.

One warning before the table, because it's the only genuinely destructive-adjacent mistake here: don't rename, move or reorganize the folders Clio creates in OneDrive. Clio rebuilds what it no longer recognizes, which leaves two folders where you wanted one and half the firm saving into the stale copy. Change the contact or matter name in Clio instead, and let it propagate outward.

Find your symptom

Symptom, cause, and what to check

Symptom	Likely cause	What to check
The connection never completes	Personal OneDrive account rather than OneDrive for Business, or a non-administrator attempting it	Retry as a Clio administrator, signed into the Microsoft 365 work or school account
Microsoft sign-in ends in a consent error	The tenant requires administrator approval before users may authorize third-party apps	Ask your Microsoft 365 administrator to grant tenant consent, then reconnect
Connected, but no folders appear yet	First pass still building the client and matter tree	Give the initial build time before treating it as a fault; confirm the root folder exists where Clio put it
A matter folder reappears duplicated or empty	Somebody renamed or moved a Clio-created folder from the OneDrive side	Restore the original name; make future name changes in Clio, never in OneDrive
Most files sync, a few never do	Reserved character in the name, a leading or trailing space, a trailing period, or an over-long full path	Rename the offending file and shorten the folder path above it
Files are in Clio's web app but not on one PC	The OneDrive sync app on that machine — a different layer entirely	Check the OneDrive icon in the system tray or menu bar on that machine; the Clio connection is not involved
SharePoint library can't be selected	SharePoint is not a Clio Manage document source	Nothing to configure — use one of the workflow paths instead
People see files their matter access should hide	M365 group permissions and Clio matter access are separate systems	Audit who can reach the mirrored OneDrive location, not just the Clio matter

Two rows deserve emphasis, because they may not be faults at all. "Connected but nothing yet" is often just the initial build; a firm with a long client list gets a large folder tree, and it's worth giving that a while before escalating. "SharePoint can't be selected" has no fix in this direction. It's an absent capability rather than a broken one, and the honest answer is to stop looking for the setting. Everything else here has somewhere concrete to look.

The most common one

The connection that won't establish

Start with the account type. It's the single most frequent cause, and it presents as a generic failure rather than a helpful message. Clio's Microsoft document source connects OneDrive for Business — the storage attached to a Microsoft 365 work or school account. A personal Microsoft account won't connect, and the attempt tends to look like a Clio problem when the mismatch is on the Microsoft side. Firms that run a mix of both, which is more common in small practices than anyone admits, spend a surprising amount of time retrying with the wrong sign-in.

Next, rule out the two authorization gates. Connecting a document source in Clio is an administrator action, so a paralegal trying it from their own login won't get far. On the Microsoft side, many tenants are configured so that users can't consent to third-party applications on their own — in that setup the Microsoft sign-in itself fails with a consent message, and only a Microsoft 365 administrator can approve it. Read the error text carefully: whether the failure names Clio or names Microsoft tells you which side of the handshake to fix. Confirm the current settings path in Clio's help center rather than hunting for a menu that may have moved.

A connection that worked and then stopped is a different animal. Authorization for a connected app can be revoked, expire, or lapse when something changes about the account that granted it — which is why these connections often break around the time the person who set one up leaves the firm or has their account reworked. If the connection was authorized from an individual's account, it's only as durable as that account. Reconnecting is normally straightforward. The durable fix is to authorize from an account the firm intends to keep, and to write down who owns the connection so the next departure doesn't silently break it.

When a few files never arrive

Filenames, commas, and path length

If almost everything syncs and a handful of files stubbornly don't, suspect the name before the connection. Microsoft blocks a reserved set of characters in OneDrive and SharePoint names — " * : < > ? / \ | — and also rejects names that start or end with a space or end with a period. There's a separate limit on the length of the entire path, counted from the root through every folder to the filename itself, and a few reserved names inherited from old Windows conventions. The details have changed over the years. Microsoft publishes the current list and the current path figure; check theirs rather than trusting a number from a blog post.

Commas aren't on the blocked list, which disappoints people who arrive convinced they're the problem. A comma won't, by itself, stop a file from syncing. What commas actually do is arrive by the hundred: a firm that names contacts in last-comma-first style gets that comma baked into every generated client folder, and from there into every path, every export, and every script that treats a comma as a separator. If you want them gone, change the contact or matter name in Clio. Never the folder in OneDrive, for the reason given above.

Path length is the quieter version of the same problem, and it's structural rather than per-file. Long client names plus long matter names plus a deep folder convention plus a descriptive filename add up faster than anyone expects, and the file that finally breaches the limit gets no explanation. Firms that hit this repeatedly usually fix it upstream by shortening the naming scheme rather than trimming individual files; the pattern that works is covered in the naming conventions guide. A folder full of agreement-FINAL-v3-actually-final.docx is a readability problem on a good day and a path-length problem on a bad one.

At firm scale

Can a large firm run this with a lot of files?

Yes, with planning — and the honest caveat that the failure mode at scale is slowness and confusion rather than a clean error. The mirror creates a folder for every synced client and every synced matter, so the shape of the folder tree is set by your matter count, not by how many documents you actually keep in Microsoft. A firm with several thousand matters, most of them long closed, gets several thousand folders whether or not anything useful is in them. Empty folders search beautifully and help nobody.

Two ceilings show up first, and neither announces itself. You notice sync lag and missing files, then work backwards. One is item count: Microsoft publishes guidance on how many files the OneDrive sync app is expected to handle across all synced libraries before performance degrades, and a firm mirroring every matter can approach that figure without anyone watching for it. The other is total path length, which large firms reach sooner because their client and matter names run longer. Check Microsoft's current numbers against your own matter count before a firm-wide rollout rather than after.

The practical move is to be selective rather than complete: mirror what the firm actively works on in Microsoft and leave the archive in Clio, where matter documents already live and where the per-file limit is 5 GB. A pilot on one practice group before enabling it firm-wide will tell you more than any published number. Storage capacity, retention, and where the archive should sit are laid out in the guide to Clio file management and storage limits.

Who can see what

M365 groups against Clio matter access

The question firms ask most often here — can an administrator see every matter? — bundles two different systems, and the answer differs for each. Inside Clio, document visibility follows matter access lists, and administrators are the people who write those lists; an administrator can generally reach any matter, if only by granting themselves access first. That's a deliberate design, not a leak. It's why access management belongs with a small number of trusted people rather than with whoever is setting up matters that week. The internal picture is worked through in the document permissions guide.

The mirror is where the surprise lives, and what makes it specific to this integration is that nobody chose it per document. A file copied by hand from Microsoft into a matter is a decision someone made once. The mirror is standing infrastructure: it creates a folder for every synced client and matter automatically, so the second copy exists whether or not anyone thought about it. Those folders sit in a Microsoft 365 account and are governed by Microsoft's permission model — Entra groups, Microsoft 365 groups, site and folder permissions — which knows nothing about Clio matter access and can't be configured from Clio. Anyone who can reach that OneDrive location sees what's in it, however tightly the matching Clio matter is restricted. In most tenants a Microsoft 365 administrator can obtain that access through ordinary tenant tooling.

Two diagnostic consequences follow. First, tightening a matter's access list in Clio doesn't retract anything already mirrored, so a matter restricted after it was synced needs the Microsoft side checked separately rather than assumed. Second, the account that authorized the connection is the one to ask about: start there, not with the firm's general M365 group structure. If the answer is uncomfortable, the options are to restrict the Microsoft location to match or to keep the matter out of the mirror altogether. Sealed proceedings, investigations into firm members, and anything under a heightened confidentiality obligation are the obvious candidates. The design-level version of this question, including how to structure Microsoft sites against matter access lists in the first place, is worked through in the OneDrive and SharePoint workflow guide.

Changing the backing store

Switching or disconnecting the document source

Changing which cloud store backs your documents is an administrator action taken in Clio's app settings, in the same place the connection was made. Clio Manage supports a short, fixed list of native document sources: Dropbox, Box, Google Drive, NetDocuments and OneDrive for Business. The exclusions are provider-specific rather than a single rule, so read the limits for the provider you're moving to rather than assuming they match the one you're leaving. That comparison, provider by provider, is in the integrations guide.

Two things to settle before you disconnect anything. First, documents that already live in Clio stay in Clio; dropping a document source doesn't empty the matter file. But the mirroring stops, so anything added on the storage side afterwards simply won't appear. Nobody gets told. Second, connecting a different account or a different provider generally begins a fresh folder structure rather than adopting whatever is already there, so expect a window in which two structures coexist and staff need telling explicitly which one is live. This isn't a step to discover the semantics of on a Friday afternoon. Confirm the current disconnect behavior in Clio's help center before doing it on a working firm.

If what you actually want is SharePoint rather than OneDrive, there's no setting to change. SharePoint libraries aren't a Clio Manage document source, so the choice is between mirroring a OneDrive for Business account and using a workflow that doesn't rely on a native connection at all. Which of those fits depends on volume and on how much Microsoft tooling your firm already pays for. That decision is the subject of the OneDrive and SharePoint workflow guide, which compares the four practical routes rather than diagnosing a broken one.

The dependable fallback

When you just need the file in the matter

Most of what goes wrong here is a connection problem, and connection problems are worth fixing properly rather than working around forever. But they're rarely worth fixing at four o'clock on a filing day. Clio's web Documents area takes drag-and-drop and handles multiple files and folders directly in the browser, with no cloud-to-cloud mirror and no sync client anywhere in the path. No failure mode on this page blocks it. That's the route when something has to land in the matter now.

For recurring inbound documents rather than one-offs, the same instinct scales: bulk upload in the browser and browser extensions that file a document straight from the page it's on both skip the integration layer entirely. For the mail-borne share of that volume, a Microsoft 365 firm already has a first-party route that touches no document source at all: Clio's Outlook add-in files a message and its attachments from the reading pane, on the same mailbox the mirror is failing beside. If the browser upload is itself the thing failing — stalls, size limits, unhelpful error text — that's a separate problem with its own fixes, in the upload troubleshooting guide.

And if you've concluded that the mirror isn't the right architecture for your firm rather than merely misconfigured, that's a legitimate conclusion. Read the workflow comparison for the alternatives, and the Clio Drive guide if the thing you were actually troubleshooting turns out to be Clio's own desktop client rather than Microsoft's.

OneDrive and Clio troubleshooting FAQ

Got more? Email [email protected].

Q.01

Why won't OneDrive connect to Clio?

Three causes account for most failed connections. First, the wrong account type: Clio's Microsoft document source connects OneDrive for Business, the work or school account that comes with Microsoft 365. A personal OneDrive account isn't supported, and the connection won't complete no matter how many times you retry. Second, the wrong Clio role: connecting a document source is an administrator action, so a regular user hitting the setup screen gets nowhere. Third, tenant consent: some Microsoft 365 tenants require an administrator to approve a third-party app before any user can authorize it, so the sign-in ends in a consent error rather than a Clio error. Confirm which of the three applies before troubleshooting further, because the fix is different in each case.

Q.02

Why did Clio recreate a whole matter folder in OneDrive after I renamed it?

Because the folder structure Clio creates on connect isn't yours to reorganize. Clio makes a root folder in OneDrive and builds per-client and per-matter subfolders beneath it, and it behaves as though the names it assigned are those folders' identity. Rename or move one from the OneDrive side and Clio treats the original as missing, then recreates the folder and its contents — which is why you end up with what looks like a duplicate. The usual result is two folders rather than a loss, but check both before assuming a document has gone: staff will already be saving into whichever one they find first. If a client or matter needs a different name, rename it in Clio and let the change flow outward. Leave the OneDrive side alone.

Q.03

Can an administrator see all matters in the Clio OneDrive folder?

This is really two questions with two answers. Inside Clio, document visibility follows matter access, and administrators are the people who set those access lists — so an administrator can generally reach any matter, if only by granting it to themselves. On the Microsoft side, the mirrored folder tree physically lives in a Microsoft 365 account, and anyone who can reach that account's OneDrive can see what's stored there regardless of how the corresponding Clio matter is restricted. In most tenants a Microsoft 365 administrator can obtain that access through ordinary tenant admin tooling. Note also that restricting a matter in Clio after it's already been mirrored doesn't retract the copy on the Microsoft side. Audit that location separately rather than assuming the Clio change covered it.

Q.04

Do commas in file or folder names break the Clio OneDrive sync?

Commas aren't on Microsoft's list of characters blocked in OneDrive and SharePoint names, so a comma by itself is rarely the reason a file fails to sync. The characters that genuinely block a name are the reserved set — quotation marks, asterisk, colon, angle brackets, question mark, forward slash, backslash and pipe — plus names that begin or end with a space or end with a period. Where commas do cause trouble is indirectly: firms that name contacts in last-comma-first style push those commas into every generated folder name, which makes paths longer and confuses downstream scripts and exports that treat commas as separators. Rename in Clio if you want them gone, never in OneDrive.

Q.05

Can a large firm with a lot of files use the Clio OneDrive sync?

It can, but scale is the thing to plan for rather than discover. The mirror creates a folder for every synced client and matter, so a firm with thousands of open and closed matters gets a folder tree of the same order, and Microsoft publishes guidance on how many files the OneDrive sync app is expected to handle across all synced libraries before performance degrades. Large firms hit two ceilings first: total item count in the mirrored location, and total path length once deep matter folders sit under long client names. Check the current Microsoft figures against your own matter count before rolling the connection out firm-wide, and consider limiting what syncs rather than mirroring everything.

Q.06

Why doesn't SharePoint show up as a document source in Clio?

Because it isn't one. Clio Manage connects a fixed short list of cloud stores natively, and the Microsoft entry on that list is OneDrive for Business only — team SharePoint libraries aren't a supported document source, so there's nothing to select and no setting that reveals one. This surprises firms whose shared matter drafting actually lives in SharePoint rather than in anybody's personal OneDrive. It isn't a bug or a permissions problem, and no amount of tenant configuration changes it. Getting SharePoint content into a matter means using one of the manual or automated workflows instead: browser download and upload, a Power Automate flow calling Clio's API, or a browser-based upload tool.

Q.07

How do I change or disconnect the storage behind my Clio documents?

A connected document source is changed by an administrator in Clio's app settings, in the same place it was connected. Two things are worth knowing before you touch it. First, disconnecting a source doesn't pull documents out of Clio — matter documents that already live in Clio stay there — but it does stop the mirroring, so files added on the storage side afterwards won't appear. Second, connecting a different account or a different provider generally starts a fresh folder structure rather than adopting the old one, so plan for a period where two structures exist and staff need telling which is live. Confirm the current disconnect behavior in Clio's help center before doing it on a working firm.

Q.08

Is there a way to get files into Clio that doesn't depend on the OneDrive connection?

Yes, and it's the right move when the connection is misbehaving and something has to be filed today. Clio's web Documents area accepts drag-and-drop and handles multiple files and folders directly in the browser, with no cloud-to-cloud mirror and no desktop sync client in the path, so a broken document source doesn't stand between you and the matter. Browser extensions that send a file straight from the page it's on into a matter cover the same ground for recurring inbound documents. Keep working the connection issue separately if the mirror matters to your workflow. But don't let a stalled integration hold up a filing when a two-minute manual upload will do.

Related guides