> 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/your-organisations-standing.md).

# Your Organisation's Standing

What your Partner Account Manager and training coordinator can see about certified headcount, and how it maps to partner status.

Under the previous programme nobody could see, by organisation, who had completed what. This page describes what is visible now, and to whom.

***

### What is reported

For each partner organisation, the Academy tracks:

<table><thead><tr><th width="300">Measure</th><th>What it tells you</th></tr></thead><tbody><tr><td><strong>Practitioner-certified headcount, by role</strong></td><td>The compliance number. How many of your engineers currently hold a valid Practitioner credential for PDI Developer, Administrator and Solution Architect.</td></tr><tr><td><strong>Credentials expiring in the next 6 months</strong></td><td>Practitioner is valid for two years. This flags who needs to recertify before your headcount drops.</td></tr><tr><td><strong>In progress</strong></td><td>Engineers who have redeemed a voucher but not yet passed — useful for spotting who has stalled.</td></tr><tr><td><strong>Gone further</strong></td><td>Staff who have voluntarily earned Associate or Certified Professional. Counts toward your certified headcount; never required.</td></tr><tr><td><strong>Seat-pool utilisation</strong></td><td>Vouchers issued against vouchers used, so you know whether to top up or whether seats are sitting idle.</td></tr></tbody></table>

***

### Your certified staff — live view

{% hint style="warning" icon="flask" %}
**Preview with dummy data.** The tabs below simulate the filtered view a partner will see once the reporting dashboard is live. Names, dates and scores are invented; the organisations are fictional. In production this is a single embedded dashboard, filtered to your organisation by the Partner ID in your signed link — not a tab picker.
{% endhint %}

{% tabs %}
{% tab title="PE-10421 · Northwind Data Services" %}
**Partner ID: PE-10421** · Practitioner-certified: **4** · In progress: **1** · Expiring within 6 months: **1**

<table><thead><tr><th width="180">Engineer</th><th width="150">Role</th><th width="120">Exam date</th><th width="90">Score</th><th width="90">Pass mark</th><th width="130">Valid until</th><th>Status</th></tr></thead><tbody><tr><td>A. Okafor</td><td>PDI Developer</td><td>14 Apr 2027</td><td>88%</td><td>70%</td><td>14 Apr 2029</td><td>✅ Certified</td></tr><tr><td>L. Brennan</td><td>PDI Developer</td><td>02 Jun 2027</td><td>76%</td><td>70%</td><td>02 Jun 2029</td><td>✅ Certified</td></tr><tr><td>M. Sato</td><td>Administrator</td><td>21 Jul 2027</td><td>91%</td><td>70%</td><td>21 Jul 2029</td><td>✅ Certified</td></tr><tr><td>R. Delgado</td><td>PDI Developer</td><td>09 Mar 2026</td><td>72%</td><td>70%</td><td>09 Mar 2028</td><td>⚠️ Expiring soon</td></tr><tr><td>P. Nkemelu</td><td>Administrator</td><td>—</td><td>—</td><td>70%</td><td>—</td><td>🔄 In progress</td></tr></tbody></table>
{% endtab %}

{% tab title="PE-10877 · Helix Analytics" %}
**Partner ID: PE-10877** · Practitioner-certified: **2** · In progress: **2** · Expiring within 6 months: **0**

<table><thead><tr><th width="180">Engineer</th><th width="150">Role</th><th width="120">Exam date</th><th width="90">Score</th><th width="90">Pass mark</th><th width="130">Valid until</th><th>Status</th></tr></thead><tbody><tr><td>S. Varga</td><td>PDI Developer</td><td>30 May 2027</td><td>83%</td><td>70%</td><td>30 May 2029</td><td>✅ Certified</td></tr><tr><td>D. Whitfield</td><td>Administrator</td><td>18 Aug 2027</td><td>79%</td><td>70%</td><td>18 Aug 2029</td><td>✅ Certified</td></tr><tr><td>C. Almeida</td><td>PDI Developer</td><td>—</td><td>—</td><td>70%</td><td>—</td><td>🔄 In progress</td></tr><tr><td>J. Lindqvist</td><td>Solution Architect</td><td>—</td><td>—</td><td>70%</td><td>—</td><td>🔄 Awaiting SA Practitioner</td></tr></tbody></table>
{% endtab %}

{% tab title="PE-11203 · Meridian Systems" %}
**Partner ID: PE-11203** · Practitioner-certified: **3** · In progress: **0** · Expiring within 6 months: **2**

<table><thead><tr><th width="180">Engineer</th><th width="150">Role</th><th width="120">Exam date</th><th width="90">Score</th><th width="90">Pass mark</th><th width="130">Valid until</th><th>Status</th></tr></thead><tbody><tr><td>T. Marchetti</td><td>PDI Developer</td><td>11 Feb 2026</td><td>94%</td><td>70%</td><td>11 Feb 2028</td><td>⚠️ Expiring soon</td></tr><tr><td>H. Kowalski</td><td>Administrator</td><td>27 Feb 2026</td><td>68%</td><td>70%</td><td>—</td><td>❌ Did not pass — retake</td></tr><tr><td>H. Kowalski</td><td>Administrator</td><td>15 Mar 2026</td><td>81%</td><td>70%</td><td>15 Mar 2028</td><td>⚠️ Expiring soon</td></tr><tr><td>E. Osei</td><td>PDI Developer</td><td>05 Sep 2027</td><td>77%</td><td>70%</td><td>05 Sep 2029</td><td>✅ Certified</td></tr></tbody></table>
{% endtab %}
{% endtabs %}

{% hint style="info" icon="code" %}
**Where the real dashboard goes.** This block is replaced by a signed Metabase embed filtered on Partner ID. The filter is locked into the signed URL each partner receives, so it cannot be edited client-side — a typed-in Partner ID alone is not access control for a table of named staff. Longer term, the Partner ID comes from login (authenticated access + adaptive content) and nothing is typed at all.

```markdown
{% embed url="https://metabase.<pentaho-host>/embed/dashboard/<signed-token>#bordered=false&titled=false" %}
```

{% endhint %}

***

### Who can see it

{% columns %}
{% column %}

#### <i class="fa-user-tie">:user-tie:</i> Your Partner Account Manager

Sees the full picture for your organisation and uses it for partner-tier reviews. This replaces the manual compliance tracking used under the previous programme.
{% endcolumn %}

{% column %}

#### <i class="fa-user-gear">:user-gear:</i> Your training coordinator

Once the seat-pool console is live, sees the same view for your own organisation, assigns vouchers from your pool, and can spot expiring credentials before they lapse.
{% endcolumn %}
{% endcolumns %}

{% hint style="info" icon="clock" %}
**Dashboard timing.** The partner-manager reporting dashboard is scheduled for the *Scale* quarter of the rollout (Q1 2028). Before then, your Partner Account Manager reports standing on request. This page will link to the dashboard when it is live.
{% endhint %}

***

### How standing maps to partner status

Practitioner-certified headcount is the input the Partner Programme uses for partner status. **The thresholds themselves — how many certified engineers, and whether they vary by partner tier — are set by the Partner Programme, not by the Academy,** and are being finalised alongside the commercial model.

{% hint style="warning" icon="circle-question" %}
**Placeholder.** Threshold table to be inserted once the Partner Programme confirms the certified-headcount requirement per tier. Until then, the requirement is simply that engineers in the three roles hold Practitioner.
{% endhint %}

### A note on "credential hoarding"

Certified headcount counts engineers who hold a credential. The Partner Programme is considering whether standing should also reflect whether those engineers are actually working on registered deals or deliveries — so that a credential earned to unlock a benefit is also a credential being used. If adopted, this page will say how that is measured. Nothing changes for you until then.

<a href="/partner-enablement-sandbox/beyond-practitioner.md" class="button secondary" data-icon="medal">Next: going beyond Practitioner</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/your-organisations-standing.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.