User Preferences (Portal)
User preferences allows you to access settings that refer to your user account only.
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 "Permissions" tab below.
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 in the Nimbus Personal App as it uses your MS Teams account credentials for Single-Sign-On.
More infos below. - Change your personal UI display language and date format. Note that this only affects your personal Nimbus experience, not actual live reporting data or the historical Reporting Model.
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:
- 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.
- The "Logout" button will not be shown, as your Nimbus login is directly tied to your MS-Teams user.
Note that the new SSO experience may not be available until your Tenant Administrator has Updated the App Manifest on your Tenant.
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)
Section: User Permissions
USER These permissions are managed and granted only by and for the currently logged-in user .
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, Calendars.Read.Shared | Will grant calendar view permissions. |
| Presence | Presence.Read.All | Shows a small presence status indicator next to the user. |
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 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.
| 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?
| 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.
|
| Given Name | | |||
| First Name | | |||
| Last Name | | |||
| Initials | | |||
| Surname | | |||
| | | | ||
| User Principal Name | | | ||
| Job Title |  | | | |
| Business Phones | | |||
| Home Phones | | |||
| Mobile Phones | | |||
| IM Address | | |||
| Department | | |||
| Street | | |||
| City | | | ||
| Company | | | ||
| Country | | | ||
| Department | | | | |
| State | | | ||
| Postal Code | |
TENANT ADMIN Here you can download the latest Microsoft PowerShell script required to:
- Provision new services.
- Confirm technical Service Settings changes made to existing services, such as applying or removing PSTN licenses.
If you know your Nimbus cluster location you can use the links below: