Admin Client Detail & Billing 🛠️

View an Organization's Detail Page

An organization's detail page is the deepest admin surface — it brings together the org's info, firm association, onboarding profile, advisory team, Pulse AI runs, users, billing, and activity log. This guide explains what's there. 💡 Tip — Who can use this For platform admins, via the Organizations (Tiers) list. Quick reference | Section | What it shows | |---------|---------------| | Organization Info | Name, slug, tier, status, currency | | Firm Association | Linked firm + billing owner | | Advisory Team | Assigned partners | | Billing | Balance, credit/debit, tier changes | | Activity Log | Recent audited actions | The detail sections Opening an organization shows several sub-sections: - Organization Info — name, slug, tier, status (read-only), and a currency selector. - Firm Association — the linked firm (if any) and the billing owner (direct vs. firm-sponsored). Choosing "No firm" archives the active workspace. - Onboarding Profile (read-only) — the client's submitted profile, if one exists. - Advisory Team — assigned partners, with assign/make-lead/unassign controls. - Pulse AI Runs — the last few AI advisor runs with status and a re-run button for failed runs. - Users — the org's members (name, email, role). - Billing — balance, lifetime tokens/spend, and credit/debit controls plus tier change. - Activity Log — the last 50 audited actions for this org. 💡 Tip — This is your one-stop view When a client has an issue or a question, start here — the detail page shows their plan, their people, their AI runs, and their recent activity in one place, so you can usually diagnose without jumping between screens.

Credit a Client's Token Balance

You can add token credit to a client's balance from the admin console — useful for service credits, trials, or making things right after an issue. This guide covers crediting a balance. 💡 Tip — Who can use this For platform admins, on an org's detail page (Billing section). Quick reference | Step | Action | |------|--------| | 1 | Credit the balance with a reason | Step 1 — Credit the balance On an org's detail page, in the Billing section, use the Credit control. Enter the amount to add and a reason (at least 10 characters). The credit is applied to the client's token balance immediately. The action is recorded in the billing audit log with the amount and your reason. 📝 Note — Debiting is also available The companion Debit control removes tokens, but it cannot take the balance below zero — if the client doesn't have enough, the debit is rejected. Use debit to correct an erroneous credit. 💡 Tip — Always explain why The reason is audited and visible in the billing trail. A clear reason (e.g. "service credit for failed AI run on July period") keeps the trail understandable and justifies the balance change to anyone reviewing later.

Debit a Client's Token Balance

You can remove tokens from a client's balance to correct an erroneous credit. This guide covers debiting. 💡 Tip — Who can use this For platform admins, on an org's detail page (Billing section). Quick reference | Step | Action | |------|--------| | 1 | Debit the balance with a reason | Step 1 — Debit the balance On an org's detail page, in the Billing section, use the Debit control. Enter the amount to remove and a reason (at least 10 characters). The debit is applied and logged. ⚠️ Warning — You can't debit below zero If the client doesn't have enough tokens, the debit is rejected. You can only remove what's there. To fully zero an erroneously-credited balance, debit the exact current balance. 💡 Tip — Use debit to reverse errors Debit is primarily for reversing an accidental or incorrect credit. For routine balance changes, use credit (to add) and let normal AI usage deduct naturally.

Associate a Firm & Set Billing Owner

On an org's detail page, you can associate the org with a firm and set whether billing is direct (client pays) or firm-sponsored (firm pays). This guide covers both. 💡 Tip — Who can use this For platform admins, on an org's detail page (Firm Association section). Quick reference | Step | Action | |------|--------| | 1 | Associate a firm and set the billing owner | Step 1 — Manage firm association and billing owner In the Firm Association section: - Associate a firm — choose a firm from the dropdown. The org then appears as a client on that firm's portal. Choosing "No firm" archives the org's active workspace. - Set billing owner — choose Direct (the client pays the platform directly and appears in platform revenue) or Firm (the firm sponsors the client; the client is excluded from platform revenue and sees a "Plan Managed by Your Firm" notice). 📝 Note — Firm association and billing owner are independent You can associate a firm while keeping billing direct, or set billing to firm-sponsored. They're separate controls — associating a firm doesn't automatically make the client firm-sponsored. 💡 Tip — Set billing owner deliberately The billing owner affects both the client's experience (whether they see upgrade options) and platform revenue accounting. Set it based on who's actually paying, not just on the firm association.

Setting a Firm's Default Billing Type

Every firm has a default billing type that decides how its new clients are billed: Direct (the client pays the Fortis Pulse platform directly) or Firm-sponsored (the firm invoices the client outside Pulse and the client is excluded from platform revenue). You set this default on the firm's page in the Admin Portal. It applies automatically when the firm adds a client in the Firm Portal or a client signs up through the firm's custom domain. 💡 Tip — Who can use this Platform administrators. The setting is per firm; each client can still be overridden individually from the client detail page. Quick reference | Step | Action | |------|--------| | 1 | Open the firm's page in the Admin Portal | | 2 | Choose the billing type in the Billing card | | 3 | Understand what the setting affects | Step 1: Open the firm's page In the Admin Portal, go to Firms and click the firm you want to configure. The firm's page shows its details, capacity limits, and — for non-system firms — a Billing card. Step 2: Choose the billing type In the Billing card, pick one of the two options and click Set Billing Type: - Direct — platform-billed. Clients the firm adds, and clients who sign up through the firm's custom domain, are billed by the platform. They appear in the platform revenue summary and can manage their own subscription and AI balance. - Firm-sponsored — off-system (excluded from revenue). The firm handles billing with the client directly. Such clients don't see payment options in the app, and their revenue doesn't count toward platform totals. The choice is recorded in the firm's audit log with the old and new value. Step 3: Understand what the setting affects 📝 Note — New clients only Changing the firm's billing type does not change clients that already exist. Existing clients keep whatever billing type they have; you can adjust any single client on its detail page under Billing Ownership. 📝 Note — Sign-ups follow the firm's type On a firm-sponsored firm's custom domain, the public sign-up page is turned off entirely — visitors are directed to sign in instead. On a direct-billing firm's domain, new sign-ups are connected to the firm and billed directly. 📝 Note — Default behavior New firms start as Firm-sponsored, matching how firm-created clients have always been handled. Switch a firm to Direct when it should hand billing over to the platform.

Manage an Org's Advisory Team

On an org's detail page, the Advisory Team section lets you assign and unassign partners and set the lead. This guide covers it. 💡 Tip — Who can use this For platform admins, on an org's detail page. Quick reference | Step | Action | |------|--------| | 1 | Assign, set lead, or unassign partners | Step 1 — Manage the advisory team In the Advisory Team section, you see assigned partners with Lead badges, domain scope chips, and a capacity indicator (active clients / tier limit). You can: - Assign a partner from the available dropdown. - Make Lead — designate the lead partner. - Unassign — remove a partner from the client. Tier partner limits are enforced — you can't exceed the tier's maximum. 📝 Note — Assignment creates workspace access Assigning a partner gives them access to that client's workspace for review, scoring, and advisory work. Unassigning revokes it. 💡 Tip — Keep the lead current The lead partner has extra capabilities (Advisory Zone uploads, consolidated log view). Make sure the right person is the lead, especially after team changes.

Re-run Pulse AI (Admin Escape Hatch)

As an admin, you can re-run the Pulse AI advisor on a client's period — useful when a run failed or the data changed. This guide covers the admin re-run. 💡 Tip — Who can use this For platform admins, on an org's detail page (Pulse AI Runs section). Quick reference | Step | Action | |------|--------| | 1 | Re-run Pulse AI from the runs list | Step 1 — Re-run Pulse AI On an org's detail page, the Pulse AI Runs section shows the last few advisor runs with their status (pending, running, completed, failed) and timestamps. For a failed run, a Re-run Pulse AI button lets you trigger a fresh attempt. Admins bypass the assignment gate that partners are subject to, so you can re-run even if you're not an assigned partner. 📝 Note — Re-run regenerates the draft Re-running regenerates the AI's scores, flags, and advisory draft from the current data. If a partner has already taken ownership (edited the advisory), coordinate with them before re-running to avoid overwriting their work. 💡 Tip — Use it to recover from failed runs If a client's advisory shows as stuck or failed, check the runs list. A re-run usually recovers it cleanly.

Force-Recompute Scores

Force-recompute is an admin escape hatch that recomputes every (or a specified) period's score records under the workspace's current framework. This guide covers when and how to use it. 💡 Tip — Who can use this For platform admins, via the force-recompute API endpoint. Quick reference | Step | Action | |------|--------| | 1 | Trigger a force-recompute with a reason | Step 1 — Force-recompute Force-recompute is triggered via the admin API (POST /api/admin/workspaces/[id]/force-recompute) and requires a reason. It recomputes pillar scores, workspace scores, and diagnostic flags for the workspace, re-stamping the framework ID. ⚠️ Warning — Use only before the client sees scores Force-recompute assumes the client never saw the old scores — it sends no client notification. Use it only as the undo path for "wrong framework assigned before the client saw scores." If the client has already seen the period's results, coordinate with the partner rather than silently recomputing. 📝 Note — It's audited The recompute writes a framework-versions audit record (kind: force_recompute) and a firm-audit-logs entry, so there's a clear trail of the action, the actor, and the reason.

View the Org Activity Log

Each org's detail page has an activity log — the last 50 audited actions for that organization. This guide covers reading it. 💡 Tip — Who can use this For platform admins, on an org's detail page. Quick reference | Step | Action | |------|--------| | 1 | Review the activity log | Step 1 — Read the activity log On an org's detail page, the Activity Log section lists the last 50 actions with the actor name, action type, details, and timestamp. It captures both admin actions (cross-logged here) and firm actions when the client belongs to a firm. 📝 Note — It captures admin and firm actions When a platform admin acts on the org (tier change, credit, assignment), it's logged here. When a firm admin acts on a firm-sponsored client, that's cross-logged too. This gives you a combined trail. 💡 Tip — Use it to investigate unexpected changes If a client's tier, billing owner, or advisory team changed unexpectedly, the activity log shows who did it and when. It's your first stop for diagnosing administrative surprises.