> 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-enablement.md).
# Partner Enablement
The single place for Pentaho partners to see what's required, get staff certified, and track where the organisation stands.
{% hint style="warning" %}
**๐งช SANDBOX โ proposed Partner Enablement space**
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 Program proposal.
{% endhint %}
One credential. Every partner engineer.
Pentaho partner compliance now means one thing: your implementation, platform and pre-sales staff each hold a hands-on Practitioner credential for their role. Not a video. Not a quiz. A real lab, a real capstone, a real credential they can put on a CV.
***
{% columns %}
{% column %}
#### :seedling: What's required
**Practitioner, and only Practitioner.**
Each partner engineer completes Level 1 โ Practitioner for the role they work in: PDI Developer, Administrator, or Solution Architect. About 13 hours, hosted lab included, open-book assessment, no proctoring. Nothing above Practitioner is required for partner compliance.
See the requirement by role
{% endcolumn %}
{% column %}
#### :medal: What's open to you
**Everything else in the Academy.**
Associate and Certified Professional are open to any partner engineer who wants to go further โ on the same terms as any other learner. They count toward your organisation's certified headcount, but they are never a condition of compliance, and can be taken individually at any time.
Going beyond Practitioner
{% endcolumn %}
{% endcolumns %}
***
The Practitioner requirement by role
Pick the role each engineer works in. Each card goes straight to the Level 1 โ Practitioner page in that role's learning path.
:arrow-progress:PDI Developer โ Practitioner
For partner implementation engineers. Build, schedule and operate PDI pipelines. 55 lessons, 7 modules, a capstone pipeline you build yourself.
{% hint style="info" icon="signs-post" %}
**Data Engineer and Analyst roles** join the partner requirement in Year Two, once those paths are built for the wider catalogue. Nothing is required for them yet.
{% endhint %}
***
### How it works
{% stepper %}
{% step %}
**Your organisation subscribes**
Partner Enablement is an annual subscription per partner organisation, arranged through your Partner Account Manager and sized to the number of engineers you need certified at Practitioner.
How enrolment works
{% endstep %}
{% step %}
**Each engineer receives a voucher URL**
Once the subscription is in place, every named engineer is sent a URL to our hosting platform and a voucher code that unlocks their role's Practitioner course. No separate login, no separate portal.
{% endstep %}
{% step %}
**Open the lab and start**
Redeem the voucher and open the first lab. The Lab Guide is embedded in the lab and starts automatically โ nothing to install, nothing to configure, no Pentaho environment of your own needed.
{% endstep %}
{% step %}
**Complete the capstone and open-book assessment**
Practitioner ends with a capstone project and an open-book assessment. On passing, the engineer downloads a credential valid for two years, and your organisation's certified headcount updates.
See your organisation's standing
{% endstep %}
{% endstepper %}
***
{% hint style="warning" icon="arrow-right-arrow-left" %}
#### Already compliant under the previous video-and-quiz programme?
You are still compliant today. The previous programme is being retired in stages through 2027, with a grace period and a lightweight bridge assessment so nobody is caught out. Read the migration page for what changes and when.
Moving from the previous programme
{% endhint %}
***
Also in this space
{% columns %}
{% column %}
**Your organisation's standing**
What your Partner Account Manager and your own training coordinator can see: certified headcount by role, who has gone on to Associate or Certified Professional, and how that maps to your partner status.
{% endcolumn %}
{% column %}
**Partner specialty content**
Content that exists only for partners โ starting with pre-sales and deal-support material for Solution Architects, plus the speciality courses partners most often ask about.
{% endcolumn %}
{% endcolumns %}
***
### Common questions
Is Practitioner really the only thing required?
Yes. Partner compliance is one credential per engineer, at Practitioner level, for the role they work in. Associate and Certified Professional exist in the catalogue and are open to anyone, including your staff, but they are optional โ never a precondition for a partner to be considered compliant.
What does it cost?
Partner Enablement is an annual subscription per organisation, arranged through your Partner Account Manager. Whether Practitioner seats are free to partners, flat-rate, or discounted by partner tier is currently being finalised โ your Partner Account Manager will confirm pricing before you subscribe. *(Placeholder โ see Commercial Decisions in the proposal.)*
Do my engineers need their own Pentaho environment?
No. Every Practitioner course runs in a hosted lab included with the voucher. The Lab Guide is embedded in the lab and starts automatically. If an engineer wants to install Pentaho locally for their own reasons, [Getting Started](https://academy.pentaho.com/getting-started/) walks through the options, but it is not needed for the course.
We hire new engineers during the year โ what happens to them?
Tell your Partner Account Manager, or use the seat-pool console once it's live, and the new hire is added to the Practitioner path for their role. The intent is for this to happen automatically on a headcount change rather than waiting for someone to remember.
How long is a Practitioner credential valid?
Two years, aligned to Pentaho major releases โ the same recertification cycle as the rest of the Academy catalogue.
I'm not sure which role an engineer maps to.
Most partner staff map cleanly: people who build pipelines are PDI Developers, people who run the platform are Administrators, people who scope and design the solution are Solution Architects. If someone is genuinely between two, read both Level 1 outlines or email us and we'll point you at the right one.
***
Still have questions?
{% columns %}
{% column %}
{% hint style="info" icon="gitbook-assistant" %}
**Quick answers about the content**
Press Ctrl + K and click **Ask** for an instant answer drawn from every page on this site.
{% endhint %}
{% endcolumn %}
{% column %}
{% hint style="info" icon="envelope" %}
**Talk to the Academy team**
For seat sizing, pricing, or anything partner-specific, email us โ we reply as soon as we can.
Email the Academy
{% endhint %}
{% endcolumn %}
{% endcolumns %}
---
# 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-enablement.md?ask=&goal=
```
`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.