On this page the following topics are covered:
- How to get access to licensing options and how to get your required Tenant Administrator access configured. This will enable your technical teams to manage the Nimbus deployment without being members of the Teams themselves.
- How to manage your available licenses and perform up- or downgrades.
The Licensing view allows Administrators to check on and re-distribute available licenses and addons in bulk. License management is done either here as described below, or via the Administration pages of Users and Services respectively.
About the Tenant State widget
Your Tenant State indicates overall availability of Features and Licenses at a glance. A tenant state can be as follows:
- Active - your Nimbus subscription is active and valid.
- Trial - your Nimbus subscription is in trial mode. You can try out Nimbus Features within the trial period.
- Suspended - your Nimbus subscription has been suspended. → See footnote below.
- Expired - your Nimbus subscription has expired. Get in contact with Luware Support if you need to renew it.
- Canceled - your Nimbus subscription is cancelled.
- Lab - a Nimbus lab subscription for test purposes.
🔎 Good to know: Your overall license contingency is also made visible via Tenant Administration > Licenses tab. To change the available license contingency, get in touch with your Customer Success partner.
🤔 What happens on a Tenant suspension? All users will not be able to login to Nimbus and related apps. Inbound / Outbound tasks will be rejected and incoming calls will be redirected to a default announcement workflow. This state can be resolved by a Luware Administrator.
Access to Licensing
Licenses can only be managed by administrator-type User Roles → see table below the most important details.
- To manage user licenses, your account must be a Tenant Admin or Organization Unit Admin.
- To manage service licenses, your account must be a Tenant Admin.
💡 Reminder: Higher-tier licenses and addons will enable Nimbus Features at additional cost. Please get in touch with your Customer Success partner to discuss your use cases and determine the best licensing scenario for your needs.
Roles with Licensing Access
There are different Roles and Permissions in Nimbus that relate to, use or enact licensing. The following table is an excerpt:
A Tenant Administrator has access to all Services and User Administration at your organisation. They also manage Resources available to all Services under the respective Tenant. One advantage of being a Tenant Administrator is that you do not have to be Team Owner or Member, but still can manage companywide Resources, Opening Hours or other Configuration-relevant items for any services within your Tenant.
🤔 How can I get Tenant Administrator rights? Create a new security group in Azure AD (or choose an existing one) and send us its Object ID. 💡 Don’t forget that you need to be a member of this security group - group owners will not be taken into account.
INC Create a Security Group
How to create a Security Group in Azure
Create New Security Group
Define Group Details
Tenant Name and Object ID
🤔 What about Partners? It is possible to give both you and your partner tenant administration rights. In this case your partner can follow the same steps as above in their own Azure AD and provide us with their Object ID.
🤔 Where to forward this Object ID? t your assigned Customer Success partner or create a request ticket via our helpdesk . We will then register the group's Object ID for your Nimbus tenant.
🤔 Can I further delegate tasks? Yes, by assigning → Organization Unit Administrator rights to additional users on your Tenant. As a Tenant Administrator you can do this via User Administration. This user acts within services, resources and users already assigned to Organization Units.
🤔 Where can I check on my current License status? Head to the Tenant Administration > Licenses tab to see your current assigned contingency of licenses.
Organization Unit Administrator
Organization Unit Administrators (or short: OU Admins) delegates with the same privileges as the Tenant Admin. However, their scope is limited to the configuration, service and user entities within their assigned Organization Units.
💡 OU Admins are restricted to managing user licenses. They cannot change service licenses.
Licenses are distinguished by types: Service Licenses and User Licenses.
✅ Click on each tab below to learn more.
🔍 Service licenses directly affect the Nimbus Features available to the individual service. To change licenses on your services:
- Click on the correponding service license you want to distribute: Advanced Routing, Enterprise Routing or Contact Center.
💡 For downgrades of services already using Enterprise Routing or Contact Center features, additional steps may apply. → See License Downgrade chapter below.
- The view shows your contingency of available service licenses, distinguished by Service types.
- You can review and "Undo" your license changes before confirming the change via "Save".
🔍 Service licenses and additional addons (apps, modalities) can also be changed indivdually in each Service Administration. Adding these licenses will enable additional settings for the respective service.
What are the user assignment type differences?
INC User Assignment Types
Each Nimbus service can be of a different user assignment type that determines how users are associated to this service:
- MS Teams-based: Directly tied to your MS Teams "Teams" as determined during Service Provisioning. Users get automatically added and synced to a Nimbus service.
- Skill-based: Applies for manually created services via Service Administration. Requires skill-assignment from users you assign to the service from within your tenant directory.
- None: Has no users, but can be configured by any administrator. Used for IVR or first-level redirection services.
☝ Important to know: The user assignment type is fixated when a service was either provisioned via MS Teams or manually created via Service Administration, e.g. for IVR or skill-based distribution purposes. A switch between MS Teams-based and Skill-based services is not possible due to how individual users are configured and how Nimbus Features operate.
🤔 Which user-assignment direction changes are allowed?
|Notes on licensing
|✅ Allowed - Prerequisite to downgrade to Enterprise Routing license.
|❌ Not allowed - the user rights and service are directly tied to the MS-Teams channel. If you remove the channel, the related Nimbus service needs to be removed as well.
|✅ Allowed - Requires a Contact Center license to upgrade.
|🔍 Not possible due to significant feature set and user permission handling differences. See User assignment types for more details.
→ We recommend to configure a new service according to your Features needed, then switch over from your previous service. While this creates a temporary "license overhead" it also guarantees near-uninterrupted service to your customers. An additional benefit is also a clear Reporting transition while minimizing the distruption to your Nimbus users until production-ready.
🤔 Why are the options restricted?
Among other features, the underlying Role Access Concept is either inherited from Teams or managed exclusively by Nimbus itself. Changes on your service structure therefore require close consideration before taking action. For example:
- Service Ownership - Which (future) MS Teams channels to use – or remove – along with a changed service / team owner structure? An example could be your users shifting to separate department structures, but the requirement to stay reachable and organized via one central service remains.
- Role Management - How to manage Service Permissions among (new or future) users with different technical expertise? An example would be a split of service ownership and additional BI reporting / supervision User Roles in scenarios where users have multiple roles in different teams.
- Incoming Task management - Which Distribution Policies and (optionally) user Skills and Responsibilities must be considered for call distribution? An example would be the need for more specialized services that can (spontaneously) onboard users with the right expertise without the need to fill your MS Teams client with extra channels.
SERVICE LICENSE FOLLOW-UP STEPS
🔎 Also refer to the following topics for detail steps:
- Enterprise - Use Case - Building a Priority Service in Enterprise Routing
- Contact Center - Use Case - Setting up a Contact Center. ✅ As administrator learn about External Tasks and how to configure advanced features of your service via the Modality Service Settings
- A list of all Workflow Activities, including those requiring certain licenses on the service.
🔍 User licenses directly affect the Nimbus Features available to the individual user. They also enable users to make use of addons and modalities. To change licenses on your users:
- Click on the correponding user license you want to distribute: Attendant Console, Interact, Contact Center, Assistant, Instant Messaging, External Task, Email.
💡 For downgrades of users already using Contact Center features, additional steps may apply. → See License Downgrade chapter below.
- The view shows your contingency of available user and addon licenses. In this example below Attendant Console licenses are distributed.
- You will see all users already having this license. Either remove it or add new users according to your license pool.
- You can review your license changes before confirming the change via "Save".
🔍 Good to know: User Licenses and additional applications (addons and apps) can also be changed individually in each user's User Administration . Adding these licenses will enable additional tabs for the respective user. Learn more about each license and additional apps by visiting the Nimbus Features page.
USER LICENSE FOLLOW UP STEPS
Once a license was applied, any administrator can start to set up the additional user details via the User Administration tabs and define necessary Configuration items such as user Skills and Responsibilities.
🔎 Also refer to the following topics for detail steps:
- Contact Center - Use Case - Setting up a Contact Center.
- Interact - Use Case - Setting up Interact.
- Attendant Console - when enabled is immediately visible for the user. ✅ As administrator you may want to check on Required User Permissions and grant permissions for extended search features within Attendant Console on your entire tenant.
- Assistant - Use Case - Setting up Assistant. ✅ This feature requires an additional Assistant App Installation.
License downgrades can be performed from within the Licensing overview. However, when Nimbus Features are already in use, a warning will be shown:
🔍 Checking for downgrades in the "Licensing" view
To downgrade from a higher tier license, any related Nimbus Features and their data entities must be removed or unassigned from the user or service. This is done via Service Administration and User Administration respectively. Refer to the License downgrade checklist below for details.
Tooltips will inform about the settings that prevent a license downgrade.
What do I need to check?
License Downgrade Checklist
Downgrade from Features that need to be checked / deactivated in order to downgrade
|Things to check
✅ Check and disable additional Context, Codes and Tags enabled in the My Sessions view.
✅ Check everything from → Enterprise Routing disable related Features.
✅ Additionally you need to...
Individual Contact Center licenses can also apply to users. There are two methods to remove a license from a user:
☝ Warning: Removing a Contact Center license from a user will remove ALL associated settings and service assignments. This action is irreversible, meaning that you must re-define this user if you ever reconsider adding the license again.
💡 As an example: a user can have individual Skills and Responsibilities and be assigned to multiple services via Agent Service Settings. Both associations are getting removed alongside with the license . If you want to re-assign or reinstate your Contact Center license at a later point you might want to check on Responsibility Profiles to ensure that the licensed user is correctly queued, according to your (remaining or new) service's Distribution Policies .
🤔 Why isn't the license downgrade automated? As features such as skills and workflows may be used across multiple services, simply removing them is not an option. A manual check ensures that features are consciously removed and don't render your remaining services unreachable, e.g. due to suddenly disabled workflow activities or missing parameters required for call routing.
🤔 I have finished my checks. What comes next? Once the steps are done, get in contact with your service partner or Luware support to downgrade your license.