> For the complete documentation index, see [llms.txt](https://docs.emsigner.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.emsigner.com/administrator-settings/admin-settings/storage-connectors/one-drive.md).

# One Drive

#### Storage Connector – One Drive

The OneDrive connector lets you push signed documents, attachments, and completion certificates from emSigner directly into a connected Microsoft OneDrive account, giving you full control over where your signed documents reside.

**Navigation:** Settings → Storage Connectors for Document Repositories → One Drive tab

The setup follows a three-step flow: **Authorize → Test Connection → Save**.

**Sending Options**

| Option                                                                   | Description                                                          |
| ------------------------------------------------------------------------ | -------------------------------------------------------------------- |
| **Include Signed documents only** *(selected by default)*                | Only the signed documents will be pushed to the selected connector.  |
| **Include attachments** *(selected by default)*                          | Attachments will also be included along with the signed documents.   |
| **Include completion certificate** *(optional, not selected by default)* | The completion certificate will be included in the connector upload. |

**Steps to Configure**

* Go to **Settings** and click on **Storage Connectors for Document Repositories**.
* Select the **One Drive** tab.
* Review the **Sending Options** — *Include Signed documents only* and *Include attachments* are enabled by default. Optionally, select **Include completion certificate**.
* **Step 1 – Authorize:** Sign in and grant emSigner access to your Microsoft OneDrive account. Once authorized, the step is marked complete. If you ever need to reconnect a different account, use the **Re-authorize** link.&#x20;

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2Fhm2eSBwC3XOiMhQp1IDI%2Fimage.png?alt=media&amp;token=046abc60-9312-4b96-9fd2-23e7c47b460b" alt=""><figcaption></figcaption></figure>

* **Step 2 – Test Connection:** Click **Generate test file**. emSigner creates a file named `emSigner/emSigner-activation.txt` in your OneDrive.&#x20;
* Open this file in your OneDrive and copy the activation code shown inside.
* Paste the code into the **Enter activation code** field and click **Activate**. On success, you'll see a confirmation: *"OneDrive connector activated."*&#x20;

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FWaGn1WdX7X0LGYCsoTx6%2Fimage.png?alt=media&amp;token=9b42d4d7-18b8-4c67-a35c-89c1f5ff0851" alt=""><figcaption></figcaption></figure>

* **Step 3 – Save:** Confirm or update your **Sending Options**, then click **Save Configuration** to complete the setup.&#x20;
* On success, you'll see the message *"OneDrive connector configured successfully."*

**Managing an Active Connector**

Once activated and saved, the page displays a banner confirming the connector is active and documents are being pushed to it.

<figure><img src="https://1693119202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXNKpOPGIHdEkmaF2RQso%2Fuploads%2FhmwnkqW4BV9XiXu7PKoI%2Fimage.png?alt=media&amp;token=163366b5-dbad-4301-ab16-4b89f822a5cd" alt=""><figcaption></figcaption></figure>

From here, you can:

* Update the **Sending Options** at any time and save the change — this triggers a *"Connector updated successfully"* confirmation.
* Click **Deactivate** to stop further documents from being pushed to this connector. Deactivating does not delete the configuration; it simply pauses delivery until reactivated.

> **Note:** Until the connector is activated, documents will continue to follow the existing storage behavior. Once activated, this connector applies at the administrator level — all future signed documents from every user of the application, including internal users, will be pushed to the configured repository (matching the selected Sending Options).
