> 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/how-enrolment-works.md).

# How Enrolment Works

Subscription, vouchers, hosted labs — the same mechanic customers use, arranged through your Partner Account Manager.

Partner Enablement uses exactly the same mechanic as the rest of the Academy: a subscription is arranged, each learner gets a voucher URL, the voucher opens a hosted lab. The only difference is who arranges it — your **Partner Account Manager**, not a customer Account Executive.

***

{% stepper %}
{% step %}
**Subscribe**

Your organisation takes out (or renews) an annual Partner Enablement subscription, sized to the number of engineers you need certified at Practitioner across PDI Developer, Administrator and Solution Architect.

Talk to your Partner Account Manager — they size it with you and place the order.
{% endstep %}

{% step %}
**Vouchers are issued**

Each named engineer receives a URL to the Academy hosting platform and a voucher code that unlocks the Practitioner course for their role. There is no separate partner login and no separate portal — it is the same platform every Academy learner uses.
{% endstep %}

{% step %}
**Open the lab**

Redeem the voucher and open the first lab. The environment is ready-made and hosted; the Lab Guide is embedded in the lab and starts automatically. Nothing to install, nothing to configure.
{% endstep %}

{% step %}
**Certify**

Work through the modules at whatever pace suits — pause and resume is fine. Complete the capstone, pass the open-book assessment, download the credential. Your organisation's certified headcount updates on [Your Organisation's Standing](/partner-enablement-sandbox/your-organisations-standing.md).
{% endstep %}
{% endstepper %}

***

### Adding people during the year

{% hint style="info" icon="user-plus" %}
**New hires and role changes.** The intent is that a new engineer joining your organisation lands in the Practitioner path for their role automatically, on a headcount change, rather than waiting for a coordinator to enrol them. Until the seat-pool console is live, tell your Partner Account Manager and a voucher will be issued.
{% endhint %}

### Who at your organisation manages this

Two people typically touch enrolment:

* **Your Partner Account Manager** at Pentaho — sizes the subscription, issues vouchers, and can see your organisation's standing.
* **Your own training coordinator** — once the seat-pool console is live, assigns vouchers to named staff from your pool without going back to Pentaho for each one.

***

### Pricing

{% hint style="warning" icon="circle-question" %}
**Placeholder.** Whether Practitioner seats are free to partners, a flat per-seat rate, or discounted by partner tier is being finalised as part of the Partner Enablement commercial decisions. Your Partner Account Manager will confirm pricing before you subscribe. This box is replaced with the published model once agreed.
{% endhint %}

<a href="mailto:academy@pentaho.com" class="button primary" data-icon="envelope">Ask about seat sizing</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/how-enrolment-works.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.