> For the complete documentation index, see [llms.txt](https://help.resouris.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.resouris.com/for-clinical-staff/worker-team-structure.md). # Your team structure Practical walk-through of the v1.7.3 P38 Cohort C worker Team-structure view at `/ui/my-resouris/team-structure`. One audience: * **Workers** (any user linked to a `staff` record with the `my_rostaire.org_chart.read` permission) — read-only view of the reporting-structure org chart. Focus defaults to you; navigate up/across via the fan-out links; time-travel via preset chips or a custom date. Requires the `my_rostaire.org_chart.read` permission (held by `staff_member` + `roster_user` by default; role-permission mappings finalise at Phase-6 RBAC UI). This view is **read-only** — to change any reporting relationship, ask your roster area admin. *** ## What this view shows * **Your own node** carries a **You** pill so you can locate yourself at a glance. * **Your direct reports** (if any) render as children under you. * **Additional managers** — if someone reports to you *and* to other managers (shared-role pattern like clinical + educational supervisor), the `[+N]` badge next to their name opens a fan-list of those extra managers. Click any to re-focus the chart on them. * **Re-focus** — click the `→` arrow next to any name to re-root the chart on that person; this lets you navigate up (to your manager, or to your manager's manager) or across (to a peer's team). * **"Return to your own team"** — visible after any re-focus; one click resets to your own node. ## Time-travel The **Chart date** ribbon at the top has preset chips + a custom date picker: * **Today** — the current reporting structure. Default. * **1 month ago / 6 months ago / 1 year ago** — jump to that date. The chart re-renders as it stood then. * **Custom date** — pick any past date via the date picker + click **Go**. Historical mode is **READ-ONLY by design** — no edit affordances would render even if you had them (workers have none anyway). Legitimate use cases: * "Who was my manager when the incident occurred?" — pick the incident date; the chart shows the manager of record. * "Who was on my team when I did the training three months ago?" — pick a date three months back; the chart shows the team as it stood then. * "When did Steven take over as the department lead?" — step through preset chips backwards until his node stops being your manager. ## Shared reporting If you or a colleague reports to **more than one** manager (a v1.7.3 feature), the `[+N]` badge lists the extra managers. One of them may be marked with a `*` — that's the **primary** manager (the canonical signer for leave / appraisal / equivalent HR flows). If you're not sure who your primary is, ask your roster area admin. ## What this view does *not* show * **Assignments / rosters** — this view is about *reporting structure*, not who's rostered onto which slot. For your roster, see [Getting started → My ReSouris](/start-here/getting-started.md#if-you-are-a-worker). * **Extended-leave / sickness / working patterns** — these are workforce-lifecycle events. Your admin can see them via the Staff-edit page; you see the effects (your own leave/sickness) via **My ReSouris → My roster** and **Submit a leave request**. * **Edit affordances** — there are none for workers. If you spot something wrong (missing manager, wrong primary), ask your roster area admin to fix via the [reporting-structure tool](/manage-people/reporting-structure-tool.md). ## Under the hood * **Storage**: MIG-171 `staff_line_management` (v1.6.8 P33) spells + v1.7.3 P38 MIG-184 (drops one-manager EXCLUDE) + MIG-185 (`is_primary` boolean). * **Tenant isolation**: standard `tenant_isolation` RLS policy on `staff_line_management`. * **Perm gate**: `my_rostaire.org_chart.read`. Held by `staff_member` + `roster_user` by default; role-permission mappings finalise at Phase-6 RBAC UI. * **Historical query**: `WHERE effective_from <= as_of AND (effective_until IS NULL OR effective_until > as_of)`. Daily resolution (§0.S5). * **No audit event on read** — viewing the org chart is not audited (§0.S6 rationale: legitimate discovery use; the info is discoverable through other channels anyway). --- # 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://help.resouris.com/for-clinical-staff/worker-team-structure.md?ask=&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.