Nimbus can be installed on your MS Teams client and used as a personalized App for easier access to Nimbus features. Generally
PRECONDITIONS
The Nimbus personal App itself must be provisioned by your Tenant Administrator during Nimbus Installation. Otherwise it will not show up for installation within your MS Teams client.
Adding the App
To add the Nimbus App to your MS Teams:
- Click on “Apps”
- Search for “Nimbus” → Note the Preconditions above.
- Click “Add”
First Sign-In and Usage
- After being made available on your Tenant, the Nimbus App can be added to permanently appear in your MS Teams sidebar.
- Once clicked upon you can sign in (Nimbus will use your company Single-Sign-On if available).
- You should now be ready to use the UI and handle incoming.
Available Functionality
The App provides the same functionality as the logging into Nimbus Portal. You can learn more on the following pages:
INC Nimbus Portal Menu Items
| Menu item | Description |
|---|---|
| My Overview | Personal Overview on your Day, Call Metrics, Status display |
| My Sessions | Task handling view, showing live tasks and customer Conversation Context. |
| Personal Dashboards | Customizable with Dashboard Widgets for inspection of Service or User-related KPIs. |
| Services Overview | A list of all your Services, assigned Users and incoming Tasks. |
| Live View | Live statistics of a selected Service with showing Tasks, Users and related trend metrics. |
| Statistics | Lookback statistics of a selected Service showing Task Results and SLA metrics. |
| Sessions List | Historical Nimbus Reporting Sessions list of a selected Service. |
| Service Settings | Access to Nimbus Features and Task Queue and Distribution Settings per Service. |
| Attendant Console | Access to individual call handling scenarios and call forwarding options. |
| Configuration | Access to configurable items used in Service Settings. |
| User Preferences (Portal) | User-Individual settings for Language, Notifications, Permissions, Logging. |
FAQ and Troubleshooting
🤔My Nimbus Context is not opening?
☝ MS Teams Limitation: Teams does not allow to open browser tabs automatically. Nimbus Features such as Conversation Context (e.g. to show Ticketing or CRM systems) may therefore require you to open Nimbus in your browser.
✅ Workaround: Use the Nimbus in Browser: In case you depend on Context, use the following URLs to log into the Nimbus Portal via your browser. The experience is nearly identical as in the App.
INC Nimbus Portal URLs
| Switzerland 01 | https://portal.ch-01.luware.cloud/ |
|---|---|
| Switzerland 02 | https://portal.ch-02.luware.cloud/ |
| Germany 01 | https://portal.dewe-01.luware.cloud/ |
| Germany 02 | https://portal.dewe-02.luware.cloud/ |
| United Kingdom 01 | https://portal.ukso-01.luware.cloud/ |
| Australia 01 | https://portal.aue-01.luware.cloud/ |
| West Europe 01 | https://portal.euwe-01.luware.cloud/ |
| East United States 01 | https://portal.use-01.luware.cloud/ |
✅ Make sure to configure your web proxies to allow access to these domains or whitelist the complete *.luware.cloud domain.
💡Note: The Portal can be open in parallel to the Nimbus App in MS Teams. All Nimbus views and Buttons update simultaneously to keep you informed of the latest status.
✅ Workaround Assistant App: Alternatively you can install and run the Nimbus Assistant app on your local PC's system tray, which allows to open call context browser tabs automatically without the need of either Nimbus App or Browser window to be in focus.
🤔 Can't see the Nimbus App in your Teams?
✅ → See PRECONDITIONS above. If the App does not show up in your “Apps” list, chances are your Tenant Administrator has not completed the Personal App Installation on your Tenant set.
🤔 Can't log into the personal App?
✅ Check Cookie Restrictions: Running the Nimbus app within the browser-based MS Teams Client (instead of the installed Teams App) bears a risk that 3rd-party cookie policies configured in the browser may cause Nimbus login issues.
This is due to the fact that Nimbus re-uses the Teams login token for its internal authentication (Single-Sign-On).
Learn more…
INC Third-Party Cookie Restriction Workaround
☝ Note of third-party cookie restriction: In 2024 Google Chrome started restricting third-party cookies “by default for 1% of Chrome users to facilitate testing, and then plans to ramp up to 100% of users in H2 2024.” Other browser vendors are likely to follow suit with similar policies.
✅For Tenant Administrators: Most Enterprise users should be excluded from the 1% experiment group. However, Luware recommends that admins proactively use the BlockThirdPartyCookies and CookiesAllowedForUrls policies in Chrome to avoid sign-in issues, as described in this MS “Teams doesn't load” help article reference.
Add the following sites to the third party cookie exception list:
[*.]microsoft.com
[*.]microsoftonline.com
[*.]teams.skype.com
[*.]teams.microsoft.com
[*.]sfbassets.com
[*.]skypeforbusiness.com
[*.]luware.cloud🤔 What are the risk scenarios?
Not following the recommendations by Google involves a risk that Nimbus stops working in Chrome (or other default browsers) when the Nimbus App is launched embedded via MS Teams.
- MS Teams client in your browser: A likely cookie-related risk scenario occurs as you launch launch the Nimbus App or Nimbus Teams Tabs. This triggers a user authentication using 3rd party cookies.
- MS Teams standalone client: Microsoft claims that Nimbus should continue working in the client. Furthermore, Nimbus standalone tab will open and work when "Open app in browser tab" link is used.
To avoid either scenario, we recommend whitelisting cookie-exceptions in your browsers so that Teams can continue continue working with Nimbus. To allow (whitelist) specific URLs in your browser, refer to the steps described in this MS “Teams doesn't load” help article reference.
🤔 What are the effects/problems?
We identified the following issues in regards to cookie-related authentication:
- Warning at startup - A warning message is shown every time when the user start Nimbus in Teams. It seems it's a general error in case of the third party cookies are blocked.
- Authentication popup issue - Returns a Cancelled By User error even if the authentication was not cancelled by user.
✅ Ask your Admin for User Permissions: If your login seems to work, but shows no Nimbus content or rejects acces, make your user was added to a Nimbus Service by any Nimbu Users acting in Admin Roles.
✅Troubleshooting - If you already had access before:
- Try logging in via browser using the Nimbus portal link to see if it's a general issue.
- If you encounter issues or see technical messages, consult with your Tenant Admin or Nimbus Support Partner.
- On continued technical issues, you can check the Luware Cloud Status and contact Nimbus support via the following channels to report the issue:
INC Luware Support Address
| Luware Website | https://luware.com/support/ |
|---|---|
| Luware Helpdesk | https://helpdesk.luware.cloud |
| Cloud Service Status | https://status.luware.cloud/ |