From 0d884e2f4f784387de789168ede95d43b070c738 Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 15:18:43 +0530
Subject: [PATCH 01/17] Create analystics.md

add the new pages for console analytics.
---
 .../docs/help/User Menu/Console/analystics.md | 26 +++++++++++++++++++
 1 file changed, 26 insertions(+)
 create mode 100644 docs/docs/help/User Menu/Console/analystics.md

diff --git a/docs/docs/help/User Menu/Console/analystics.md b/docs/docs/help/User Menu/Console/analystics.md
new file mode 100644
index 000000000..fa7b45e29
--- /dev/null
+++ b/docs/docs/help/User Menu/Console/analystics.md	
@@ -0,0 +1,26 @@
+---
+sidebar_position: 1  
+title: Analytics  
+---
+
+### **Documents Signed**  
+Displays the total number of documents you have signed.  
+
+---
+
+### **Templates Count**  
+Shows the total number of templates you have created.  
+
+---
+
+### **Emails Sent**  
+Indicates the total number of emails you have sent.  
+
+---
+
+### **Storage Used**  
+Displays the total amount of storage space you have utilized.  
+
+---
+
+If you need further assistance, please contact our support team at **support@opensignlabs.com**.

From f9eb9201f0a0680ea8ca8ea2b02b87a6e90c635e Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 15:23:57 +0530
Subject: [PATCH 02/17] Modify Console category in _category_.json

Updated the label and position for the Console category and changed the description for clarity.
---
 docs/docs/help/User Menu/Console/_category_.json | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 docs/docs/help/User Menu/Console/_category_.json

diff --git a/docs/docs/help/User Menu/Console/_category_.json b/docs/docs/help/User Menu/Console/_category_.json
new file mode 100644
index 000000000..1e4d56d48
--- /dev/null
+++ b/docs/docs/help/User Menu/Console/_category_.json	
@@ -0,0 +1,8 @@
+{
+  "label": "Console",
+  "position": 1,
+  "link": {
+    "type": "generated-index",
+    "description": "The console application is accessible only to the admin; other users do not have access to it."
+  }
+}

From ae6f72764610ddf09753b8fa7f3ea86989e6ef8e Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 15:44:57 +0530
Subject: [PATCH 03/17] Create general.md for OpenSign General settings

Added documentation for the General section in OpenSign, covering settings for signature types, public profile indexing, and email template customization.
---
 docs/docs/help/User Menu/Console/general.md | 42 +++++++++++++++++++++
 1 file changed, 42 insertions(+)
 create mode 100644 docs/docs/help/User Menu/Console/general.md

diff --git a/docs/docs/help/User Menu/Console/general.md b/docs/docs/help/User Menu/Console/general.md
new file mode 100644
index 000000000..35ef902b6
--- /dev/null
+++ b/docs/docs/help/User Menu/Console/general.md	
@@ -0,0 +1,42 @@
+---
+sidebar_position: 2
+title: General
+---
+
+# General
+
+The **General** section in OpenSign includes essential settings that allow the admin to manage and control the overall configuration of the OpenSign platform.
+
+---
+
+## Enabled Signature Types
+
+Admins can define which signature types are available at the organization level.  
+
+All users under your account will only see the signing methods you enable here in their **Preferences**. They will not be able to use any signature methods that are disabled by the admin.
+
+**Example:**  
+Adam, the administrator of your company account, disables the **Typed** signature option in the **Manage Signature Types** settings. As a result, Ursula, a team member, will no longer see the **Typed** signature option in her preferences.
+
+Ursula can still enable or disable any of the remaining signature methods for each document she creates.  
+When she sends a document to Sofia (a signer), Sofia will only see the signature methods that Ursula selected during the document creation process.
+
+> **Note:** Managing **Signature Types** at the organization level is available only on the **Teams** plan.  
+> This feature is not included in the **Professional** or **Free** plans.
+
+![Signature type setup console](https://github.com/user-attachments/assets/c8c3de19-e82e-464a-977b-cdf3fd12aed7)
+
+---
+
+## Allow Indexing of Public Profile
+
+If this option is enabled, the user’s public profile will be indexed and appear in search results.
+
+---
+
+## Email Template Customization
+
+This setting allows the admin to control whether users can create and manage their own email templates.
+
+- If the admin **disables** this setting, team users **cannot** create custom email templates for request signatures or document completion notifications.  
+- If the setting is **enabled**, users can customize their own individual templates.

From d973a8fea4f44099d5a8dd4aa2ae8387fbd48d38 Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 17:19:11 +0530
Subject: [PATCH 04/17] Create branding.md

added the help text for branding page
---
 docs/docs/help/User Menu/Console/branding.md | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 docs/docs/help/User Menu/Console/branding.md

diff --git a/docs/docs/help/User Menu/Console/branding.md b/docs/docs/help/User Menu/Console/branding.md
new file mode 100644
index 000000000..9d808c550
--- /dev/null
+++ b/docs/docs/help/User Menu/Console/branding.md	
@@ -0,0 +1,20 @@
+---
+sidebar_position: 4
+title: Branding
+---
+
+# 🔧 Branding
+
+## **Custom Subdomain**
+This page is accessible only to **Enterprise** users. Here, users can configure their own custom subdomain and access the OpenSign application directly through it.
+
+---
+
+## **App Name**
+Users can set a custom application name to reflect their brand identity.  
+This name will appear in custom template page titles and other areas across the application, helping maintain consistent branding.
+
+---
+
+## **App Logo**
+Users can upload their own logo to display within the application instead of the default OpenSign logo, reinforcing their brand presence.

From 83e953717625b3bf454524f72472d6717ecdcfdf Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 18:29:40 +0530
Subject: [PATCH 05/17] Create emails.md

Added the help text to setup customize email template at organization level.
---
 docs/docs/help/User Menu/Console/emails.md | 61 ++++++++++++++++++++++
 1 file changed, 61 insertions(+)
 create mode 100644 docs/docs/help/User Menu/Console/emails.md

diff --git a/docs/docs/help/User Menu/Console/emails.md b/docs/docs/help/User Menu/Console/emails.md
new file mode 100644
index 000000000..e579c623e
--- /dev/null
+++ b/docs/docs/help/User Menu/Console/emails.md	
@@ -0,0 +1,61 @@
+---
+sidebar_position: 5
+title: Email Templates
+---
+
+# 📧 Company Email Template Settings
+
+This page allows the **admin user** to configure and manage customized email templates at the **organization level**.  
+If you prefer not to grant users permission to set up their own email templates, you can define a single set of templates here that will apply to all users within your organization.
+
+---
+
+## 🧩 Set Up Custom Email Templates at the Organization Level
+
+**Step 1:** Log in to your OpenSign account using valid credentials (**admin access required**).  
+**Step 2:** Navigate to the **Profile Menu** and click on **Console**.  
+**Step 3:** Go to the **Email** tab. Here, admin users can create, edit, and manage organization-level email templates.
+
+<img width="800" alt="custom email templates" src="https://github.com/user-attachments/assets/b2fd3497-3e2b-4acc-b8a5-09bad8a5e5ba"></img>
+
+---
+
+## ✉️ Request Signature Email
+
+This email is automatically sent to all signers when a document is shared for signing.
+
+- Customize the **subject line**, **greeting**, **message body**, and **footer** to match your brand’s tone and style.  
+- Use dynamic placeholders like `{{document_title}}`, `{{receiver_name}}`, and `{{signing_url}}` for personalization.  
+- Personalized messages increase open rates and help recipients clearly understand the signing request.
+
+---
+
+## 📩 Document Completion Email
+
+This email is sent to all signers and the document owner once the signing process is successfully completed.
+
+- Contains a summary message along with the **signed document** and **completion certificate** as attachments.  
+- Customizing this template helps maintain brand consistency even in post-signature communications.  
+- Ideal for sharing **legal confirmations**, **audit trails**, or **record-keeping** updates.
+
+---
+
+### 🔄 Reset Template Text
+
+Click the **Reset** button to restore any modified email template back to its **default OpenSign version**.  
+After resetting, make sure to click **Save** to apply the changes.
+
+---
+
+## 🛠️ Additional Notes
+
+- All custom email templates support **rich text formatting** and **dynamic variables**.  
+- Updates take effect immediately and apply to **all new documents** created after the change.  
+- Organizations can enforce consistent branding and compliance across all user emails.  
+- If no custom email template is configured, and users are not allowed to create individual templates, OpenSign will automatically use the **OpenSign default email templates**.
+
+> 💡 **Tip:** Always preview your templates before saving to ensure correct formatting and placeholder usage.
+
+---
+
+For further assistance with OpenSign™ features or APIs, contact our support team at **[support@opensignlabs.com](mailto:support@opensignlabs.com)**.

From 5888387dd09caf75f69f21d81302b7c4843df934 Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 19:35:21 +0530
Subject: [PATCH 06/17] Create custom_filestorage.md

added the help content for console custom file storage.
---
 .../User Menu/Console/custom_filestorage.md   | 57 +++++++++++++++++++
 1 file changed, 57 insertions(+)
 create mode 100644 docs/docs/help/User Menu/Console/custom_filestorage.md

diff --git a/docs/docs/help/User Menu/Console/custom_filestorage.md b/docs/docs/help/User Menu/Console/custom_filestorage.md
new file mode 100644
index 000000000..6a7376ff3
--- /dev/null
+++ b/docs/docs/help/User Menu/Console/custom_filestorage.md	
@@ -0,0 +1,57 @@
+---
+sidebar_position: 5
+title: Custom File Storage
+---
+
+# 💾 Custom File Storage
+
+## 🔔 Set Up File Storage
+
+This page allows users to configure their own file storage to store documents securely on their personal servers.
+
+By default, all users are connected to **OpenSign’s default file storage**.  
+If you prefer to use your **own custom file storage**, follow the steps below.
+
+You can create an **AWS S3 bucket** to store your uploaded documents through OpenSign.  
+To configure OpenSign with your cloud storage setup, refer to this guide:  
+👉 [Cloud Storage Setup Guide](https://docs.opensignlabs.com/docs/self-host/cloud-storage/s3)
+
+---
+
+### 🪣 Steps to Configure Custom Storage
+
+1. Click the **Add New** button.  
+2. Fill in the following details:
+
+   - **Unique File Adapter Name:** Enter a unique name for your storage configuration.  
+   - **Storage Provider:** Choose your provider — currently, OpenSign supports **AWS S3** and **DigitalOcean Spaces**.  
+   - **Bucket Name:** Specify your storage bucket name.  
+   - **Region:** Enter the region where your bucket is hosted.  
+   - **Endpoint:** Provide the endpoint URL of your storage service.  
+   - **Base URL:** Enter the base URL used to access stored files.  
+   - **Access Key ID:** Enter your storage access key ID.  
+   - **Secret Access Key:** Enter your storage secret access key.
+
+3. Once all details are filled, click **Save and Activate** to enable your custom file storage.
+
+After activation:
+- All your documents will be stored in the configured storage provider.  
+- You will be automatically logged out to clear any previous file adapter data from your local session.  
+- Upon logging in again, your custom file storage will be active, and all future documents will be saved there.
+
+---
+
+### ⚠️ Important Note
+
+In some cases, documents stored in your custom file storage may not load in OpenSign due to **CORS (Cross-Origin Resource Sharing)** policy restrictions.  
+If you’ve activated custom file storage, make sure your storage configuration **allows OpenSign to access your documents** and does **not block requests** due to CORS errors.
+
+---
+
+## 💬 Need Help?
+
+If you need help setting up or testing your custom file storage integration, contact our support team at  
+📩 **[support@opensignlabs.com](mailto:support@opensignlabs.com)**
+
+**Happy Signing with OpenSign™!**
+

From 76699d7dc954383c69b63003b207234d0e027ede Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 19:41:41 +0530
Subject: [PATCH 07/17] Create signing_certificate.md

pfx certificate content updates.
---
 .../User Menu/Console/signing_certificate.md  | 63 +++++++++++++++++++
 1 file changed, 63 insertions(+)
 create mode 100644 docs/docs/help/User Menu/Console/signing_certificate.md

diff --git a/docs/docs/help/User Menu/Console/signing_certificate.md b/docs/docs/help/User Menu/Console/signing_certificate.md
new file mode 100644
index 000000000..a5903ef8c
--- /dev/null
+++ b/docs/docs/help/User Menu/Console/signing_certificate.md	
@@ -0,0 +1,63 @@
+---
+sidebar_position: 6
+title: Custom Signing Certificate
+---
+
+# 🔐 Custom Signing Certificate
+
+The **Custom Signing Certificate** page allows you to upload and manage your own **digital signing certificate** (PFX format) for secure and verified document signing in OpenSign.
+
+By default, OpenSign uses its **built-in signing certificate** to digitally sign documents.  
+However, if your organization has its own **custom certificate (PFX or P12 format)**, you can upload and activate it here.
+<img width="1722" height="814" alt="pfx cerificate upload" src="https://github.com/user-attachments/assets/a5668f61-332d-49c5-ace2-5f0f92d3b68f" />
+
+---
+
+## 🪪 What is a PFX Certificate?
+
+A **PFX** (or **P12**) certificate is a password-protected digital certificate file that contains:
+- A **private key** (used for signing documents securely)
+- A **public certificate** (used to verify the signature’s authenticity)
+
+Using a custom certificate enhances trust and compliance by ensuring all signed documents carry your organization’s **digital identity**.
+
+---
+
+## ⚙️ How to Upload Your Custom Certificate
+
+Follow these steps to set up your custom signing certificate:
+
+1. **Log in** to your OpenSign account using your admin credentials.  
+2. Navigate to the **Console → Signing Certificate** section.  
+3. In the **Custom Signing Certificate** panel:
+   - Click **Choose File** and upload your `.pfx` or `.p12` certificate file.  
+   - Enter your **certificate password** (required to unlock the private key).  
+4. Click **Update** to save and activate your custom signing certificate.
+
+> Once updated, all new documents signed using your OpenSign account will be digitally signed with your uploaded certificate.
+
+---
+
+## 🧾 Using the Default OpenSign Certificate
+
+If you wish to revert to the standard OpenSign certificate:
+- Simply click **Use default OpenSign™ certificate**.  
+- OpenSign will replace your custom certificate with its default one.
+
+---
+
+## 🛡️ Security Notes
+
+- OpenSign securely encrypts and stores your uploaded certificate.  
+- Ensure that your PFX file and password are valid and belong to your organization.  
+- Invalid or expired certificates may prevent successful document signing.  
+- Use strong passwords for your certificate to maintain compliance and security.
+
+---
+
+## 💬 Need Help?
+
+If you encounter any issues while uploading or activating your certificate, contact our support team at  
+📩 **[support@opensignlabs.com](mailto:support@opensignlabs.com)**
+
+**Empower your brand with trusted digital signatures — securely with OpenSign™.**

From 9de3331cd243ca74c4ac8d9e7e94d7c750fa0080 Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 19:57:22 +0530
Subject: [PATCH 08/17] Create organizations.md

added the help content on manage organizations page.
---
 .../help/User Menu/Console/organizations.md   | 43 +++++++++++++++++++
 1 file changed, 43 insertions(+)
 create mode 100644 docs/docs/help/User Menu/Console/organizations.md

diff --git a/docs/docs/help/User Menu/Console/organizations.md b/docs/docs/help/User Menu/Console/organizations.md
new file mode 100644
index 000000000..1ae098e58
--- /dev/null
+++ b/docs/docs/help/User Menu/Console/organizations.md	
@@ -0,0 +1,43 @@
+# 🏢 Organizations
+
+The **Organizations** section allows administrators to manage company or team entities within **OpenSign**.  
+Each organization represents a workspace under which users, templates, and signing workflows are grouped and managed.
+
+---
+
+## 🚀 How to Set Up Organizations in OpenSign
+
+1. Log in to your **OpenSign** account using an **Admin account**.  
+2. Click on your **profile menu** (top-right corner) and select **Console**.  
+3. Once the **Console app** opens, navigate to the left sidebar and expand the **Teams** menu.  
+4. Click on **Organizations**.  
+5. The **Organizations Management** panel will appear, displaying the list of existing organizations and an option to add new ones.
+
+> 🔒 **Note:** The **Console** and **Organizations** pages are accessible only to **Admin users**. Regular users will not see this option in their menu.
+
+---
+
+## ➕ Add a New Organization
+
+To create a new organization:
+
+1. Click the **➕ (Add)** icon at the top right of the Organizations panel.  
+2. In the **Add Organization** popup:  
+   - **Name** — Enter the name of your organization. *(This field is required.)*  
+3. Click **Submit** to save or **Reset** to clear the input.
+
+> 💡 **Tip:** Use a clear and unique organization name (e.g., *OpenSign Labs*, *PS Inc.*) for easier identification in reports and team assignments.
+
+---
+
+## ⚙️ Manage Organizations
+
+The **Organizations table** lists all existing organizations with the following columns:
+
+- **Sr.No** — Serial number of the organization.  
+- **Name** — The registered name of the organization.  
+- **IsActive** — Toggle to activate or deactivate the organization.
+
+> 🔒 **Note:** Deactivating an organization will disable all associated users and workflows until it’s reactivated.
+
+---

From 806bb2e387ec416a4a2214fcedb0dad220ec0222 Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 19:58:28 +0530
Subject: [PATCH 09/17] Update organizations.md

updated the sidebar menu.
---
 docs/docs/help/User Menu/Console/organizations.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/docs/help/User Menu/Console/organizations.md b/docs/docs/help/User Menu/Console/organizations.md
index 1ae098e58..c4661d771 100644
--- a/docs/docs/help/User Menu/Console/organizations.md	
+++ b/docs/docs/help/User Menu/Console/organizations.md	
@@ -1,3 +1,8 @@
+---
+sidebar_position: 7
+title: Preferences
+---
+
 # 🏢 Organizations
 
 The **Organizations** section allows administrators to manage company or team entities within **OpenSign**.  

From 162e07bacc3aabbc7bae90f3a3e805cb9e4f10c7 Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 20:08:59 +0530
Subject: [PATCH 10/17] Create orgadmin.md

added the new help text for manage orgadmin page.
---
 docs/docs/help/User Menu/Console/orgadmin.md | 106 +++++++++++++++++++
 1 file changed, 106 insertions(+)
 create mode 100644 docs/docs/help/User Menu/Console/orgadmin.md

diff --git a/docs/docs/help/User Menu/Console/orgadmin.md b/docs/docs/help/User Menu/Console/orgadmin.md
new file mode 100644
index 000000000..c1b934de2
--- /dev/null
+++ b/docs/docs/help/User Menu/Console/orgadmin.md	
@@ -0,0 +1,106 @@
+---
+sidebar_position: 8
+title: Org Admins
+---
+
+# 👥 Org Admins
+
+The **Org Admins** section allows administrators to manage organization-level admin users within **OpenSign**.  
+Org Admins are responsible for managing users, templates, and signing workflows for their assigned organizations.
+
+---
+
+## 🚀 How to Access the Org Admins Page
+
+1. Log in to your **OpenSign** account using an **Admin account**.  
+2. Click on your **profile menu** (top-right corner) and select **Console**.  
+3. From the **left sidebar**, expand the **Teams** menu.  
+4. Click on **Org Admins**.  
+
+You’ll now see the **Org Admins Management Panel**, which displays all existing organization admins and seat usage.
+
+> 🔒 **Note:** The **Org Admins** page is accessible only to **Admin users**. Regular users will not see this option in their menu.
+
+---
+
+## 🧾 Org Admins Overview
+
+The **Org Admins** table lists all organization admins along with their key details:
+
+- **Sr.No** — Serial number.  
+- **Name** — Full name of the Org Admin.  
+- **Email** — Registered email address.  
+- **Organization** — Associated organization.  
+- **IsActive** — Toggle to activate or deactivate an Org Admin.  
+- **🗑️ Delete** — Remove an Org Admin permanently.
+
+> ⚠️ **Caution:** Deactivating an Org Admin restricts their access without deleting their data.  
+> Deleting permanently removes their access and data cannot be recovered.
+
+---
+
+## 🪙 Available Seats
+
+At the bottom-right corner of the Org Admins page, you will find the **Available Seats** indicator.
+
+
+- **Example:** `Available seats: 2/5  
+  - **2** — Indicates the number of seats currently in use.  
+  - **5** — Represents the total number of seats purchased.
+
+This helps you monitor how many Org Admin accounts can still be added under your current subscription.
+
+> 💡 **Tip:** Once all available seats are used, you can purchase additional seats using the **Buy more users** option.
+
+---
+
+## ➕ Add a New Org Admin
+
+To create a new organization admin:
+
+1. Click the **➕ (Add)** icon at the top-right corner of the Org Admins page.  
+2. The **Add User** popup will appear.
+
+### 🧩 Add User Fields
+
+- **Name** — Enter the Org Admin’s full name (Required).  
+- **Email** — Enter a valid email address (Required).  
+- **Password** — A random password will be auto-generated.  
+  - ⚠️ Copy and share it securely with the user — it will not be visible again.  
+- **Phone** — Optional field.  
+- **Organization** — Select the organization this user belongs to.  
+- **Remaining Users** — Displays how many more admins can be added under your available seats.
+
+Click **Submit** to create the Org Admin.
+
+---
+
+## 💳 Buy More Users (Add Seats)
+
+If you’ve reached your seat limit, you can buy more user seats to add additional Org Admins.
+
+1. Click on **Buy more users ➕** located at the top-right of the Org Admins page.  
+2. The **Add Seats** popup will appear.
+
+
+### 🧾 Add Seats Fields
+
+- **Quantity of users** — Enter the number of additional seats you want to purchase. *(Required)*  
+- **Price** — Automatically calculated based on the number of users selected (e.g., `1 * 20 = $ 20`).  
+
+Click **Proceed** to continue with the purchase.
+
+### 💬 Help Text for Add Seats Popup
+
+> - The price updates automatically based on the number of seats entered.  
+> - Once payment is successful, your **Available Seats** count updates in real-time.  
+> - You can then add new Org Admins under the increased seat capacity.
+
+---
+
+## 💬 Need Help?
+
+If you face any issues while managing Org Admins or purchasing seats, feel free to reach out to our support team:  
+📩 **[support@opensignlabs.com](mailto:support@opensignlabs.com)**
+
+**Empower your organization’s admins with OpenSign™!**

From 61be45cba289c11776a3be92ee569e592e3a79be Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Mon, 3 Nov 2025 20:34:31 +0530
Subject: [PATCH 11/17] Update organizations.md

updated the content of manage organization
---
 .../help/User Menu/Console/organizations.md   | 46 +++++++++++++++----
 1 file changed, 36 insertions(+), 10 deletions(-)

diff --git a/docs/docs/help/User Menu/Console/organizations.md b/docs/docs/help/User Menu/Console/organizations.md
index c4661d771..fb9fdf313 100644
--- a/docs/docs/help/User Menu/Console/organizations.md	
+++ b/docs/docs/help/User Menu/Console/organizations.md	
@@ -1,12 +1,35 @@
 ---
 sidebar_position: 7
-title: Preferences
+title: Organizations
 ---
 
 # 🏢 Organizations
 
-The **Organizations** section allows administrators to manage company or team entities within **OpenSign**.  
-Each organization represents a workspace under which users, templates, and signing workflows are grouped and managed.
+The **Organizations** section in **OpenSign** allows administrators to create and manage **separate groups** within a **Team or Enterprise account**.  
+Each organization acts as an **independent workspace** with its **own users, teams, templates, and signing workflows**.
+
+---
+
+## 🧩 What Are Organizations in OpenSign?
+
+An **Organization** represents a **distinct sub-account** under your main (team or enterprise) OpenSign account.  
+Organizations are completely **isolated** from each other — meaning:
+
+- Teams and users from one organization **cannot view or access** teams, documents, or users from another organization.  
+- Each organization functions as its own **secure workspace** within your overall account.  
+- You can manage multiple organizations from a **single admin console**, ensuring centralized control.
+
+### 💼 Example Use Case
+
+If your company manages multiple **clients or departments**, each with its own teams and sub-users, the **Organizations** feature is perfect for you.
+
+For example:
+- An agency can create **individual sub-accounts** for each client (Client A, Client B, etc.).
+- Each client’s team members and workflows remain **private and independent**.
+- The **main admin (enterprise account holder)** retains full control and visibility from the console.
+
+> 💰 **Billing:** All organizations under the same account are billed centrally by the **primary account holder**.  
+> This ensures simplified management and unified subscription handling.
 
 ---
 
@@ -16,9 +39,10 @@ Each organization represents a workspace under which users, templates, and signi
 2. Click on your **profile menu** (top-right corner) and select **Console**.  
 3. Once the **Console app** opens, navigate to the left sidebar and expand the **Teams** menu.  
 4. Click on **Organizations**.  
-5. The **Organizations Management** panel will appear, displaying the list of existing organizations and an option to add new ones.
+5. The **Organizations Management** panel will appear, displaying a list of existing organizations and the option to add new ones.
 
-> 🔒 **Note:** The **Console** and **Organizations** pages are accessible only to **Admin users**. Regular users will not see this option in their menu.
+> 🔒 **Note:** The **Console** and **Organizations** pages are accessible only to **Admin users**.  
+> Regular users will not see this option in their menu.
 
 ---
 
@@ -26,23 +50,25 @@ Each organization represents a workspace under which users, templates, and signi
 
 To create a new organization:
 
-1. Click the **➕ (Add)** icon at the top right of the Organizations panel.  
+1. Click the **➕ (Add)** icon at the top-right corner of the Organizations panel.  
 2. In the **Add Organization** popup:  
-   - **Name** — Enter the name of your organization. *(This field is required.)*  
+   - **Name** — Enter the name of your organization. *(Required)*  
 3. Click **Submit** to save or **Reset** to clear the input.
 
-> 💡 **Tip:** Use a clear and unique organization name (e.g., *OpenSign Labs*, *PS Inc.*) for easier identification in reports and team assignments.
+> 💡 **Tip:** Use clear and descriptive names (e.g., *Client Alpha*, *Marketing Division*, *PS Inc.*)  
+> for easier management and reporting.
 
 ---
 
 ## ⚙️ Manage Organizations
 
-The **Organizations table** lists all existing organizations with the following columns:
+The **Organizations table** lists all existing organizations with the following details:
 
 - **Sr.No** — Serial number of the organization.  
 - **Name** — The registered name of the organization.  
 - **IsActive** — Toggle to activate or deactivate the organization.
 
-> 🔒 **Note:** Deactivating an organization will disable all associated users and workflows until it’s reactivated.
+> ⚠️ **Note:** Deactivating an organization disables all its associated users and workflows until it is reactivated.
 
 ---
+

From 8538f0710a43618947a80d364fe2f6d9449ef515 Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Tue, 4 Nov 2025 10:50:46 +0530
Subject: [PATCH 12/17] Update signing_certificate.md

added new screenshot on the pfx certificate page.
---
 docs/docs/help/User Menu/Console/signing_certificate.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/docs/help/User Menu/Console/signing_certificate.md b/docs/docs/help/User Menu/Console/signing_certificate.md
index a5903ef8c..a64a33deb 100644
--- a/docs/docs/help/User Menu/Console/signing_certificate.md	
+++ b/docs/docs/help/User Menu/Console/signing_certificate.md	
@@ -43,6 +43,7 @@ Follow these steps to set up your custom signing certificate:
 If you wish to revert to the standard OpenSign certificate:
 - Simply click **Use default OpenSign™ certificate**.  
 - OpenSign will replace your custom certificate with its default one.
+<img width="861" height="408" alt="pfx_Certificate" src="https://github.com/user-attachments/assets/9063d927-c28f-4bb5-ac36-caeebc3845fc" />
 
 ---
 

From 0bbfe5ae3db03bd75136cd09de42e2c444c7529c Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Tue, 4 Nov 2025 12:47:16 +0530
Subject: [PATCH 13/17] Update organizations.md

updated the help text for the organization page.
---
 docs/docs/help/User Menu/Console/organizations.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/docs/help/User Menu/Console/organizations.md b/docs/docs/help/User Menu/Console/organizations.md
index fb9fdf313..c232a0106 100644
--- a/docs/docs/help/User Menu/Console/organizations.md	
+++ b/docs/docs/help/User Menu/Console/organizations.md	
@@ -71,4 +71,6 @@ The **Organizations table** lists all existing organizations with the following
 > ⚠️ **Note:** Deactivating an organization disables all its associated users and workflows until it is reactivated.
 
 ---
+If you require more help, feel free to reach out to our customer support on support@opensignlabs.com.
 
+Happy signing with OpenSign™!

From 3d4e43ede5b4f09a84b40c8c28374917d2efdc77 Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Tue, 4 Nov 2025 12:50:14 +0530
Subject: [PATCH 14/17] Update orgadmin.md

update the org admin page help text
---
 docs/docs/help/User Menu/Console/orgadmin.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/help/User Menu/Console/orgadmin.md b/docs/docs/help/User Menu/Console/orgadmin.md
index c1b934de2..35959ebca 100644
--- a/docs/docs/help/User Menu/Console/orgadmin.md	
+++ b/docs/docs/help/User Menu/Console/orgadmin.md	
@@ -6,7 +6,7 @@ title: Org Admins
 # 👥 Org Admins
 
 The **Org Admins** section allows administrators to manage organization-level admin users within **OpenSign**.  
-Org Admins are responsible for managing users, templates, and signing workflows for their assigned organizations.
+Org Admins are responsible for managing users, templates, and signing workflows for their organizations.
 
 ---
 

From e093d7a5f47171cd370798ea0f23ee0a92244afe Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Tue, 4 Nov 2025 13:06:21 +0530
Subject: [PATCH 15/17] Update general.md

updated the image on the general page
---
 docs/docs/help/User Menu/Console/general.md | 42 ++++++++++++++-------
 1 file changed, 29 insertions(+), 13 deletions(-)

diff --git a/docs/docs/help/User Menu/Console/general.md b/docs/docs/help/User Menu/Console/general.md
index 35ef902b6..f62f736b0 100644
--- a/docs/docs/help/User Menu/Console/general.md	
+++ b/docs/docs/help/User Menu/Console/general.md	
@@ -3,40 +3,56 @@ sidebar_position: 2
 title: General
 ---
 
-# General
+# General Settings
 
-The **General** section in OpenSign includes essential settings that allow the admin to manage and control the overall configuration of the OpenSign platform.
+The **General Settings** section in OpenSign provides key administrative settings to help you manage and control the overall configuration of your OpenSign platform.
+
+---
+
+## 🚀 How to Access the General Settings Page
+
+1. Log in to your **OpenSign** account using an **Admin account**.  
+2. Click on your **profile menu** (top-right corner) and select **Console**.  
+3. From the **left sidebar**, choose **General**.
+
+You’ll now be on the **General Settings** page.
+
+> 🔒 **Note:** The **General Settings** page is available only to **Admin users**. Regular users will not see this option in their menu.
 
 ---
 
 ## Enabled Signature Types
 
-Admins can define which signature types are available at the organization level.  
+Admins can define which signature types are available across the organization.  
 
-All users under your account will only see the signing methods you enable here in their **Preferences**. They will not be able to use any signature methods that are disabled by the admin.
+All users under your account will only have access to the signature methods you enable here in their **Preferences**. Any disabled methods will be hidden from their options.
 
 **Example:**  
-Adam, the administrator of your company account, disables the **Typed** signature option in the **Manage Signature Types** settings. As a result, Ursula, a team member, will no longer see the **Typed** signature option in her preferences.
+If Adam, the admin of your organization, disables the **Typed** signature type in the **Manage Signature Types** section, Ursula (a team member) will no longer see the **Typed** signature option in her preferences.
 
-Ursula can still enable or disable any of the remaining signature methods for each document she creates.  
-When she sends a document to Sofia (a signer), Sofia will only see the signature methods that Ursula selected during the document creation process.
+However, Ursula can still enable or disable any of the remaining signature types for each document she creates.  
+When she sends a document to Sofia (a signer), Sofia will only be able to use the signature methods that Ursula selected during the document setup.
 
-> **Note:** Managing **Signature Types** at the organization level is available only on the **Teams** plan.  
+> **Note:** Managing **Signature Types** at the organization level is available in the Teams and Enterprise plans.  
 > This feature is not included in the **Professional** or **Free** plans.
 
-![Signature type setup console](https://github.com/user-attachments/assets/c8c3de19-e82e-464a-977b-cdf3fd12aed7)
+<img width="918" alt="General settings" src="https://github.com/user-attachments/assets/60681095-6e53-4667-9f47-b3d4d38ab4b3" />
 
 ---
 
 ## Allow Indexing of Public Profile
 
-If this option is enabled, the user’s public profile will be indexed and appear in search results.
+When this option is enabled, user's public profiles will be indexed by search engines and may appear in search results.
 
 ---
 
 ## Email Template Customization
 
-This setting allows the admin to control whether users can create and manage their own email templates.
+This setting determines whether team members can create and manage their own email templates.
 
-- If the admin **disables** this setting, team users **cannot** create custom email templates for request signatures or document completion notifications.  
-- If the setting is **enabled**, users can customize their own individual templates.
+- If **disabled**, users **cannot** create or modify custom templates for signature requests or completion notifications. 
+- If **enabled**, users can design and manage their own personalized email templates.
+
+---
+
+Need help? [Join our Discord community](https://discord.com/invite/xe9TDuyAyj) for instant support.

From 4145ce8c0c8af7a941a8941846ac9ba17aed938d Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Tue, 4 Nov 2025 13:31:46 +0530
Subject: [PATCH 16/17] Update custom_filestorage.md

updated the content on the custom file storage page.
---
 .../User Menu/Console/custom_filestorage.md   | 58 +++++++++++++++----
 1 file changed, 47 insertions(+), 11 deletions(-)

diff --git a/docs/docs/help/User Menu/Console/custom_filestorage.md b/docs/docs/help/User Menu/Console/custom_filestorage.md
index 6a7376ff3..db9ce4bc0 100644
--- a/docs/docs/help/User Menu/Console/custom_filestorage.md	
+++ b/docs/docs/help/User Menu/Console/custom_filestorage.md	
@@ -5,22 +5,52 @@ title: Custom File Storage
 
 # 💾 Custom File Storage
 
+## 🌩️ Introduction to BYOC (Bring Your Own Cloud)
+
+OpenSign supports **BYOC (Bring Your Own Cloud)** — allowing you to **store your documents in your own cloud storage** instead of OpenSign’s default storage.  
+
+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**.  
+
+> 🧠 **Why BYOC?**  
+> - Maintain complete ownership and control of your documents.  
+> - Comply with internal, regional, or client-specific data policies.  
+> - Choose your preferred cloud region or provider for better performance and compliance.  
+
+---
+
+## 🚀 How to Access the Custom File Storage Setup
+
+Follow the steps below to navigate to the **Custom File Storage** setup page in OpenSign:
+
+1. Log in to your **OpenSign** account using an **Admin account**.  
+2. Click on your **profile menu** (top-right corner) and select **Console**.  
+3. In the **left sidebar**, go to **Storage**.  
+
+<img width="1722" height="814" alt="Custom file storage" src="https://github.com/user-attachments/assets/813f6685-3f36-40e4-aaaf-0d8b86bdc3b7" />
+
+You will now be on the **Custom File Storage** setup page where you can configure your own storage provider.
+
+> 🔒 **Note:** Access to Custom File Storage settings is available only to **Admin users**. Regular users will not see this option in their menu.
+
+---
+
 ## 🔔 Set Up File Storage
 
-This page allows users to configure their own file storage to store documents securely on their personal servers.
-
 By default, all users are connected to **OpenSign’s default file storage**.  
-If you prefer to use your **own custom file storage**, follow the steps below.
+If you prefer to use your **own custom cloud storage (BYOC)**, you can easily configure it here.
 
-You can create an **AWS S3 bucket** to store your uploaded documents through OpenSign.  
-To configure OpenSign with your cloud storage setup, refer to this guide:  
+You can set up an **AWS S3 bucket** or **DigitalOcean Space** to store your uploaded documents securely.  
+To configure OpenSign with your cloud storage, refer to this detailed guide:  
 👉 [Cloud Storage Setup Guide](https://docs.opensignlabs.com/docs/self-host/cloud-storage/s3)
 
 ---
 
 ### 🪣 Steps to Configure Custom Storage
 
-1. Click the **Add New** button.  
+1. Click the **Add New** button.
+
+<img width="861" height="408" alt="Add new workspace" src="https://github.com/user-attachments/assets/0f734c6a-e2ac-445a-8194-746b9c202f0a" />
+
 2. Fill in the following details:
 
    - **Unique File Adapter Name:** Enter a unique name for your storage configuration.  
@@ -35,23 +65,29 @@ To configure OpenSign with your cloud storage setup, refer to this guide:
 3. Once all details are filled, click **Save and Activate** to enable your custom file storage.
 
 After activation:
-- All your documents will be stored in the configured storage provider.  
+- All your documents will be stored in the configured **BYOC storage provider**.  
 - You will be automatically logged out to clear any previous file adapter data from your local session.  
 - Upon logging in again, your custom file storage will be active, and all future documents will be saved there.
 
+<img width="861" height="408" alt="custom file storage" src="https://github.com/user-attachments/assets/1add417d-f745-4e00-8cf3-7dcd9798f4db" />
+
 ---
 
 ### ⚠️ Important Note
 
-In some cases, documents stored in your custom file storage may not load in OpenSign due to **CORS (Cross-Origin Resource Sharing)** policy restrictions.  
-If you’ve activated custom file storage, make sure your storage configuration **allows OpenSign to access your documents** and does **not block requests** due to CORS errors.
+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.  
+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.
 
+👉 [Read the article to learn how to set up CORS policies](https://docs.opensignlabs.com/docs/self-host/cloud-storage/s3)
 ---
 
 ## 💬 Need Help?
 
-If you need help setting up or testing your custom file storage integration, contact our support team at  
-📩 **[support@opensignlabs.com](mailto:support@opensignlabs.com)**
+If you need help setting up or testing your BYOC or custom file storage integration, contact our support team at  
+📩 **[support@opensignlabs.com](mailto:support@opensignlabs.com)**  
+
+Or join our community for instant assistance:  
+💬 [Join our Discord](https://discord.com/invite/xe9TDuyAyj)
 
 **Happy Signing with OpenSign™!**
 

From d868fdf6f201d1c189d2290d813c889c3a0f978c Mon Sep 17 00:00:00 2001
From: pravin <pravin@nxglabs.in>
Date: Tue, 4 Nov 2025 13:52:34 +0530
Subject: [PATCH 17/17] Update custom_filestorage.md

---
 docs/docs/help/User Menu/Console/custom_filestorage.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/docs/help/User Menu/Console/custom_filestorage.md b/docs/docs/help/User Menu/Console/custom_filestorage.md
index db9ce4bc0..146d7763c 100644
--- a/docs/docs/help/User Menu/Console/custom_filestorage.md	
+++ b/docs/docs/help/User Menu/Console/custom_filestorage.md	
@@ -79,6 +79,7 @@ In some cases, documents stored in your **custom (BYOC)** file storage may not l
 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.
 
 👉 [Read the article to learn how to set up CORS policies](https://docs.opensignlabs.com/docs/self-host/cloud-storage/s3)
+
 ---
 
 ## 💬 Need Help?