WEBDIENSTE/OpenSign
1
0
Fork 0
mirror of https://github.com/OpenSignLabs/OpenSign.git synced 2026-08-20 06:35:54 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update Preferences.md

Browse Source 
updated Preferences page contents.
This commit is contained in:
pravin
2025-05-20 11:26:49 +05:30
committed by GitHub
parent 70abddec3a
commit c059e95fa9
1 changed files with 136 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/docs/help/Settings/Preferences.md
+136 -39
View File
@@ -18,24 +18,29 @@ The **Allowed Signature Types** section defines which signature methods are avai
- ✅ **Upload**: Upload a scanned or saved image of your signature.
- ✅ **Default**: Use the default signature stored under *My Signature* in settings.
⚙️ The options selected here will determine what appears in the signature widget during the signing process.
⚙️ The options selected here will determine what appears in the signature widget during document creation and signing. You can also change these preferences while creating the document.
---
## 🔄 Multi-Level Signature Type Control
**OpenSign™ v2.6.0** introduces flexible control over signature options at three levels:
### 📄 Document-Level
Set different signature types per document, ideal for adapting to specific legal or regulatory requirements.
### 👤 User-Level
Each user can define their preferred signature options, ensuring a familiar and consistent signing experience.
**OpenSign™** introduces flexible control over signature options at three levels:
### 🏢 Organization-Level
Admins can enforce company-wide signing policies by restricting signature methods platform-wide.
> This layered control helps teams maintain compliance while optimizing usability.
> In the **Console Application > General**, admins can set allowed signature types at the organization level. Only the selected types will be shown on the **Preferences > Signature** page for users.
### 👤 User-Level
> Navigate to **Settings > Preferences** to configure user-level signature types.
If a user sets preferred types here, only these will be shown when adding signature or initial widgets during document creation.
### 📄 Document-Level
> While creating a document, users can set specific allowed signature types.
Only these will be available to the signer—useful for legal or regulatory requirements.
---
@@ -46,43 +51,28 @@ Enable or disable email or in-app notifications when a document is signed.
- **Yes** – Receive alerts for each completed signature.
- **No** – Notifications are turned off.
**Details:**
The document creator will receive an email notification whenever a signer signs the document.
**Note**: Regardless of this setting, a completion email with the signed document and completion certificate attached is always sent to all signers and the document owner.
> User can change this option while creating the document or template.
**Details**:
The document creator will receive an email notification whenever a signer signs the document.
**Note**: Regardless of this setting, a **completion email** with the signed document and completion certificate is **always sent** to all signers and the document owner.
---
## 📬 Send in Order
Decide whether the document should be signed sequentially or simultaneously by multiple signers.
Decide whether the document should be signed **sequentially** or **simultaneously** by multiple signers.
- **Yes** – Signers receive the document in a set order.
- **No** – All signers receive the document at once.
**Details:**
Choose how you want the signing requests to be sent to the document signers:
> User can change this option while creating the document or template.
- **Yes**: Sends the signing request to the first signer initially. Once the first signer completes their part, the next signer in the sequence receives the request. This continues until all signers have signed. This ensures the document is signed in a specific order.
**Details**:
- **No**: Sends signing links to all signers simultaneously. Each signer can sign at their convenience, regardless of whether others have signed. This method is faster but does not enforce any order.
Select the option that best suits your document processing needs.
---
## 🧭 Timezone & Date Format
Customize the **Timezone** and **Date Format** according to your regional preferences.
- Supports **12-hour** or **24-hour** time formats.
- Affects the timestamp shown on the platform and audit trails.
---
## 🧪 LTV Enabled Signatures (BETA)
Enable **Long-Term Validation (LTV)** to ensure the authenticity of the signature over time.
*Currently in beta testing.*
- **Yes**: Signers are notified one after another. The next signer gets access only after the previous has completed signing.
- **No**: All signers receive links at the same time. They can sign independently of one another.
---
@@ -93,10 +83,117 @@ The tour feature provides guidance for first-time users. You can turn this off f
- **Yes** – Show onboarding tips.
- **No** – Disable tour prompts *(recommended for experienced users)*.
**Details:**
- **Yes**: Enables a guided tour for signers, providing instructions during the signing process.
- **No**: Disables the guided tour, ensuring a faster, uninterrupted experience.
> User can change this option while creating the document or template.
**Tip**: If your signers are familiar with OpenSign™ and use it frequently, disabling the tour can create a more seamless experience. Choose the option that best fits your document signing needs.
**Details**:
- **Yes**: Enables guided tooltips for the signer during the signing process.
- **No**: Disables the tour, speeding up the signing experience.
💡 **Tip**: Disable if your users are already familiar with OpenSign™.
---
## 🧭 Timezone & Date Format
Customize the **Timezone** and **Date Format** according to your regional preferences.
These settings are reflected in:
- Document Completion Certificates
- Signing Logs
- Webhooks
### 📅 Date Format
- Used as the **default format** for date widgets when creating documents.
- Applies in all flows including APIs.
### 🕒 Time Format
- Supports **12-hour** and **24-hour** formats.
- Affects timestamps in certificates, logs, and webhooks.
---
## 🧪 LTV Enabled Signatures
**LTV (Long-Term Validation)** ensures that signatures remain valid and verifiable even after certificates expire or are revoked.
### 🔐 Key Features:
- Embeds certificate chain
- Includes CRLs and OCSP responses
- Enables offline verification
- Complies with PDF standards like **PAdES**
### 📌 Why It Matters:
Even if a certificate becomes invalid in the future, the LTV-enabled signature stays verifiable.
### ✅ Use Cases:
- Legal Contracts
- Financial or Medical Records
- Long-term archiving requirements
---
## 📧 Email Templates
In the **Preferences > Email** tab, users can customize email templates for:
### ✉️ Request Signature Email
Once set, all signers will receive the customized request email.
### 📩 Document Completion Email
On completion, all signers receive the custom-formatted email with the signed document.
---
## 🔒 Security
### ✅ Two-Factor Authentication (2FA)
Adds a second verification step when logging in.
### Benefits:
- Enhances account protection
- Requires time-based code from an app like Google Authenticator
### How to Enable:
1. Go to **Security > Setup 2FA**
2. Scan the QR Code with an authenticator app
3. Save Recovery Codes for backup
4. Enter verification code to complete setup
> If 2FA is enabled, you’ll be prompted for a verification code after entering your password.
---
### 🛡️ Passkey Authentication
Passkeys offer **passwordless** and **phishing-resistant** sign-in.
#### 🔐 Key Features:
- Use fingerprint, face ID, or device PIN
- Passwordless and secure
- Reduces credential theft risks
### 🛠 How to Register a Passkey:
1. Click **Register another passkey**
2. Your device prompts biometric or PIN-based authentication
3. On success, the passkey is saved and listed under **Your Passkeys**
### 🧾 Managing Your Passkeys
Each passkey entry shows:
- Name (e.g., "Windows Edge")
- Created Date
- Last Used Date
- Credential ID
#### ✏️ Rename:
Click the **pencil icon** to rename a passkey.
#### 🗑 Delete:
Click the **trash icon** to remove a passkey.
⚠️ This revokes access via that method.
---
For more assistance with OpenSign™ features or APIs, contact our support team at **[support@opensignlabs.com](mailto:support@opensignlabs.com)**.