# SharePoint

Connect SharePoint as a storage library: auth, sites, drives, permissions.

> Kind: Storage library · Updated: May 19, 2026

SharePoint is the most common storage behind CloudFiles. This page is the single source of truth for SharePoint setup — every flow action, tutorial and API doc links here instead of re-explaining SharePoint concepts.

## How SharePoint maps to CloudFiles

| SharePoint concept | CloudFiles term | Example ID |
|---|---|---|
| Tenant + site collection | Library | sharepoint_a8x2 |
| Site → Document library | Drive | b!xT9k… |
| Folder in a library | Resource (folder) | 01ABC… |
| File | Resource (file) | 01DEF… |

> **Why “Drive ID” is required on SharePoint but not Dropbox** — SharePoint nests drives inside sites; flat storages (Dropbox, Box, S3) don’t. Provider-aware parameter tables on action pages show exactly which IDs you need — switch the provider there to compare.

## Connect the integration user

Connect an org-level SharePoint account used for automations (file backup, folder creation). Use a service account with access to all relevant sites — automations run as this user.

*[img: Settings → Storage → Connect SharePoint]*

## Register sites

After auth, register each site you want visible in CloudFiles. Unregistered sites won’t appear in the Content Library or in folder pickers — the cause of the classic “I cannot see my SharePoint sites” FAQ.

## SharePoint REST API authorization

Advanced features (site creation from flows, metadata search) need elevated REST authorization granted by a SharePoint admin. Without it, basic file operations still work.

## Used by

⚡ Create Folder 📘 Lead → Account folder move ⌁ GET /v1/folders 🔧 SharePoint admin-approval error