Global settings

Global variables allow you to influence the overall behavior of the system to accommodate your specific requirements. In the Global Settings table, you can enter the variables and their values. No input validation occurs when you add values or make changes. In some cases, if the value that is entered for a global variable is not a valid entry, a default value is used instead.

Adding global settings
From the menu click Settings and then click Global Settings. To add a new global setting, click Add new variable (+).

Links to sections

System Settings

Session timeout, Feedback email address, and Quickstart 

Other System Settings

Bulk edits, Vendor access and Oomnitza users show or hide switch

Email Settings

Header, Footer, Sender, and Sender name

Password Security Settings

Min length, requires Lowercase letter, Uppercase letter, Digit, and Special character

SAML Settings

Email, First name, and Last name

Attachment Settings

Max size, and File types

Security Settings

Allowed domains and Alerts switch for usernames, emails, and password changes and, allowed plugin domains

Configuration Migration Settings

Name of target instance, Credentials for target instance, and Configuration switch for the target instance

Telemetry Data Settings

Control collection

System Settings

Key	Description
session_timeout	The timeout duration of an Oomnitza user session in minutes. That is the amount of time a session will be kept active before it times out and will require the user to login again. The default value is 20 minutes and will apply if this key is not set or if it is set to an invalid value. The maximum allowed value is 1440 minutes (which is a day).
feedback_menu.Link	You can set the email address for feedback in Oomnitza. If the setting is not added as a global setting or if an email address is not specified, the link will not be shown in the GUI. The email address that you enter for this setting is also the contact email address for users who forget their passwords. The feed back link displays when you click the user icon , which is next to the Log out button on the menu. The default value is mailto:[e-mail].
system.disable_quickstart	To enable the Quickstart wizard, add the key as a global variable and set the key value to 0. Super Administrators can use the Quickstart wizard to apply best practice packages and to streamline the initial implementation of Oomnitza. If the key is not added as a global variable or if the key value is set to 1, the Quickstart wizard is disabled.
system.display_oomnitza_users	Manage the visibility of Oomnitza users in the customer instance. Default value: No Possible values: 1/0, true/false, True/False, Yes/No, yes/no, y/n, Y/N, YES/NO If the parameter is not set or does not match requirements, the default value will be set.

Other System Settings

Key	Description
system.bulk_edit_records_limit	Set a limit for the number of bulk edits that can be made at the same time. Default value: 1000 Minimum value: 1 Maximum value: 1000 You can complete bulk edits for assets, accessories, people, and locations. See bulk edits for assets
system.disable_oomnitza_vendor_access	Disables / Enables access to your instance by Oomnitza Support and Implementation teams.  Default value: No Possible values: 1/0, true/false, True/False, Yes/No, yes/no, y/n, Y/N, YES/NO
system.display_oomnitza_users	Manage the visibility of Oomnitza users in the customer instance. Default value: No Possible values: 1/0, true/false, True/False, Yes/No, yes/no, y/n, Y/N, YES/NO If the parameter is not set or does not match requirements, the default value will be set.

Email Settings

Key	Description
email.header	When this key exists, it allows you to overwrite the default email header for all outgoing emails (system notifications, password reset, scheduled reports, approval requests and workflow notifications). Setting the email.header value allows you to reflect your corporate branding in the header of such emails. The value for this should include HTML code. It is recommended to enclose the header in a div tag with id message_header, like: <div id="message_header">your logo and header go here</div>
email.footer	Similar to the email.header, this key allows you to overwrite the footer for all outgoing emails. Setting the email.footer value allows you to reflect your corporate branding in the footer of such emails or to include reminders about upcoming events. The value for this should include HTML code. It is recommended to enclose the header in a div tag with id message_footer, like: <div id="message_footer">your logo and header go here</div> When this key is set, the system will append the unsubscribe link below the footer.
email.sender	You can specify the email address of the sender for the emails that are sent by Oomnitza. You add a key called "email.sender" and a value for the sender address such as  [e-mail]. All of the emails sent from Oomnitza will use the email address as an alias. If the key isn't specified, the default sender address no-reply@<domain>.oomnitza.com is used. Please keep in mind that this does allow you to overwrite the email sender. However, the sending email server, the SMPT Server at our end, will remain the same and might be recognized as spam if not properly specified within your email system as a valid sender. Important When you change the email sender setting, you must ensure that the email server of the recipient is configured to receive emails from both the sender that you specify and the Oomnitza SMTP server. Otherwise, the emails might be flagged as spam or rejected. To resolve this issue, change the email sender address to <your-domain-name>@no-reply.oomnitza.com or to no-reply@<your-domain-name>.oomnitza.com.
email.sender_name	The name of the person/organization/mailbox on whose behalf the email was sent.

Password Security Settings

The password security settings allow you to define passwords requirements for users that authenticate directly at the Oomnitza Login page with a username and password.

Key	Description
password.min_length	Minimum password length Default value: 8 Min length: 8 Max length: 256 If the parameter is not set or does not match the length requirements, the default value will be set.
password.require_lower_case	Defines whether at least one lower case letter is required within the password.  Default value: Yes Possible values: 1/0, true/false, True/False, TRUE/FALSE, Yes/No, yes/no, y/n, Y/N, YES/NO
password.require_upper_case	Defines whether at least one upper case letter is required within the password Default value: No Possible values: 1/0, true/false, True/False, TRUE/FALSE, Yes/No, yes/no, y/n, Y/N, YES/NO
password.require_digit	Defines whether at least one digit is required within the password Default value: Yes Possible values: 1/0, true/false, True/False, TRUE/FALSE, Yes/No, yes/no, y/n, Y/N, YES/NO
password.require_special_char	Defines whether at least one special character is required within the password. Default value: Yes Possible values: 1/0, true/false, True/False, TRUE/FALSE, Yes/No, yes/no, y/n, Y/N, YES/NO Within Oomnitza System, we allow following characters as special characters: \|!@#$%^&*()_+-={}"'`~/?.>,<[]]+

SAML Settings

The SAML setting allow you to specify other field mappings for SAML authentication flows. Within the SAML authentication flow (which applies to all SAML authentications, like Okta, OneLogin and so on) we always expect the username within the attribute NameID of the SAML payload. By default, we would expect the NameID to be username as well as email address for the user, however in some cases you may not have the email be identical to the username and for that you can override the default behavior as outline below.

Key	Description
SAML.email	Setting the parameter in Global Settings table allows you to specify a different parameter for the email address of the user. If set, it will be used to populate the user's email, instead of just copying the NameID. If NOT set - meaning the default behavior - the email will be copied from the NameID and will just equal to the username. In case your SAML payload does not even have an email address, the JIT provisioning for users may not work, but SSO can still be achieved by simply defining SAML.email = email in the Global Settings table.
SAML.firstname	The alternative mapping for the first name
SAML.lastname	The alternative mapping for the last name

Attachment Settings

Attachment settings allow you to define parameters for the files that can be attached to Assets, Users, and other objects in Oomnitza via the media tab.

Key	Description
attachments.max_file_upload_size	The max allowed size of file to upload Default value: 5242880 (in bytes) Max size: 20971520
attachments.extensions	Specified files extension types allowed for upload as attachments The user should enter a comma-delimited list with no spaces. e.g. doc,docx,xls,xlsx,png,jpeg Default list of extensions: .jpeg, .jpg, .png, .pdf, .xlsx, .xls, .doc, .docx, .pptx, .ppt, .txt, .mp3, .MOV, .M4A If the provided value is invalid, the system should filter it out.

Security Settings

Key	Description
security.allowed_cors_domains	Specifies domains allowed for CORS. When the global is not set and the request from the other domain has come, the system should NOT do anything. BUT if it is set, the system should check the domain match and accept or reject it. The user should enter a comma-delimited list with no spaces. Example  zendesk.attacker.site,mail.google.com If the provided value is invalid (contains special characters), the system should filter it out.
security.enable_personal_data_change_emails	By default, users are not alerted when their username, email address, or password changes. To enable alerts, add the variable, and enter one of these values:  1, true, True, TRUE, Yes, yes, y, or YES To disable alerts, enter one of these values: 0, false, False, FALSE, No, no, n, N, or NO
security.allowed_plugin_domains	List of the allowed plugin domains such as the plugin domains for Zendesk, Jira, Freshservice, and Salesforce. The list of the allowed plugin domains can be extended, but not overwritten. Enter a comma-separated list of the plugin domains with no spaces, such as: jira-plugin-server.oomnitza.com,cloudfront.net Invalid values, such as values that contain special characters, are ignored.

Configuration Migration Settings

Key	Description
migrations.subdomain	Defines the name of the target instance to where you want the configuration to migrate to. Please use the instance name without the .oomnitza.com extension.
migrations.credential	Defines the name of the credential to use to communicate to the target instance. When using this global setting, use a name without spaces.
migrations.disableConfig	Prevents the configuration migration from making changes in production for Objects, Roles, and Screens. Default value: No Case sensitive Possible values: 1/0, true/false, True/False, Yes/No, yes/no, y/n, Y/N, YES/NO

Telemetry Data Settings

Key

Description

system.disable_telemetry_data

By default, telemetry data is collected for monitoring purposes by Oomnitza. By adding a global variable, you can control the collection of this type of data. Valid values To switch the collection of telemetry data off, you can enter any one of the following values: 1, or True, or Y ,or Yes. To switch the collection of telemetry data on, you can enter any one of the following values: 0, or False, or N ,or No. Note: The values aren't case sensitive. For example, you can enter ‘yes’ or ‘yes’, or ‘No’ or ‘No’.