Help Center
Search for the articles here or browse the categories below.
Browse by topic
Find guides, tutorials, and answers organised by category.
Popular articles
What other people are reading right now.
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).
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.
Platform Configuration 🛠️Configure Benchmarks (Matrix)
The Benchmarks page lets you set target benchmarks per business stage and industry for each FORTIS metric. Benchmarks drive scoring and the Executive-tier benchmark comparison. This guide covers configuring them. 💡 Tip — Who can use this For platform admins, under Benchmarks. Quick reference | Step | Action | |------|--------| | 1 | Edit benchmark values per stage/industry with a reason | Step 1 — Configure benchmarks Go to Benchmarks. Use the stage buttons (startup, growth, mature, transformation) and industry dropdown to scope the view. ("All industries" sets the stage default; a specific industry creates an override.) The matrix table shows each metric with its label, pillar, unit, direction, and an editable Benchmark input (with the effective value and a source badge — Override vs Default). Edit values, then Save Changes (N) opens a reason modal (at least 10 chars) before the PATCH. You can also Reset scope (rewrites overrides back to defaults) or use CSV export/import. 📝 Note — Benchmarks are service-role data The benchmark matrix is service-role-only. Reads and writes go through the admin endpoints, not the client-facing API. 💡 Tip — Use industry overrides sparingly Start with solid stage defaults, then add industry overrides only where a metric genuinely differs by industry (e.g. churn norms in SaaS vs. manufacturing). Too many overrides make the matrix hard to maintain.
Admin Overview & Clients 🛠️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.
Admin Client Detail & Billing 🛠️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.
Admin Client Detail & Billing 🛠️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.