We have clients who are concerned about the security of their survey data and do not want to manage additional credentials. It would be beneficial to have a white-labeling or open-source option for embedding dashboards securely, without exposing the full dashboard URL or requiring additional login credentials.

This has been mentioned before by other clients.

They would like their end client to be able to use SSO to login to Displayr.

Customer would like to be able to have SSO (Single Sign On) for their own customers viewing their published documents. This is essentially SSO for Displayr viewers via our customers.

User states: “We have a client who is looking to set up an SSO within their organization for a dashboard that we are building for them. The client has another Displayr dashboard with a different vendor and mentioned that they need to have a new subdomain created for them? I honestly know nothing about this kind of thing and was hoping someone would be able to help us out/point us in the right direction.”

User wants to be able to hook up clients' SSO to their account so when employees leave clients' companies, they can automatically be revoked from accessing Displayr dashboards.

Details -

User was concerned that end-client would not notify them of employees leaving and those employees could potentially be able to access confidential Displayr dashboards. For very large clients, user also doesn’t want to have to manually manage access of potentially hundreds of client-users on their dashboards. Because the customer wants to use their own SSO on their account, currently only way around this is to create separate company specifically for Client dashboards and SSO, and buy additional licenses for that account.

In a scenario queried by a user, could access rights between these 4 countries be separated? Such that viewers for country 1 (based on Google SSO) would only be able to see the dashboard for that country, etc); eg. can we have multiple SSOs setup within 1 license, and keep access rights separated?

Right now if a client of our customer wanted to implement SSO for their projects our customer does for them we would have to create a new account and set up SSO on that account to accommodate for this. This would mean our customer now has 2 or more accounts that they need to manage.

The ask is be able to apply SSO at a document level or group level so there is no need to create a separate account/s to accommodate for this.