WorkOS Home¶

Draft product explanation. The intended Home screens are designed, and current frontend routes can load the four backend summary views for an authorized workspace. Local design-preview mode can still show sample snapshots. A connected code path does not establish hosted availability, complete data or reader acceptance; those remain unverified.

Home is the starting point for understanding work in a workspace and choosing where to continue. It brings together requests, approvals, leave, projects, cases, records, correspondence, shared work and communication. Use it to spot something worth investigating, then open the owning workspace for the complete information and permitted actions.

Choose a view¶

The Home guide explains the intended navigation and what to do when information is missing or unexpected. Home does not replace the full request, leave, project, record, correspondence or shared-work journey.

Understand counts before acting on them¶

Home combines different kinds of measures. They are not all complete totals, and they do not all describe the same people or time period.

• My work lists: approval, request, leave and project counts describe the selected previews, with at most ten entries per list. A count of ten may mean more work exists. A smaller count does not mean every other workspace or kind of task has been checked.
• Record lanes: the four queues provide their own full returned counts, with a short preview of up to five entries each. Do not add the queues to claim a count of unique documents; their scopes can overlap.
• Documents previews: each memo state, letter state, approval list and shared-work direction is limited to ten displayed entries by the summary. These are not all-time correspondence or exchange totals.
• Request summaries: the total covers recorded request workflows. The current “approved” figure means completed workflows; “under review” groups several ongoing and waiting states; “rejected” is currently derived from returned workflows. A return for correction is not necessarily a final rejection. The three displayed percentages need not add to one hundred because other workflow states can exist.
• Active people: this measure counts people with WorkOS access who are not recorded as on ongoing leave. It does not measure online presence, attendance, productivity, or everyone entitled to sign in. Active plus inactive does not necessarily equal total staff.
• Documents on record: the current source counts Workforce file entries. It does not establish a complete count of all governed records, attachments, letters and documents across the platform.
• Projects: active means not completed or canceled in this summary. “Due soon” covers the next fourteen days, including the boundaries; it does not include an already overdue target date.
• Shared work needing action: this is a state-based subset of inbound work. It does not guarantee that you personally have a permitted action on every item. Overview and Documents use different list limits, so their counts can differ.
• Inbox and conversations: unread lanes, conversations and messages count different units. They are not interchangeable with unique tasks or work that requires a decision.

Recent activity on Overview is the current user's activity preview. It is not the full workspace history. Use the activity guide when you need the appropriate complete history and scope.

Access and responsibility¶

You need a valid workspace session, WorkOS access, and the permissions required by the contributing areas. Home does not grant missing permissions or bypass approval authority. The current Overview composition includes staff and executive-dashboard permission checks as well as other domain reads; ordinary WorkOS membership alone does not guarantee that every summary can load.

Employees can use My work to choose a starting point. Managers should confirm the full queue and assignment before reallocating work. Executives should use purpose-built reporting and its definitions for organizational decisions: Home mixes personal previews and workspace totals and is not an employee performance scorecard. Tenant administrators and support can help investigate access or loading problems without treating an empty screen as proof of no work. External participants only see the areas their own access permits; a collaboration invitation does not grant this whole Home view.

Freshness, missing information and costs¶

These summaries read several areas independently. They do not provide a single guaranteed fresh snapshot of all work, and a failing required read can prevent a tab from loading. A sample, blank result or zero should never be used as proof that there are no pending approvals or obligations.

The current live display preserves a reported zero and shows unavailable values when a count is missing or unusable. A list can separately show no items or that its items are unavailable. Counts and lists are not independently reconciled by the screen, and some combined sections can show available content while another input is missing. Use the owning workspace to investigate a disagreement before concluding that work is complete.

The Live summary caption describes the view; it is not a certificate that every contributing source was checked at one instant. Local preview examples also do not become real work because that caption is visible. Confirm the workspace and distinguish an unavailable result from a loaded short list.

Home itself performs reads and navigation. Decisions, submissions, publication, signing and other changes happen in their owning features, with their own authority and commercial rules. No new price, quota, billing commitment or service guarantee is established by viewing a Home card.