Organization oversight
Aggregate JIS across every operator in your deployment.
One dashboard call returns the health of human oversight across your whole deployment.
What this is
GET /v1/organization/dashboard returns org-level aggregates: mean and median JIS, band distribution, operators below compliance threshold, per-domain rollups, and a compliance status flag.
When to use
- Compliance officer’s Monday review.
- Executive dashboard tile.
- Quarterly board-reporting feed.
Fetch the dashboard
Python
dash = client.organization_dashboard()
print(dash.organization.name, dash.tier)
print("Mean JIS:", dash.dashboard.mean_jis)
print("Operators at risk (<60):", dash.dashboard.at_risk_count)
print("Compliance status:", dash.dashboard.compliance_status)
TypeScript
const dash = await client.organizationDashboard();
console.log(dash.dashboard.mean_jis, dash.dashboard.compliance_status);
cURL
curl https://api.cohesionauth.com/v1/organization/dashboard \
-H "X-API-Key: $COHESION_API_KEY"
Compliance threshold
An organization cannot claim EU AI Act Article 14 compliance if:
- more than 10% of operators in high-risk oversight roles have JIS
< 60, or - any operator in a critical-decision role has JIS
< 40.
The dashboard response surfaces this as compliance_status: "compliant" | "at_risk" | "non_compliant".
Per-domain rollup
Healthcare, aviation, financial services, legal, pharmaceutical, and critical infrastructure each have different decay parameters. The dashboard reports per-domain mean JIS and at-risk counts so you can see where maintenance is needed first.
Errors you might see
| Status | Meaning | Fix |
|---|---|---|
401 | Bad key | See authentication |
429 | Rate limit | See rate limits |
Next step
- Produce the regulator-facing report: generate compliance proof
- Intervene on low-scoring operators: maintain judgment quality
- Full endpoint: GET /v1/organization/dashboard