Google Blob Storage

Storage Connector – Google Blob Storage

The Google Blob Storage connector lets you push signed documents, attachments, and completion certificates from emSigner directly into a Google Cloud Storage bucket of your choice, giving you full control over where your signed documents reside.

Navigation: Settings → Storage Connectors for Document Repositories → Google Blob Storage tab

The setup follows a two-step flow: Test Connection → Activate.

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.

Configuration Fields

Field	Description
Bucket Name (required)	The name of the target Google Cloud Storage bucket where documents will be stored. The bucket must already exist before configuring the connector.
Default Credentials Json data (required)	The entire service-account key file content, in JSON format. The service account must have the Storage Object Admin role on the bucket (create, read, and delete permissions).

Steps to Configure

1. Go to Settings and click on Storage Connectors for Document Repositories.

2. Select the Google Blob Storage tab.

3. Review the Sending Options — Include Signed documents only and Include attachments are enabled by default. Optionally, select Include completion certificate.

4. Enter the Bucket Name.

5. Paste the full service-account JSON key into the Default Credentials Json data field. Ensure the service account has the Storage Object Admin role on the bucket and that the bucket already exists.

1. Click Generate test file to validate the connection under Step 1: Test Connection.

2. Once the test succeeds, proceed to Step 2: Activate to enable the connector.

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).