User Preferences (Portal)

User preferences allows you to configure settings that refer to your user account only

💡 User Preferences are structured into tabs, explained in the following:


Here you can: 

  • Log out of Nimbus in case you want to sign in with a different user. 
    💡 Note that the Logout is not visible for users in Nimbus Personal App as it uses your MS Teams account credentials for Single-Sign-On. 
  • Change your personal UI display language and date format. 
    💡This only affects your personal Nimbus experience, not actual live reporting data or the historical Reporting Model.
  • Change your default theme setting (light, dark, synced with your browser).

SSO Experience

When you are running the Nimbus Personal App within MS Teams - or opening an Nimbus Teams Tab  - your login credentials may be re-used to also sign you into Nimbus.

In this case:

A one-time consent window may appear, informing that the Nimbus App will use your MS Teams credentials for login. The "Sign in with Microsoft" button directly signs you into Nimbus (without asking for credentials), or may not appear at all.

💡 Note that session tokens can still expire, requiring you to re-authenticate regularly. A "Logout" button will not be shown, as your Nimbus login is directly tied to your MS-Teams user.

No SSO available to you yet? Ask you administratror to Upload the lastest Nimbus App Manifest.



User Notifications

By default Nimbus does notify the user on incoming calls. However, on External Tasks there is no call to notify the user about, so the MS Teams client will not show any notification (toast) either. Nimbus therefore offers a notification feature that can be toggled on


Contact Center Please note that External Tasks are a Contact Center feature. Both service and user need to be licensed, as otherwise there will no External Tasks feature support, and thus no notifications being sent.


💡 Good to know: With Assistant client installed on your PC, a pop-up window will already be presented on your desktop during any incoming service task (external or other). In this case you may may not need the extra notification features listed below.

Audio Notifications

When enabled this plays an audio notification for as long as an External Tasks is in "incoming" state. The audio file will be looped until the task is accepted or rejected.


  • Nimbus Portal needs to be open either via the Nimbus Personal App in MS Teams or in your Edge/Chrome browser to play the audio.
  • Allow Nimbus to play sound in your browser.  Your audio playback depends on your default output device and the volume set for your browser.

Show me how to configure this...

To allow sound playback in your browser (Chrome):

  1. In Navigate to your Browser Settings > Privacy and Security > Site Settings > Sound
  2. Alternatively enter the following into your address bar:
  3. Add an entry to the "Allowed to play sound" section. with the following content:
  4. Ensure that "Sites can play sound" is also enabled.


Sound still not playing? Check your volume levels:

  1. Right-click your speaker tray icon
  2. Select "Open Volume Mixer"
  3. Ensure that your main volume leveloutput device and browser volume are correctly set.


Browser Notifications

  • When enabled a browser notification is sent via Windows the desktop sidebar an incoming External Task.
  • When clicking on the notification you will be brought directly to the Nimbus Portal > My Sessions view.

A Desktop notification sent by Chrome, using your Nimbus user language settings.


  • Nimbus Portal needs to be open in your Edge/Chrome browser. 
  • Ensure that settings for both your browser and MS Windows allow for notifications to be sent.

Show me where to configure this...

In Windows 11:

  1. Click on Start and search for "Notifications". Alternatively you navigate via Start > Settings > System > Notifications 
  2. Ensure that both "Notifications" and your Browser App entry are toggled "On"

In your browser:

  1. Open "Settings" and search for "Notifications" - shown below is an example for Google Chrome:
  2. Ensure that "Sites can ask to send notifications".
  3. You might be requested to allow Nimbus when the first notification is being sent. You can also review allowed 

💡 Note: Keep in mind Windows 11 "Do not Disturb" mode can also prevent Notifications from being shown.



Here you can manage permissions depending on the role of your logged-in user account:

  • As User - Review your personal permissions granted to Nimbus in order to perform basic user searches (calendar, presence, contacts)
  • As Admin - Review tenant wide permissions  needed to unlock advanced search features (e.g. user details, filtering)

Required User Permissions


Nimbus call distribution and search functionality greatly depends on the permissions granted by the user.

When logging into Nimbus for the first time, your User Preferences (Portal) Icon will display a warning to inform that permission consent is required.

🤔 What happens if I don't grant these permissions ?

Nimbus still works without giving these permissions, but is limited to your basic Microsoft Teams client functionality: Call Accept and On-Hold. Your user may review Reporting details but not interact with services in a productive way. M ore advanced Nimbus Apps and Features such as Attendant Console will only work with the permissions. Without consent, Nimbus cannot search users within your Tenant and/or check calendar entries of your contacts to determine user availability to distribute calls.

🔍The individual sections of this page are explained in further detail below.


Section: User Permissions

USER These permissions are managed and granted only by and for the currently logged-in user.

A user preferences dialog showing missing permissions

Please note:

  • You can either grant single permissions or all at once by clicking "Consent" on the "All Features" row. → A popup will open to inform you about the required permissions (it not previously granted already).
  • When single-granting permissions, note that any related Nimbus features requiring the same permissions will also be checked off as "OK" as their permission needs are fulfilled.


🤔 What are the individual permissions needed for?

  • Features marked with "☝" in the table below are required for any productive work with Nimbus - otherwise the Call Handling features and Apps like Attendant Console will not work properly.
  • A separate consent request is prominently shown in the Contact Search of Attendant Console upon opening for the first time.
Feature Required Permission Effects
☝ Basic Search User.Read          
Basic search for users via name.
☝ Exchange Contacts Search Contacts.Read          
Expands the search to the current user's Exchange Directory. 
☝ Calendar View Calendars.Read,          
Will grant calendar view permissions.
Presence Presence.Read.All Shows a small presence status indicator next to the user.

Nimbus User Permissions

Section: Admin Permissions

TENANT ADMIN The permissions can be managed and granted by any tenant administrator - either as single permissions or all at once. When your currently logged-in user has Service Administration rights you can see the following section:


Since Nimbus cannot detect if you are also a Global Tenant Administrator, this section shows field to copy the URL.


  • If you are the Tenant Admin, simply paste the URL to your browser and grant the permissions.
  • If you are not the Tenant Admin, send the link to any Tenant Administrator to grant consent for all Nimbus users.

→ In either case an Azure permissions dialog opens, allowing to grant consent. This needs to be done only once by any tenant administrator with the corresponding rights. Afterwards the permissions should be granted to all future users of Nimbus.

💡 Each user needs to to log out and back in for tenant-wide changes to take effect.

Feature Required Permission Effects
Advanced Search User.Read.All

Basic search for users via name works without consent.

Advanced Search will grant filtering permissions according to predefined search categories / fields (e.g. city, department, job title)

Nimbus Admin Permissions

🤔 Which fields are covered by these advanced search permissions?

Search fields by source - Click here to learn more...

Fields covered by Nimbus user search

Searchable Fields and Filters Nimbus   
Address Book
Tenant Directory
(User Address Book)
Display Name ✅ 🔍 ✅  ✅ 🔍

KNOWN LIMITATION The search covers the predefined Nimbus Address Books fields, but no custom-fields can currently be searched. We are working to gradually alleviate this situation and make the search experience more consistent.

✅ Fields are supported by search.

🔍 Fields additionally support "CONTAINS" as search operator.

Example: Searching for 'cha' will not only find 'Chadwick' but also 'Michael' 

➕ These fields support Filter capabilities which can be used to narrow down a contact search in Attendant Console.

User.Read.All permissions must be granted to use this feature. 💡 As a Tenant Admin, head to the Nimbus Portal > User Preferences > Permissions "Tab" > Advanced Search and manage consent for your entire tenant.

Given Name   ✅   
First Name ✅ 🔍    
Last Name ✅ 🔍    
Initials ✅ 🔍    
Surname   ✅   
Mail ✅ 🔍 ✅ 
User Principal Name ✅ 🔍 ✅   
Job Title ✅ 🔍 ➕  ✅ ➕ ☝ ✅ 🔍 ➕ ☝
Business Phones ✅ 🔍     
Home Phones ✅ 🔍    
Mobile Phones ✅ 🔍    
IM Address ✅ 🔍    
Street ✅ 🔍    
City ✅ 🔍 ➕ ✅ ➕ ☝  
Company ✅ 🔍 ➕   ✅ ➕ ☝
Country ✅ 🔍 ➕ ✅ ➕ ☝  
Department ✅ 🔍 ➕ ✅ ➕ ☝ ✅ ➕ ☝
State ✅ 🔍 ➕ ✅ ➕ ☝  
Postal Code ✅ 🔍

Section: Bot Registration

Each Nimbus user that needs to handle Instant Messages from external customers needs to "register" once with a bot that will be sending out Chat Handling sessions. 

💡 Good to know: If you are not involved in Chat Handling from either services or Interact you do not need to register with the bot.

🤔 Why is this required? The bot needs to act as "mediator" between external customer and internal Nimbus user. As there is no call toast or ring notification, the bot will use Adaptive Cards as primary means of checking if a user is ready to accept a pending chat session.

In case you decide to Uninstall Nimbus or do not participate in a service team anymore, you can revoke the consent with the according button in your User Settings:

  1. This link will open your Office Portal
  2. Head to App-Permissions menu → Opens in a new browser.
  3. Identify the Luware Inc. Apps product (e.g. Nimbus) therein and revoke the permissions.

💡 Note: Certain app permissions may not be revokeable because the Tenant Administrator gave his consent, overriding your individual user settings.



Here you can do the following:

Download the latest Microsoft PowerShell script. The script is required to Provision new services and confirm technical Service Settings changes made to existing services, such as applying or removing PSTN licenses. 💡 An outdated script will version-check and require you to update to the latest version if necessary.

💡 If you know your Nimbus cluster location you can use the links below:


Table of Contents