#FeatureFRIYAY July: we added Single Sign-on, no-code Integrations and more!
Posted On 30/07/2021
We’ve got some exciting product updates to share this month. If you’re looking to improve your security & compliance, while granting your end-users more options for personalization and control, keep on reading!
You can now choose your data tenancy region!
Recently, we made it possible for you to pick your data tenancy region when you sign up for Cumul.io. This allows you to choose where your data with Cumul.io is stored. You have the option to choose between Europe and US.
This way, you can make sure that all your data is stored in the region that makes sense to you, whether that’s in the EU or the US. Why is this important? Let’s have a run through:
For some, data tenancy regions might be a question of legal compliance. This would especially help those of you based in the US, making it possible to have your data with us stored locally. But equally, you might be subject to GDPR and other regulations, requiring you to have your data stored in the EU. This choice is now completely up to you!
Latency! As our query engine can now also be located closer to wherever your data source is, it will also mean improvements with regards to latency.
If you are already a Cumul.io customer, we will soon start giving you the possibility to migrate from our EU cloud to the US cloud. If you are interested in this, please contact our support team.
‘Integrations’: manage embedded dashboards without code
The possibility to embed dashboards inside your own platform of web application is core to our Cumul.io platform. It’s fast & relatively easy to do this via our Integration API, but so far, this has been the only way to fully manage your embedded analytics.
If you’re a non-technical user of our platform, you’ll be excited to hear that you can now manage your embedded dashboards from within the Cumul.io UI!
We added a brand new tab to the platform, called ‘Integrations’. Now, what are integrations and how do they work?
What are Integrations?
Integrations are collections of dashboards and datasets with customized access rights. These collections can be embedded in your application by using a single code snippet.
In that way, you can easily create collections for different customers, departments (e.g sales, marketing, customer success,…), and more.
Why use integrations?
As a non-technical user, that means you can now manage your integrations and dashboard collections without writing a single line of code. No more bugging your IT team! From within our simple UI, you can now:
Grant specific user rights to a collection of dashboards & datasets
Dynamically change dashboards via lists & pickers, instead of hardcoding the dashboard IDs
Track usage per user & per dashboard
Each dashboard will have a unique name, or ‘slug’, which will be added to the code. So, whenever you want to swap an existing dashboard, simply use our dashboard picker to select a new dashboard instead of changing IDs in the code. Your changes will be live immediately!
How to create an integration?
Creating an integration is a simple, 3-step process that requires no code:
Select the dashboards you want to include in your embedded collection
Select the datasets that should be accessible in the embedded dashboards
Set the correct access rights: decide whether the user of the embedded dashboard can view, use or edit the dashboards & datasets. If you want specific users to get access to only a specific subset of your dataset, you can add these rules right inside the UI as parameterizable filters.
Once you went through these steps, simply add the code snippet to your application or have your developer implement it with simple copy-paste!
If you’d like to learn more about Integrations and see them in action, replay our customer success team’s webinar below for a full run-down.
Note: Because access to Integrations is granted to individual users, this requires a specific type of authorization tokens called SSO tokens, or single sign-on tokens. Instructions on how to generate these tokens are included in the Integrations modal.
SSO authorization is brand-new to Cumul.io! Find out more below, where we’ll discuss this in more detail.
Single Sign-On Authentication is now available in Cumul.io
When it comes to authentication, we all know the hassle of logging in to multiple applications with separate logins and passwords. Especially when you have to login multiple times within the same application, this causes a bad user experience, which you’ll absolutely want to avoid.
In addition, with raising cybersecurity concerns every day, it’s now more important than ever to have a secure authentication mechanism in place.
As a user-friendly and secure solution, Cumul.io now offers Single Sign-on tokens for authentication to your embedded dashboards. This means that your platform users will only need to authenticate once in order to get access to the embedded dashboards (s)he is allowed to see.
What are the benefits of SSO authorization tokens in Cumul.io?
For those already using our existing temporary authorization tokens, it’s important to note that your current tokens will keep functioning, and are still a secure mechanism for authentication.
The new SSO tokens, however, enable a bunch of new use cases, which temporary tokens do not support. Because SSO tokens can identify unique users, your can give your end-users much more control to generate their own content & dashboards. Some examples:
Allow end-users to personalize or even edit their dashboards;
Let end-users set personalized alerts;
Allow personalized scheduled exports for each end-user;
Get more statistics and improved auditing on user accounts & usage of dashboards.
In a nutshell, if you want to grant your end-users more control and personalization options, SSO tokens are a huge improvement to your embedded analytics setup!
More flexible to use and to import elements into your web app;
Easier to set up, maintain, check dependencies and manage risks;
Less development, and overall less lines of code needed;
Lightweight component, resulting in better performance;
It’s published on npm, and can be versioned;
Our web component will become the default for Cumul.io embedding, giving access to new features and use cases.