Admin Overview & Clients 🛠️

Admin Console Overview

The admin console is the platform-wide control center for Fortis Pulse — where you manage organizations, partners, firms, frameworks, billing configuration, and platform settings. This guide orients you to what's available. 💡 Tip — Who can use this For platform admins (the admin role). Firm admins use a separate portal. Quick reference | Section | What you manage | |---------|-----------------| | Dashboard | At-a-glance platform stats | | Onboarding | Clients in trial / onboarding | | Organizations | Clients and their tiers | | Partners | Advisory partner profiles | | Frameworks | Scoring framework templates | | Pricing/Revenue | Billing configuration and revenue | The console at a glance When you sign in as an admin, your dashboard shows summary stats — active clients, monthly revenue, advisory partners, and pending onboarding — plus a tier distribution breakdown and tables for the client pipeline and partner performance. From here, your main work areas are: - Onboarding — review and approve (or reject) pending client applications, assigning partners during approval. - Organizations (Tiers) — create organizations, change tiers, and dive into each org's detail (billing, advisory team, users, activity). - Partners — create partner accounts, edit profiles and photos. - Firms — create firms, manage members and capacity. - Frameworks — edit framework templates (pillars, metrics, flag rules). - Pricing — configure token rates, tier prices, quotas. - Revenue — view and export revenue. - Benchmarks, CMS, Document Categories, Domains, Industries, Users, AI Prompts — platform configuration surfaces. 📝 Note — Every mutation is audited Nearly every admin action writes an audit record (billing audit log, firm audit log, or framework version log), and pricing/benchmark changes require a reason. This keeps a clear trail of administrative changes.

Understand the Client Pipeline

The client pipeline on your admin dashboard gives you a filterable view of every organization — their tier, status, fees, partners, latest period, and session advisory health. It's your operational view of the platform's client base. 💡 Tip — Who can use this For platform admins, on the admin dashboard. Quick reference | Step | Action | |------|--------| | 1 | Filter and review the client pipeline | Step 1 — Read the pipeline On the admin dashboard, the Client Pipeline table lists organizations. You can filter by Tier and Status (active, trial/trialing, paused, churned). Each row shows: - The client name (links to their detail page). - Tier and Status badges — "Trial" for a client on their free trial, "Trialing" for a paid-tier client still in a trialing state, plus "Firm-sponsored" where the firm manages billing. - Fee per month — their tier's price. - Partners — assigned advisory partners. - Period — their latest financial period and its status. - Sessions — completed versus the required cadence (with an on-track indicator). - An advisory check flagging any missing advisory logs. 💡 Tip — Use filters to find what needs attention Filter by "Trial / Trialing" to see clients still in onboarding or on their free trial, or by status to spot churned or paused accounts. The session and advisory columns quickly reveal clients who are falling behind on engagement.

Create a New Organization

You can create a new client organization directly from the admin console — useful for provisioning an account outside the normal self-serve signup flow. This guide covers creating an org. 💡 Tip — Who can use this For platform admins, under Organizations (Tiers). Quick reference | Step | Action | |------|--------| | 1 | Create an org with a name and tier | Step 1 — Create an organization Go to Organizations (the Tiers page) and click New Org. Enter the organization name and pick its starting tier (Access, Partner, or Executive). The slug is generated automatically from the name. New organizations start in a trialing subscription state (shown as "Pending" until activated). If the slug collides with an existing org, you'll get a conflict error — choose a different name. 📝 Note — New orgs start as trial A newly created org begins in the trialing state, not active. It becomes active once a subscription is set up or the onboarding is approved. This mirrors the self-serve signup lifecycle. 💡 Tip — Most clients come through self-serve The typical flow is a client signing up themselves and appearing in your Onboarding queue for approval. Direct creation is for cases where you need to provision an account manually (for example, a firm-sponsored client or a special setup).

Review & Approve Client Onboarding

When a client signs up, their application lands in your Onboarding queue as "Pending." You review their profile, assign advisory partners, and approve (or reject) to activate their account. This guide covers the approval flow. 💡 Tip — Who can use this For platform admins, under Onboarding. Quick reference | Step | Action | |------|--------| | 1 | Review the profile, assign partners, approve or reject | Step 1 — Approve or reject an application Go to Onboarding to see pending applications. Click one to open the review page, which shows the client's full profile — industry, stage, team size, revenue range, cadence, contact details, targets, challenges, and the advisory domains they've requested. To approve: 1. Assign advisory partners from a suggestion list. Suggestions are auto-ranked by expertise overlap with the requested domains, with capacity flags ("At capacity") shown. Select one or more partners. 2. Designate a Lead partner among those you assign. 3. Set each partner's domain scope (which advisory areas they'll cover for this client). 4. Click Approve & Activate. This creates the partner assignments, sets the org to active, and notifies the assigned partners and client users. To reject: click Reject — the org's status becomes "churned" and the client is notified that their application wasn't approved. 📝 Note — Approval requires an active workspace The API expects the org to already have an active workspace. Self-serve signups create one as part of the flow; if you're approving an org that lacks one, that needs to be resolved first. 💡 Tip — Use the expertise ranking The partner suggestion list ranks by how well a partner's expertise matches the client's requested domains. Start from the top of the list — those partners are the best fit — and check capacity before assigning.

Assign Partners & Set Domain Scope

Assigning the right advisory partners to a client — and scoping their domains — shapes the advisory relationship. You can do this during onboarding approval or adjust it later from the org's detail page. This guide covers managing assignments. 💡 Tip — Who can use this For platform admins, during onboarding or on an org's detail page. Quick reference | Step | Action | |------|--------| | 1 | Assign partners, set lead, scope domains | Step 1 — Manage the advisory team On an organization's detail page, the Advisory Team section lists assigned partners with their Lead badge and domain scope chips, plus a capacity indicator (active clients / tier limit). You can: - Assign a partner from the dropdown of available partners. - Make Lead — designate which partner is the lead (leads can upload Advisory Zone documents and see the consolidated log). - Set domain scope — choose which advisory domains each partner covers. - Unassign — remove a partner from the client. 📝 Note — Tier partner limits apply Each tier has a maximum number of partners (enforced during assignment). You can't assign more partners than the tier allows. If you need more, raise the tier first. 💡 Tip — Match domains to expertise When scoping a partner's domains, align them with that partner's expertise (shown on their profile). This ensures each advisory area is covered by someone qualified and avoids overlapping, unclear ownership.

Change an Org's Tier

You can change an organization's subscription tier from the admin console — upgrading or adjusting their plan. This guide covers the tier change flow and what it affects. 💡 Tip — Who can use this For platform admins, on an org's detail page or the Tiers list. Quick reference | Step | Action | |------|--------| | 1 | Change the tier with a reason | Step 1 — Change the tier On an organization's detail page (Billing section) or inline on the Tiers list, choose a new tier (trial, pulse_ai, access, partner, or executive) and provide a reason. The change: - Sets the tier and updates the subscription state (a trial move keeps trialing; others go active). - Retires any prior processor subscription and inserts a new active subscription row (30-day period, priced from the tier's config, with the tier's included quota). - Writes a billing audit log entry and, if the client belongs to a firm, cross-logs a client.tier_changed entry to the firm audit log. 📝 Note — Tier changes take effect immediately The new tier's features and quotas apply right away. If you're downgrading, the client may lose access to features they were using — communicate the change so it's not a surprise. 💡 Tip — Always record a clear reason The reason you enter is audited. A clear reason (e.g. "client upgraded per request" or "correcting mis-set tier during setup") keeps the audit trail useful for future reference.

Set an Org's Currency

You can set or change an organization's reporting currency from the admin console. This guide covers the currency setting. 💡 Tip — Who can use this For platform admins, on an org's detail page. Quick reference | Step | Action | |------|--------| | 1 | Choose the currency | Step 1 — Set currency On an org's detail page (Organization Info section), use the currency selector to choose from the supported currencies. The change applies to how the client's monetary values are displayed and which payment processor is used for their billing. 📝 Note — Currency drives payment routing The client's currency determines which payment processor handles their transactions (Paystack, Flutterwave, or Stripe, depending on the currency). Changing currency can change the processor. 💡 Tip — Set it once during setup Currency is best set once during onboarding and not changed afterward, since mid-stream changes can complicate billing. If a change is genuinely needed, do it between billing cycles.