Application Settings Overview
Application Settings Overview
Published on May 6, 2026
4 minute(s) read
Settings that apply to your instance as a whole, rather than to specific flows or blocks, can be found in Administration > System Settings.
The Settings page is divided into the following sections:
- Document Classification
- Identification
- Transcription
- Custom Supervision
- General
- Performance
- Beta Features
Below is a table of the available non-beta application settings, what they enable, which section they are in, and what their default values are.
Document Classification settings
| Setting | Description | Default Value |
|---|---|---|
| Continuous Classification model improvement | When this setting is enabled, the system will train new models automatically and then deploy those models after their training is complete. To learn more, see Automatic Document Classification. | Enabled |
| Training Data Management for Classification | When this setting is enabled, submission data is used for model training in Training Data Management. | Disabled |
Identification settings
| Setting | Description | Default Value |
|---|---|---|
| Continuous Field Locator model improvement | Automatically trains and deploys new Field Locator models. To learn more, see Identification Settings. | Disabled |
| Training Data Management for Field ID | When enabled, a sampling of submission data is sent to Training Data Management to train future iterations of Field Identification models. | Disabled |
| [v41.2 and later] Training Data Management for Table ID | When enabled, a sampling of submission data is sent to Training Data Management to train future iterations of the model. | Disabled |
Transcription settings
Projected Automation Based on Target Accuracy
This graph shows the levels of automation you can expect for each field type, based on the target accuracies you’ve entered in your flow’s settings. You can view the expected automation levels for a specific flow by selecting it from the Select Flow drop-down list.
To learn more about setting target accuracies, see the General Transcription settings section of Flow Settings. For an overview of Transcription settings, see Transcription Settings.
Transcription Masking
| Setting | Description | Default Value |
|---|---|---|
| Currency Mask Prefix | Currency mask prefix to use during Manual Transcription Supervision and Transcription QA. | $ |
Custom Supervision settings
| Setting | Description | Default Value |
|---|---|---|
| Show Custom Supervision Tasks as separate items | Allows users to control how Custom Supervision tasks appear on the Perform Tasks page ( Tasks > Perform Tasks). Learn more in Perform Tasks Tab. |
- When enabled:
- Each Custom Supervision Task type is shown separately, but only if there are active tasks of that type.
- When disabled (default behavior):
- All Custom Supervision tasks are grouped under Custom Supervision on the Perform Tasks page.
Note: - Separate Custom Supervision task types are displayed in alphabetical order, not by creation time or deadline. | Disabled |
General settings
| Setting | Description | Default Value |
|---|---|---|
| PII Data deletion (images and fields only) | This setting allows users to periodically remove images and PII data from the system. | Disabled |
| PII Deletion policy | If PII Data deletion is enabled, this setting allows you to delete the data at a specific time. You can also choose to delete PII a certain number of days after either submission completion or submission creation. | 30 days after |
| submission complete date | ||
| starting at 12:00 PM | ||
| Submission record deletion | If PII Data deletion is enabled, this setting allows you to delete submission records that have had their PII deleted and have already been used in Transcription Automation Training (if enabled). | Disabled |
| Submission record deletion policy | If Submission record deletion is enabled, allows you to specify how long after PII deletion or Transcription Automation Training to delete submissions. You can also specify the time of day that submissions will be deleted and how much time the system will spend on submission deletion each day. | 30 days after min window starting at 12:00 pm, 5 hours |
| Activity Log deletion | If enabled, the system deletes entries from the Activity Log after a specified period of time. The user can also configure the time of day and runtime for the deletion job; if the job does not delete all of the data scheduled for deletion, the remaining data will be deleted the next time the job runs. | Disabled |
| Activity Log deletion policy | If Activity Log deletion is enabled, this setting allows you to specify how many days should pass after an activity before that activity’s record is removed from the Activity Log. It also allows you to specify the time of day that the deletion will take place. | 90 days after the activity starting at 2:00 pm |
| Activity Log deletion maximum runtime | If Activity Log deletion is enabled, this setting allows you to specify how many minutes the system will spend deleting Activity Log records each day. | 30 minutes |
| PDF extraction | If enabled, when a user uploads a PDF to the layout editor for a structured document, Hyperscience will use the PDF metadata to create fields for the layout. | Disabled |
| Submission upload | If enabled, users can upload submissions by clicking Create Submission on the Submissions page. | Enabled |
| Submission processing | This setting allows you to set a system-default deadline for the processing of submissions. To learn more, see Prioritizing Submissions. | 24 hours after submission creation |
| Business Calendar | This setting allows you to specify a single set of business days and holidays for your instance, which can then be factored into the submission-processing deadlines you define at the instance, layout variation, or Input Block levels. For more information, see Prioritizing Submissions. | Weekdays are business days, Saturdays and Sundays are non-business days, no holidays specified |
| Session timeout | This setting controls when an inactive user will be automatically logged out of the system. | 240 minutes |
| QA uniqueness | After a keyer completes a Transcription Supervision or Field ID Supervision task for a field, they will not be able to work on QA tasks of the same type on that field if there is another active keyer. | Enabled |
Performance settings
| Setting | Description | Default Value |
|---|---|---|
| Gather health statistics | This setting gathers health statistics covering a 48-hour period. Disabling the setting may improve system performance and makes the Health Statistics cards at Settings > System & Health grayed out. | Disabled |