Configuration

System settings are separated into panels centered around certain features. All setting changes are saved by clicking the Save button at the bottom of the page.

General

These fields deal with common or miscellaneous settings.

  • External Base URL: This field defines the beginning of links generated by the system, such as the emailed links for forms or tasks.

  • Default Domain: This is the default domain for users logging in with Entra ID. If multiple domains with Entra ID exist, users logging into other domains will need to select theirs from the dropdown.

Notifications

This section allows admins to configure system-wide notification policies.

The Instant Task Notification policy and Periodic Task Report Policy dropdowns specify the default notification behavior for all users. 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.

Periodic task report timing is configured system-wide through the following fields.

  • Daily Report Time: The specific time of day to send the daily report.

  • Weekly Report Time: The specific time of day to send the weekly report.

  • Day of Weekly Report: The day of the week when the report will be sent.

Security

This section allows admins to configure password policies for the system. Individual domain settings may override these policies.

  • 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

These fields are used to connect to an SMTP server, which is used to send form emails and task notifications.

  • From: The email user that LiveForms will send emails as.

  • mail.smtp.host: Address of your SMTP server.

  • mail.smtp.port: The port on the SMTP server servicing messages.

  • 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 server.

Payment Portal Configuration

This section defines the connection information for Herring Bank Financial Payments. 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.

Jenzabar Portal Configuration

These settings are used when using the Jenzabar Portal API.

  • Target Tenant (Domain): This option selects which domain will use Jenzabar.

  • Manage/Create Users: Sets whether users can be managed or created within LiveForms for the Jenzabar target domain.

  • Auto-Create Roles: Creates roles in the target domain based on user data from Jenzabar.

The Jenzabar API endpoint URL in LiveForms is {LiveFormsBase}/api/portal where {LiveFormsBase} is the base URL from the general LiveForms config.

Captcha

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

GeoLite2

This section holds the API key for GeoLite2 which allows forms to ask for the user’s location data.

This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com.

Support Settings

This section specifies the default email used when users click on the help tab.

AI configuration

This section allows administrators to configure the system default AI model used for the rule assistant. Current settings are compatible with OpenAI’s API. Individual domains may override these settings to use different AI models.

  • 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 assistants.

    • Assistant: Uses a model which can be trained with files and additional context 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.