BEFORE YOU START
Access to the Admin Panel is granted via the following links:
Nimbus Admin URLs
✅ 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:
The Nimbus administration opens the "Overview" by default for all users of the Administrator Group.
💡 This view differs slightly depending on your administration role. Multi-Tenant Admins get a Tenant selection while Single-Tenant Admins will directly be presented with the list of services within their Tenant.
Top Area Widgets
Sum of all services currently provisioned.
🔍 Learn more about this by visiting Nimbus Installation.
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.
Aggregated volume of call sessions all services.
💡 Mouse over the diagram to get additional infos.
Lists users which have been set "Active" at least once during the shown period.
How to set the "Active" state?
🔍 A user's "Active" state can be set to enabled via either of the following means:
💡 Good to know:
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
In a Multi-Tenants setup, entries are unfolded in a drill-down fashion:
Tenant > Service > Service Users
🔍 The details of each level are explained below.
On "Tenant" level a list with the following details is shown:
Description / Purpose
|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.
|Sessions 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)
|Date when tenant was first registered with Nimbus.
Unfolding a Tenant entry via the > arrow reveals the "services" under that tenant.
Description / Purpose
|service clear name as defined in Microsoft services Client-
|See status overview as described above.
|Assigned total service team members
💡 Summarized from the according Microsoft Teams channel, regardless of their "Active" state
|Overall total sessions on that service.
|Last 14 days
Sessions over the last 14 days.
💡 Mouse over details provided for each day.
|Date when service was first provisioned for Nimbus.
Unfolding a service entry via the > arrow reveals the Users of that particular service.
💡 This equals the Team Members
Description / Purpose
|User Name as defined in MS services
|User Principal Name (unique) under the current domain
|Amount of (other) services that the user is part of, including the current viewed service.
Indicates if the user is available to take calls or inactive (e.g. Offline).
🔍 Also see User States.
|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 Microsoft Teams IM presence.
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.
Signals the user role (member or owner) of the respective service.
🔍 Roles can be assigned via User Administration or get automatically granted from being Team Owner in a MS Teams-based team.
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
|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