|
| 1 | +--- |
| 2 | +sidebar_position: 5 |
| 3 | +title: Custom File Storage |
| 4 | +--- |
| 5 | + |
| 6 | +# 💾 Custom File Storage |
| 7 | + |
| 8 | +## 🌩️ Introduction to BYOC (Bring Your Own Cloud) |
| 9 | + |
| 10 | +OpenSign supports **BYOC (Bring Your Own Cloud)** — allowing you to **store your documents in your own cloud storage** instead of OpenSign’s default storage. |
| 11 | + |
| 12 | +With BYOC, organizations and users gain **greater control, privacy, and compliance flexibility** by connecting their preferred cloud providers such as **AWS S3** or **DigitalOcean Spaces**. |
| 13 | + |
| 14 | +> 🧠 **Why BYOC?** |
| 15 | +> - Maintain complete ownership and control of your documents. |
| 16 | +> - Comply with internal, regional, or client-specific data policies. |
| 17 | +> - Choose your preferred cloud region or provider for better performance and compliance. |
| 18 | +
|
| 19 | +--- |
| 20 | + |
| 21 | +## 🚀 How to Access the Custom File Storage Setup |
| 22 | + |
| 23 | +Follow the steps below to navigate to the **Custom File Storage** setup page in OpenSign: |
| 24 | + |
| 25 | +1. Log in to your **OpenSign** account using an **Admin account**. |
| 26 | +2. Click on your **profile menu** (top-right corner) and select **Console**. |
| 27 | +3. In the **left sidebar**, go to **Storage**. |
| 28 | + |
| 29 | +<img width="1722" height="814" alt="Custom file storage" src="https://github.com/user-attachments/assets/813f6685-3f36-40e4-aaaf-0d8b86bdc3b7" /> |
| 30 | + |
| 31 | +You will now be on the **Custom File Storage** setup page where you can configure your own storage provider. |
| 32 | + |
| 33 | +> 🔒 **Note:** Access to Custom File Storage settings is available only to **Admin users**. Regular users will not see this option in their menu. |
| 34 | +
|
| 35 | +--- |
| 36 | + |
| 37 | +## 🔔 Set Up File Storage |
| 38 | + |
| 39 | +By default, all users are connected to **OpenSign’s default file storage**. |
| 40 | +If you prefer to use your **own custom cloud storage (BYOC)**, you can easily configure it here. |
| 41 | + |
| 42 | +You can set up an **AWS S3 bucket** or **DigitalOcean Space** to store your uploaded documents securely. |
| 43 | +To configure OpenSign with your cloud storage, refer to this detailed guide: |
| 44 | +👉 [Cloud Storage Setup Guide](https://docs.opensignlabs.com/docs/self-host/cloud-storage/s3) |
| 45 | + |
| 46 | +--- |
| 47 | + |
| 48 | +### 🪣 Steps to Configure Custom Storage |
| 49 | + |
| 50 | +1. Click the **Add New** button. |
| 51 | + |
| 52 | +<img width="861" height="408" alt="Add new workspace" src="https://github.com/user-attachments/assets/0f734c6a-e2ac-445a-8194-746b9c202f0a" /> |
| 53 | + |
| 54 | +2. Fill in the following details: |
| 55 | + |
| 56 | + - **Unique File Adapter Name:** Enter a unique name for your storage configuration. |
| 57 | + - **Storage Provider:** Choose your provider — currently, OpenSign supports **AWS S3** and **DigitalOcean Spaces**. |
| 58 | + - **Bucket Name:** Specify your storage bucket name. |
| 59 | + - **Region:** Enter the region where your bucket is hosted. |
| 60 | + - **Endpoint:** Provide the endpoint URL of your storage service. |
| 61 | + - **Base URL:** Enter the base URL used to access stored files. |
| 62 | + - **Access Key ID:** Enter your storage access key ID. |
| 63 | + - **Secret Access Key:** Enter your storage secret access key. |
| 64 | + |
| 65 | +3. Once all details are filled, click **Save and Activate** to enable your custom file storage. |
| 66 | + |
| 67 | +After activation: |
| 68 | +- All your documents will be stored in the configured **BYOC storage provider**. |
| 69 | +- You will be automatically logged out to clear any previous file adapter data from your local session. |
| 70 | +- Upon logging in again, your custom file storage will be active, and all future documents will be saved there. |
| 71 | + |
| 72 | +<img width="861" height="408" alt="custom file storage" src="https://github.com/user-attachments/assets/1add417d-f745-4e00-8cf3-7dcd9798f4db" /> |
| 73 | + |
| 74 | +--- |
| 75 | + |
| 76 | +### ⚠️ Important Note |
| 77 | + |
| 78 | +In some cases, documents stored in your **custom (BYOC)** file storage may not load in OpenSign due to **CORS (Cross-Origin Resource Sharing)** policy restrictions. |
| 79 | +If you’ve activated custom file storage, ensure your cloud configuration **allows OpenSign to access your documents** and does **not block requests** due to CORS errors. |
| 80 | + |
| 81 | +👉 [Read the article to learn how to set up CORS policies](https://docs.opensignlabs.com/docs/self-host/cloud-storage/s3) |
| 82 | + |
| 83 | +--- |
| 84 | + |
| 85 | +## 💬 Need Help? |
| 86 | + |
| 87 | +If you need help setting up or testing your BYOC or custom file storage integration, contact our support team at |
| 88 | +📩 **[support@opensignlabs.com](mailto:support@opensignlabs.com)** |
| 89 | + |
| 90 | +Or join our community for instant assistance: |
| 91 | +💬 [Join our Discord](https://discord.com/invite/xe9TDuyAyj) |
| 92 | + |
| 93 | +**Happy Signing with OpenSign™!** |
| 94 | + |
0 commit comments