> 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 accredited headcount, and how it maps to partner status.

{% 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 %}

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>Baseline headcount, by role</strong></td><td>The compliance number. How many of your engineers currently hold their role's valid baseline course accreditation: Level 1 — Practitioner for PDI Developer, Business Analyst and Administrator. The Solution Architect and Solution Analyst paths are optional and not part of the baseline.</td></tr><tr><td><strong>Course accreditations expiring in the next 6 months</strong></td><td>Baseline course accreditations are valid for two years. This flags who needs to renew their accreditation 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 gone on to Associate, Certified, a Speciality course or the Solution Architect or Solution Analyst path. Counts toward your accredited 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>

```mermaid
%%{init: {"theme":"base","themeVariables":{"fontFamily":"Arial, Helvetica, sans-serif","fontSize":"13px","lineColor":"#64748b","primaryColor":"#dbeafe","primaryBorderColor":"#1d4ed8","primaryTextColor":"#1e3a8a","noteBkgColor":"#fef3c7","noteBorderColor":"#b45309","noteTextColor":"#78350f"}}}%%
stateDiagram-v2
  direction TB
  [*] --> Voucher_issued: a seat assigned&nbsp;&nbsp;&nbsp;&nbsp;
  Voucher_issued: Voucher issued&nbsp;&nbsp;&nbsp;&nbsp;
  In_progress: In progress&nbsp;&nbsp;&nbsp;
  Accredited: Accredited&nbsp;&nbsp;&nbsp;
  Expiring: Expiring within six months&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  Lapsed: Lapsed&nbsp;&nbsp;&nbsp;
  Gone_further: Gone further&nbsp;&nbsp;&nbsp;
  Voucher_issued --> In_progress: voucher redeemed, lab opened&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  In_progress --> Accredited: capstone done, exam passed&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  Accredited --> Expiring: eighteen months on&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  Expiring --> Accredited: renewed&nbsp;&nbsp;&nbsp;
  Expiring --> Lapsed: not renewed&nbsp;&nbsp;&nbsp;
  Lapsed --> Voucher_issued: a new seat&nbsp;&nbsp;&nbsp;
  Accredited --> Gone_further: Associate, Certified, a Speciality, or the Solution Architect or Solution Analyst path&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  note right of Voucher_issued: Seat-pool utilisation counts vouchers issued against vouchers used&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
  note right of Accredited: Baseline headcount by role counts these, and Gone further&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
```

<p align="center"><em>How one engineer moves between the measures above.</em></p>

***

### Your accredited 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.

* PE-10421 — Northwind Data Services
* PE-10877 — Helix Analytics
* PE-11203 — Meridian Systems
  {% endhint %}

{% @partner-compliance/partner-compliance %}

{% 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 course accreditations 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 (Q2 2027). 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

Baseline headcount is the input the Partner Programme uses for partner status. **The thresholds themselves — how many accredited 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 accredited-headcount requirement per tier. Until then, the requirement is simply that engineers in the three required roles hold their role's baseline course accreditation.
{% endhint %}

### A note on "accreditation hoarding"

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

<p align="center"><a href="https://academy.pentaho.com/partner-enablement-sandbox/moving-from-the-previous-programme.md" class="button primary" data-icon="arrow-right-arrow-left">Next: Moving From the Previous Programme</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/your-organisations-standing.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.
