Deployment Management

Zoho Analytics allows you to build, test, and deploy your analytics content in a controlled way through Deployment Management. This feature connects multiple workspaces through a series of ordered stages, say Development, Testing, and Production, and lets you push your views and reports from one workspace to the next. Your production workspace stays clean and stable while your team continues to build in the earlier stages.

Instead of editing reports directly in a live workspace, you make your changes in a Development workspace, validate them across different stages, and deploy the finalized content to the live workspace only when it is ready. Every deployment is tracked and saved as a version, so you always know who deployed what and when, and you can restore a stage to an earlier version if a deployment does not work as expected.

Who can use

Deployment Management is intended for administrators who manage analytics content across teams and need a governed way to move changes from development to production workspaces. It is useful in scenarios such as the following:

• A business intelligence team builds dashboards in a Development workspace, validates them in a Testing workspace, and publishes the approved dashboards to a Production workspace that business users rely on.
• An enterprise with strict governance needs every change to be reviewed and traceable before it reaches the actual reports used for decision making.
• A consultant maintains separate workspaces for a client and needs a repeatable, low risk way to roll out report updates without disturbing live data.
• An organization standardizes a set of core reports and pushes consistent updates to multiple downstream workspaces.
• A dashboard update deployed to Production shows incorrect KPI values, and the team restores Production to the last stable version while the fix is made in Development.

Feature Requirements

Supported Plans

Deployment Management is available on the Premium and Enterprise plans of Zoho Analytics.

Who Can Access

Only the Account Administrator and Organization Administrators can create deployment flows, edit them, deploy content, and restore versions. Because a flow can include workspaces that belong to different organizations, this access is limited to administrators who can act across those organizations.

Where to Find It

Open Deployment Management from Data Administration under Organization Settings.

1. Understanding Deployment Management

Before you create your first flow, let us explore how Deployment Management is organized and what happens when you deploy.

Deployment Hierarchy

Deployment Management is built on three levels:

• Deployment Management is the top level section where you view and manage everything related to this feature, and monitor all your deployment flows.
• Deployment Flow is a container that holds an ordered set of stages. Each flow represents one promotion path, such as Development to Testing to Production.
• Stage is a single step within a flow. Each stage is mapped to one workspace and is shown in a fixed order, such as Stage 1 (Development), Stage 2 (QA Testing), and Stage 3 (Production). The order of the stages defines the direction in which content is promoted.

Every successful deployment to a stage is saved as a version of that stage, numbered in order (Version 1, Version 2, and so on). The first stage in a flow has no versions, as content is never deployed into it.

What Gets Deployed

When you deploy, Zoho Analytics copies the metadata of your views and reports from the source stage and applies it to the target stage. The metadata describes how your content is built. A deployment includes the following:

• Tables and their schema, including column names, data types, default formats, and display names
• Query tables, including the SQL query and output schema
• Charts, including formulas, measures, dimensions, aggregations, filters, sorting, axes, legends, and user filters
• Pivot, summary, and tabular reports, including row and column fields, aggregations, subtotals, grand totals, report filters, and sorting
• Dashboards, including the grid layout, widget positions and sizes, text widgets, images, and interactions such as cross filtering, drill through, and URL actions
• Calculated fields, user filters, and parameters
• Lookups and joins, including table relationships and join keys
• Themes and formats, including number and date formats, color palettes, and conditional formatting rules
• Drill paths, hierarchies, custom groups, alerts, schedules, and variables
• Folders, whose structure of levels and reports is preserved during deployment

A version captures the same content that is deployed.

2. Creating a Deployment Flow

You create a flow using a two step wizard. Step 1 collects the deployment flow details and defines its stages. Step 2 assigns a workspace to each stage.

Follow the below steps to open the wizard:

1. Navigate to Deployment Management from Data Administration under Organization Settings.
2. Click Create Deployment Flow.

Step 1: Flow Details and Stages

In the New Deployment Flow dialog that opens, enter the Flow Name and Description (optional). The dialog displays a set of stages, ordered one below the other.

1. Enter the Stage Name in the respective fields.
2. Click Add Stage to add a new stage. Each new stage is added to the end of the list.
3. To remove a stage you added in the current session, click the Delete icon next to it.
4. Click Next to continue.

Step 2: Assign Workspaces

In the next step of the wizard, assign a workspace to each stage.

1. For the first stage, select an existing workspace or create a new workspace from the organization where the flow is being created.
2. For the subsequent stages, either create a new workspace or select an existing workspace within your organization or another organization where you are an admin.
3. To reassign a stage, click Change Workspace and select again.
4. When you assign workspaces, Zoho Analytics runs a compatibility check between them. If the workspaces pass the check, click Next. If a workspace does not pass, reassign that stage before you proceed.
5. Review each stage along with its assigned workspace and click Create to finalize.

3. Deploying Changes

Deploying promotes the views from one stage to the next stage in the flow. The Flow page lists each stage as a separate card in an ordered pattern. You can review the changes across any stage before starting a deployment.

Each stage card shows the assigned workspace and a set of tabs. The tabs available depend on the stage's position in the flow:

• Changes lists the differences to be deployed, shown as added, modified, and deleted items, with the count in brackets. For the first stage, this tab lists the modifications made in that workspace. For the downstream stages, it compares the stage against its source stage.
• History lists all the deployments made from that stage to the next stage, so you can trace what was promoted over time. Each entry shows the user who deployed, the number of views deployed, the date and time, and the deployment notes.
• Versions lists the versions saved for the stage after each successful deployment. Refer to Restoring a Previous Version.

Deploying to the Next Stage

Follow the below steps to deploy the analytics content from one stage to the next:

1. Click Deploy to {Stage Name} on the source stage, such as Deploy to QA Testing.
2. In the Confirm Deployment dialog that opens, review the content that will be deployed.
3. Filter the items by Status to view New, Modified, or Failed items, and open the Views side panel to review the specific views involved.
4. Add Notes (optional) to describe the deployment, then confirm.

[GIF placeholder: deploy-to-next-stage.gif] Deploying from one stage to the next: clicking Deploy to {Stage Name}, filtering by Status in the Confirm Deployment dialog, adding notes, and confirming.

Tracking the Deployment Progress

Once you click Deploy, the deployment begins and its progress is shown on the Flow page.

• An In Progress indicator appears between the two stages while the deployment runs.
• When the deployment completes successfully, the indicator changes to a tick mark, and you receive a notification confirming the result. A new version is added to the Versions tab of the target stage.
• Click the success indicator between the stages to open the deployment details and see exactly what changes moved from one stage to the next.

Empty States

• When a stage has no changes to show, it displays Nothing Found.
• The Production stage displays Awaiting first deployment until it receives content for the first time.
• The Versions tab stays empty until the stage receives its first successful deployment.

4. Restoring a Previous Version

Every successful deployment to a stage is saved as a version. If a deployment does not work as expected, you can restore the stage to an earlier version.

Restoring a Stage

Follow the below steps to restore a stage to a previous version:

1. Open the required flow.
2. On the card of the stage you want to restore, click the Versions tab. Each version shows its number, such as Version 1, and the date and time it was saved.
3. Click Restore below the required version.
4. Confirm the restore in the dialog that opens.

The stage's views return to the state saved in the selected version. Views that were changed or removed since that version are restored, and views that were added after it are deleted. Other stages are not affected, and newer versions remain in the list.

Reviewing a Restore

Each restore is recorded in the Activity History of the stage, such as Activity History - Production. The panel shows the Target Workspace and groups the affected views by action:

• Restored lists the views brought back to their state in the selected version.
• Deleted lists the views removed because they were not part of the selected version.

Each view shows the user who performed the action and the date and time, such as Restored by Zylker on 26 October, 2026 05:17:05 AM PDT. Use Search Views to find a view by name, or filter the list by view type, such as charts, pivot tables, or dashboards.

5. Managing Deployment Flows

The Deployment Management home page lists all the flows you have created. Each flow is shown as a card so that you can see its structure and status at a glance.

Each flow card displays the following:

• Flow Name and Description, a one line summary of the flow's purpose.
• Flow Progress, a horizontal stage timeline that shows the stages in the flow and where changes were last deployed.
• More Actions, a menu to Edit, Duplicate, or Delete the flow.

Managing Stages

After a flow is created, you can update a stage's details, change the workspace mapped to it, and manage its connections and users.

Open the deployment flow you want to update. On the Flow page, click the More icon on a stage card to access Edit Stage Details, Manage Connections, and Access Controls.

Edit Stage Details

In the Edit Stage Details dialog, click Change Workspace to reassign the workspace mapped to that stage. The stage card updates to reflect the new workspace. You then set up its data sources, and the compatibility checks run again.

Manage Connections

Click Manage Connections to open the Data Sources page of the workspace assigned to that stage, where you can review and reauthenticate its connections.

Access Controls

Click Access Controls to manage the users of the assigned workspace. You are redirected to the Manage Users page in Workspace Settings.

6. Activity History

The Activity History gives you a complete record of everything that has happened in a deployment flow, such as flow creation, workspace mapping, data source changes, deployments, rollbacks, and deletions. On the Flow page, click the History icon in the top right corner to view all the activities in that flow.

Each entry in the Activity History includes the following:

• Date and Time of the action
• Stage on which the action was performed
• Performed By, the user who carried out the action
• Notes added with the action, such as a deployment comment
• Changes / Activities, shown as color coded badges, where green indicates added items and red indicates deleted items

Click a change count to see the specific views that were added or removed, and filter the list by Action to focus on a particular type of activity. For example, select Rollback to see only the versions that were restored.

The details of a deployment or restore on a stage open in the Activity History panel for that stage, where the affected views are grouped by action, such as Restored and Deleted. You can search the views by name and filter them by view type. Refer to Reviewing a Restore.

7. Data Source Behavior

As content moves between stages, Zoho Analytics applies a few rules to keep your data sources connected correctly.

• Compatibility: The source and target workspaces must use the same data source with similar tables. You can use multiple data sources in the first stage, but the downstream stages must use a single source type to prevent deployment conflicts.
• Duplicate table names: If two sources have tables with the same name, such as Accounts from CRM and Accounts from Books, the second table is given a suffix such as Accounts (Books). Connections are matched using stable internal identifiers, so your reports are never broken.
• Source types: Local drive uploads copy metadata only, and you can refresh the data using the import into table option. Feeds, databases, and data lakes can use a new or the same connection. Connector sources cannot be changed.
• Restoring versions: Restoring a stage to a previous version restores content only. The connections and data sources of the stage's workspace are not changed.

8. Frequently Asked Questions

1. Does deploying or restoring a version overwrite my data?

No. Deployments and restores work only on metadata, which is the definition of your views and reports. The underlying data in the workspace is not moved or overwritten. Deploying replaces existing view definitions in the target stage with those from the source stage, and restoring returns them to the definitions saved in the selected version. Views added after that version are deleted.

2. Who can create deployment flows, deploy content, and restore versions?

Only the Account Administrator and Organization Administrators can create flows, edit them, deploy content, and restore versions.

3. Can I undo a deployment?

Yes. Every successful deployment saves a version of the target stage. To undo a deployment, open the stage's Versions tab and click Restore on the version before it. Refer to Restoring a Previous Version.

4. Why does the first stage not have a Versions tab?

Versions are saved when content is deployed into a stage. The first stage is where content is created, and nothing is deployed into it, so it has no versions.

5. Does restoring a version affect other stages?

No. A restore applies only to the selected stage. Other stages keep their current content. To restore more than one stage, restore each stage separately.

6. Can I return to a newer version after restoring an older one?

Yes. Newer versions remain in the stage's Versions tab after a restore. Click Restore on the newer version to return to it.

7. How many stages can a flow have?

A flow can have a minimum of two stages and a maximum of ten stages. The first and last stages cannot be deleted.

8. What happens if the compatibility check fails?

You are prompted to reassign that stage. Confirm that the same data source is used and that the tables are similar to the other workspaces in the flow, then try again.

9. Can I change a stage's workspace after creating the flow?

Yes. Change a stage's workspace from its More menu. Reassigning a workspace requires setting up its data sources again, and the compatibility checks run again. The stage's versions start again from the next deployment.

10. Can I deploy to a workspace on a free plan?

Yes. If the flow creator is on a paid plan, you can push views and reports to a target workspace on a free plan, subject to that plan's limits. Data sources that use business application connectors are not supported on free plans and show Not supported on Free plan. To deploy them, move the target workspace to a supported plan, or use a data source that the free plan supports.

11. How do I duplicate or delete a deployment flow?

To duplicate a flow, select Duplicate from the flow card's More menu. The duplicate opens with the name, description, and stages carried over from the original, which you can customize before saving. To delete a flow, select Delete from the same menu. Deleting removes only the flow configuration and its versions. The workspaces and their content are not deleted, and the Deployment Management badges are removed from the associated workspaces.