> ## Documentation Index
> Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Current-stage client workspace

> Review and complete stage-relevant work directly in the client side card.

Select a client in **Admin → Onboarding**. The card shows the verified business/Location
and Operations contact separately, the current stage, owner, KYC, setup count and next
action. A contact’s company name never substitutes for an unverified Location.

## Work the current stage

| Stage | Work available in the card |
| - | - |
| New — Paid | Form submission, verified kickoff booking and account linking when needed |
| Compliance | Payment Verified, Slack Joined, Skool Joined, named identity review, private support-channel access, kickoff attendance and its CRM completion date |
| Setup In Progress | CRM checklist, setup outcomes, website status and links, partner-page verification, technical attendance and the relevant FM call |
| Final QA Check | Exact unmet requirements, account links, completed evidence and explicit approval to go Live |

The Compliance completion date is read-only here. Confirm attendance through the
verified kickoff call controls; use **Sync completion date** when the recorded attendance
and CRM date need reconciliation.

Simple outcomes expose **Verify complete** on their row; open the row only for evidence
and instructions. Completed outcomes expose **Reopen step** inside their completed group.
Completed setup outcomes
stay in a compact disclosure. **All requirements** reveals earlier and future CRM fields;
it never changes the client’s stage. **Show current stage** returns to the focused view.
If the CRM stage changes while a draft is open, finish or discard the draft before the
workspace follows the new stage.

**View full client** and the expand arrow add space while preserving the current stage,
selected view, open editors and drafts. Collapsing preserves the same context.

## Distinct checks stay distinct

CRM checkboxes save with **Save**. Task verification, partner-page changes, shared updates,
identity and appointment changes use their own controls. A verified account outcome does
not automatically check an unrelated CRM acknowledgment. Slack Joined, private-channel
access and the Operator’s Slack acknowledgment are separate facts. Training acknowledgment
and Skool Joined are also separate. A completed setup checklist is not approval to go Live.

The **Partner application page** task groups its CRM connection checkbox and its page
verification. Its summary reports both states. Changing the CRM checkbox uses **Save**;
it never verifies the page. URL edits and page verification still use the task's actions.
You can change the checkbox back before saving while keeping other CRM edits. Save or
discard those edits before verifying the page or changing another setup task.

**Slack support workspace** shows access to My Funding Machine Support. Operators join
with their onboarding email and free Slack accounts. Use its explicit refresh, pause/resume
or reviewed reconnect controls when needed. Expand **Review or edit channel** in Compliance
to adopt an existing private channel before automatic setup reserves one. Reserved channels
cannot be replaced or cleared there. See [Slack workspace setup](/staff/slack-workspace).

## Calls, notes and exceptions

* **Current call** shows the relevant kickoff or FM booking. Attendance and appointment
  management are adjacent. Choose **Showed** or **No show** only after confirming what
  happened; attendance is unavailable before the call starts. FM2 **Not needed** remains
  a staff waiver, with its existing reverse action.
* **All calls & notes** shows call history, manual technical dates, contact details, tasks
  and notes. Appointment assignments, search period and overrides are in **Troubleshooting**.
* **Add a note** opens a private staff note saved to this client’s CRM contact. It is
  separate from **Edit shared team update**, which is visible to the Operator and records
  the next action, responsible party and optional review date. Clearing that update does
  not clear CRM Missing Info or complete a task.
* **Next action** names the first unmet stage requirement, explains what is wrong and links
  to its fix. Stage review lists every requirement the same way.
* **Actions** opens Change owner, Hold / resume or Review stage. Opening a control never
  performs its action.
* Mapping problems, holds, Missing Info, canceled or unconfigured identity, reopened identity and uncertain saves remain
  visible across stages. Optional phone/texting stays collapsed unless a purchase needs
  review. Recovery keeps the existing evidence, wait and reconciliation requirements.
* **Edit follow-up** opens the relevant hold or Missing Info field, including configured
  multiple-choice fields. It does not change the Operator-visible shared team update.

A notice inside the card identifies disabled CRM editing or disabled account setup.
Clients remain searchable, with genuine blockers visible. An unknown mapping is shown
as needing review; the UI does not infer rollout membership.

Selecting, expanding and switching views read saved data only. **Refresh bookings**,
**Refresh links** and **Refresh setup connections** retain their explicit provider and
CRM behavior. **Refresh links** also syncs links to CRM and can advance the onboarding
stage when its requirements are met. Connection refresh can provision a private Slack channel when its configured
gates permit it; browsing never starts provisioning.
Bookings and Slack connection details show their last provider check, or state that they
have not been checked. A saved status does not imply a fresh provider request.

The footer shows unsaved work and its applicable save/discard action. Save or discard
another kind of draft before submitting a different operation. An uncertain save must
be reconciled before retrying. Closing the client warns before discarding unsaved work.
See [Focused onboarding workspace](/staff/onboarding-workspace) for entry points and permissions.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.