Skip to main content

​
Overview

The SharePoint integration lets Grady work directly in your Microsoft SharePoint Online document libraries. It can inventory sites and libraries, browse folders, read file metadata and managed-metadata tags, search across document content, pull files into a working session, and file new documents back into the folders you choose — with tags applied. Access is deliberately narrow. You pick the exact folders Grady may touch and whether each is read-only or read-and-write. Until you pick at least one, Grady can access nothing.
Access: Must be enabled for your organization. Contact your Gradial team to get access.

​
Why use Gradial with SharePoint

Most marketing teams keep briefs, brand guidelines, case studies, decks, and approved assets in SharePoint — then spend real time hunting through it and hand-carrying files into other systems. With SharePoint connected:
  • Grady finds things by meaning, not folder memory — full-text search across document content, not just file names
  • Documents become inputs — Grady can read a Word doc, compare two PDFs, or check hero-image dimensions without you downloading anything
  • SharePoint becomes a destination — generated documents get filed into the right folder with the right tags
  • It bridges to your other connected systems — pull assets out of SharePoint and into AEM, or attach documents to Workfront tasks, in one conversation

​
What Grady can do

​
What Grady can never do

Deletion, moving, copying, sharing, and publishing are not restricted by policy — those operations do not exist in the integration at all. There is no way to phrase a request that removes, relocates, or externally shares a SharePoint file through Grady.
Microsoft’s consent screen lists broader permissions, including delete. That’s a limitation of how Microsoft describes permission bundles — Gradial requests write access because applying tags and columns requires it. The integration itself has no delete operation.

​
How access works

Two independent boundaries apply, and both must allow an action:
1

The connecting user's own SharePoint permissions

Grady acts as the person who connected the integration. It can never see or do more in SharePoint than that person can. Your existing SharePoint permissions remain the outer limit.
2

The folder allow-list you configure in Gradial

Within that, you narrow further — Grady is confined to an explicit list of folders, each marked read-only or read-and-write.
Because Grady acts as the connecting user, connect SharePoint using an account whose access covers the folders you intend to allow — and one that will persist. If that person leaves the organization, loses their SharePoint access, or has their session revoked, the integration stops working for everyone and an admin must reconnect it.
The allow-list fails closed. A newly connected SharePoint integration with no folders configured grants Grady no access at all. Requests for anything outside the list are refused, searches only ever return in-scope results, and folder counts reflect only in-scope items — so Grady never reports or reasons about content you haven’t shared with it.

​
Before you start

You’ll need:
  • A Gradial organization admin — connecting an integration requires the Manage settings permission in Gradial
  • A Microsoft work or school account with access to the SharePoint sites you want to connect
  • Microsoft administrator involvement, in most cases — see below
  • The folder URLs you want Grady to use, ready to paste

​
Do you need a Microsoft admin?

Usually yes, in practice. The Microsoft Graph permissions Gradial requests are not, by Microsoft’s own definition, admin-consent-required — a regular user is technically able to approve them for themselves. However, most enterprise Microsoft 365 tenants disable user consent entirely as a matter of policy. In those tenants the approval must come from a Microsoft administrator, who can either:
  • Grant tenant-wide admin consent to the Gradial application, or
  • Perform the connection themselves
Plan for a Microsoft admin to be involved. If you’re not sure how your tenant is configured, the fastest path is to have a Microsoft 365 administrator complete the connect flow — it takes a few minutes and removes the guesswork.

​
Connect SharePoint

1

Open the SharePoint integration

In Gradial, go to Settings → Integrations, find SharePoint, and start the connect flow.The Add SharePoint dialog explains what happens next. Read the notice — it covers the two things people most often ask about: that a Microsoft administrator may need to approve access, and that Microsoft’s approval screen lists broader permissions than Gradial actually uses.
2

Approve access at Microsoft

Select Connect with Microsoft. You’ll be taken to Microsoft to sign in and approve access. If your tenant requires administrator approval, the flow will say so — hand it to a Microsoft admin at that point.Once approved, you’re returned to Gradial with the connection established but no folders yet allowed. Grady still can’t access anything.
3

Choose the folders Grady can use

Gradial opens the folder picker immediately after connecting. You can also reopen it later from the SharePoint integration row.Each row in the Choose SharePoint folders dialog is one allowed folder. The fastest way to add a folder is to paste its URL:
  1. Open the folder in SharePoint in your browser
  2. Copy the URL from the address bar
  3. Paste it into Paste a SharePoint folder URL and select Add
Gradial resolves the URL into the correct Site, Document library, and Folder — you don’t need to know SharePoint’s internal naming. For example, a pasted URL might resolve to site sites/Gradial, library Documents, folder Grady Dev.Prefer to type the values yourself? Use Add Manually and fill the three fields directly. Leave Folder blank to allow the whole library, and leave Site blank for your tenant’s main site.
4

Set the access level for each folder

Each folder has its own Access setting:
  • Read only — Grady can browse, read metadata, search, and download. Uploads, folder creation, and tag changes are refused.
  • Read & write — Grady can additionally file documents into the folder, create subfolders, and set tags and column values.
Grant read-and-write only where Grady genuinely needs to file work back. A read-only folder is a hard boundary, not a preference.
5

Test, then save

Select Test Read Access to check that each folder is actually reachable with the connected account’s permissions. A folder that comes back unreachable is usually a typo in a manually entered path, or a folder the connecting user can’t actually see.Select Save to apply the list. Changes take effect immediately.
6

Assign the integration to an Environment

Go to Settings → Environments, select the Environment you want SharePoint available in, and add the SharePoint integration to it. This makes it available to all Workspaces in that Environment. Repeat for any other Environments that need it.
If a Workspace isn’t seeing SharePoint, check this first — an unassigned integration is the most common cause.

​
Adding or changing folders later

Reopen the folder picker from the SharePoint integration row at any time. Add folders as new work comes in, change an access level, or remove a folder with the delete icon on its row. Removing a folder immediately revokes Grady’s access to it.

​
Limits

  • Uploads and downloads are capped at 250 MB per file.
  • Uploads never overwrite. If a file of the same name already exists, the upload is saved under a slightly different name rather than replacing the existing document.
  • Tags may lag an upload. Grady can file a document and set its tags in one step. If the file lands but the tag update fails, Grady tells you the document is uploaded but not tagged, and can set the tags in a follow-up step. Treat that warning as real — don’t assume tagging succeeded.
  • Search is scoped to one allowed folder at a time, not the whole tenant.
  • Tags are read one item at a time. Managed-metadata values come back reliably when Grady inspects a single item, not from bulk folder listings.

​
Troubleshooting

​
Example prompts