Core Settings

SigningHub Core is responsible for performing background housekeeping tasks like documents deletion, emails sending, auto reminders sending, documents auto declining and many other important tasks.

This subsection specifically discusses the settings related to SigningHub Core for your on-premises deployment

Configure the "Core Settings" parameters in SigningHub Global Settings

Click the "Configurations" option from the left menu.
Click the "Global Settings" option.
Global Settings will appear, select the "Core Settings" option from the top right drop down.
Configure these settings as required and click the "Save" button from the screen bottom.
See the below table for fields description.
To make the "Email Retry Count" and "Read Notifications Deletion Duration (days)" related changes effective, click the "Save" button from the bottom of the screen. However for rest of the core related configurations, restart the Core from IIS to make them effective.

Global Settings - Core Settings
Fields	Description
Email Retry Count	Specify the number of retry attempts (i.e. 5) SigningHub Core should make to send an email, in case it is failed in the first attempt due to any technical issue. This thread is executed after 20 mins for the first time and then after every 60 minutes, till the specified count is reached. After this number of retries, a failure email alert will be sent to the document owner.
Failed Requests Retry Count (Document Processing \| Workflow Completion)	Specify the number of retry attempts (i.e. 5) SigningHub Core should make to push the publishing requests of document processing and workflow completion reports onto their configured URLs, in case they are failed in the first attempt due to any technical issue. This thread is executed after every 6 hours till the specified count is reached. Please note: The document processing report is published on Enterprise Settings> Advanced > More> Send Document processing report as XML The workflow completion report is published on Enterprise Settings> Integration> Workflow Completion Report> Server URL After this number of retries: In case of document processing report, SigningHub Core will delete the publishing request and add an entry in the info log. In case of workflow completion report, SigningHub Core will send the workflow completion report to the respective enterprise owner via an email attachment.
Read Notifications Deletion Duration (days)	Specify the number of days (i.e. 7) after which SigningHub Core should delete the on-screen read notifications of the end users. The specified number of days (i.e. 7) old read notifications will be deleted from each user's "Notifications" screen in SigningHub Desktop Web.
Retry Sending Emails	Tick this check box to configure SigningHub Core to retry sending those emails that were failed in the first attempt due to any technical issue. SigningHub Core will make the specified number (i.e. Email Retry Count) of retry attempts to send that emails. This thread is executed after 20 mins for the first time and then after every 60 minutes, till the specified count (i.e. Email Retry Count) is reached.
Delete Documents Asynchronously	Tick this check box to configure SigningHub Core to purge the deleted documents (i.e. mark as deleted) from database. This thread is executed after every 60 minutes.
Send Summary Emails	Tick this check box to configure SigningHub Core to look for the users who have configured daily summary emails in their account settings, and send these emails accordingly. Summary emails are sent to the document recipients from SigningHub, for all their pending documents on each day end, instead of sending individual email notifications for every document that is shared with them. This thread is executed daily at 1 AM according to the server deployment timezone.
Clean Document Storage	Tick this check box to configure SigningHub Core to purge documents on the basis of the following rules, and also clean the document storage directory as configured in Document Storage. This thread is executed daily at 2 AM according to the server deployment timezone, and will delete the following documents: Delete unused and dangling documents, i.e. delete all the document packages that have 0 documents or those packages for which there is no folder item in database. Auto decline documents, i.e. decline all the document packages on which the 'Document Access Duration' permission is applied, and their access duration has expired. Auto delete documents, i.e. delete all the document packages against those service plans for which "Auto Deletion" is enabled and the documents are due to be deleted as per configured number of days in service plan, see details. Delete temp files from data directory, i.e. delete unused chunks of documents which are 2 days old, and are created inside the Document Storage when an upload is failed on SigningHub Desktop Web.
Clean Database	Tick this check box to configure SigningHub Core to perform the useful activities that help deleting obsolete data from the database and optimising the storage resources. This thread is executed daily at 3 AM according to the server deployment time zone, and will perform the following activities: License expiry, i.e. check licence expiry date in database and notify user as per the "License Alert Settings" configurations. License signature quota notification, i.e. check signature quota in the license and notify user via email as per the "License Alert Settings" configurations. Delete older notifications, i.e. delete those notifications whose "Read Notifications Deletion Duration (days)" has passed and are also read by the user. Delete older Remote Authorised Signing Requests (RAS), i.e. delete those remote authorised signing requests from database that have been expired. Delete revoked certificates, i.e. delete all those certificates from the database that have been revoked for any reason. Delete expired sessions, i.e. delete those sessions from database that are expired. Delete expired refresh tokens, i.e. delete those refresh tokens from database that are expired. Delete inactive guest users, i.e. delete those guest users who have not performed any activity in SigningHub for 60 consecutive days. In such a case no notification email will be sent to them prior to deleting their account. Delete inactive users, i.e. delete inactive users based on the service plan configurations. Delete failed push requests, i.e. delete all the failed push requests that are older than 15 days.
Delete Activity Logs	Tick this checkbox to configure SigningHub Core to delete all activities for the end users . This will further bring a field "Activity logs retention period (months)" to specify number of months (i.e. 12) prior to which activity logs will be deleted from each user's "Activity" screen in SigningHub Desktop Web.. This thread is executed daily at 2 AM according to the server deployment time zone. In case, the thread is turned off, the system will not delete activity logs automatically.
Send Reminder Notifications	Tick this checkbox to configure SigningHub Core to look for the configured reminders of each user (Document Recipient) in the queue and send them accordingly.This will further bring a field "Send Reminder Notification Time (UTC)" to specify the reminder notification time. This thread is executed daily at configured time according to the UTC time zone. In case, the thread is turned off, the system will not send auto-reminder notifications automatically.
Synchronize Active Directory Contacts	Tick this check box to configure SigningHub Core to sync Active Directory contacts of all those enterprises, for which Active Directory provisioning is enabled and Active Directory Security Group(s) are mapped to their enterprise roles. SigningHub Core will fetch all the Active Directory users of such enterprises and add them as their Enterprise Contacts. If a contact already exists in the "Enterprise Contacts" section, then it will be discarded. This thread is executed daily at 4 AM according to the server deployment time zone.
Reset Service Plan Statistics	Select this check box to configure SigningHub Core to run a thread for resetting the statistics of trial plans by the following mechanism: The system will get all the service plans that have Billing Mode set as Trial and Auto Reset Constraints is enabled. The system will get all the Enterprises and Individual Users whose Auto Reset Date is less than the current date. The system will reset the statistics (including signatures/workflows) of the fetched service plans. The system will update Auto Reset Constraints in database with addition of 30 days so that user and enterprises can consume the provision accordingly. The thread is executed every day at 1:00 AM according to the server deployment time zone. In cases like when you do not have any trial based plans in your deployment, clear the check box to disable this thread.
Downgrade Service Plan	Select this check box to configure SigningHub Core to run a thread for downgrading paid plans by the following mechanism: The system will get all the plans that have Billing Mode set as Online The system will check all enterprises and individual users as per their last billing date. In case expiry date (including grace period) has been reached and payment is not made, then Core will downgrade the plan based on configurations. Downgrade Plan will cover the following actions: The current service plan of the Enterprise and Individual users will be downgraded according to the Service Plan configured in SigningHub Admin under Global Settings > Service Plan. Cancel Agreement with Vendor and SigningHub, and mark billing status as inactive. Add user activity Notify User - the notifications will be send to account owner based on the settings configured under Notifications. Downgrade user's service plan Reset statistics of workflow and signature as per the downgraded service plan Update user information (life cycle) as Other in HubSpot This thread is executed every day at 1:30 AM according to the server deployment time zone. In cases like when you do not have any paid plans in your deployment, you may clear the check box to disable the thread. In case, the thread is turned off, the system will not downgrade the plans automatically. The means that the users (of the plans that need downgrading) will still be able to perform signatures if their plan's limit hasn't reached yet. In case, the limit has reached, they will not be able to perform any activity on SigningHub, and system will prompt the users accordingly.

There is another important thread that automatically runs on weekly basis, i.e. Rebuild Database Indexes

As obvious from its name, this thread rebuilds database indexes and is executed on every Sunday at 6 AM according to the time zone of server deployment.