LEXI follows a multi-tenant architecture, which means our Enterprise customers can in turn have their own (enterprise) customers. Our cloud instances are completely white-labelled for our enterprise customers.
When an Enterprise customer (who wants to further sell to their enterprise clients) requests LEXI for a white-labelled cloud instance, we create an instance for them, map it to their dashboard URL and create a login for the Enterprise customer. This user type is called Enterprise Super Admin (ESA).
ESA (Enterprise Super Admin):
The primary role of ESA account is Client Management and Request for White Labeled Apps.
When our Enterprise customer gets a request from their own customer for a cloud instance, they can create what we call an Enterprise Client (using the Client Management feature in the ESA account). A separate white-labelled Dashboard URL and white-labelled User portal URL is requested from the Enterprise Client and is entered in the ESA account. A unique login is created for the Enterprise Client called the Client Super Admin account (CSA). ESA can also request for White labeled apps and Installer app for the Enterprise Clients.

Note: All corporate users (internal) of the Enterprise Client use their own Dashboard URL. The end users of the Enterprise Client (their external customers) use the User Portal URL.
CSA (Client Super Admin):
The primary use case for this account is Corporate User Role creation and Corporate User creation for the Enterprise client. We already have 5 predefined roles (Client Super Admin, Admin, Manager, Customer Service Agent and Installer). CSA can also create their own custom roles.
Once the role creation is completed, CSA can create their own corporate users to manage the Enterprise Client Instance.
Admin:
The primary use case for this account is to create corporate users for the Enterprise client instance. They can also see the End User (customer) details.
Manager:
The primary use case for this account is to Manage the instance and provide support to the End Users (customers). The manager can see all the End User details, the user configuration and can also download logs and provide support. The Manager also maps Customer Service agents to individual End Users.

We will soon introduce load-balanced and round-robin end user mapping with customer service agents.
Customer Service (CS):
The primary use case for this account is to provide support to End Users (customers) assigned to their account. The CS can see all the End User details, the user configuration and can also download logs and provide support.
Installer:
The primary use case for this account is to set up the Gateway and devices for the eventual end user (customer).
For example, a Home builder may want to install the Gateway and Devices well ahead of the Homeowner. Once the installation is complete, a code is generated which is shared with the Eventual End User. Using this code, the End User can claim ownership of the setup and use the devices.
The LEXI Cloud Structure is depicted in the below diagram for easy understanding: