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.

(lightbulb) Note that these apply universally to all of Nimbus features and extensions, so you need to memorize them only once.

View Selection

Main functionality is sorted 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 Unit (short: OU) to distinguish access to services and other configurable elements (e.g. workflows or audio files).

  • 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.

(info) Read the chapter on Organization Unit 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. You can use the "Open in Browser" functionality at any time to seamlessly continue working outside of the Teams App.

(warning) Please note when using this function: 

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

(tick) We therefore recommend using Nimbus in browser or the teams-installed app exclusively at a time for a consistent experience.


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

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 or text-feedback when mousing over a control that is interactive when clicked

Clickable controls

Widgets that have active controls will turn the cursor into a hand-symbol.

  • 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 signal interactive elements

Table Sorting

You can also click on table headers such  the task list, available members, or reporting statistics to sort by their 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

(tick) Precondition: Your workflow "Distribution Type" needs to be set to any of the "Pickup" variants for this to show. 

Pickup controls are a concept specific to Nimbus. The buttons know different states depending on your team's workflow settings:

  • 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 pickup controls are greyed out to indicate that you are not eligible to take the call (e.g. caller is still in queue or being handled otherwise)

(info) No or inactive pickup controls may be shown when the "Distribution Type" of your team workflow is set to "broadcast" or "direct" call. In these cases the call distribution is handled automatically by Nimbus and you just need to accept calls within Microsoft Teams.

Chart Filtering & View Change

(tick) 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
    (lightbulb) 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.