Required User Permissions

MINIMUM REQUIRED 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          
User.ReadBasic.All
Basic search for users via 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

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:

AZURE PORTAL - GRANT PERMISSION LINKS

Since Nimbus cannot detect if you are also a Global Tenant Administrator, this section 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)

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
O365   
Tenant Directory
Exchange   
(User Address Book)
Notes
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.

Table of Contents