BEFORE YOU START
Access to the Portal (Frontend UI) of Nimbus is granted via the following links. Note that the URL is depending on where your Nimbus Nimbus Installation was done for the first time:
Nimbus Portal URLs
Switzerland 01 | https://portal.ch-01.luware.cloud/ |
---|---|
Switzerland 02 | https://portal.ch-02.luware.cloud/ |
Germany 01 | https://portal.dewe-01.luware.cloud/ |
Germany 02 | https://portal.dewe-02.luware.cloud/ |
United Kingdom 01 | https://portal.ukso-01.luware.cloud/ |
Australia 01 | https://portal.aue-01.luware.cloud/ |
West Europe 01 | https://portal.euwe-01.luware.cloud/ |
East United States 01 | https://portal.use-01.luware.cloud/ |
✅ Make sure to configure your web proxies to allow access to these domains or whitelist the complete *.luware.cloud domain.
Note that User permissions are required to access the Nimbus Portal:
- Read about Role Access Concept to understand how to access Nimbus services.
- Your service / team owner or tenant administrator will need to grant you any of the viable Portal Roles and assign you as Members / Agents to a Nimbus service before you see any data in the portal.
- If your Administrator has not given consent on your behalf, Nimbus will inform you about Required User Permissions. These are needed to access your presence status and perform searches in your local directory.
💡 After your first login, we strongly recommend that you read this guide all the way through. At the end of this page, you will find additional resources for each individual UI (view) of Nimbus.
General Nimbus UI concepts
While designed to seamlessly integrate with Microsoft Teams in terms of its design, Nimbus uses the following modern concepts to enhance the UI experience with additional features.
💡 Note that these apply universally to all of Nimbus features and extensions, so you need to memorize them only once.
View Selection
My Overview
|
My Overview offers a high-level metrics view on your services, sessions, and user data. 💡Things of Note:
💡Good to know:
|
Organization Units
|
Nimbus uses a hierarchical access-concept called Organization Units (short: OU). This concept is very important separate the visibility of data, users, services and all configurable elements such as workflows, codes, audio files etc.). 💡Things of Note:
🔍 If you are managing a team we highly recommend reading about Organization Units to learn more about this concept. |
Nimbus Teams App (and Teams Tab)
|
The Teams App is an optional way for users to access Nimbus via Microsoft Teams as a Nimbus Personal App. 💡Things of Note:
💡Good to know:
|
Open in Browser
|
As a cloud product, Nimbus works both within the Microsoft Teams app as well as an external browser. You can use the "Open in Browser" option at any time to seamlessly continue working outside the Teams App. ☝Things to keep in mindCredentials for the Nimbus Login (your Microsoft O365 account) may be required when clicking the website link. Limitations to the Microsoft Teams mobile client or browser may impact responsiveness of the Nimbus UI. If any issues occur, try clearing your browser cache or switching browsers to see whether the problem persists. Status changes (e.g. your "Active" team status, call queue handling, reporting data) persist between the Nimbus browser window and the Teams App. You can have multiple instances of Nimbus open; however, refreshing data may briefly cause mismatched data to display. Teams requires exclusive access to your headset / microphone. Keep it in mind when opening Nimbus multiple times. Features like Conversation Context require Nimbus to run in browser, as the Nimbus App cannot open tabs “on demand” within the MS Teams client. A workaround for this is Assistant which can open the browser context for you. |
Mouse-Over tooltips
|
Most controls and widgets allow you to interact via mouse-over to display further details and tooltips. 💡Things of Note:
|
Clickable controls
Widgets with active controls will show a hand-symbol cursor. This can toggles, pulldowns, 💡Things of Note:
|
Call Pickup controls
|
Pickup controls may be visible for certain services, e.g. within a Queue widget or task list. ✅Precondition:“Pickup” is Service Settings and workflow queue-handling configured. Queue Activities in a service workflow need to be set to any of the "Pickup" Distribution Types for this to show. 💡Things of Note:
|
Table Sorting
|
You can also click on table headers such task lists, available users, or reporting metrics to sort by that criteria. 💡Things of Note:
|
Chart Filtering & View Change
✅ Precondition: Data needs to be available for the filters to have a visible effect.
|
Chart Filtering can be applied to any diagram with a legend nearby. Some charts also support further control via mouse. 💡Things of Note:
|