Let Sasha read files that live in OneDrive, SharePoint or Google Drive without uploading them

Settings → Shared Drives signs Sasha into one business OneDrive, SharePoint library or Google Drive, so people can browse those files in Sasha without uploading them.

Where
Settings → Shared Drives (the avatar menu, then Settings). The provider's sign-in page sends you back to the same tab.
Who
Only admins can set up connections. Sasha has no setting that gives this right to staff. Admin and staff accounts browse the connected drives.
Needs
An app registration at Microsoft (client ID, secret value, directory ID) or an OAuth client at Google, with the redirect address from the connection card. SharePoint also needs the library's Drive ID.

What this screen is for

Shared Drives connects Sasha to a business cloud drive. People then browse the drive's files in Sasha, and Sasha reads each file from the drive when it is needed. Nothing is uploaded or copied in.

The Cloud Drive Connections banner explains the screen; its arrow opens more detail. Below it, five tiles show the state of each type: Microsoft 365 OneDrive, Microsoft SharePoint Library, Google Drive, Notion and GitHub. Each tile shows Available, Connected or Action needed. A drive tile also shows the connection name, or "2 drives connected", or "2 drives awaiting sign-in".

Settings, Shared Drives tab: five tiles for OneDrive, SharePoint, Google Drive, Notion and GitHub, each with its state, and the Add Connection button

This page is about OneDrive, SharePoint and Google Drive. For Notion, see Connect Notion so Sasha can read and work with your Notion pages. For the GitHub synced folders section lower on the screen, see Copy a folder from a GitHub repository into a project, read-only, and keep it up to date. To compare all five, see Choose and understand the connectors that put your files and pages in Sasha's file tree.

Add a connection

  1. Click Add Connection. The button changes to Hide Connection Form.
  2. Choose the Provider.
  3. Type a Display name that your team will recognise, for example "Finance Google Drive".
  4. Choose the Scope: Read & write (the default) or Read-only. See "Scope" below.
  5. For Microsoft SharePoint Library, fill in Drive ID *. Site ID and Root folder ID are optional. The form explains three ways to find the Drive ID and lists the Microsoft permissions the app needs.
  6. Click Save Connection. The connection appears below with Needs authorization.

The new connection form on the Shared Drives tab: Provider, Display name and Scope, with Save Connection

With Microsoft SharePoint Library chosen, the form is longer:

The Add Connection form with Microsoft SharePoint Library chosen: Provider, Display name, Scope, the OneDrive or SharePoint note, the required permissions, How to Get Your Drive ID, and the Drive ID, Site ID and Root folder ID fields

Sign Sasha in

Each connection card has the fields for the app you registered at the provider:

Field What to enter
Client ID The application (client) ID
Client secret (Value, not Secret ID) The secret's value. After a save, the box shows "Stored"
Tenant / Directory ID Microsoft only: your directory ID
Redirect URI Shown by Sasha. Click Copy and add it to the app registration

A OneDrive connection card marked Needs authorization and Read-only: Client ID, Client secret with Stored, the directory ID, Connect, and the Redirect URI with its Copy button

The badges at the top of the card give the provider type, the state (Connected or Needs authorization) and the scope (Read-only or Read & write). A SharePoint card also has SharePoint library identifiers, with the Drive ID and Save library.

A SharePoint connection card: SharePoint library identifiers with Drive ID, Site ID, Root folder ID and Save library, above the client fields and the Redirect URI

  1. Add the Redirect URI to your app registration at Microsoft or Google. For the steps, see Set up the Microsoft side so Sasha can sign in to OneDrive or a SharePoint library or Set up the Google side so Sasha can sign in to your Google Drive.
  2. Fill in the client fields on the card and click Connect.
  3. Sign in at Microsoft or Google with the business account and approve.
  4. The provider sends you back to this tab. A message says, for example, "Microsoft 365 authorized successfully." The card then shows Connected, "Account:" with the signed-in account, "Last refresh:" and "Access expires:".

Notion works differently: there is no sign-in. You paste an API token from a Notion connection, and you choose the pages Sasha can see in Notion. For the steps, see Connect Notion so Sasha can read and work with your Notion pages.

If the provider does not give Sasha a long-term sign-in, Sasha shows "Provider did not return a refresh token. Ensure consent is granted." Approve the consent screen in full and try again.

Scope

Scope Microsoft Google
Read-only Sasha asks only for read permissions Sasha asks for full access to the drive
Read & write Sasha asks for read and write permissions Sasha asks for full access to the drive

The banner recommends Read-only. The form starts at Read & write, so choose Read-only yourself if you want it.

Where the files show

A connection with Connected shows as a folder in the Shared Drives group at the top of the file tree. The folder has the connection's display name. A connection that waits for a sign-in does not show.

Open a folder to list it. Sasha asks the drive each time, and keeps the listing for 15 seconds and a search for 10 seconds. A change in the drive shows at the next open, at the latest 15 seconds later. Open a file to read it. From the file tree, people can also upload, move, rename and delete files, on any scope (see "Limits to know").

If Sasha cannot list a folder, the file tree shows "Failed to load cloud directory". See the questions above.

For Claude to read the drives in a chat, an admin also registers the Drive MCP (Shared Drives) card in Settings → Tools. See Choose and understand the connectors that put your files and pages in Sasha's file tree.

What Sasha keeps for each connection

When a sign-in completes, Sasha makes one internal record for the connection, which Sasha calls a mount. The screen does not show it. It holds:

  • Access mode: read or read and write. It follows the Scope of the connection.
  • Health: mounted, degraded or unmounted. Sasha sets it when it starts and when it prepares the drive. If the preparation fails, for example because the sign-in cannot be renewed, the health is degraded and the record keeps the error. Every 5 minutes Sasha marks every OneDrive, SharePoint and Google Drive record as mounted again. This is not a check of the drive.
  • Cache profile, quota and retry time: these exist in the record, but Sasha does not use them. Sasha reads the drive live, and the cache times above apply to every connection.

For Notion, the health comes from a real call to Notion. See Connect Notion so Sasha can read and work with your Notion pages.

The other buttons

  • Refresh cache on a card: Sasha forgets its stored listings for that connection. The next browse asks the drive again.
  • Refresh at the top: reloads the list of connections.
  • Save library (SharePoint only): saves new library identifiers.
  • Reconnect: repeats the sign-in. You must type the client secret again.
  • Remove: asks "Remove this connection? Any cached listings will be cleared." and then deletes the connection and its stored sign-in.

How it is kept safe

  • The client secret and the provider's sign-in are stored encrypted on your Sasha server. The secret never returns to the browser. If whoever runs your Sasha has not set an encryption key, Sasha uses a built-in key that gives little protection.
  • Sasha checks each return from the provider with a one-time value. A mismatch shows "State validation failed. Please try again."
  • Sasha renews the drive's access by itself when it is about to expire, for example when Sasha starts. A failed renewal shows as Last error on the card.
  • Sasha records file actions on the drives.

Limits to know

  • Today, Cancel on the new connection form hides the form but causes an error in the page, and does not clear what you typed. Use Hide Connection Form instead.
  • The display name and the client credentials belong to the provider type, not to one connection. A second Google Drive connection renames the first, and a new client secret on one OneDrive connection changes it for every OneDrive connection.
  • Reconnect clears the working sign-in before you reach the provider. If you stop part way, the drive stays disconnected until you finish a sign-in.
  • For Google, Read-only does not stop changes. Sasha does not check the scope before an upload, a new folder, a move or a delete, on any provider.
  • Remove does not cancel Sasha's access at Microsoft or Google.
  • The banner says "Real-Time Sync". Sasha does not sync the drives. It reads them live, with the short cache above.
  • "Failed to load cloud directory" in the file tree does not give the reason. The card shows a failed sign-in only.
  • The Drive MCP card says that drive connections come from "Settings → Drives". The tab is Shared Drives.
  • The Redirect URI is built from the address the browser used. If your Sasha sits behind a proxy that changes the address, check that the URI shows your public address before you register it.
  • Browsing the drives needs the cloud-drives:use capability (admin and staff). Whether the server checks it depends on how your Sasha is set up. Ask whoever runs your Sasha.

Questions

Are the files copied into Sasha?

No. Sasha reads them from the drive when someone opens a folder or a file. Folder listings are kept for 15 seconds and search results for 10 seconds, then Sasha asks the drive again.

Which accounts can I connect?

A Microsoft 365 business OneDrive, a SharePoint document library, or a Google Drive. Personal (consumer) OneDrive accounts are not supported.

OneDrive or SharePoint?

Choose OneDrive for the files of one business user. Choose SharePoint Library for a shared library, such as the files of a Teams team or a department. SharePoint needs the Drive ID of the library.

Does Read-only stop changes?

For Microsoft, yes in practice. Sasha asks Microsoft only for read permissions, so Microsoft refuses changes. For Google, no. Sasha asks Google for full access to the drive whatever you choose, and Sasha does not block uploads, moves or deletes on a Read-only connection.

Connect fails with AADSTS50011 or redirect_uri_mismatch. Why?

The redirect address registered at Microsoft or Google does not match the one on the connection card exactly. Click Copy next to Redirect URI on the card, paste it into the app registration, and try again.

Where do people see the drives?

In the file tree, in a group named Shared Drives.

Can Claude search the drives in a chat?

Only if an admin also sets up the Drive MCP card in Settings → Tools. A connection on this tab alone gives people the files in the file tree.

Does Remove cancel Sasha's access at Microsoft or Google?

No. Remove deletes the connection, its stored sign-in and its cached listings in Sasha only. Also remove the app's access in your Microsoft or Google admin settings.

What are the Notion and GitHub tiles?

Two more connectors on the same screen. Notion puts the Notion pages you share in the file tree; see the Notion setup page. A GitHub synced folder copies one folder of a repository into a project; see the GitHub synced folders page. The page about file connectors compares all five.

Why does a drive folder in the file tree say "Failed to load cloud directory"?

Sasha could not list the folder at the provider, and the message does not say why. If the connection card shows Last error, the sign-in failed, so click Reconnect. If not, check that the connected account can open the folder at Microsoft or Google.

Why does a staff account see a "Missing required capability" message on this tab?

Setting up drives needs the cloud-drives:manage capability. Only admins hold it. Sasha has no setting that gives this right to staff.

Built with BernardCookie settings