By continuing to use this site, you agree to the storing of first- and third-party cookies on your device to enhance site navigation; analyze site, product, and service usage; and assist in our marketing and promotional efforts. Cookie Policy

Skip to Content


Account-level settings are the highest level available (unless you have SuperAdmin access). Many settings provide a baseline that are then expanded on, specified, or even potentially overwritten at the site level or lower.

Only level 10 users can edit account settings.

General SettingsLink to this section

  • Account Name*: The name assigned to your account. This can't be edited.
  • First Name: First name of the account owner or main contact.
  • Last Name: Last name of the account owner or main contact.
  • Email Address: Email address of the account owner or main contact. System messages are sent to this address from
  • Phone: Phone number of the account owner or main contact.
  • Institution: The name of your school or institution.
  • Street: Street address of your institution.
  • City
  • State
  • ZIP
  • Country


The identifying information above is not used to contact you, apart from system emails.

Account OptionsLink to this section

  • Time Zone: Set the default time zone for your account. This creates the date/time stamps in the system and affects scheduled actions. If left blank, Omni CMS uses the time zone of the server it's hosted in; for all SaaS customers, this is "America/Los Angeles." Users and sites can have their own time zone, which takes precedence.
  • Locale: This formats the date/time stamps and chooses a default dictionary. The default is "English (United States)," which sets an English-language dictionary and formats date/time stamps as MM/DD/YYYY. Users and sites can have their own locale, which takes precedence.
  • Help URL: Overrides the URL that users go to when they click Help in the Main menu. If left blank, it points to the Omni CMS support site.
  • JustEdit: Set whether the JustEdit interface is disabled or enabled for everyone, or give administrators or users the ability to set it.
  • Always Use HTTPS: Turning this on opens the HTTPS validator, which checks all URLs managed in Omni CMS to ensure they're HTTPS. Once your site passes the check, you can enable HTTPS everywhere, which always serves your Omni CMS account over HTTPS. Without this, only certain pages containing sensitive info (such as login credentials) are served over HTTPS.
    • This is an Omni CMS setting and won't affect your live website.
    • Before turning on this setting, the team that manages your production server should convert your website to HTTPS. You can also contact our helpdesk for assistance.
    • The validator contains the following sections:
      • Templates Files Review: The HTTPS validator can't check URLs within the coding of templates and other files. These can be switched from HTTP to HTTPS via find and replace. Checking this box confirms you made the switch.
      • Settings Review: Checks the various URLs that are directly managed in the Omni CMS interface. Click "View results in a new window" to see a detailed list of all items that need to be edited to pass.
      • Image Gallery Assets Review: Image gallery assets that reference HTTP are automatically republished once HTTPS is enforced, along with subscribing pages. This option shows how many assets and pages will be republished; click "View results in new window" for a more detailed list.
      • Media RSS Items Review: Media RSS items that reference HTTP are automatically republished once HTTPS is enforced, along with any feeds containing them. This option shows how many items, feeds, and feed groups will be republished; click "View results in new window" for a more detailed list.
    • Once all settings are validated, and you confirm that your templates and files are HTTPS-valid, the Enable button becomes available.

Login SettingsLink to this section

  • Failed Login Attempts*: Sets the default number of consecutive failed attempts at logging in before a user is locked out, between one and nine. This cannot be left blank. Administrators can unlock locked-out users from Setup > Users.


Publish SettingsLink to this section

  • Page Check: Enable or disable page check for all users, or let administrators set for users or let users set for themselves its availability.
  • Page Check Options: If page check is enabled, these appear. Select which checks you want to be included:
    • Spell Check: Identifies spelling errors on the page; users which have permission can add words to the custom dictionary
    • Link Check: Checks the validity of links on the page.
    • W3C Validate: Checks the markup of the page for W3C compliance.
      • Checks against the Nu HTML Checker, including HTML5 standards.
    • Accessibility Check: Checks pages according to the accessibility guideline specified. If this is selected, "Accessibility Guideline," "Accessibility Options," and "Accessibility Exceptions" become available.
  • Accessibility Guideline: Choose which guideline you want to measure pages against for page check and OU Insights:
    • BITV: German accessibility standards
    • Section 508: USA federal requirements for accessibility
    • Stanca Act: Italian accessibility standards
    • WCAG 1.0, 2.0, 2.1 (A-AAA): Web Content Accessibility Guidelines
  • Accessibility Options: Choose which kinds of problems the accessibility check reports.
    • Known problems must always be shown and are verified as causing an error.
    • Likely problems are identified by the system as likely to cause an error, but need user review.
    • Potential problems are items where the system has identified code that may or may not cause an error.
  • Accessibility Exceptions: You can create exceptions for specific accessibility guidelines. Exceptions are listed in a separate tab when page check or final check is run, and if a page must pass accessibility check to be published, exceptions don't count as problems that need to be resolved for the page to pass. Exceptions don't appear as items in Insights reports.
    • The "Active Exceptions" tab shows all exceptions that are currently being applied. To add a new exception, go to the "Available Guidelines" tab and select a guideline. A reason for the exception is required.
    • Exceptions can be deleted by hovering over them and clicking "Remove Exception." Select multiple exceptions to remove more than one at once.
    • These exceptions are specific to the type of guideline chosen. If you change the accessibility guideline you use to run checks, you'll have to re-add exceptions. However, if you return to a previous guideline with exceptions configured, those exceptions are still there.

This video was recorded in OU Campus v10. While the interface may have a slightly different look, the platform functionalities did not drastically change in the OU Campus 11 release.

  • Publish Threshold: Defines the maximum number of pages that are auto-published when an asset is published, or a page is moved or renamed with dependency manager, if a user level 8 or lower is performing the publish. If the number of pages that need to be auto-republished exceeds the threshold, the user is notified that a level 9 or 10 user needs to complete to the action. The maximum value is 99,999. If set to 0, there is no limit.
  • Default Tweet/Wall Post: Enter default text to be inserted into the social media field when publishing a page.

Login PageLink to this section

  • CAS or Shibboleth URL: If you are using CAS or Shibboleth authentication, enter a fully-qualified URL to replace the Omni CMS default login page. For CAS, this should be the CAS service's base URL (without the trailing /login).
  • Announcement URL: If you are using the default Omni CMS login page (LDAP or no external authentication), you can change the content that displays on the page. Enter a full URL of a webpage into the field, and the content is loaded into the iframe on the login page. The page must be HTTPS, but can be any web format. The recommended size is 720 x 600.
  • Logout URL: Set the page that shows up after a user logs out. This is required if you are using CAS or Shibboleth.

WebhooksLink to this section

By setting a webhook, you can have Omni CMS trigger code you write when specified files perform an action. On the action, Omni CMS sends an HTTP post containing JSON data about the action to the specified URL. Whatever happens then depend on the URL content, what data it is programmed to receive, etc.

In the "Webhook URL" field, enter the URL that you want Omni CMS to send information to. Only one URL can be entered. The URL must be HTTPS, have a valid SSL certificate, and be accessible to the Omni CMS server. Clicking the "Test" button sends dummy data to the webhook URL so you can test how it functions, and returns the HTTP response, as well as the data your script returns (should there be any).

Folders must be opted in via folder or site access settings for files within to trigger the webhook. Once opted in, any action across any site goes to the one webhook specified for the account. This is because a single action can trigger actions across multiple sites, such as republishing an asset that causes page publishes. Bigger operations such as site publish send two webhooks, one for the planned action and one for once the action completes. For actions triggered not directly by the user but by another Omni CMS action (e.g. asset publish, publish triggered by renaming or moving files), only the site-level webhook is activated, should it be on. If any files in a batch publish trigger a webhook, then data on all files in the publish/entire publish operation is sent to the webhook.

The actions that trigger a webhook, whether completed successfully or causing an error, are:

  • File publish
  • Folder publish
  • Asset publish*
  • Site publish
  • RSS publish
  • File recycle
  • Folder delete

* For asset publish to trigger a webhook, webhooks must be turned on in site access settings.

Auxiliary SitesLink to this section

Content located in auxiliary sites isn't handled by dependency manager. Any changes to content names or locations within the auxiliary site need to be updated manually on Omni CMS pages.

Adding an auxiliary site does not create a new site with files or a folder structure; it only allows Omni CMS to retrieve files from a preexisting FTP location.

Auxiliary sites are typically used as repositories for media, such as images and video. They can't be accessed via the Omni CMS interface, apart from when inserting links, images, or videos onto a page, where they are accessible from the list of available servers in the upper-right corner of the file chooser.

An auxiliary site can be on the same production server as the main site and identified as its own website, on a separate server, or even a subfolder of your main website in Omni CMS. In any instance, FTP account settings must be available to set up an auxiliary site. The connection is read-only, and files cannot be uploaded to the auxiliary site via the file chooser.

As many auxiliary sites can be added as necessary. If they are added via account settings, they are accessible from all sites in the account. Auxiliary sites can also be added at the site level.

To create a new auxiliary site from Setup > Account, click +Add. The options are the same as those for the site FTP settings.

An existing auxiliary site can be edited by clicking on its name. To delete an existing site, click the "X" icon next to its name. This doesn't delete files or folders from the site; it only disconnects Omni CMS from the site.

Add-OnsLink to this section

To add custom links to the Add-Ons menu, click +Add, and enter the following information:

Add-ons can be reordered by dragging and dropping them in the list. Click X to delete an add-on.

Optional FeaturesLink to this section

Enable additional features here. Once enabled, some features require additional configuration.

  • Asset Manager: Allow access to viewing and creating assets for all users.
  • Binary Management: Enable binary management for the account. Once enabled, this can be enabled or disabled for each site in site settings.
  • Dependency Manager: Enable dependency manager for the account. Turning off dependency manager does not remove dependency tags. To turn dependency tags back into links, revert the sites.
  • LDP: If the LDP module has been purchased, turn it on here.
  • Multi-Browser Preview: Enable multi-browser preview for pages. Click "Configure" to choose which operating system, browser, and version combinations are available to users. From the array, select the combinations you want to be available as options in multi-browser preview.
    • Check "Automatically select new browser versions" to automatically include new browser versions in the selected combinations.
    • Check "Select all" to automatically give users access to all preview options.
  • Reveal Site Password: Show the Production Server FTP password in site settings to any user (level 10 administrators only) viewing the settings.
  • Name: Enter a friendly name for the add-on, such as the title of the page.
  • URL: Enter the URL to the add-on page.
  • Admin Access Only: Select this for the add-on to only be visible to level 9 and 10 users.
  • Open in New Window: Select this for the add-on to open in a new browser tab.