The "Users" view allows your to search, create and configure Nimbus users. It consists of the following elements:

  • A user list with search with search and create options. (lightbulb) The availability of Nimbus users is directly tied to your (Azure) user directory. You can search users by common or unique criteria such as @domain or their O365 ID.
  • A user detail view, opened when clicking on or creating a user. The view is distinguished by several tabs as explained further below.

User permissions and Licensing

  • All Nimbus tenant admins have access to the "Users" management view. However, actions may be limited by the respective Roles and Permissions granted to your user.
  • Via this view, licenses may be freely distributed to users , immediately enabling additional Nimbus Features for that user .
  • Enabling a feature is usually accompanied with new configuration tabs shown for that user. Each tab is explained in further detail below.

User details screen - Additional tabs become visible as licenses are applied

Creating Users

Nimbus distinguishes services by their User assignment type:

  • MS Teams-based: Directly tied to your "Teams" the users get automatically added to a Nimbus service
  • None: For IVR or first-level redirection services
  • Skill-based: Manual skill-assignment from users you add from within your tenant directory.

Good to know

(lightbulb) In it's default mode of operation, Nimbus will add users automatically to the user list, synched with your MS Teams structure as any new Nimbus service during Service Provisioning

(question) When should I create Nimbus users manually?

Use CaseDescription
Contact Center Agent

In case you want to create a Contact Center service without a direct MS Teams "Team" connection you can add users manually by searching within your O365/Azure user directory. By individually a ssigning licenses to those users you enable Skills and Responsibilities for skill-based distribution within any (future) Contact Center service type.

Frontpage Support / First Contact Some users may not directly participate in a Nimbus service, but use Luware Interact to directly communicate with customers via embedded Website widget. These users need to be added to the Nimbus list before setting up Interact.

(info) Things to note:

  • Manually added users will get login access to the Nimbus portal but may not see any relevant reporting data until they are part of at least one service.
  • Certain Features are individually enabled as extensions within the Service Settings of a service. → For example, one service may have the Attendant Console extension enabled for its users, so the menu option becomes available to all of them.
  • Any user that already exists in any Nimbus Service does not need to be recreated / added again and can be upgraded for further licenses and use cases. A user can act in multiple different Roles simultaneously.
  • Nimbus keeps track of users only for its internal Organization Units and Roles and Permissions assignment system. Any Nimbus users are always created by reading from your existing O365 / Azure user directory. Nimbus does not create user accounts on its own.

Removing Users

(warning) Removing users will also remove their permission to access to the Nimbus portal. Please note that there are constraints that may prevent you from removing a user. A tooltip over an inactive deletion icon will inform you why deletion is not possible.

User List with (inactive) delete controls
  • You can delete any user that has been manually added before and is not synched to a MS.
  • Users automatically created (e.g. during Service Provisioning) are tied to an active service team and cannot be deleted.
  • Users removed from the Azure user directory are also automatically removed from Nimbus.
  • Deleting users in the Nimbus UI will not remove them from your O365 / Azure user directory, nor remove them from MS Teams. 

General Tab

The "General" tab shows details of a user :

ColumnDescription / Purpose

Display Name

Display name of the user, as shown in the Nimbus UI.
Organization unit

The Organization Units of this user.

(lightbulb) Note: This determines the items the user can see within  Nimbus, not necessarily reflecting which services or rights this user has.

First NameFirst Name - as provided by user directory.
Last NameLast Name - as provided by user directory.

User Principal Name to which calls get forwarded to by Nimbus.

O365 IDUnique Azure / O365 ID under which the user is identified by.
DepartmentDepartment field (blank if not specified within Azure). 
Attendant Console enabled

Shows if that user is enabled to access Attendant Console - a separate Luware application that can also run as add-in within Nimbus. 

(info) Refer to the Attendant Console section for further info on how to use this product.

Active Profile

Shows the currently active Responsibility Profile for that user.

Number of routing services

Shows the amount of teams that this user is a part of.

(question) Why can I not change these details? User details are provided by your tenant's user directory. Changes are made by your local tenant administrator. Details may not be altered from within Nimbus to avoid field conflicts.

Why Nimbus adds users automatically

After Service Provisioning Nimbus adds additional "service" users to its list, based on their Organization Units and team affiliation, This " MS Teams-based " mode is the default for Nimbus "Advanced Routing".

It acts as follows:

Known Issue - User synchronicity on deleted teams

When a MS Teams teams is removed manually - without prior Uninstallation of the related Nimbus service - the users are not shown within the user administration list anymore. However, the team and its members are still shown within Service Administration until the Nimbus team is fully removed from Azure. 


  • In the user administration users will only be shown when part of at least one (still) operational service. This is synched with your tenant user directory and intended design.
  • Nimbus keeps a history of the team members (retrieved from MS teams channel) even after the channel was removed from the teams client. To the User / Service Administrator this will appear as a mismatch of user count.

User Licenses

Additional licenses may be enabled per user to allow for additional Nimbus Features.

  • The Contact Center license allows assignment of Skills and Responsibilities. This is done to allow skill-based call distribution via Distribution Policies
    → Enabling this feature enables the "Skills" tab.
  • The Attendant Console license enables access to Attendant Console features for that user, to be found within the Nimbus frontend main menu.
  • The Interact license enables access to Web Interact features, allowing the user direct interaction with customers visiting via a Website or different Frontend.

(lightbulb) Some features may appear disabled or are hidden for the time being as their configuration, access and reporting concepts are being finalized.

Enabling related service features

To make use the full capabilities of Nimbus, services can also be adjusted with additional licenses and their user assignment type.

→ This is covered within Service Administration.

(info) To disable features in use, please read our our License downgrade information.

Services Tab

The "Services" tab shows the Nimbus service teams the user is currently a part of:

ColumnDescription / Purpose


Display name of the service as shown in the Nimbus UI. Can be changed via the Service Settings.

Amount of users in total within that service.

User Assignment Type

Specifies how this user was assigned to a service:

Roles Tab

The "Roles" tab allows you to inspect and assign roles to a particular user. It also provides an overview in which Organization Units the role applies. 

(info) Visit Roles and Permissions for more detailed information or expand the excerpt table below 

Table: Nimbus role based access concept (RBAC)
Nimbus RoleAccess to
Backend Admin UI
Access to Frontend Portal UI and Live Call DataAccess to Reporting (BI) OData InterfacePermissions Scope (within the assigned Organization Unit)Notes
Partner Administrator(plus) (minus)(minus)

Granted by Luware Support for selected Service Partners.

Tenant Administrator


(plus) (minus)(plus)

Granted by Luware Support or selected Service Partners.

(lightbulb) Details will be discussed during your Onboarding and first Nimbus Installation .

Organization Unit (OU) Administrator


(plus) (plus)


Manually delegated role by a Tenant Admin via User Administration > Roles. OU Admins can perform most administrative configuration tasks 

(lightbulb) Details will be discussed during your Onboarding and first Nimbus Installation.

Team/Service Owner


  • Full access to data entities (services, users, configuration) within the assigned organization unit.
  • Can perform all "User / Agent" duties (e.g. take calls, do after-call work)
  • Can access to Historical Reporting Data directly from the database, via Power BI OData Interface, e.g. by using the Power BI Template.

Granted and named depending on Service type

  • Team Owners - For Auto-Synced to MS Teams Channel roles. Automatically granted rights to fully manage the respective Nimbus service.  No manual assignment needed.
  • Contact Center Nimbus Service Owner - a manually granted role Contact Center-exclusive role. Granted via Service Administration > "Permissions " Tab. An associated Microsoft Teams channel is not required.

(lightbulb) Regardless of name, both types "Team/Service Owners" have the same rights to fully configure their own services.

Service Supervisor



See (info)

(info) Power BI 

    • Can access Power BI OData interface to view service sessions and related user sessions. 
    • No access to extended User States reporting metrics. 

  • No access to
    • Call pickup controls in the frontend UI when applied as standalone role.

Manually granted by a Tenant Admin via  User Administration > Roles.

(lightbulb) An optionally granted role to add to any existing user permission set.

Contact Center Requires a Contact Center license on the user.

User Supervisor



See (info)

(info) Power BI 

  • No access to
    • Call pickup controls in the frontend UI when applied as standalone role.
    • Service-Metrics in the corresponding frontend Reporting views. → Also refer to the Notes.

Manually granted by a Tenant Admin via  User Administration > Roles.

(lightbulb) An optionally granted role to add to any existing user permission set.

Contact Center Requires a Contact Center license on the user.

KNOWN LIMITATION If a user has only Supervisor and not a Team Owner / Service Admin role, only the "UserStates" datasets in the report will be shown: UserStates, StateTypes, ResponsibilityProfile, OU, Users. Other tabs and queries in the BI Report may appear blank.
→ This is intended by design to prevent exposure of individual Service/User/Session data to the wrong audiences. To see a full dataset, the same user also needs a "Service/Team Owner" role assigned.


(Team Member, Service Agent)




Note: Once added to Nimbus, any user can have multiple roles, e.g.

Participate as Agent Team A,
Service Owner for Team B,
Supervisor for Team C.

You can review these roles via User Administration > Roles tab and review the roles of a user.

This role is granted based on Service Type:

  • Team Members - For Auto-Synced to MS Teams Channel roles. No manual assignment needed.
  • Contact Center Service Agents - a manually granted role Contact Center-exclusive role. Granted via Service Administration > "Permissions " Tab.

(lightbulb) All Nimbus user accounts are synched from the Customer Tenant's user directory. Users log into Nimbus using O365 credentials, but only see Nimbus services and data when they become Team members or Service Agents respectively.

Additional Notes

  • A Tenant Administrator, may act outside of the Organization Units this restriction. Roles can be granted or removed from the Tenant Admin, but will have no effect in Nimbus to avoid locking that user out of any administrative tasks.
  • Manual Role management is limited to Tenant Administrators or higher.
  • Certain roles are granted automatically or outside of this tab's view, so the "Edit" or "Remove" buttons may not be shown for all entries.

A User's "Roles" Tab, listing various roles and the OU scope they apply in

Skills Tab

Allows assignment of previously configured skills to this user. (info) Learn more about this on: Skills and Responsibilities.


  • The "Skills" tab is only available when the user has a Contact Center license assigned in the "General" Tab.
  • Skills and Categories need to be defined first before you can assign them. Read here how to create and apply Skills and Responsibilities.

Profiles Tab

Allows assignment of previously configured profiles to this user. (info) Learn more about this on: Responsibility Profiles.


  • The "Profiles" tab is only available when the user has a Contact Center license assigned in the "General" Tab.
  • A profile relies on multiple User Skills and Responsibility Levels to be defined first.

N/A Reasons Tab

Allows to assign Not Available Reasons to a user. 


  • The "N/A Reasons" tab is only available when the user has a Contact Center license assigned in the "General" Tab.
  • Reasons are defined in the Configuration as described on the Not Available Reasons page.

(info) Reasons are selected by users within Assistant upon entering a "Not available" User State .

Interact Tab

(tick) Precondition: The Interact license needs to assigned to a user for the settings to become visible. → See User Administration.

Editing Interact user details

After the User has the according license the Interact-tab will become visible.

The following elements can be configured:

Element Description
User Enabled
  • When enabled the user considered as call contact for Interact.
  • When disabled the user is deactivated as a contact for Interact. 

(lightbulb) Nimbus distributed service calls will still reach the user despite of this setting.

(lightbulb) Interact licenses remain active for this user regardless of this toggle.

Restrict Access

Toggle that applies Interact Domain Templates (CORS) as "whitelists"

  • When enabled, web page access to this service and this user is limited to domains specified in the CORS templates. 
  • When disabled. any web page may access the service and contact this user via the snippet.
Domain Template

Lists configured Interact Domain Templates (CORS) available under the same Organization Unit as the current user.

User Snippet

Default script with settings of current user, which is later can be inserted into a the web page and used as a contact widget.

(warning) Please note that the "Contact ID" and "WidgetKey" are unique to the current user and should not be mixed up.

(lightbulb) For easy Snippet Code retrieval use the "Copy" button.

(lightbulb) To test contacting this user, use the use the "Preview".

Assistant Tab

(tick) Precondition: The Assistant license needs to assigned to a user for the settings to become visible. → See User Administration.

→ After the User has the according license the Assistant-tab will become visible.

Adding Assistant Templates

The following elements can be configured:




Used to Add previously configured Direct Call Templates. Items under the same Organization Units (or higher) can be assigned top this user.

(lightbulb) The templates will be called in the order they were added to the list.

Related Service Settings: Context and Service Call Templates

Note that Direct Call Templates and their related actions only trigger only for direct calls to this particular Agent.

To assign actions for all Assistant users in a service:

  1. You need define separate Service Call Templates first.
  2. Assign these service templates via the Service Settings > Context tab. → They will now trigger for all users of that service, in addition to any individual user templates.

(lightbulb) Note that the same " Conversation Context " items can be assigned to open in both Nimbus portal for Assistant. Context has no functional relation to direct or user call templates and can be applied in combination or individually.