> For the complete documentation index, see [llms.txt](https://help.docupilot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.docupilot.app/deliveries/sharepoint.md).

# SharePoint

Upload the generated documents to your Sharepoint

To configure a SharePoint delivery:

1. Navigate to Template > Deliveries
2. Choose **Sharepoint** from list of available deliveries.
3. Fill in desired fields and Save.

<figure><img src="https://191679573-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LDwD-wIOendMUiQ8uVr%2Fuploads%2F5ug1obAIZyMixWV7d93z%2FSharePoint%20Delivery.png?alt=media&amp;token=43cc70ce-09e6-4c3b-95ac-08b653b9c0f4" alt=""><figcaption></figcaption></figure>

The following fields are available when configuring the SharePoint delivery:

<table data-header-hidden="false" data-header-sticky data-search="false"><thead><tr><th width="239.00390625">Field Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Give this delivery a name for your reference.</td></tr><tr><td><strong>Select Account</strong></td><td>Pick the SharePoint account to use. Click the <strong>Link</strong> icon (🔗) and follow the on-screen instructions to integrate a new Sharepoint account.</td></tr><tr><td><strong>Base Folder Path</strong></td><td>Select the base folder by clicking <strong>Select Folder</strong> and choosing a location from the SharePoint folder picker.</td></tr><tr><td><strong>Path</strong></td><td><p>Enter the folder path within the selected base folder. You can specify a <strong>nested</strong> <strong>folder path</strong> up to 3 levels deep. For example <code>GlobalSales/RegionA/DivisionA1</code>  is allowed, but <code>GlobalSales/RegionA/DivisionA1/SubDivisionA11</code>  is not.</p><p></p><p>Tokens can be used to create dynamic folder paths. For example, <code>{{CustomerName}}/Contracts</code>.</p><p></p><p>If no folder path is specified, the file will be saved in the configured base path.</p></td></tr><tr><td colspan="2"><strong>Advanced Settings</strong></td></tr><tr><td><strong>On Success Callback URL</strong> (optional)</td><td>A URL that should be invoked after a successful delivery.</td></tr><tr><td><strong>Emails to notify on delivery failure</strong> (optional)</td><td>List of email addresses that should be notified if the delivery fails. Defaults to Workspace Owner's email if none configured.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.docupilot.app/deliveries/sharepoint.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.