Domain Settings

This page allows administrators to configure settings specific to the selected domain. By default, domains will inherit the system settings, but may override them as needed. Entra domains will have additional settings for connecting to Microsoft Entra ID, which can be found on the Entra Management page.

General

The Concurrent User Limit defines the maximum number of users that may be logged into this domain at one time.

The Default Language sets the language for system generated text like default emails and metadata. The user interface will still follow the language of the user’s browser. Currently English, Portuguese, and Spanish are supported, though more languages may be added if a translation file is provided.

Note

Translations can be placed at {Tomcat directory}\webapps\liveforms\WEB-INF\classes\ with file name in the format messages_{lang}_{REGION}.properties. Then admins can add an entry in the dropdown in the file {Tomcat directory}\webapps\liveforms\WEB-INF\views\common-nav-top.jsp.

The Default Country or Region dropdown changes how dates will be formatted in form submissions. They can either follow the convention of the selected domain language, or it can be set to a specific country’s common format.

When Enable User Name Editing is checked, users will be able to change their username in their profile.

Notifications

This section allows you to override the system notification policies for the domain. Instant task notifications are sent the moment a task appears in the user’s task list. Periodic task reports are sent at a specified time and contain a list of all tasks assigned to the user.

Options include:

  • Opt-in: Users must explicitly select the option in their profile to receive notifications.

  • Opt-out: Users receive notifications by default, but may unselect the option in their profile.

  • Enforced: Users are forced to receive notifications, provided they have their email set up.

Security

This section allows admins to configure password policies for the domain. Admins may override the password requirements, expiration, and limits independent of each other.

  • Minimum Password Length: The minimum number of characters a password must have. When set to 0, there is no minimum length.

  • Require Symbols: If enabled, passwords must contain at least one symbol.

  • Require Numbers: If enabled, passwords must contain at least one number.

  • Require Mixed Case: If enabled, passwords must contain at least one uppercase and one lowercase letter.

  • Password Expiration: If enabled, passwords will expire after a set number of days. When set to 0, passwords will never expire.

  • Reset Expiry Periods: Resets the expiration timer for all users when the configuration is saved.

  • Old Password Limit: The number of previous passwords that cannot be reused. When set to 0, there is no limit on reusing old passwords.

E-mail Configuration

Email configuration allows sending emails for task notifications and form rules. Domains may override the systems email settings so it may have its own SMTP options.

  • The From field is the email address sending the messages.

  • mail.smtp.host is the server address that will be handling email requests.

  • mail.smtp.port is the port on the server which accepts SMTP requests.

  • mail.smtp.auth determines if log in information is required to connect to the SMTP.

  • mail.smtp.starttls.enable this option sets whether TLS encryption will be used for connection.

  • Username and Password are used to authenticate access with the SMTP.

Payment Portal Configuration

This section defines the connection information to Herring Bank’s payment services. Domains may override these settings for different payment connections.

When configuring an account with Financial Payments, the LiveForms callback URL is: https://<server>/liveforms/web/fpPaymentGateway where <server> is the server name where LiveForms is hosted. This URL is used by Herring Bank to notify the form of a successful payment, thus this URL must be accessible from the public internet. Forms will use Fee as the transaction type when a charge is done with this service. The testing and production URL that forms will send Financial Payments to can be configured using the URL fields.

Callback Username and Password allow payment requests to be authenticated, and will be provided by Herring Bank when making an account with them.

dbs eSign

This section configures the connection to Connective eSign, which provides electronic signature certificates.

  • API URL is the address to the eSign service.

  • API Login is the API user login.

  • API Password is the password to the API if required.

  • Default Initiator is the Connective eSign user that will initiate signature procedures.

Captcha

This section holds the captcha key which is required for captcha controls to function.

Feedback Contact

This allows a custom help contact for users in this domain. Feedback information includes the Entity name, support E-mail, and help Phone number.

AI configuration

This section allows administrators to configure the domain’s AI model used for the rule assistant. Current settings are compatible with OpenAI’s API.

  • AI API Key: The API key used to send and receive requests with the AI service. Setting this blank will disable the AI assistant.

  • AI Completion URL: The URL endpoint for the AI service to generate completions.

  • AI Model: The specific AI model to use for generating completions. The default value is gpt-4o-mini.

  • AI Type: The type of AI interaction. Current options include Chat and Assistant.

    • Chat: Uses the default untrained model for requests. Can be given system context to help generate more relevant responses. These models generally respond faster and use fewer tokens, but may not be as accurate as trained models.

    • Assistant: Uses a model which can be trained with files through the OpenAI dashboard. The assistant ID field is used to specify which assistant to use for requests. The default assistant asst_PAoPakedg30dsFlbeWcgVXhp has been trained with our rules and control documentation. While responses are more accurate, assistants use more tokens and can take longer to respond.