> 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/partner-specialty-content.md).

# Partner Specialty Content

Content that exists only for partners — pre-sales and deal-support material, plus the speciality courses partners most often ask about.

Most of what partners need is the same as what customers need, which is why partner engineers are pointed at the same learning paths as everyone else. This page is for the small amount that is partner-specific.

***

### Pre-sales and deal support

{% hint style="info" icon="compass-drafting" %}
**For Solution Architects and pre-sales leads.** Material aimed at the bid and scoping stage rather than the build — reference architectures, sizing guidance, and how to position Pentaho against the alternatives a customer is likely to be comparing.

*Placeholder — this section is populated once the Solution Architect Practitioner level is scoped. Until then, the Solution Architect Level 3 and Containers speciality below are the closest available content.*
{% endhint %}

***

### Speciality courses partners ask about

These are standalone courses from the open catalogue, not partner-exclusive — listed here because they come up most often in partner delivery work.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-box" style="color:blue;">:box:</i> <strong>Containers</strong></td><td>Containerised Pentaho Server deployment end to end — build the EE image, Podman Compose, K3s, Helm, production HA. 15 lessons, 7 modules.</td><td><a href="https://academy.pentaho.com/solution-architect-path-sandbox/speciality-courses/containers">https://academy.pentaho.com/solution-architect-path-sandbox/speciality-courses/containers</a></td></tr><tr><td><i class="fa-key" style="color:blue;">:key:</i> <strong>Integrating Authentication Mechanisms</strong></td><td>SAML, OIDC/Keycloak and Kerberos/IWA for Pentaho Server — the non-directory authentication customers ask partners to set up. 12 lessons, 3 modules.</td><td><a href="https://academy.pentaho.com/administrator-path-sandbox/speciality-courses/integrating-authentication-mechanisms">https://academy.pentaho.com/administrator-path-sandbox/speciality-courses/integrating-authentication-mechanisms</a></td></tr><tr><td><i class="fa-robot" style="color:blue;">:robot:</i> <strong>AI Pipelines</strong></td><td>Integrating inference into PDI pipelines and building AI agents. Part of the PDI Developer speciality tier.</td><td><a href="https://academy.pentaho.com/pdi-developer-path-sandbox/speciality-courses/ai-pipelines">https://academy.pentaho.com/pdi-developer-path-sandbox/speciality-courses/ai-pipelines</a></td></tr></tbody></table>

***

### Suggest content

If there is something partners keep needing on customer projects that the Academy doesn't cover, tell us — that is exactly what this page is for.

<a href="mailto:academy@pentaho.com?subject=Partner%20specialty%20content%20suggestion" class="button primary" data-icon="envelope">Suggest partner content</a>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.pentaho.com/partner-enablement-sandbox/partner-specialty-content.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.