Within Nimbus the user settings are available at the left side of your main menu.
Here you can:
- Log out of Nimbus in case you want to sign in with a different user.
- Change your personal UI display language and date format. Note that this only affects your personal view, not actual live reporting or the historical Reporting Model.
- Manage permissions granted to Nimbus.
First Login: User Consent
When logging into Nimbus for the first time you will be asked to grant required User Permissions, allowing Nimbus to query contact data and use call features under your user name.
Not granting these permissions will greatly reduce the functionality of Nimbus and related apps. This has to be done for each Nimbus user and team individually, or can be done by an Administrator. → More details in the chapters below.
New SSO Login 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:
Please note that the new SSO experience may not be available to you until your Tenant Administrator has Updated the App Manifest on your Tenant.
These permissions are managed and granted only by and for the currently logged-in user .
- 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.
|Basic search for users via name.|
|Exchange Contacts Search|
|Expands the search to the current user's Exchange Directory.|
|Will grant calendar view permissions.|
Shows a small presence status indicator next to the user.
TENANT ADMIN The necessary permissions can be managed and granted by any tenant administrator - either as single permissions or all at once.
Since Nimbus cannot detect if you are a Tenant Administrator, this will show a field to copy the URL.
- If you are the Admin, simply paste the URL to your browser and confirm.
- If you are not a Tenant Admin, send the link to any Tenant Administrator to confirm consent for all Nimbus users.
→ In either case an Azure permissions dialogue 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.
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 search permissions?
|Searchable Fields and Filters||Nimbus |
(User Address Book)
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.
These fields have additional Filter capabilities. An "Advanced Search" (User.Read.All) permission must be granted by a Tenant Admin to use this feature.
|User Principal Name|
What are the Provisioning / Powershell Scripts and links on my User Settings?
TENANT ADMIN To execute these scripts you will need tenant administrator rights. Nimbus relies on those scripts to detect and apply changes to your Service Settings, check PSTN licenses and apply the according tenant-side settings and policies automatically.
Also refer to:
- Roles and Permissions > "Tenant Administrator"
- Service Provisioning > Provisioning via Microsoft PowerShell