> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# SharePoint

> Connect your SharePoint document libraries so Grady can find, read, tag, and file documents — inside the folders you explicitly allow, and never with the ability to delete.

## 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.

<Info>
  **Access:** Must be enabled for your organization. Contact your Gradial team to get access.
</Info>

### 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

| Capability              | What it means                                                                                             |
| ----------------------- | --------------------------------------------------------------------------------------------------------- |
| **Inventory**           | List reachable sites and their document libraries                                                         |
| **Browse**              | Page through a folder's files and subfolders                                                              |
| **Read metadata**       | File size, image dimensions, and list-item column values including managed-metadata tags and descriptions |
| **Search**              | Full-text search over document content and file names, within an allowed folder                           |
| **Download**            | Pull a file into the working session to read, parse, compare, or migrate                                  |
| **Upload**              | File a document into a library folder, optionally setting its columns and tags                            |
| **Create folders**      | Add a folder inside a library                                                                             |
| **Update fields**       | Set tags, descriptions, and other column values on an existing item                                       |
| **Show its own access** | Report exactly which folders it can read and write, and test that they're reachable                       |

### 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.

<Note>
  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.
</Note>

***

## How access works

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

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Warning>
  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.
</Warning>

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

<Tip>
  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.
</Tip>

***

## Connect SharePoint

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.

    <Note>
      If a Workspace isn't seeing SharePoint, check this first — an unassigned integration is the most common cause.
    </Note>
  </Step>
</Steps>

### 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

| What you see                          | What it means                                                                                                                                                                                                    |
| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Grady says a path isn't available** | The folder is outside the allow-list. Add it in the folder picker, or point Grady at a folder that is on the list. Grady won't retry — the answer won't change.                                                  |
| **Grady refuses to upload or tag**    | The destination is a **Read only** folder. Change it to **Read & write** if that's intended.                                                                                                                     |
| **A folder tests as unreachable**     | Either the path is wrong, or the connecting user can't see that folder in SharePoint. Confirm the path by pasting the folder URL instead of typing it.                                                           |
| **The connection needs reconnecting** | Delegated Microsoft access can be invalidated by a password change, a Conditional Access policy requiring re-authentication, or an admin revoking consent. An admin reconnects from **Settings → Integrations**. |
| **A Workspace can't use SharePoint**  | The integration isn't assigned to that Workspace's Environment.                                                                                                                                                  |

***

## Example prompts

```
Search our SharePoint case studies folder for manufacturing customers and
summarize the three most recent ones.
```

```
Read the messaging section of Brand/Guidelines/brand.docx in SharePoint and
tell me whether the attached draft follows it.
```

```
Take every image in the Brand Assets/2026 folder in SharePoint, carry each
image's description across as alt text, and upload them to AEM.
```

```
Write the Atlas launch case study as a Word document and file it in our
SharePoint case-studies folder, tagged for the Atlas campaign.
```

***

## Related

* [Box →](/docs/integrations-administration-and-setup/integrations/box) — the same document workflows, with Box's collaborator-based access model
* [Office Docs →](/docs/campaign-management/office-docs) — how Gradial creates and works with Word, Excel, and PowerPoint files
* [Digital Asset Management →](/docs/asset-management/digital-asset-management)
* [Integrations Overview →](/docs/integrations-administration-and-setup/integrations/get-started-with-integrations)