Configure S3 data access
This article explains how data access is scoped in Analytics β Amazon S3, how to connect BI tools to your bucket, and what to do if you need to change your access configuration.
Before you begin
- Your organization must have an active Analytics Plus license and the S3 Data Share add-on.
- You must have received S3 bucket access credentials from the Zenoti Implementation team.
- Decide which BI tool or data warehouse you will use to consume the data.
Data scoping options
When your S3 Data Share subscription is provisioned, Zenoti configures the scope of data delivered to your bucket. There are three scope levels:
| Scope | Description |
|---|---|
| Organization | All data across every center in your organization |
| Zone | Data for all centers belonging to a specific zone |
| Center | Data for a single center |
Each scope level receives its own S3 bucket. If your organization has subscriptions at multiple levels (for example, one organization-level bucket and separate center-level buckets), each is provisioned independently.
How scoping affects the data in your bucket
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 data filtered to the centers in that zone or to the specific center. In addition, these buckets also include a copy of org-level reference tables that contain shared configuration data. These shared reference tables cover items such as campaigns, product and service categories, discounts, donations, and custom form definitions β data that is defined at the organization level but applies across centers.
The following dimension tables are replicated from the organization level into every zone-level and center-level bucket:
| Table | Description |
|---|---|
Bi_DimAgent |
Agent reference data |
Bi_DimCampaign |
Campaign definitions |
Bi_DimCategoryProducts |
Product-to-category mappings |
Bi_DimCategoryServices |
Service-to-category mappings |
Bi_DimCustomForms |
Custom form definitions |
Bi_DimDiscount |
Discount definitions |
Bi_DimDonations |
Donation type definitions |
These tables are included so that your center- or zone-level data can be correctly joined to org-level reference records without needing a separate org-level subscription.
Changing your data scope
Data scoping is configured during onboarding and cannot be changed through the Zenoti admin portal. To change the scope of an existing subscription β for example, to move from center-level to zone-level, or to add a new zone bucket β contact the Zenoti Implementation team.
S3 bucket credentials
Your S3 bucket and access credentials are provisioned by Zenoti as part of the onboarding process. Zenoti provides:
- The S3 bucket name and region.
- AWS access credentials for connecting to the bucket.
- The root folder path within the bucket.
Store these credentials securely. If you lose access or your credentials expire, contact the Zenoti Implementation team to have them reissued.
Important: Your S3 bucket is read-only. You can read data files and schema definitions from the bucket, but you cannot write data back to it. Any attempt to upload or modify files in the bucket will be rejected.
Connecting BI tools to your S3 bucket
Analytics β Amazon S3 delivers standard CSV files that are compatible with any tool or platform that can read from Amazon S3. Common integration patterns include:
Amazon Athena
Register your S3 bucket as an external data source in Athena using the schema definitions from the SchemaFull folder. Query your data directly in S3 using standard SQL without loading it into a separate database. Athena is a natural fit if your organization already uses the AWS ecosystem.
Snowflake
Use Snowflake's COPY INTO command or an external stage definition to load CSV files from your S3 bucket into Snowflake tables. The SchemaFull schema files define the column names and order needed to create matching table structures in Snowflake.
Databricks
Mount your S3 bucket as a Databricks file system path or use the spark.read.csv API to load files directly. Databricks Delta Lake workflows can ingest incremental GroupID folders as they appear.
Power BI
Connect Power BI to your S3 data by first loading it into an intermediate database (such as Snowflake, Amazon Redshift, or Azure SQL), then connecting Power BI to that database using its native connector. Direct S3-to-Power BI connections require an intermediary.
Tableau
Tableau connects to S3 data most effectively through an intermediary database. Alternatively, Tableau can read CSV files directly from S3 using the Amazon S3 connector available in Tableau Desktop.
General guidance
Regardless of which tool you use:
- Use the SchemaFull folder to understand column names and order for each table β CSV files do not include headers.
- Process GroupID folders in ascending numeric order to reconstruct the full dataset (full load in GroupID 1, then apply each incremental in sequence).
- Skip any folder ending in
_processingβ this suffix indicates a data refresh is still in progress. - Check the SchemaUpgrade folder after Zenoti platform releases to identify any schema changes before reloading data.