---
title: "Get Control Plane Relationships"
method: GET
path: "/control-plane/relationships"
---

# Get Control Plane Relationships

`GET /control-plane/relationships`

## Request

- Base URL: `https://usemeridian.us` (the document declares no server; this is the origin it was published from)
- URL: `https://usemeridian.us/control-plane/relationships`
- Auth: none declared

Permission-aware workspace -> project -> one-level-subproject tree.

Returns exactly the projects ``GET /projects`` would show this caller
(same scoping helper, same tenant-isolated db connection), annotated with
an explicit ``relationship_scope`` label per row and an overall
``scope`` label ("workspace" for an owner/workspace-wide member, "project"
for a project-scoped member) so the UI never has to guess what it is
looking at. Nesting subprojects under their parent is left to the
dashboard's existing, already-unit-tested ``flattenHierarchy`` helper
(``dashboard-subprojects.ts``) — deliberately not re-implemented here,
per the design note's reuse recommendation.

## Response `200`

Successful Response

- object

---

[API](https://skmtc.dev/usemeridian/apis/meridian.md) · [All operations](https://skmtc.dev/usemeridian/apis/meridian/llms.txt) · [OpenAPI document](https://skmtc.dev/usemeridian/apis/meridian/revisions/f37a894bd374?raw)