Staging draft Work in progress · For review; coverage and acceptance incomplete

Explore your organization and review coverage¶

The Organogram describes how organizational units, positions and reporting relationships fit together. It helps employees find the relevant team, managers check responsibility and cover, and authorized administrators prepare changes. A position describes a seat in the organization; the person assigned to it can change over time.

Availability: These steps follow WorkOS 06 Final Screens. The inspected frontend is a preview with sample structures and assignments. Its success messages are simulated and do not prove a saved or published change. Confirm that your environment has a connected release before using its information for operational decisions. This guide covers browsing and risk review; detailed administration instructions are still being reconciled.

Understand the building blocks¶

Concept	What it means
Structure view	One named version of the organization. The current published view supplies live structure; drafts contain proposed arrangements.
Unit	A department, unit, division, directorate, team or branch. Units can have parent and child units.
Position	A named seat within a unit, linked to a reusable job title. It can have reporting relationships and a fallback position.
Job title	A reusable name and short code. Its label alone does not define seniority, a reporting line or product permissions.
Head position	The position designated to lead a unit. The current browsing rules also mark these positions as critical.
Primary holder	The person with a primary assignment effective at the time being viewed.
Acting cover	A separate, time-bound or open-ended acting assignment. Both a primary holder and an acting person can be recorded.
Co-occupant	An additional operational occupant. This assignment alone does not count as leadership cover in the browsing summary.
Fallback position	Another position that may supply cover when the seat has no current primary or acting assignment. A configured fallback does not prove that someone is available there.
Pooled queue	A shared work-routing destination. A position can belong to queues, but membership alone does not establish that it can receive or complete every item.

Organization structure and WorkOS roles serve different purposes. A management title or position does not grant every product permission. Changing a person's roles also does not change their unit, reporting line or assignment dates. See People and access for those distinctions.

Before you begin¶

Use the correct workspace and an account authorized for the information you need. Structure administration, assignment history and job titles have permission boundaries. Permission to view a structure does not automatically allow editing or publication. If access is restricted, ask your workspace administrator for the appropriate access; do not use another person's account.

For managers and executives, confirm the selected view's name, code and publication status before discussing staffing decisions. A draft represents a proposal. Sample numbers in the design and preview are examples, not a staffing report. Platform staff and support still need authorized access to a customer's workspace; this public guide grants none.

Open the correct structure¶

In WorkOS, open Operations under People & Governance.
Choose Organogram, then Structure views.
Identify the current published structure or the draft you intend to review. Check its name, code and status.
Choose Open structure for the published view or Open draft for a proposal.
Check the selected structure's heading again before drilling into a unit or position. Use Back to return through the journey.

The current catalogue combines the active published view with saved unpublished drafts. It is not a complete archive of every previously published structure. A missing catalogue item therefore does not, by itself, mean that its history was deleted. The inspected catalogue has no server-backed search, paging, bulk operations or comparison tool.

An empty result means no structure was returned for this catalogue. Authorized administrators can start with Create first draft or review job titles. A failed load and restricted access are different states; neither should be interpreted as an empty organization.

Explore units and positions¶

The intended selected-structure screen offers three presentation modes over the same structure:

Mode	How to use it
Hierarchy	Follow parent-child units. Expand the next level or collapse to the top. On narrower screens, scroll horizontally to follow deeper branches.
Positions	Review positions grouped by unit, including title, occupant or cover, reporting line and coverage. Expand branches and use Show more where rows are initially collapsed.
List	Review unit summaries and open a unit for detail. A visible-row count may describe only the portion currently shown.

Expanding a branch or switching modes changes what you see; it does not reorganize the company. Saved expansion preferences are not established by the current implementation.

Open a unit to review its parent, head position, immediate child units and positions. Open a position to review its job title, primary holder, acting cover, administrative manager, functional and advisory relationships, fallback and pooled queues. These relationships have different purposes; do not assume a functional or advisory relationship automatically replaces the administrative reporting line.

Published and draft information must remain distinct. If a drill-in unexpectedly shows a different structure or loses your selected draft, return to the catalogue and reopen the intended view. Report the mismatch before relying on the result.

Read coverage without confusing it with employment or access¶

The current browser calculates a seat's summary in this order:

Summary	Current meaning
Filled	A primary assignment is effective now. This label can still appear when a separate acting assignment is also effective.
Acting cover	No primary assignment is effective, but an acting assignment is.
Fallback cover	Neither primary nor acting cover exists on this seat, but the immediately referenced fallback position has primary or acting cover.
Critical gap	A head position has none of the above cover.
Vacant	Another position has none of the above cover.

The design currently emphasizes acting cover when both people are present. That presentation needs reconciliation with the current summary rules. Review the primary and acting people separately; do not infer the person who will receive a particular workflow task from a single badge.

Effective start and end times matter. The current read includes the exact end instant, and a future assignment is not current cover before its start. The assignment ledger can therefore contain people who do not appear in the current summary. Confirm the relevant time and time zone when reviewing a transition.

Coverage is separate from employment state, leave, sign-in access and product permissions. The current structure browsing calculation does not filter an assignment by the person's active-employment or WorkOS-access state. It also includes saved inactive units and positions. A filled seat, a visible person or a queue label is not a complete eligibility or availability check.

An Active units label must count active units specifically; the total returned units can also include inactive units. Critical-position counts currently follow unit head positions. Do not interpret them as an independently maintained criticality score for every role.

Review assignment history¶

Open the intended position and confirm its structure and position name.
Review Assignment history for the cover type, person and effective window.
Compare current, scheduled and ended assignments. The ledger places the newest start first; it is not limited to current occupants.
Use the current primary and acting details alongside the ledger to understand today's coverage.
If information is wrong, ask the authorized structure owner to correct it. The intended correction journey changes the saved assignment; it is not a delete-history action.

No assignments yet is a valid empty ledger for an existing position. It is different from a missing position, denied access or a failed load. Assignment history describes saved assignments and dates; it is not an immutable history of every edit made to those assignments.

Review risks, simulation and validation¶

The intended draft journey includes Risks, Simulation and Validate draft. These answer related but different questions:

View	What it tells you
Risks	The returned structure issues, their severity, affected items and whether they are marked as operational risks.
Simulation	Publication issues alongside a selected set of operational risks. It does not publish, predict business performance or execute a workflow.
Validation	Whether the current publication checks contain a critical issue. A ready result may still include warnings.

When reviewing a draft, inspect the affected items in Risks, then use Simulation to distinguish publication issues from operational concerns. An authorized editor can run validation. Resolve blocking issues through the authorized administration process and validate again after changes. A prior ready result is not proof that a later publish attempt will succeed.

The current checks identify uncovered head positions, units without effective leadership, vacant seats, missing administrative manager links, queue dependencies on uncovered positions and acting cover ending within fourteen days. Workflow-destination warnings here are inferred from position coverage; they are not proof that every configured workflow definition has been inspected or tested.

One underlying gap can produce several issue rows. An uncovered head can appear as a critical vacancy, an unresolved destination and an authority-chain issue. A missing manager can produce more than one category. Totals count those rows; they are not counts of distinct people or unique business problems. Avoid summing overlapping category totals into a new score.

Always establish that the selected draft loaded successfully before interpreting a result. The current validator rejects a missing view, reports an already-published view as blocked, and checks that the designated root belongs to the structure. With no designated root, exactly one top-level unit is needed for automatic selection. Critical risks cannot be hidden by the presence of selected warnings, but the returned publication issues need not list every critical risk. Read the full Risks view as well.

Readiness still does not certify the entire organization graph, every staff member's eligibility or every work-routing destination. Warnings may remain and there is no critical-issue override in this flow. The connected experience must distinguish missing data, failed validation and a result for the correct draft. The draft guide explains root selection and publication.

Recover from common problems¶

Situation	What to do
The structure is loading	Wait for the result. Do not treat placeholders as actual counts.
The load failed	Use Try again. If it continues, give support the workspace, selected structure and approximate time through the approved channel.
Access is restricted	Ask the administrator to check the specific permission required. Viewing, editing and publishing are separate.
A unit or position cannot be found	Reopen the intended structure. It may be a draft/live selection mismatch or an unavailable item; do not assume deletion.
Coverage and assignment history look different	Compare effective dates, primary and acting assignments, fallback and the time of each read. Refresh before escalating.
Ready appears alongside warnings	Review the warnings and returned readiness separately. Ready does not mean every risk has disappeared.
A preview says a change was saved	Treat that message as demonstration behavior until a connected release and an actual saved result have been verified.

Support requests should identify the affected structure or position without copying unnecessary personal information. Keep employee records and sensitive operational details within your organization's authorized channels.

For adoption, assign an accountable structure owner, agree who reviews proposals and who may publish, and check real assignment transitions and restricted-user behavior. Continue with Prepare, review and publish an organization structure for draft lifecycle steps and current creation, copying, replay and deletion limitations. Follow Maintain titles, units, positions and assignments for editing steps and save/correction limits. How your organization structure directs work explains core recipient selection and its differences from placement and coverage. Remaining consumer/recovery verification and the initial audience walkthrough remain open. These guides do not establish deployment readiness, a compliance certification or a delivery date.