Skip to main content

What’s New

Qrvey 9.0
Qrvey Version 9.0 is now available! This release introduces multi-platform hosting (Azure & AWS), a redesigned Dashboard, extensive widget customizations, and numerous features, enhancements, bug fixes, and performance improvements.
Learn More
Qrvey 8.8
Qrvey Version 8.8 (LTS) is now available to customers! This version supports FIPS for GovCloud and includes tons of bug fixes and performance improvements.
Learn More
Qrvey 8.7
Version 8.7 of the Qrvey platform is now available to customers! This version includes new features including area charts, the ability to pivot and export data, as well as numerous bug fixes and performance improvements.
Learn More
Qrvey 8.6
Version 8.6 of the Qrvey platform is now available to customers. This version includes several new feature enhancements and performance improvements.
Learn More
Required Update for 8.5.1
Attention 8.5.1 customers: for any 8.5.1 instance deployed prior to 08/05/2024, an update is required to ensure you are running the latest images.
Learn More
Qrvey 8.5
Version 8.5 (LTS) of the Qrvey platform is now available to customers. This version includes several new features and performance improvements.
Learn More
End-of-life Schedule
We've added a new article that lists the features and endpoints that have been scheduled for deprecation. All features and endpoints will be supported for (1) year after the release date of the LTS version that contains the alternative.
Learn More
Version: 9.0

Sharing in Widgets

Dashboards (excluding Legacy Dashboards) have the concept of Ownership. When a user creates a dashboard, you must pass a clientId to identify the user and an orgId to identify the organization the user belongs to. If this user wants to share the dashboard, they can share it with their organization (defined by the user's orgId) or pass the orgs object to share it with specific users or roles within the same organization.

How Sharing Works

Sharing must occur within the same organization. The user who wants to share the dashboard must have a valid clientId and orgId.

To share a Dashboard with another user, they must must have:

  • orgId
  • orgs.users[] with the user's clientId and valid email.

Note: The string org:0 is internally reserved for the "Qrvey Composer Org". In other words, assets made within Qrvey Composer are associated with "org:0", so use that string to display them in an embedded scenario.

Any widgets that need to access dashboard information, such as Automation (Flows), must also pass the clientId and orgId. This ensures that only dashboards the clientId has access to are listed, as well as charts inside them when attached to Send Email actions.

When embedding Dashboards created within Composer:

  • Set orgId: "org:0", to associate it with the "Qrvey Composer" Organization.
    Note: If you pass "org:0" into a widget, it will behave as if it is in Composer.
  • Then pass the desired clientId to enable Dashboard personalization.
  • These options will function just like in Composer, even displaying the Composer users for sharing.

Example:

"orgs": [
{
"orgId": "org:0",
"users": [
{
"clientId": "john_smith",
"email": "john_smith@qrvey.com"
}
]
}
]

When accessing a dashboard that has been shared with a role, assign the role to the user so they can access the dashboard.

{ // the dashboard config object
"appId": "XVDq3Xr",
"userId": "Sk7HuNH",
"clientId": "jane_doe",
"expiresIn": "1y",
"orgId": "org:0",
"roles": ["QA"]
}

Include roles in orgs.orgRoles[] to share the dashboard with specific roles:

"orgs": [
{
"orgId": "org:0",
"orgRoles": ["QA"]
}
]

For JWT/Config-Based Sharing in Embedded Dashboards, embed the dashboard with the orgs[] object in the QV Token or config object. This enables the UI to display the list of users and roles for sharing.

{
"appId": "XVDq3Xr",
"userId": "Sk7HuNH",
"clientId": "jane_doe",
"expiresIn": "1y",
"orgId": "org:0",
"roles": ["QA"],
"orgs": [
{
"orgId": "1",
"orgRoles": [
"QA"
],
"users": [
{
"clientId": "john_smith",
"email": "john_smith@qrvey.com"
}
]
}
]
}