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

# SharePoint

> Send copies of a project's files into your own SharePoint document libraries.

Connect SharePoint and you can copy a project's files out of BuildVision into
your own document libraries, where your estimators already work.

> [!NOTE]
>
> Connecting SharePoint is an organization admin task. You'll find it in
> **Settings > Integrations**, under **Files**. Anyone on your team can send
> files once the connection exists.

BuildVision writes copies. Your files stay in BuildVision, and nothing is read
back out of SharePoint.

## Choose how BuildVision connects

The choice changes whose name appears on the files in SharePoint, and how long
the connection lasts.

| | Sign in with Microsoft | Company-wide |
| - | - | - |
| **Who SharePoint shows as the author** | You | BuildVision |
| **Where files can go** | Sites you can already open yourself | Sites your tenant has granted |
| **Setup** | You sign in | A Microsoft 365 global administrator approves BuildVision once |
| **Lasts** | Stops working if your Microsoft account changes | Does not depend on any one person staying |

> [!NOTE]
>
> Both methods need a Microsoft 365 administrator's approval the first time,
> because reading your sites and writing files are permissions Microsoft
> reserves for admin consent. If sign-in ends with a message about needing
> admin approval, that's what happened. After an admin approves BuildVision
> once, anyone can sign in.

## Connect

**1. Open the integration**

Go to **Settings > Integrations** and select **SharePoint**.

**2. Choose a method**

Pick **Sign in with Microsoft** or **Company-wide**. Company-wide also asks
for your Microsoft directory (tenant) ID, which your administrator finds on
the Microsoft Entra ID overview page.

**3. Approve BuildVision**

Follow the Microsoft screen. For **Sign in with Microsoft**, sign in with a
work account. For **Company-wide**, your administrator approves BuildVision
for the whole tenant.

**4. You're connected**

BuildVision returns you to the SharePoint page and shows the connection as
**Connected**.

## Send a project's files

**1. Select the files**

Open a project and go to **Files**. Select the files you want to send. The
header checkbox selects everything currently shown, so filtering the list
first is a quick way to send one trade or one phase.

**2. Choose Send to SharePoint**

Select **Send to SharePoint** in the bar that appears.

**3. Pick a destination**

Choose a site, then a document library, then a folder. Leave **Create a
project folder** selected to put the files in a subfolder named after the
project.

**4. Send**

BuildVision reports how many files arrived and links to the folder in
SharePoint.

> [!WARNING]
>
> Send up to 25 files at a time.

## What happens to files already there

Sending the same file twice replaces the earlier copy rather than creating a
second one, so re-sending a project after an addendum keeps one copy of each
file. If two selected files share a name, BuildVision numbers the second one
rather than overwriting it.

Leaving **Create a project folder** selected keeps projects apart. Without it,
two projects with a file of the same name write to the same place.

## Disconnect

Open **Settings > Integrations**, select **SharePoint**, and disconnect. Files
already copied into SharePoint stay where they are.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.