Different settings and controls can be changed for an Organization (tenant) within the Exoprise platform. Changing settings requires the administrator role within the system.
To change Organization settings navigate to Admin > Settings from the left-hand menu. If you don’t see the Admin men then you don’t have administrative privileges.
General Settings
In this section you can change the name of the organization and click ‘Save’ to rename it.
Allow API access
This setting controls whether users within the Organization can utilize API access to add/remove sensors or alter configurations. Users don’t have to use API access if you enable this feature.
Allow dashboard embedding
Exoprise dashboards and tabs can be embedded in other web-based products (iframes/frames) such as SharePoint, Microsoft System Center and more. Disable this feature for all users via this Organization setting.
Logo Settings
The Exoprise portal can be branded with a corporate logo. Adding a logo will display the logo in the upper right instead of the Exoprise logo. An uploaded logo can be utilized for the main portal experience as well as some user-facing pages like Service Watch setup and management.
To Add the Logo
To add a corporate logo:
- Navigate to Admin > Settings, navigate to the Logo section
- Click ‘Upload logo’ to add or replace the image
- To just use the logo for user-facing pages, uncheck ‘Use logo for portal’
- Click save to upload and save the settings
Image Requirements
Ideally, the logo should be on a transparent background. The image will be scaled to 160 pixels wide and 35 pixels tall so choose an image with the same dimensions or similar proportions.
Here are some samples:
160px by 34 sample image, all black transparent background
178px by 40 sample image, all white, transparent background
160px by 34 sample image, mostly white, transparent background
Private Site Alarm Logging
Control alarm log distribution to private sites in this section. If you enable alarm logging to multiple sites, by default, the alarms are sent to all of them. We see many customers turn this on, and we’re never clear why they are doing this. You don’t need to enable this feature if all you want to do is ensure that alarms are generated from sensors running on sites – that always happens.
Anyway, the preferred way of organizing the sites for alarm logging is to choose a few sites that are integrated with on-premises systems like Splunk or SCOM and then enable alarm logging for those sites. Then, in this section, enable alarm logging to the ‘Highest priority site’ and choose the site order.
This way, the alarms will be distributed to the preferred site and then, if the site goes offline, the alarms will be distributed to the site that is next in line.
That is how prioritized alarm logging works.