Close

Organization Settings

Omniata has built-in tools for managing common settings across applications and for the organization itself. It can be accessed by selecting the main navigation on the left top corner, and selecting Global Settings.

The following elements can be configured:

Environments

Environments are used for separating data from different phases of your application development. Three Environments exist by default: Development, Staging, and Production. Although you can use the environments as you see fit, the aim for each is covered below.

Development
Your local development machine or build.
Staging
Your staging server. A staging server is usually used to QA a new version of your application, before pushing it to production.
Production
Your production servers. Production servers are the ones that provide the services to your consumers.

You can modify the display names of the environments. For example, Staging Environment can be renamed as QA. Dashboards show data from one Environment at a time. Reporting Tables can be scoped to contain data from only certain Environments.

Data for each Environment is stored physically isolated from the other Environments. If you track Events from one UID in environment A (e.g. Development), and then track Events with the same UID in environment B (Production), those will be considered different users. The acquisition date of the user the day when the UID sent its first Event to the respective Environment.

Following actions can be taken with Environments:

  • Create new Environment.
  • Move the Environment up or down in the hierarchy. This affects the order of the Environments when selecting one in the Dashboards.
  • Edit the display name of the Environment.
  • Delete the Environment.

Lookup Tables

Lookup Tables allow you to make a “lookup” of a value received in an Event, and store the returned value in a Data Field. This can be very useful in the case where you only send the id of an object of which you have more information offline, or in the case that you want to normalize data.

There are some built-in Lookup Tables by default, for example for converting two-character country codes (e.g. “DE”) to country names (e.g. “Germany”). These cannot be modified. You can create new Lookup Tables whenever needed.

On this section you can:

  • Search Lookup Tables by their name.
  • Create new Lookup Table.
  • Show the content of Lookup Table.
  • Upload data into Lookup Table using CSV file. This is applicable only for custom Lookup Tables.
  • Export the content of Lookup Table as CSV file. This is applicable only for custom Lookup Tables.
  • Edit the Lookup Table. This is applicable only for custom Lookup Tables.
  • Delete the Lookup Table. This is applicable only for custom Lookup Tables.

To learn how to manage, create or edit Lookup Tables check the Lookup Tables guide.

Platforms

The Platforms global configuration has now been deprecated. This legacy option refers to the platforms on which your application runs on. For example, iOS, Android, or Web. This will show by default “All Platforms (All Devices)”.

The current Platform information is included in an Event Parameter. This configures all users and metrics as cross-platform. This enables the panel to track your users across different platforms, as long as they have the same UID.

In case you need to keep users isolated per platform, configure and add the needed platforms on this panel. For each created and active platform you will also need the corresponding API Keys.

Service Status

Access to reports on Omniata’s Event API and Channel API status. The charts show the availability of Omniata Channel API as measured by Pingdom. The charts will show for each API the following:

Metric Units
Uptime Percentage of day.
Outages Number of incidences.
Downtime In minutes.
Avg Response Time In milliseconds.
Slowest Average In milliseconds.
Fastest Average In milliseconds.

User Management

This panel allows to control the organization access on a per-role basis. A role can be scoped to a specific environment or application, users are then associated with a role and the permissions are applied. The organization-level user management controls access to data and application objects. Each application can locally control access to dashboards if needed.

On this panel you can:

  • Invite users to the Omniata panel.
  • Associate a user with an existing role.
  • Create new roles.
  • Delete roles.
  • Configure role permissions.

See the section on User Management for a more in-depth look at user management tasks.

Organization Settings

Allows you to change the organization name shown in the panel. In addition, you have an option to choose an icon for the organization.

This article was last updated on May 2, 2017 12:10. If you didn't find your answer here, search for another article or contact our support to get in touch.