ZenotiHelp

Configure Redshift data share access

ZTZenoti Docs Team Updated October 27, 2026 6 min readHow-to

This article explains the licensing requirements, cluster options, data scoping, and access provisioning process for Analytics β€” Redshift Data Share.

Note: For a conceptual overview of Analytics β€” Redshift Data Share, see Analytics β€” Redshift Data Share overview.

Before you begin

  • Your organization must have an active Analytics Plus license and the Redshift Data Share add-on enabled by Zenoti.
  • Redshift Data Share provisioning is performed by the Zenoti Implementation team. You cannot configure access through the Zenoti admin portal.
  • Have your intended data scope (organization, zone, or center level) identified before contacting the Zenoti Implementation team.

On this page


License requirements

Analytics β€” Redshift Data Share requires two licenses:

License Role
Analytics Plus Base license required for all analytics data warehouse functionality
Redshift Data Share add-on Paid add-on that enables direct SQL query access to the Redshift data warehouse

Both licenses must be active for your Redshift Data Share access to function. If either license lapses, your access will be suspended until the license is reinstated. Contact your Zenoti account representative to purchase or renew licenses.

Redshift Data Share vs S3 Data Share

Zenoti offers two data delivery mechanisms that consume the same underlying data warehouse. Both provide access to the same star schema β€” the same dimension tables, fact tables, and consolidated tables β€” but they differ in how you access the data.

Feature Redshift Data Share S3 Data Share
Access method SQL queries via any Redshift-compatible client Read CSV files from an S3 bucket
Cluster Shared or dedicated Redshift cluster N/A (data delivered to your own S3 bucket)
Real-time query Yes, within the data refresh latency window (approximately 1–2 hours) No β€” data is exported in batch cycles
Delivery format Live SQL query results CSV files organized by table and refresh cycle
Best suited for Ad-hoc analysis, BI tool connections, interactive dashboards Data pipeline ingestion, ETL into your own warehouse, archival

You can subscribe to both Redshift Data Share and S3 Data Share simultaneously if your organization needs both interactive query access and batch file delivery.

Cluster types

When your Redshift Data Share is provisioned, your organization is assigned to one of two cluster types:

Shared cluster

A shared cluster is a multi-tenant environment where multiple Zenoti customers share the same Redshift infrastructure. This is the default option and provides a cost-effective way to access the full star schema data warehouse.

Your data is isolated from other customers through scoping β€” you only see data for your own organization, zone, or center based on your configured scope level.

Dedicated cluster

A dedicated cluster is a single-tenant environment provisioned exclusively for your organization. Dedicated clusters provide isolated performance β€” your query workloads are not affected by other customers.

With a dedicated cluster, data is processed in parallel on both the shared and dedicated clusters. This means your dedicated cluster receives the same data at the same refresh cadence as the shared cluster, and the query experience on both cluster types is identical β€” same tables, same columns, same data. Your queries run in an isolated environment with no contention from other organizations.

Dedicated clusters are available for organizations with higher performance requirements. Contact the Zenoti Implementation team to discuss dedicated cluster options.

Data scoping configuration

When your Redshift Data Share subscription is provisioned, Zenoti configures the scope of data available in your data share. There are three scope levels, and each scope level creates its own separate data share endpoint with its own connection credentials:

Scope Description Endpoint
Organization All data across every center in your organization One endpoint covering the full organization
Zone Data for all centers belonging to a specific zone One endpoint per zone
Center Data for a single center One endpoint per center

If your organization needs access at multiple levels β€” for example, one organization-level endpoint and separate center-level endpoints for franchise owners β€” each is provisioned independently as a distinct data share endpoint.

How scoping works

Data is automatically partitioned according to your configured scope level. When you connect and run queries, you see only the data that falls within your scope β€” no additional filtering is required on your part.

Organization-level subscriptions receive the complete dataset β€” all centers, all transactions, and all reference data for your organization.

Zone-level and center-level subscriptions receive transaction and operational data filtered to the centers in that zone or center. In addition, these endpoints also include org-level reference dimension tables that contain shared configuration data (such as campaigns, product and service categories, discounts, and custom form definitions). These shared reference tables are included so that your scoped data can be correctly joined to org-level reference records without needing a separate organization-level subscription.

Example: A franchise organization with 12 centers across two zones provisions one organization-level endpoint for the corporate analytics team, one zone-level endpoint for each regional manager, and one center-level endpoint for each individual center owner. Each endpoint is provisioned independently and provides credentials scoped to the appropriate level of data.

Requesting access

Redshift Data Share access is provisioned by the Zenoti Implementation team. You cannot configure access yourself through the Zenoti admin portal.

To get started:

  1. Contact your Zenoti Implementation team or account representative to request Redshift Data Share access.
  2. Confirm your intended data scope β€” organization, zone, or center level β€” and whether you need multiple endpoints.
  3. Zenoti provisions your cluster access β€” the Implementation team configures your data share, including your scope level and cluster assignment (shared or dedicated).
  4. Zenoti provides the Redshift cluster endpoint, port, database name, username, and password you need to connect.
  5. Once provisioned, the system populates the data warehouse with your complete historical data. This may take some time depending on your organization's data volume.
  6. After the full load completes, incremental data refreshes run automatically approximately every 1–2 hours. You do not need to take any action to start or schedule data refreshes.

Changing your access configuration

To change the scope of an existing subscription, add a new scope level, or request a dedicated cluster, contact the Zenoti Implementation team. Access configuration changes cannot be made through the Zenoti admin portal.

Tips

  • Plan your scope before requesting provisioning. Changing your scope level after provisioning requires the Zenoti Implementation team to re-provision your endpoint and issue new credentials. Identify whether you need organization-, zone-, or center-level access β€” or a combination β€” before your initial request.
  • Request multiple endpoints in a single provisioning request. If your organization needs endpoints at more than one scope level, submit all requests together. Each endpoint is provisioned independently, so providing the full list upfront reduces turnaround time.
  • Store your credentials securely before connecting your BI tool. Zenoti provides your cluster endpoint, port, database name, username, and password at provisioning time. Save these to your organization's credential store immediately β€” if you need them re-issued later, you must contact the Zenoti Implementation team.

Troubleshooting

  • Connection refused or credentials rejected after provisioning. Verify that the endpoint address, port, database name, username, and password exactly match the credentials Zenoti provided. Credentials are case-sensitive. If the values are correct and the connection still fails, contact the Zenoti Implementation team β€” your cluster access may not yet be fully active.
  • Queries return no rows, but data is expected. The initial full load may still be in progress. Allow additional time after provisioning before assuming data is missing. If the issue persists after several hours, contact the Zenoti Implementation team to confirm that the full load completed successfully.
  • Data appears to be older than expected. Data refreshes run approximately every 1–2 hours. If your data is more than a few hours out of date, check whether a longer refresh delay is expected for your data volume. If the gap extends beyond 6 hours, contact the Zenoti Implementation team to investigate.
Was this article helpful?
Your feedback helps us improve our documentation.