Deploying Content Seamlessly Across Tenants [VIDEO] 

Deploying new applications, features, and content across multiple tenants can be a complex process. Qrvey’s embedded analytics solution offers an elegant multi-tenant content deployment solution that simplifies and streamlines rollout to your SaaS application tenant base.

What is Content Deployment

Content deployment encompasses the tools to release new reports, dashboards, datasets, automation workflows, and more to all or specific tenants in your SaaS application. 

Additionally, this is also how engineering and DevOps manage deployments across environments such as dev to QA and QA to production. 

Why is Content Deployment Important for Embedded Analytics to be Successful

Content deployment is crucial for embedded analytics solutions as SaaS companies operate within a development process that sees content created in lower development environments and moved up through staging and testing environments before being released to production environments.

With content deployment from Qrvey, SaaS companies can selectively release new content, but more importantly, run checks on all new content before releasing to production. 

Content deployment enables product leaders with options such as: 

• Creating MVPs or betas for select customers
• Selling advanced features or reports as add-ons to premium customers
• Offering custom data models unique to specific tenants

Essentially, this is the best tool for product leaders to add another layer of customization so analytics are not a one-size-fits-all for an entire SaaS customer base.

How to Use Content Deployment in Qrvey’s Embedded Analytics Solution in 4 Steps

Step 1 – Packaging the Content

The first step is creating a release package in Qrvey. You select the source app and content like datasets and dashboards to package. Qrvey stamps all objects with a version number to avoid impacting the source while packaging. Dependencies like data connections are automatically detected and included.

Step 2 – Specifying the Deployment Details

Next, you define a deployment that specifies exactly what content to deploy from the release package. You can choose to update an existing app or create a brand-new onboarding app for tenants. Additional parameters like naming conventions can be configured as well.

Step 3 – Executing the Deployment Job

A deployment job ties everything together by mapping the packaged content to target servers and tenant recipients. The job can be scheduled or executed on demand. Deployments involving multiple content packages or target environments can be modeled using blocks.

Step 4 – Validating the Successful Content Delivery

Once deployed, you log in as users from different tenants to validate that the packaged content has been properly provisioned to each tenant workspace as intended. Testing verifies the end-to-end deployment operation before rollout to production.

Multi-Tenant Content Deployment Made Simple

Qrvey takes the complexity out of deploying apps, data, and other analytics objects seamlessly across your tenant base. Packaging, deployment jobs, and validation enable pushing content in a consistent, auditable, and efficient manner to any number of tenants.

Qrvey’s robust embedded analytics make it easy to roll out new content across your entire tenant population. Qrvey knows how important it is to manage content and address the unique needs of various companies/tenants.

Schedule a demo to see Qrvey’s multi-tenant deployment capabilities in action. 

Watch a quick demo video here to see content deployment in action: