Frontend Portal Overview

An introduction to Nimbus Portal and general UI concepts

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.luware.cloud/
Germany 01 https://portal.dewe-01.luware.cloud/
Germany 02 https://portal.dewe-02.luware.cloud/
UK 01 https://portal.ukso-01.luware.cloud/
Nimbus Portal URLs

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

✅ 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. Please refer to the following chapters:

  • Read about Role Access Concept to know how you get access to Nimbus services. Your service / team owner or tenant administrator needs to grant you access and assign you to services 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 highly recommend to read this chapter to the bottom. At the end of this page you will find further pointers to each individual UI (view) of Nimbus. 

 

General Nimbus UI concepts

While generally 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

 

Main menu functionality is distinguished into different "views", which are accessible within a sidebar located at the left-hand side. 

  • Small tool-tips will be displayed on mouse-over to guide you prior to changing the view.
  • Every view usually consists of multiple widgets, small information blocks that fulfill a specific purpose such as displaying a list of tasks, users or statistics
  • Changing views will also force a refresh of the widgets inside.

Organization Units

 

Nimbus uses a hierarchical access-concept called Organization Units (short: OU) to distinguish access and visibility to services (and other configurable elements such as workflows, codes, audio files etc.).

  • In some UI views you will notice a selector on top. This allows to toggle the same view but seen from a different service team (OU) perspective.
  • When in Configuration the OU concept also applies to distinguish by an item's OU affiliation (e.g. a workflow being assigned to and thus only visible to the "Documentation Team")
  • Data entities and configuration elements may be assigned to a "System" level OU by administrators, meaning that they will be available to all underlying "child-OU" services.

🔍 Read the chapter on Organization Units to learn more about this concept.

Open in Browser

 

Being a cloud-product Nimbus works both within the Microsoft Teams app as well as an external browser. use use the "Open in Browser" functionality at any time to seamlessly continue working outside of the Teams App.

🔍 Please note when using this function: 

  • Clicking the link will open the Nimbus portal in your browser, requiring you to re-authenticate yourself with your Microsoft account. Depending on your account used you may have different permissions and get Nimbus functions shown in your browser compared to your MS Teams client.
  • Limitations to the Microsoft Teams mobile client or browser may impact responsiveness of the Nimbus UI. When issues occur we recommend clearing your browser cache or switching browsers to test if the problems reoccur.
  • Status changes (e.g. your "active" team status, call queue handling, reporting data) persist between Nimbus browser window and Teams App. You can have Nimbus open multiple times, however refreshing data may briefly cause a mismatch of data shown.
  • When opening Nimbus several times, keep in mind that MS Teams requires exclusive access to your headset / microphone.
  • Some features like Conversation Context require Nimbus to run in browser as the Nimbus App has no possibility to open tabs within the MS Teams client "on demand".

For the most consistent experience we therefore recommend using Nimbus EITHER in browser OR as MS Teams App at the same time.

Mouse-Over

 

Most controls and widgets allow you to interact via mouse-over to display further details and tooltips.

Some examples involve:

  • Mousing over charts and diagrams to get numeric data points.
  • Getting the complete text contents of a control that is otherwise cut-off by design or resolution limitations (e.g. long names, announcement text, file names, etc.).
  • Getting visual feedback on an interactive control that changes state when clicked.

Clickable controls

 

Widgets with active controls will show a hand-symbol cursor.

  • By clicking toggle switches you can quickly change your presence state or the states of your team members (when given team ownership permissions).
  • Other controls allow you to switch views / filter within a widget, e.g. when changing the time or scope of data
  • When editing / deleting data such as workflow or properties the cursor also changes to a hand to signal that elements or views may change when clicked.

Table Sorting

 

You can also click on table headers such task lists, available users, or reporting metrics to sort by that criteria.

  • Repeated clicks change the sorting from ascending to descending
  • A refresh (or switch) to another view will reset the sorting back to default.

Call Pickup controls

 

Pickup controls may not be visible for every service show in your task list, as defined per Service Settings and workflow queue-handling configuration:

CONDITIONS

  • A service's workflow " Distribution Type " needs to be set to any of the "Pickup" variants for this to show.
  • When the "Distribution Type " of your service workflow is set to "broadcast" or "direct" call, no pickup controls may be shown at all. In these cases the call distribution is handled automatically by Nimbus and you just need to accept calls within your Microsoft Teams UI.
 
  • Active pickup controls are highlighted in a signal color. They are clickable and initiate a Microsoft Teams call (or conference with a Nimbus bot for recording purposes)
  • Inactive or no pickup controls indicate that you are not eligible to take the call (e.g. caller is still in queue, already being handled, or your Nimbus flagging you as not eligible to handle further calls)

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.

  • You can click on a legend entry to hide/show corresponding entries            
    → 💡 The filters only show a visible effect if there is data available and within the selected time period / data range.
  • Use your mouse-wheel to zoom and left click to drag a chart along the X-Axis to closer inspect data points.
  • The view will reset once you change the range of data (attempting to fit all data points on screen). It will also reset when you switch between Nimbus tabs/views.

Table of Contents