/lo/one-on-ones and provides a list of scheduled one-on-one meetings, with stats cards, an upcoming sessions panel, filtering by status and participant, and the ability to schedule new sessions.
Overview
TheOneOnOnesPage loads all one-on-ones via useOneOnOnes(organizationId, filters), the next three upcoming via useUpcomingOneOnOnes(organizationId, 3), and organization members via useOrganizationMembers. Three stat cards display totals (the specific metrics surfaced are not labeled in the header JSX and require SME confirmation). A participant filter dropdown is populated from orgMembers. One-on-one records are rendered as OneOnOneCard components. The “Schedule 1-on-1” button opens OneOnOneFormDialog. Selecting a card navigates to /lo/one-on-ones/:oneOnOneId.
Who it’s for
RequiresLO_PERMISSIONS.DASHBOARD_VIEW (lo.dashboard.view) via the shared LOViewGuard. Creating one-on-ones uses lo.one-on-ones.create.
Before you start
lo.dashboard.viewpermission required.- Organization members must be configured for the participant filter to populate.
Steps
1
Navigate to 1-on-1s
Go to
/lo/one-on-ones. The page loads all 1-on-1 sessions for the organization.2
Review upcoming sessions
The upcoming sessions section shows the next three sessions from
useUpcomingOneOnOnes.3
Filter sessions
Use the participant and status dropdowns to narrow results.
4
Open a session
Select a
OneOnOneCard to navigate to /lo/one-on-ones/:oneOnOneId for full detail.5
Schedule a new 1-on-1
Select “Schedule 1-on-1” to open
OneOnOneFormDialog.Key concepts
- OneOnOneFilters: accepts
statusand participant filters. - useOrganizationMembers: provides org-scoped member list for the participant dropdown.
- profiles: members are mapped to
{ id, full_name }for the form.
Viewing a 1-on-1
The 1-on-1 Details screen is accessible at/lo/one-on-ones/:oneOnOneId and provides tabbed management of a single one-on-one session, including notes, feedback items, and status transitions.
The OneOnOneDetailPage fetches the session via useOneOnOne(oneOnOneId), linked feedback via useFeedback(organizationId, { oneOnOneId }), and mutations via useOneOnOneMutation. The breadcrumb shows "${manager.full_name} & ${employee.full_name}". The page renders the session date, status via OneOnOneStatusBadge, manager and employee names with avatars (fetched via a direct Supabase query for profiles). Two tabs — Notes and Feedback — show OneOnOneNotesEditor and a list of FeedbackCard components respectively. The “Add Feedback” button opens FeedbackFormDialog. Edit and Delete actions are in the header; deletion uses AlertDialog confirmation.
Requires LO_PERMISSIONS.DASHBOARD_VIEW (lo.dashboard.view) via the shared LOViewGuard. No additional explicit permission gate is applied in this component.
Before you start: the one-on-one identified by :oneOnOneId must exist, and the manager and employee profiles must exist in the organization.
- Open a 1-on-1 session: navigate to
/lo/one-on-ones/:oneOnOneIdor select a session from the 1-on-1s list. - Review session info: note the session date, status badge, and manager/employee names.
- Take or review notes: on the Notes tab, use
OneOnOneNotesEditorto write or update session notes. - Review or add feedback: on the Feedback tab, view existing feedback linked to this session or add new feedback via
FeedbackFormDialog. - Edit the session: select Edit to open
OneOnOneFormDialogin edit mode. - Delete the session: select Delete and confirm in the
AlertDialogto remove the session.
- OneOnOneStatusBadge: displays the current status of the session.
- Feedback filter:
useFeedbackis called with{ oneOnOneId }to show only feedback linked to this session. - Profiles query: profiles for manager and employee are loaded via a direct Supabase query scoped by
organization_id.
Related
Leadership
Leadership core overview.
Governance & parity
Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or
billing advice. Verify against your organization’s policies and applicable
regulations before using it for clinical, compliance, or billing decisions.
Protected health information (PHI) shown in the product is governed by your
tenant’s access controls and is never exposed in this documentation.
Documentation sources
Documentation sources
- src/routes/lo.tsx
- src/cores/lo/pages/OneOnOnesPage.tsx
- src/cores/lo/pages/OneOnOneDetailPage.tsx
- src/cores/lo/hooks/useOneOnOnes.ts
- src/cores/lo/hooks/useOrganizationMembers.ts
- src/cores/lo/hooks/useFeedback.ts