> 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/partner-enablement-sandbox/beyond-practitioner.md).

# Beyond Practitioner

Associate, Certified and Speciality courses are open to any partner engineer on the same terms as any other learner — optional, never required.

{% hint style="warning" icon="eye" %}
**SANDBOX — draft page.** A preview for review only. Nothing here is live. Role links point at the sandbox learning paths; pricing and the migration timeline are placeholders pending the commercial decisions in the Partner Enablement Programme proposal.
{% endhint %}

Your role's baseline is the requirement. Beyond it, any partner engineer can go on to any other course in the Academy — Level 2 — Associate, Level 3 — Certified, a Speciality course, or the Solution Architect and Solution Analyst paths — on the same terms as any other learner. None of it is required for partner compliance: the requirement is Level 1 — Practitioner for the PDI Developer, Business Analyst and Administrator roles, as [The Practitioner Requirement](https://academy.pentaho.com/partner-enablement-sandbox/the-practitioner-requirement.md) sets out.

***

### What is required and what is optional

<table><thead><tr><th width="300">Course</th><th>For partner staff</th></tr></thead><tbody><tr><td><i class="fa-seedling">:seedling:</i> <strong>Level 1 — Practitioner</strong></td><td><strong>Required</strong> for the PDI Developer, Business Analyst and Administrator roles. The partner compliance bar for those roles.</td></tr><tr><td><i class="fa-leaf-oak">:leaf-oak:</i> <strong>Level 2 — Associate</strong></td><td>Optional. Open to any engineer who wants it, individually. On the Business Analytics path, Level 2 is the four Analytics Developer courses.</td></tr><tr><td><i class="fa-tree-deciduous">:tree-deciduous:</i> <strong>Level 3 — Certified</strong></td><td>Optional. Open to everyone — customer, partner or independent — on identical terms.</td></tr><tr><td><i class="fa-sparkles">:sparkles:</i> <strong>Speciality courses</strong></td><td>Optional. Standalone courses such as Containers, High Availability and Enterprise Security, or the five analyst Specialities on the Business Analytics and Solution Analyst paths, open to any engineer on the same terms.</td></tr><tr><td><i class="fa-compass-drafting">:compass-drafting:</i> <strong>Solution Architect path</strong></td><td>Optional. For partners who wish to get Pentaho certified, and the PDI Developer's route beyond Practitioner. No levels: DI Developer, then Installation, then the Containers, High Availability and Enterprise Security Speciality courses, leading to the Certified Solution Architect certification.</td></tr><tr><td><i class="fa-magnifying-glass-chart">:magnifying-glass-chart:</i> <strong>Solution Analyst path</strong></td><td>Optional. For partners who wish to get Pentaho certified on the analytics side. No levels: Business Analyst, then the four Analytics Developer courses — Schema Workbench, Metadata Editor, Report Designer and CTools — leading to the Certified Solution Analyst certification.</td></tr></tbody></table>

What each path involves is set out on its own page: [PDI Developer](https://academy.pentaho.com/pdi-developer-path-sandbox/pdi-developer.md), [Business Analyst](https://academy.pentaho.com/business-analytics-path-sandbox/business-analytics.md), [Administrator](https://academy.pentaho.com/administrator-path-sandbox/administrator.md), [Solution Architect](https://academy.pentaho.com/solution-architect-path-sandbox/solution-architect.md) and [Solution Analyst](https://academy.pentaho.com/solution-analyst-path-sandbox/solution-analyst.md).

***

### How the paths run

The Administrator path is built in levels: Level 1 — Practitioner, Level 2 — Associate, then Level 3 — Certified. The Business Analytics path runs Level 1 — Practitioner, then Level 2 — Associate (the four Analytics Developer courses), with Level 3 — Certified coming soon. The two certification paths have no levels. The Solution Architect path, where a PDI Developer continues beyond Practitioner, is a set sequence of five courses — DI Developer, Installation, then three Speciality courses, Containers, High Availability and Enterprise Security — leading to the Certified Solution Architect certification. The Solution Analyst path is Business Analyst, then the four Analytics Developer courses.

```mermaid
%%{init: {"theme":"base","themeVariables":{"fontFamily":"Arial, Helvetica, sans-serif","fontSize":"13px","lineColor":"#64748b","clusterBkg":"#fafaf9","clusterBorder":"#d6d3d1","edgeLabelBackground":"#ffffff"},"flowchart":{"curve":"basis","nodeSpacing":28,"rankSpacing":44,"padding":22,"wrappingWidth":600,"htmlLabels":true}}}%%
flowchart LR
  classDef tool fill:#dbeafe,stroke:#1d4ed8,color:#1e3a8a,text-align:left,rx:6,ry:6
  classDef server fill:#ede9fe,stroke:#6d28d9,color:#3b0764,text-align:left,rx:6,ry:6
  classDef check fill:#fef3c7,stroke:#b45309,color:#78350f,text-align:left,rx:6,ry:6
  classDef off fill:#f5f5f4,stroke:#a8a29e,color:#78716c,text-align:left,rx:6,ry:6
  subgraph LV["Business Analyst · Administrator&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]
    direction TB
    L1["<b>Level 1 — Practitioner</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br/>required for partner compliance&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]:::check
    L2["<b>Level 2 — Associate</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br/>optional&nbsp;&nbsp;&nbsp;"]:::tool
    L3["<b>Level 3 — Certified</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br/>Administrator; Business Analytics coming soon&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]:::tool
    SPC["<b>Speciality courses</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br/>optional, standalone&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]:::off
    L1 --> L2 --> L3
    L1 -.-> SPC
  end
  subgraph SA["The Solution Architect path · no levels&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]
    direction TB
    S1["<b>DI Developer</b>&nbsp;&nbsp;&nbsp;&nbsp;<br/>the same course as PDI Developer, Level 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]:::server
    S2["<b>Installation</b>&nbsp;&nbsp;&nbsp;&nbsp;"]:::server
    S3["<b>Containers — Speciality</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]:::server
    S4["<b>High Availability — Speciality</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]:::server
    S5["<b>Enterprise Security — Speciality</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]:::server
    S6["<b>Certified Solution Architect</b>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br/>the certification&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"]:::check
    S1 --> S2 --> S3 --> S4 --> S5 --> S6
  end
```

<p align="center"><em>The Business Analyst and Administrator levels, and the Solution Architect path a PDI Developer continues on.</em></p>

***

### Certified: open to everyone

{% hint style="success" icon="unlock" %}
Level 3 and the certification paths are **not partner-gated and not partner-exclusive.** Any individual can pursue them through the standard catalogue — on the same terms, whether they work for a partner, a customer, or themselves. A partner engineer who completes one counts toward your organisation's accredited headcount, but it is never a precondition for compliance.
{% endhint %}

Where they already exist in the sandbox paths:

* [Administrator, Level 3 — Certified](https://academy.pentaho.com/administrator-path-sandbox/administrator/level-3-certified.md) — SSO, transport and data security, big-data security, peer-reviewed capstone and proctored exam.
* [Solution Architect, Installation](https://academy.pentaho.com/solution-architect-path-sandbox/solution-architect/installation.md) — where a PDI Developer continues after DI Developer: install the complete Pentaho platform end to end, then the Containers, High Availability and Enterprise Security Speciality courses.
* [Solution Analyst](https://academy.pentaho.com/solution-analyst-path-sandbox/solution-analyst.md) — Business Analyst, then the four Analytics Developer courses.

***

### Speciality courses

Speciality courses are standalone courses from the open catalogue, and they are part of going beyond Practitioner too. Containers, High Availability and Enterprise Security complete the Solution Architect path; Enterprise Security is Integrating Authentication Mechanisms, the same Speciality the Administrator path offers. Five analyst Specialities — Semantic Model Editor, Embedded Analytics, Analytics Performance, Multi-tenant Analytics and Preparing Data for Analytics — sit beside the Business Analytics and Solution Analyst paths, and are coming soon. Others, such as AI Pipelines, stand on their own. See [Partner Speciality Content](https://academy.pentaho.com/partner-enablement-sandbox/partner-speciality-content.md) for the ones partners most often ask about.

***

### Pricing for optional levels

{% hint style="warning" icon="circle-question" %}
**Placeholder.** The default position is that partner staff pay full catalogue price for Associate, Certified and the certification paths, the same as any learner. Whether a partner discount applies to them is one of the open commercial decisions. Your Partner Account Manager will confirm.
{% endhint %}

### Why go further?

Not for compliance — for the deal. Solution Architects are the people who most often win or lose a partner bid at the scoping stage, which is why the optional Solution Architect path runs from DI Developer and Installation through the Containers, High Availability and Enterprise Security Speciality courses to the Certified Solution Architect certification. Everything beyond the baseline is optional for a reason: the people who need it will know.

<p align="center"><a href="https://academy.pentaho.com/partner-enablement-sandbox/partner-speciality-content.md" class="button primary" data-icon="sparkles">Next: Partner Speciality Content</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/partner-enablement-sandbox/beyond-practitioner.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.
