#Company shift dashboard

Module id: MOD-COMPANY-SHIFTS
Doc profile: capability

Company operators post and manage shifts, review applicants, browse contractors, approve time cards, and update company profile/settings on /company/shifts. This module owns the company dashboard page and is the sole implement owner for shared reusables Detailed job view, End job popup, and Row actions — contractor and time-tracking modules consume those components without forking them.

#Purpose

Hiring companies need one authenticated home to run the marketplace day-to-day: see open and closed shifts, publish new jobs with rates and headcount, open a shift for edit and applicant actions, start or end time tracking from a row, mark contractors Preferred / Do not Book / No show, approve logged time and mark payment send, and review dashboard/report metrics. Observable outcomes are persisted shifts / time_entries rows (and contractor-user list memberships that include the signed-in company user) under company-scoped RLS, with money and approval flags written only through server-authorized RPCs (MON-CLIENT-WRITES / LOG-CLIENT-WRITES).

#Scope boundaries

#Actors

#Capability composition

The company dashboard is one host route with mutually exclusive tab panels driven by URL nav values. Nested tabs=postjob and tabs=detail overlay the shifts list without adding sidebar items. Shared reusables mount from list rows and from other modules.

Bubble evidence for panels and reusables is under Traceability / IR evidence.

#Primary journeys

Journeys are reconstructed from company dashboard workflows and shared reusable workflows (ButtonClicked → NewThing / ChangeThing / ScheduleAPIEvent / ChangePage / Show-Hide / SetCustomState). Where a step only opens another module’s full UI (chat thread body, Stripe Connect plugin), the step is marked out of scope.

#J1 — Enter company dashboard and switch tabs

1. A signed-in company user opens /company/shifts (with or without tab).
2. The host renders under the cabinet workspace and stamps the page root; non-company or signed-out visitors are redirected or denied.
3. URL tab selects exactly one panel: empty/dashboard → dashboard; company_shifts → shifts list (+ Post a New Job); contractors → contractors; time_tracking → time-tracking; payments → payments; reports → reports; profile → profile; settings → settings.
4. Nested tabs=postjob or tabs=detail opens post/detail overlays without inventing extra sidebar entries.
5. Session/role read failure shows a clear error or redirect — never a blank authenticated shell.

#J2 — Filter and browse company shifts

1. On tab=company_shifts, the operator sees Posted / Upcoming / Closed filters bound to shift_type (default filter custom state posted).
2. The repeating list shows Job Title, Location, Assigned Contractor, Skillset, Required Hours, Date, and HR columns, or empty “No result found.”
3. The list loads only shifts owned by the current company profile, filtered by shift_type, with pagination and an explicit max page size.
4. Stop Hiring opens Popup stop hiring; confirm persists shift_type = upcoming and stop_hiring = true through server-authorized updates. Closed is filter-only (sets list custom state type_ = closed). Close the job is visible but has no ButtonClicked workflow in the export — do not invent a persist path.
5. Opening a row / details control mounts the shared Detailed job view (and/or tabs=detail).
6. Load/filter/mutation failures show plain-language UI errors.

#J3 — Post a new job and publish to marketplace

1. Operator chooses Post a New Job (tab stays on company shifts; nested tabs=postjob) and fills the new-job form (title, date/time Wisconsin, hours, policies, contacts, seats needed, skill set, rates, experience).
2. Post creates a shifts row with shift_type = posted, company ownership, and the form field map from DATA-MODEL; Discard resets/hides without insert.
3. After insert, when the new shift’s date is after current date/time, the app invokes edge function shift (JWT; company or service scheduler roles) instead of a browser-trusted API secret.
4. Edge shift only continues the notify chain when at least one contractor user already lists that shift; it does not invent Stripe Connect/KYC.
5. Invalid/empty parent group blocks Post; failures show inline errors.

#J4 — View, edit, and manage applicants on a shift

1. Operator opens Detailed job view for a bound shift and sees transcribed labels (Location, Experience, Directions, Was posted at, Start Date/Time, Wisconsin time, Hours required, pay practice, contacts, policies, assigned contractors).
2. Edit the job PATCHes shift fields through server-authorized paths; company_rate / contractor_rate only via RPC.
3. Stop hiring confirm sets shift_type = upcoming and stop_hiring = true, then closes the dialog.
4. Cancel contractor removes the user from assignee lists and from the contractor’s shifts membership after the 2-hour/4-hour pay note confirm.
5. Contractor don’t show up adds the user to the no-show list and adjusts dependability counters server-side.
6. Empty assignees show “There you’ll see assigned contractors for this shift”; mutation failures stay inline; Discard/Confirm reset groups.

#J5 — Row actions and end job popup

1. Shared Row actions shows Details, Start tracking, and End (visibility respects closed-shift custom state).
2. Details opens the shared Detailed job view for the bound shift — no second detail tree.
3. Start tracking creates a time_entries row (company_request false, contractor = current user, send false) via server insert/RPC, then navigates per source ChangePage.
4. End shows End job popup; Cancel resets/hides without writes.
5. Submit writes tracking notes, sets send true, and computes paid_amount from logged hours/minutes × skill rate inside a server RPC (MON-CLIENT-WRITES).
6. Postmark/notification connectors may be stubbed behind env with timeout; no new money rails.

#J6 — Browse contractors, Preferred, and message

1. On tab=contractors, operator searches and filters by Location and Skills over a paginated contractor list (empty “No result found.”).
2. Preferred / Do not Book / No show up mutate the viewed contractor user’s preferred_list_user / do_not_book_list_user / no_show_up_list_user by adding or removing the signed-in company user (CurrentUser) under RLS — not writes to the company operator’s own profile lists.
3. Send a message creates a chat row visible to both users and navigates to /chat (chat body remains MOD-CHAT).
4. Back to all returns from contractor detail to the list; load/save errors are visible.

#J7 — Approve time cards and send payments

1. On tab=time_tracking, operator sees company-scoped time entries with column labels and empty “Nothing was found. Try again later!”.
2. Approve / Multipal approval set company approval and/or sent-for-payment only via transactional server RPC.
3. Logged hours/minutes edits recompute paid_amount on the server from shift skill rates (same family as End job popup).
4. On tab=payments, operator sees Previous payments / Upcoming payment schedule headings, Unpaid status copy, and Multipal payment using the same server send path.
5. Existing Stripe account display may be read-only; Connect plugin actions are not implemented here (MON-MARKETPLACE).
6. Dialogs dismiss on success; failures show visible errors.

#J8 — Dashboard metrics, reports, profile, and settings

1. On tab=dashboard, operator sees KPI labels (Current open shifts, Percentage of open shifts, Placement rate, Total Cancellation rate, Time to fill shift, Repeat contractors, Average weekly cost) and empty “You have no shifts for today.” when appropriate.
2. Metrics come from company-scoped queries (or honest zeros) — no fabricated Connect balances.
3. Reports shows Cancellations/No shows, TradeForce Usage, Total budget for the month with empty “Nothing was found at the moment.” and paginated lists.
4. Profile fields align with company onboarding where they overlap; Save PATCHes profiles under RLS.
5. Settings mounts only evidenced chrome — no undocumented Connect onboarding.

#Vertical slices (decompose)

#Key UI states

#Navigation contracts

#Style and fidelity

Company dashboard uses the cabinet workspace outlet (.surface-card main). Transcribe visible copy and stamp data-bubble-id on migrated roots: page, panel groups (dashboard, company shifts, contractors, time track, payments, reports, profile, settings), Post a New Job, new-job form, Detailed job view, Row actions, End job popup, and primary list/RG roots. Shared tokens come from the app-level stylesheet that SHELL-LAYOUT (MOD-SHELL) delivers out of IR styles (ir/slices/styles____part_all.json — 49 styles, 8 color tokens, 1 font token); this cycle's module map has no separate design-system module, so do not defer a token to one. Preserve Wisconsin time copy on date/time fields. Prefer-control button copy is Preferred (not “Prefer”).

#Failure modes

#Traceability

#Naming (idiomatic) — source → target

#IR evidence

#Module evidence roots

• bTITd — company_dashboard_shifts page (/pages/bTIbd); tab panels, post/list/detail workflows
• bTIgC — DetailedViewJob definition (/element_definitions/bTIgD); sole shared detail UI
• bTHkx — EndJobPopup definition (/element_definitions/bTHky); sole end-shift popup
• bTHTn — RGaction definition (/element_definitions/bTHTo); Details / Start tracking / End
• bTMBT — API event shift (/api/bTMBU); contractor-count gate + ScheduleAPIEventOnList → tracking helper

Supporting segments: ir/slices/bTIbd____root.json, ir/slices/bTIbd__elements____remaining_children.json, ir/slices/bTIbd__elements__bTHQp__elements____remaining_children.json, ir/slices/bTIbd__workflows____part_A.json, ir/slices/edef_bTIgD____root.json, ir/slices/edef_bTHky____root.json, ir/slices/edef_bTHTo____root.json, user types shifts / job / company / custom_rate, option shift_type.

#Path-key ↔ inventory id aliases

#Panel visibility (URL nav)

#Shift type option set

List filter custom state type_ defaults to posted. Closed filter workflow bTJfl (trigger bTIcH) only SetCustomState type_=closed — it does not ChangeThing the shift.

#Stop Hiring vs Close the job (list)

• Stop Hiring (bTIdf) → workflow bTJft: ShowElement + DisplayGroupData on Popup stop hiring (bTIeJ).
• Confirm ChangeThing action bTJgL: shift_type_option_shift_type → upcoming, stop_hiring_boolean → true on ElementParent shift.
• Close the job (bTIdl, path element bTIdn): button text “Close the job”; zero ButtonClicked workflows on page or element_definitions after sanitized export chase — treat as unwired UI, not a persist path.
• Decompose COSHIFT-LIST AC that claims Close the job persists is export-drift; implement follows this chase.

#Preferred / Do not Book / No show ownership

• Contractor detail group binds to URL param contractor (bTJxD0 chain under bTJph).
• Preferred button (bTJyd0) copy is “Preferred”; workflow bTJzT0 / action bTJzZ0 ChangeThing ElementParent: add CurrentUser to preferred_list_user, remove from do_not_book_list_user.
• Do not Book: bTJzd0 / bTJzj0 — remove CurrentUser from preferred, add to do_not_book.
• No show: bTJzl0 / bTJzr0 — add CurrentUser to no_show_up_list_user.
• Fields live on the viewed contractor user, not on the company operator’s profile.

#Post / edit → edge shift

• Post workflow ScheduleAPIEvent (bTLtQ): schedules bTMBT when PreviousStep (NewThing) date_date greater_than Current Date/Time; passes new shift as parameter.
• Edit workflow ScheduleAPIEvent (bTMBl): same API event after ChangeThing on the shift.
• API shift (bTMBT): runs when Search count of contractor-role users whose shifts_list contains the parameter shift is ≥ 1; action ScheduleAPIEventOnList toward tracking helper (bTLsx family) with short delay.
• Target: JWT edge function shift — never ship service role to the browser.

#Privacy / feature notes

• shifts and time_tracking1 carry Bubble privacy roles (see DATA-MODEL / overview).
• Residual company / job types: no separate migrate journeys; ownership via profiles.role=company and shifts.company_id.
• Money writes (rates, paid_amount, sent_for_payment, approve flags) require server/RPC authority (MON-CLIENT-WRITES / LOG-CLIENT-WRITES).
• Stripe Connect / KYC remain MON-MARKETPLACE — out of this module’s implement scope.

#Decompose refs

tooling/cursor-impl-cycle/output/decompose/MOD-COMPANY-SHIFTS.json — items COSHIFT-HOST through COSHIFT-DASHBOARD-META.