> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/solution-analyst-path-sandbox/speciality-courses/multi-tenant-analytics.md).

# Multi-tenant Analytics

Coming soon — Serve many customers or business units from one set of cubes and domains: row-level isolation, content and access per tenant, branding, and isolation proven with test users.

{% hint style="warning" icon="eye" %}
**SANDBOX — draft page.** **🚧 In development — coming soon.** This Speciality is still being written. The outline below comes from the draft course `analyst-tenant-specialty` in Pentaho Content Manager: module and lesson names, kinds and estimated times are taken from its lab manifests, and may change before release. The labs have not yet been tested on a lab server. Items marked REPLACE-ME need an owner's confirmation.
{% endhint %}

Serve many customers or business units from one set of cubes and domains: row-level isolation with a Dynamic Schema Processor and metadata security, content and access per tenant, tenant branding, and isolation proven with test users.

{% columns %}
{% column %}

<p align="center"><i class="fa-file-lines" style="color:green;">:file-lines:</i><br><strong>11 lessons</strong><br><em>across 5 modules</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-flask" style="color:orange;">:flask:</i><br><strong>6 workshops</strong><br><em>hands-on labs</em></p>
{% endcolumn %}

{% column %}

<p align="center"><i class="fa-clock" style="color:cyan;">:clock:</i><br><strong>~8h 40m</strong><br><em>estimated</em></p>
{% endcolumn %}
{% endcolumns %}

{% hint style="success" icon="cloud-arrow-up" %}
Every workshop will be hands-on, on a Windows lab machine with the Lab Guide embedded. REPLACE-ME — confirm the hosted lab for this Speciality.
{% endhint %}

***

<h3 align="center">Before you start</h3>

{% columns %}
{% column %}
{% hint style="success" icon="circle-check" %}
**What you'll need**

Schema Workbench and Metadata Editor, including their data-security lessons, and day-to-day administration of users, roles and folders in the User Console. The Dynamic Schema Processor workshop compiles a small Java class.
{% endhint %}
{% endcolumn %}

{% column %}
{% hint style="info" icon="tag" %}
**Built against**

Pentaho Enterprise Edition **11.0.0.0-232**, the build every course on the Academy runs, on a Windows lab machine.
{% endhint %}
{% endcolumn %}
{% endcolumns %}

***

{% hint style="info" icon="trophy" %}

#### What you'll build

One Pentaho Server serving three tenants — EMEA, North America and APAC — from one Steel Wheels cube and one metadata domain: a Dynamic Schema Processor and metadata constraints that filter rows per tenant, a folder, role set and theme per tenant, and a test plan that proves no tenant sees another's data. The capstone does it again: three tenants on one platform.
{% endhint %}

***

<h3 align="center">Course outline</h3>

<p align="center"><i class="fa-file-lines" style="color:green;">:file-lines:</i> reading · <i class="fa-flask" style="color:orange;">:flask:</i> hands-on workshop</p>

{% hint style="info" icon="circle-info" %}
This is the draft outline. Times are the lab guides' own estimates, and the course is not yet open for enrolment.
{% endhint %}

<table data-search="false"><thead><tr><th width="382">Module</th><th width="115" align="center">Reading</th><th width="132" align="center">Workshops</th><th width="100" align="right">Time</th></tr></thead><tbody><tr><td>Getting Started</td><td align="center">2</td><td align="center">—</td><td align="right">~30m</td></tr><tr><td>Row-level Isolation</td><td align="center">1</td><td align="center">2</td><td align="right">~2h</td></tr><tr><td>Content and Access</td><td align="center">1</td><td align="center">2</td><td align="right">~1h 40m</td></tr><tr><td>Testing and Governance</td><td align="center">1</td><td align="center">1</td><td align="right">~1h</td></tr><tr><td>Capstone Project</td><td align="center">—</td><td align="center">1</td><td align="right">~3h 30m</td></tr><tr><td><strong>Total</strong></td><td align="center"><strong>5</strong></td><td align="center"><strong>6</strong></td><td align="right"><strong>~8h 40m</strong></td></tr></tbody></table>

{% stepper %}
{% step %}

### <i class="fa-rocket" style="color:blue;">:rocket:</i> Getting Started

`2 readings · ~30m`

How to get the most out of this guide, and the patterns Pentaho supports for serving more than one tenant.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2F6T3BPZ91WkACiCgxvvw0%2Ftenant-three-kinds.svg?alt=media" alt="The user emea_analyst, with the role Tenant EMEA or a tenant session variable, feeds three panels. Data: the TenantSales cube, where the DSP writes EMEA into the filters, and the TenantOrders domain, with a constraint per tenant role. Content: the EMEA folder, shared with Tenant EMEA; NA and APAC are not listed. User interface: the theme tenantemea. Isolated only when all three are in place."><figcaption><p>Three kinds of multi-tenancy: one tenant role drives the data, the content and the look, and a tenant is isolated only when all three are in place</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Before You Start</td><td>~15m</td></tr><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Multi-tenancy Patterns in Pentaho</td><td>~15m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-filter" style="color:blue;">:filter:</i> Row-level Isolation

`1 reading · 2 workshops · ~2h`

Give each tenant only its own rows: a Dynamic Schema Processor for the cubes and metadata security constraints for the domains.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FGzuYXxmugpaT9E6txonk%2Ftenant-filter-placement.svg?alt=media" alt="Three panels for an EMEA analyst. Dimension only: CUSTOMER_W_TER filtered, ORDERFACT not; Territory shows EMEA only, but the grand total, 10,645,949.18, is every territory&#x27;s and leaks. Fact only: ORDERFACT filtered by a subquery; the total is 5,008,224.32, but other territories stay in filter and prompt lists, so names leak. Both: both tables filtered, 5,008,224.32, isolated."><figcaption><p>Where the filter goes: only a filter on both the customer table and the fact table keeps EMEA's analyst to EMEA's rows and EMEA's names</p></figcaption></figure>

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FAIg5LnxHHLPWdxiXvPT4%2Ftenant-dsp-sequence.svg?alt=media" alt="A sequence across Analyzer as emea_analyst, the SteelWheelsTenant data source, Mondrian and TenantSchemaProcessor. 1, the schema holds TERRITORY = &#x27;%TENANT%&#x27;. 2, Analyzer opens TenantSales; the DynamicSchemaProcessor parameter names the class. 3, the processor reads the tenant session variable or the one tenant role and writes &#x27;EMEA&#x27;. 4, Mondrian filters every query. 5, one schema per tenant."><figcaption><p>How a Dynamic Schema Processor works: the class edits the schema text for each user, and Mondrian filters every query with the result</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Overview of Row-level Isolation</td><td>~15m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>A Dynamic Schema Processor per Tenant</td><td>~1h</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Metadata Security Constraints by Tenant</td><td>~45m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-folder-tree" style="color:blue;">:folder-tree:</i> Content and Access

`1 reading · 2 workshops · ~1h 40m`

Folders, roles and permissions per tenant, and each tenant's own look in the User Console.

<figure><img src="https://1021209504-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fu2m9COjKaS0E9nT7B9bQ%2Fuploads%2FzJBqf5t7xE0v2jOBTX1c%2Ftenant-folders.svg?alt=media" alt="Public, readable by Authenticated, passes its ACL down to Public, Tenants. Dashed arrows marked inheritance broken lead to the EMEA, NA and APAC tenant folders, each with inheritance cleared, Authenticated removed, its tenant role with Read and Write and Administrator with all. Under each, its own user, emea_analyst, na_analyst or apac_analyst, finds one folder."><figcaption><p>Tenant folders: Tenants inherits from Public, and each tenant folder stops inheriting and is shared with its own tenant role only</p></figcaption></figure>

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Overview of Content and Access</td><td>~15m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Folders, Roles and Permissions per Tenant</td><td>~40m</td></tr><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Tenant Branding</td><td>~45m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-clipboard-check" style="color:blue;">:clipboard-check:</i> Testing and Governance

`1 reading · 1 workshop · ~1h`

Prove the isolation with test users, and keep shared models in step as tenants are added.

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Prove Isolation with Test Users</td><td>~45m</td></tr><tr><td><i class="fa-file-lines" style="color:green;">:file-lines:</i></td><td>Governing Shared Models</td><td>~15m</td></tr></tbody></table>

</details>
{% endstep %}

{% step %}

### <i class="fa-trophy" style="color:blue;">:trophy:</i> Capstone Project

`1 workshop · ~3h 30m`

Three tenants on one platform: shared cubes and domains, each tenant seeing only its own rows, content and look.

<details>

<summary>See the full breakdown</summary>

<table data-search="false"><thead><tr><th width="79"></th><th>Lesson</th><th width="90">Time</th></tr></thead><tbody><tr><td><i class="fa-flask" style="color:orange;">:flask:</i></td><td>Capstone: Three Tenants, One Platform</td><td>~3h 30m</td></tr></tbody></table>

</details>
{% endstep %}
{% endstepper %}

***

{% hint style="info" icon="award" %}
**Optional, not part of the path**

Speciality courses are open to any learner who wants to go further. They are not among the five mandatory courses of the Certified Solution Analyst path. The course ends in a capstone project. REPLACE-ME — confirm whether it carries its own exam and course accreditation.
{% endhint %}

***

<p align="center"><a href="https://academy.pentaho.com/solution-analyst-path-sandbox/speciality-courses.md" class="button secondary" data-icon="arrow-left">Back to Speciality Courses</a></p>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.pentaho.com/solution-analyst-path-sandbox/speciality-courses/multi-tenant-analytics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
