DocuSign Collection

SearchBlox provides a DocuSign Collection that allows you to index documents and envelopes stored in your DocuSign account. This feature enables SearchBlox to securely connect to DocuSign using API credentials, retrieve relevant documents, and crawl their content. The indexed data can then be searched efficiently, making it easier to access and manage signed agreements and related files.

Creating a DocuSign Collection

You can create a DocuSign Collection by following these steps:

• Log in to the Admin Console, go to the Collections tab, and click Create or the “+” icon.

• Select DocuSign Collection as the collection type.

• Enter a unique name for the collection. The name must contain 3–36 alphanumeric characters, and only underscores (_) are allowed.

• Enable or disable RAG (Retrieval Augmented Generation) depending on your requirement. Enable it if the collection will be used for AI-powered search or chatbot responses.

• Enable Knowledge Graph if you want SearchBlox to extract entities and relationships from the documents in the collection.

• Choose whether the collection should be Private or Public. Enable Private Collection Access to restrict the collection to authenticated users only.

• Configure Collection Encryption if you want to encrypt document content or specific metadata fields.

• Select the Collection Language based on the language used in the documents. The default language is English.

• Click Create to create the DocuSign Collection.

• After the collection is created, you will be redirected to the DocuSign Settings / Authentication section to configure the connection and access details.

Configuring DocuSign Settings

To configure DocuSign integration for your collection, follow these steps:

1. Go to the DocuSign Settings tab within the collection.

2. Enter the Integration Key.
   This is the DocuSign API Integration Key (Client ID) obtained from your DocuSign developer account. It uniquely identifies your application.

3. Enter the Secret Key.
   Provide the API Secret Key associated with your DocuSign integration. This is used for secure authentication.

4. Enter the Account ID.
   Specify your DocuSign Account ID, which identifies your DocuSign account and is required for API operations.

5. Enter the Base URL (Optional).
   Provide the DocuSign API base URL.

   • Default (Sandbox): https://demo.docusign.net
   • Production: https://www.docusign.net
     Use the appropriate URL based on your environment.

6. Enter the Access Token.
   This is the OAuth access token used to authenticate API requests to DocuSign. It is required for making API calls.

7. Enter the Refresh Token (Optional).
   Provide the OAuth refresh token to obtain a new access token when the current one expires, ensuring uninterrupted access.

8. Click Save to store the configuration and enable the system to access and manage DocuSign documents.

Schedule and Index

Sets the frequency and the start date/time for indexing a collection. Schedule Frequency supported in SearchBlox is as follows:

• Once
• Hourly
• Daily
• Every 48 Hours
• Every 96 Hours
• Weekly
• Monthly

The following operation can be performed in Azure blob collections

Manage Documents Tab

• Using Manage Documents tab we can do the following operations:

  1. Filter
  2. View content
  3. View metadata
  4. Refresh
  5. Delete

• To delete a file from your collection, enter the file path and click "Delete".

• To see the status of an indexed file, click "View Metadata".

Data Fields Tab

Using Data Fields tab we can create custom fields for search and we can see the Default Data Fields with non-encrypted collection. SearchBlox supports 4 types of Data Fields as listed below:

Keyword
Number
Date
Text

• Once the Data fields are configured, collection must be cleared and re-indexed to take effect.

Docusign Collection Models

The Models page allows you to configure and override AI models used for embeddings, reranking, and LLM-based features within the collection.

Embedding

• Provider specifies the embedding provider used to generate vector representations of documents.
• Model defines the embedding model used to convert document content into vectors for semantic search.

Reranker

• Provider specifies the reranker provider used for improving search result relevance.
• Model defines the reranker model used to re-score and reorder search results based on relevance.

LLM

• Provider specifies the Large Language Model provider used for AI-powered features.

• Model defines the LLM used for tasks such as document enrichment, summaries, and SmartFAQs.

• These settings override global configurations and apply only to the current collection.