Updating organization settings

System Admins can update any of the following settings:

• Instance name, subdomain, locale, time zone, and notifications
• Several branding settings
• Several security settings

Permissions

Only System Admins can update organization settings.

Steps

1. Open Launchpad.
2. If your company uses more than one instance in Diligent One, make sure the appropriate instance is active.
3. Select Platform Settings > Organization.

   If you do not see Organization as an option, the account you used to sign in does not have Admin privileges.

4. Click Update Organization.
5. Click the tab and modify your details for any of the following fields and click Save changes.

Tab	Field	Description
Organization	Customer name	Your customer name. Typically, this is your company name. This value is assigned by Diligent and you cannot edit it. If you need to change this value, contact Support.
	Name	The name of your Diligent One instance. This is not necessarily your company name. If your company has multiple Diligent One instances, each instance can have a name that describes the purpose of that instance. The maximum character length is 255.
	Subdomain	Typically, the name of your organization. The subdomain name displays in the URL as http://[subdomain].projects.highbond.com . If your organization has enabled Single Sign-On (SSO), the subdomain combines with a region code to form the custom domain users use to sign into Diligent One. Caution Changing the subdomain breaks any previously referenced URLs, as well as URLs in workflow emails.
	Locale	Sets the default language for new Users and System Admins in the Diligent One instance. When new users are created and invited to a Diligent One instance, the language locale will default to the organization locale. Invitation emails are received in the language of the user locale. Existing users' locales will not change when the organization's locale changes. To use the Reports app in a specific, supported language, you must set the language in your browser settings. Reports does not respect your Locale for language settings.
	Timezone	The time zone in which your organization operates. The default setting is based on the time zone of the first user added to the Diligent One instance. Results displays datetime data to non-licensed users using the organization's time zone. For more information, see Working with time zones.
	Fiscal Year End Date	The year end date that your organization uses for assurance plans and scheduling in Projects. The default is December 31. The year end date can be the end of any month. For more information, see Defining assurance plans and Scheduling projects.
	Enable desktop notifications for new versions of ACL for Windows optional	Sends notifications about newly available versions of ACL for Windows to users. Users that belong to multiple Diligent One instances, and that have this option selected for one of their Diligent One instances, receive notifications. Notifications display in the Windows system tray. Note This option only controls notifications for users that are using Analytics 14.1 and below.
Security settings	Password Expiration optional	Defines a password life in days. For more information, see Diligent Security.
	Session Timeout	The amount of time for an inactive session to timeout. This setting is overridden by other factors. The minimum session timeout is 15 minutes. If a user has access to multiple instances of Diligent One, the shortest timeout from any of their instances is used for all of their instances. If this instance of Diligent One is set to use Single Sign On (SSO), and timeout settings for your SSO identity provider are longer, your identity provider's settings are respected. For security purposes, ensure that your identity provider's expiry is less than your instance's session expiry. For more information, see Configuring Single Sign-On (SSO). For more information, see Diligent Security.
	Platform-wide two-factor authentication optional	Enforces multi-factor authentication for all users in your organization. For more information, see Configuring two-factor authentication (2FA or MFA).
	Enhanced password settings optional	Enforces stronger password requirements for all users in your organization. Once this is enabled, users will be asked to change their passwords at their next login with the following requirements: Password length must be a minimum of 15 characters containing mixed case, numbers, and special characters. Once users have changed their password, they can't change it again for a minimum of one day. Note Suppose you choose not to enable password enhancements. In that case, the default password settings are that you can't reuse the previous 25 passwords and password length must be a minimum of 8 characters containing mixed cases and numbers.
	Notifications	Notifies System Admins when users are added or removed from a Diligent One instance.
	Allow Access Only From The Following IP Addresses optional	Restricts user IP address access to Diligent One websites. Configure a list or range of allowed IP addresses from which users can access Diligent One. Adding even one IP address to the text box enables this option. Once this option is enabled, all IP addresses that you want to grant access to, must be specified in the text box. Otherwise, unless specifically added, all other IP addresses are restricted. If there are no IP addresses in the text box, this option is not enabled which means all IP addresses are allowed access to Diligent One. Note Individuals can only access *highbond.com , or any public link created in Diligent One, if their IP is allowlisted. Individuals using mobile devices or other public networks may need to use a VPN in order to access Diligent One. IP allowlisting only impacts access to Diligent One data. IP allowlisting does not impact activating Analytics. Currently, only IPv4 is supported. As a result, do not use IPv6 with the enabled IP allowlist. For more information, see Diligent Security.
	Disable IP pinned tokens optional	This allows sessions with dynamic IPs. Select the Disable IP pinned tokens checkbox to prevent users from being blocked if your networks swap IPs during a session. Otherwise, the system expects the same IP address to be used for all requests.
Branding	Tagline optional	The slogan for your organization. The tagline displays under your logo on your reports.
	Report Cover Page Image optional	The front page to be used in your reports. The report cover page image size should be no bigger than 900 x 300 pixels. Images wider than 900 pixels will be resized to scale. .png, .jpg and .gif files are supported. The maximum file size is 5MB. Note Use images with an RGB color model only. Other color models, such as CMYK, are not supported.
	Logo optional	Your organization's logo. The logo is displayed in your reports, and within the footer of system email notifications. The logo size should be no bigger than 300 x 300 pixels. Logos wider than 300 pixels will be resized to scale. .png, .jpg and .gif files are supported. The maximum file size is 5MB. Note Use images with an RGB color model only. Other color models, such as CMYK, are not supported.
	Primary color optional	The primary color to be used in your reports. The primary color only applies to the report title, footer tagline, and heading titles in PDF reports.
	Secondary color optional	The secondary color to be used in your reports. The secondary color only applies to the private and confidential header and footer, and in the heading line break in PDF reports.