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:

General

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.

 
 
 

Notifications

User Notifications

By default, Nimbus does only notify the user on incoming Audio/Video calls. However, on certain channels of communication (such as External Task or Email) there is no call event in MS Teams to notify the user about. The Teams client will therefore not have any notification toast to show. Nimbus therefore offers a notification feature that can be toggled on via your individual user preferences.

Visibility / Licensing: Notification settings described on this page are only shown when the External Task or Email modalities are enabled on your General User Settings. Please note that additional modalities are subject to License Management. It may also be that certain modalities are disabled on your entire tenant, so the according settings may not be shown on your user account.

💡 Good to know: With Assistant App 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 the audio notification setting is enabled Nimbus plays an audio notification via your Browser or MS Teams for as long as the task is in "incoming" status. The audio file will be looped until the task is accepted or rejected.

PRECONDITIONS

  • 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:
    chrome://settings/content/sound
  3. Add an entry to the "Allowed to play sound" section. with the following content:
    [*.]nimbus.cloud
  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.

PRECONDITIONS

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

 
 
 
 

Permissions

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

Affects all Nimbus Users: Please read carefully

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

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

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

 

Section: User Permissions

Nimbus Users: These permissions are managed and granted only by and for your currently logged-in user.

Missing permissions warning in the Portal UI next to your user icon: Mouse over the indidivual items to see which detail permissions are needed.

Missing Permission Warning

When your user is missing permissions (usually when Nimbus was just provisioned or new features were added), a warning is shown on your user icon. 

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

💡 You can also mouse over the individual entries to check which detail permissions are granted.

💡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          
User.ReadBasic.All
Basic search for users via their clear name.
☝ Exchange Contacts Search Contacts.Read          
Contacts.Read.Shared
Expands the search to the current user's Exchange Directory. 
☝ Calendar View Calendars.Read,          
Calendars.Read.Shared
Will grant calendar view permissions.
Presence Presence.Read.All Shows a small presence status indicator next to the user.
Nimbus User Permissions
 
 

🤔 What happens if I don't grant these 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.

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. More advanced Nimbus Apps and Features such as Attendant Console or Chat bot interaction will only work with these permissions. 

 
 

🤔 My Permissions show as already granted, why?

A global Administrator on your Tenant can already grant most permissions on your behalf. If this has been done, no warnings and related further action may be required anymore. Also, 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.
  • Any related Nimbus features requiring the same permissions will also be checked off as "OK" as their permission needs are fulfilled.
 
 
 

Section: Admin Permissions

These 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 also shows field to copy the URL.

Procedure:

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

🤔 Which fields are covered by these advanced search permissions?

INC Supported User Search Fields

Required Permissions

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. Read Required User Permissions for more details.

 

Legend

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


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

 
Searchable Field Nimbus   
Address Books
O365   
Tenant Directory
Exchange   
(User Address Book)
Notes
Id       Nimbus internal entity ID
External.Id       ID the system where the entry was imported from.
Display Name ✅ 🔍 ✅  ✅ 🔍 Firstname / Lastname combination
Given Name   ✅    First name
First Name ✅ 🔍     First name
Last Name ✅ 🔍     Last / Family name
Initials ✅ 🔍     Initials (e.g. "JK")
Surname   ✅    Surname
Mail ✅ 🔍 ✅  Email Address
User Principal Name ✅ 🔍 ✅    Consists of: user name (logon name), separator (the @ symbol) and domain name (UPN suffix)
Job Title ✅ 🔍 ➕  ✅ ➕ ✅ 🔍 ➕ Job Title
Business Phones ✅ 🔍     Business Phone
Home Phones ✅ 🔍      Home Phone
Mobile Phones ✅ 🔍     Mobile Phone
IM Address ✅ 🔍     IM SIP Address
Street ✅ 🔍     Streed Address
City ✅ 🔍 ✅ ✅ ➕   Code and City
Company ✅ 🔍 ✅   ✅ ➕ ☝ Company 
Country ✅ 🔍 ➕ ✅ ➕   Country of Origin
Department ✅ 🔍 ➕ ✅ ➕ ✅ ➕ ☝ Department
State ✅ 🔍 ➕ ✅ ➕   State
Postal Code ✅ 🔍     Postal Code
Picture, binary       User Picture
External.CustomField1-10       Custom Field

 

 

 

 

 

 

 
 

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.

Bots are required to post Adaptive Cards to you and inform you about incoming chat tasks

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

💡 Good to know: If you are not handling Chat or the Instant Messaging modality from either services directly via Interact you do not need to register with the bot.

 

In case you decide to Uninstall Nimbus or do not participate in any Nimbus service anymore, you can revoke the consent manually 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.

 
 
 

Provisioning

Here you can 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:

 
 

Logging

Allows to enable anonymized logging features for technical analysis provide them as download for technical support. 

Logging and Performance 

☝ Logging settings are by default disabled for performance reasons and may not be shown for your user at all. Please note the special behavior of these toggles:

  • Logging will remain ON as long as you stay on the tab. 
  • Logging will remain ON as you logout and back in again.
  • Logging will will turn OFF as you close the Nimbus tab and open a new one.

✅ If requested by your support, please enable this setting to capture logs during issue reproduction steps, then disable the setting again.

 
SignalR Logging

Logs information in regards to the SignalR library which tracks presence UI status changes and asynchronous notifications.

More info: https://learn.microsoft.com/en-us/aspnet/signalr/overview/testing-and-debugging/enabling-signalr-tracing 

MSAL Logging 

Logs information in regards to the Microsoft Authentication Library which controls user authentication and access.

More info: https://learn.microsoft.com/en-us/entra/msal/dotnet/advanced/exceptions/msal-logging 

Attendant Console Logging Logs for SignalR processing of delivered data and related http updates shown on screen via Attendant Console.
User-Side Logging Features

Captured Logs

Captured logs are anonymized and created every hour. They contain: 

  • Connect-/Disconnect time - with timestamps.
  • Reconnection attempts - with timestamps.
  • Any unhandled errors (exceptions).

✅ Saved logs remain available in your user preferences for download until manually deleted. If requested by support, please download the logs and provide them as attachment to either support tickets or via mail.

INC Luware Support Address

 Luware Website https://luware.com/support/
Luware Helpdesk https://helpdesk.luware.cloud 
Cloud Service Status https://status.luware.cloud/
Luware support contact details
 
 

Table of Contents