eMite and Genesys Cloud Divisions


Genesys Cloud Divisions

In Genesys Cloud, administrators can separate and group configuration objects into separate divisions. A division is a way to group and segregate objects but keep them inside the same organization. 

For example, you can create divisions by business units, countries, and office locations, then assign configuration objects to each division.
After you create and configure divisions, you can use roles to grant user access to divisions, and thus the objects within each division.

Every organization includes a single, default division called the Home division. 

More information about Genesys Cloud divisions: https://help.mypurecloud.com/articles/divisions-overview/


eMite Equivalent

The equivalent of Genesys Cloud Divisions in eMite are Index Groups. The following table shows how Genesys Cloud configuration objects map to eMite configuration objects:

Genesys Cloud

eMite

Genesys Cloud

eMite

Organization

Instance

Division

Index Group

Object (Queues, Agents, Flows, etc.)

Index (QueueHistory, AgentHistory, CallSegments, etc.)


Standard eMite Configuration

What is the standard eMite configuration for customers using multiple Genesys Cloud Divisions?

The standard configuration (included as part of eMite’s Genesys Cloud QuickStart) is to onboard data from multiple Divisions into a single index group. In this scenario;

  • A single set of OAuths is required which grant access to all required divisions

  • A single set of user groups and broadcast accounts are provided for all users, irrespective of their division.

Please see https://prophecyinternational.atlassian.net/wiki/spaces/ID/pages/264536140 for more information on how to configure Genesys Cloud for eMite


Data Segregation within Standard eMite Configuration

How can data be segregated within the standard eMite configuration, to restrict dashboard users within one Division from accessing data in one (or more) other Divisions?

Every eMite index (and real time) now includes a division dimension which can be used to filter the data on a particular division.
Once the reports and dashboards are created and filtered on one (or more) divisions, they can be shared with other users in Read Only mode, restricting them from accessing data outside of their own division.


Non-Standard Division Requirements

What “non-standard” options are available to be scoped and quoted under a separate Statement of Work?

eMite is a powerful and flexible BI platform that can be configured in many different ways to achieve a business outcome. eMite has many options when it comes to segregating data, but these all involve additional services. Therefore, these options are not included in eMite’s Genesys Cloud QuickStart.

The following are examples of non-standard requirements around divisions:

  • New customers who want to onboard data from multiple Divisions into multiple Index Groups, so there is an exact 1:1 mapping between an Index Group and a Division.

  • New customers who require a custom 1:many or many:1 configuration between Genesys Cloud Divisions and eMite Index Groups.

  • New customers who require require a single index group which encapsulates everything along with multiple index groups which segregate out the data.

  • Existing customers who would like to add new Index Groups to segregate out new divisions.

Please always ensure your Divisions are configured in Genesys Cloud, and that data (Contact Center activity) are already generated within them before eMite is deployed.