Administration

Before you start

Access to the Admin Panel is granted via the following links:

_{Admin Panel URLs:}

Switzerland: https://admin.luware.cloud/
Germany: https://admin.dewe-01.luware.cloud/
UK: https://admin.ukso-01.luware.cloud/

Make sure to configure your web proxies to allow access to these domains or whitelist the complete *.luware.cloud domain.

Special user permissions are required to administrate Nimbus. Please refer to the following chapters:

Read about Roles and Permissions to know how Nimbus syncs to your user directory and grants user access.
As Administrator you might also want to know about Required Permissions for Nimbus services and features.

Role-Specific UI

The Nimbus administration opens the "Overview" by default for all users of the Administrator Group. This view differs slightly depending on your administration role.

Tenant Admin View

Tenant Admin View - Providing a services overview under the assigned tenant

Partner Admin View

Partner Admin View - Providing an overview over all tenants and their respective services

Top Area Widgets

Widget	Description
Provisioned / Enabled (Status)	Sum of all tenants currently provisioned. Learn more on this by reading Nimbus Installation. For Tenant Admins this will change to "Enabled services" instead as they only work within a provisioned tenant.
Total services	Lists all services under the provisioned tenants and their respective provisioning state. A legend description of the different states can be found in chapter "Total Services" below.
Call Volume	Aggregated volume of calls over the shown period for all services.
Active Users	Lists users which have been at least set active once during the shown period. How set the "Active" state? A user's " Active " state can be set to enabled via either of the following means: Via each user's own Dashboard in any Nimbus service-enabled channel. Via the Nimbus personal app > My Services view, where service members can manage the active state for multiple services simultaneously. Good to know: Each service has an individual Service Settings where new users can be set "Active" by default. This may contribute to the statistics even if the (new) service members haven't set themselves active on their own. Even if users just set themselves "Active" - without taking any calls or handling other Nimbus tasks - they will still count towards this metric. Service owners can also manage the "Active" state of their members.

Total Services - Status Widget

The "Total services" widget on top of the "Overview" summarizes your services in an escalated manner. Think of it as a service's lifetime-workflow that starts with "uncompleted" and ends with "pending deletion" of a service.

The states (from top to bottom) are as follows:

UNCOMPLETED - Provisioning has started. A new service has been created in Nimbus database, but also needs to registered in Microsoft Azure. See Nimbus Installation
SERVICES APPLIED - The provisioning is completed and the service is ready to be called. Nimbus will distribute calls among the service and log them for reporting statistics.
SERVICES RUNNING - A service has been called and calls have been recorded in the Nimbus database.
PSTN APPLIED - A service is now reachable via PSTN. Numbers require a phone licence to be requested from Microsoft.
PSTN RUNNING - A service has been called via PSTN and calls have been recorded in the Nimbus database.
SUSPENDED - A service user has opted to "remove Nimbus completely" from the services tab. → After 30 days the corresponding Nimbus service will be "pending deletion"
PENDING DELETION - services that have exceeded "suspended" time or have been removed by a tenant administrator will be pending for deletion. Once de-registered from Azure the services will be removed permanently.

Good to know

A service state is always unique and unambigous, meaning that a service can only have one status at a time.
A service that is pending for deletion can be restored from Luware if it has not been completely de-registered from Azure or completely removed from your local services instance.

Learn more about service provisioning and removal in the Nimbus Installation chapter.

Tenant / Service Entry Listings

Tenants be unfolded in a drill-down fashion in a path of:

Tenant
   > Service
           > Service Users

CODE

The details of each level are explained below.

Tenant

On "Tenant" level a list with the following details is shown:

Column	Description / Purpose
Domain	Base level domain under which the service (and service members) are registered under
Number of services	Amount # of services under the respective tenants, also displayed as graph. Their state and the graphical representation is described under "Total Service" above.
Call Volume / Last 14 days	Aggregated calls under that tenant in a small relative view. Detailed call metrics can be inspected for each service → See table entry below
Monthly Active Users	Users under the current tenant that have been set active at least once this month (either by themselves or their supervisors)
Daily Active Users	Users under the current tenant that been set active at least once on this day (either by themselves or their supervisors)
Since	Date when tenant was first registered with Nimbus.

Service

Unfolding a Tenant entry via the > arrow reveals the "services" under that tenant.

Column	Description / Purpose
Service	service clear name as defined in Microsoft services Client-
State	See status overview as described above.
Users	Assigned total service team members summarized from the according Microsoft Teams channel, regardless of their "Active" state
Call Volume / Last 14 days	Aggregated calls to that service.
Monthly Active Users	Users in the current service that have been set active at least once this month (either by themselves or their supervisors).
Daily Active Users	Users in the current service that been set active at least once on this day (either by themselves or their supervisors).
Provisioned Since	Date when service was first provisioned for Nimbus.

Service Users

Unfolding a service entry via the > arrow reveals the Users of that particular service.

This equals the Team Members

Column	Description / Purpose
Name	User Name as defined in MS services
UPN	User Principal Name (unique) under the current domain
Memberships	Amount of (other) services that the user is part of, including the current.
State	Indicates if the user is available to take calls or inactive (e.g. Offline).
Time in State	Time since last state change (Available / Inactive) occurred. Note that this is a Nimbus exclusive state and not tied to the to MS services IM presence.
Active	Displays if the user is set to active to take calls for the corresponding service. A user can have a different active state when part of multiple services and toggle his states accordingly. Refer to the My services page explaining this concept further.
Role	Signals if the user is either member or owner of the respective service.

Administration Use Cases

Use Cases - Common Scenarios

As Nimbus gets more features and complexity added, our Knowledge Base will expand alongside with "Administration-related Use Cases" that cover various aspects in a "step-by-step" fashion. Follow them to get a good understanding of the structure and concept behind Nimbus.

Name and Goal of the Use Case	_UCID
Use Case - Setting up Interact	_{UC NIMB 005}
Use Case - Routing unassigned numbers to Nimbus	_{UC NIMB 006}
Use Case - Setting up a Federation IT Helpdesk	_{UC NIMB 007}
Use Case - Filtering Attendant contact search via MS Graph	_{UC NIMB 012}
Use Case - Adding external Address Books via Power Automate	_{UC NIMB 013}
Use Case - Setting up a basic IVR Service	_{UC NIMB 015}
Use Case - Setting up a Contact Center	_{UC NIMB 016}
Use Case - Tracking extended user presence via Azure guest accounts	_{UC NIMB 028}
Use Case - Setting up Assistant	_{UC NIMB 030}