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

# Settings

> Run commissions predictably - set payout schedules, minimum amounts, currency, and the billing details used on statements.

export const Headless = ({prompts = []}) => {
  const PromptRow = ({prompt}) => {
    const [copied, setCopied] = useState(false);
    const copy = () => {
      try {
        navigator.clipboard?.writeText(prompt);
      } catch {}
      setCopied(true);
      setTimeout(() => setCopied(false), 1600);
    };
    return <div className="group flex items-center justify-between gap-3 px-4 py-3 transition-colors hover:bg-[#FD90FF]/[0.06]">
        <span className="text-sm leading-relaxed text-zinc-700 dark:text-zinc-200">{prompt}</span>
        <button type="button" onClick={copy} aria-label={copied ? "Copied to clipboard" : "Copy prompt"} className={`shrink-0 rounded-md p-1.5 transition-all hover:bg-[#FD90FF]/10 focus:opacity-100 focus:outline-none ${copied ? "text-[#FD90FF] opacity-100" : "text-zinc-400 opacity-0 group-hover:opacity-100 dark:text-zinc-500"}`}>
          {copied ? <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M20 6L9 17l-5-5" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg> : <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <rect x="9" y="9" width="11" height="11" rx="2" stroke="currentColor" strokeWidth="2" />
              <path d="M5 15V5a2 2 0 0 1 2-2h10" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>}
        </button>
      </div>;
  };
  return <>
      <p>
        Introw is <strong>headless</strong> by design: run everything here in plain language from Claude, ChatGPT,
        Slack, Teams, or your own CRM through Introw's <a href="/features/developer/mcp">MCP server</a>, with every
        action written straight back to your CRM source of truth. The portal is one surface, never the only one.
      </p>

      {prompts.length > 0 ? <div className="not-prose my-6 overflow-hidden rounded-2xl border border-zinc-200/80 bg-white shadow-sm dark:border-white/10 dark:bg-white/[0.02]">
          <div className="flex items-center gap-2 border-b border-zinc-200/80 bg-gradient-to-r from-[#FD90FF]/10 via-[#FD90FF]/5 to-transparent px-4 py-2.5 dark:border-white/10">
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4 text-[#FD90FF]" aria-hidden="true">
              <path d="M12 2.5l2 5.5 5.5 2-5.5 2-2 5.5-2-5.5L4.5 10l5.5-2 2-5.5z" fill="currentColor" />
              <path d="M18.5 14l1 2.6 2.6 1-2.6 1-1 2.6-1-2.6-2.6-1 2.6-1 1-2.6z" fill="currentColor" opacity="0.55" />
            </svg>
            <span className="text-xs font-semibold uppercase tracking-wider text-zinc-500 dark:text-zinc-400">
              Try it from your LLM
            </span>
          </div>

          <div className="flex flex-col divide-y divide-zinc-100 dark:divide-white/[0.06]">
            {prompts.map(prompt => <PromptRow key={prompt} prompt={prompt} />)}
          </div>

          <a href="/headless" className="flex items-center justify-between gap-2 border-t border-zinc-200/80 px-4 py-2.5 text-sm font-medium text-zinc-600 no-underline transition-colors hover:text-[#FD90FF] dark:border-white/10 dark:text-zinc-300">
            <span>See the full headless playbook</span>
            <svg viewBox="0 0 24 24" fill="none" className="h-4 w-4" aria-hidden="true">
              <path d="M5 12h14M13 6l6 6-6 6" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" />
            </svg>
          </a>
        </div> : <Card title="See the headless motion" icon="wand-magic-sparkles" href="/headless">
          The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
          from Claude, ChatGPT, Slack, and your CRM.
        </Card>}
    </>;
};

> Commission Settings make the whole program run on autopilot the way you want: choose how often payouts happen, hold small balances until they are worth paying, and set the billing details that appear on every statement.

## What it does

Commission Settings define how your payout program behaves by default. You choose a payout
schedule, monthly, quarterly, fiscal quarterly, or manual, so payouts happen on a predictable
cadence. You set a minimum payout amount so tiny balances roll forward instead of generating
trivial payments. And you set the company billing information that appears on the statements
partners receive.

These settings, together with your organisation's currency and fiscal year, keep the commission
program consistent run after run. Once configured, your team spends its time reviewing and paying
rather than re-deciding the rules each cycle.

## The problem it solves

Inconsistent payout rules create confusion and extra work:

* **Payout timing is ad hoc** → Set a schedule so payouts run predictably.
* **Tiny balances clog the process** → Set a minimum so small amounts roll forward.
* **Statements lack the right details** → Set company billing info used on every statement.
* **Currency and fiscal periods are unclear** → Align with your organisation's currency and fiscal year.

## From problem to solution

Commission Settings turn one-off decisions into standing rules. Configure the schedule, minimums,
and billing details once, and every payout cycle follows them. The program runs predictably, and
your team focuses on review and payment.

## Use cases

<CardGroup cols={2}>
  <Card title="Predictable schedules" icon="circle-check">
    Run payouts monthly, quarterly, or manually.
  </Card>

  <Card title="Sensible minimums" icon="circle-check">
    Hold small balances until they are worth paying.
  </Card>

  <Card title="Complete statements" icon="circle-check">
    Set billing details that appear on every statement.
  </Card>

  <Card title="Consistent periods" icon="circle-check">
    Align payouts with your currency and fiscal year.
  </Card>
</CardGroup>

## Impact

* **Low total cost of ownership** - Partner ops sets the rules once, with no engineering.

## Who it's for

<CardGroup cols={2}>
  <Card title="Partner Operations" icon="user">
    Configures schedules and minimums.
  </Card>

  <Card title="Finance" icon="user">
    Sets billing details and reconciles statements.
  </Card>
</CardGroup>

## Works with

{/* CONNECTS:START - generated content goes here */}

<CardGroup cols={2}>
  <Card title="Commission Plans" icon="hand-holding-dollar" href="/features/commissions/commission-plans">
    Defaults every plan inherits.
  </Card>

  <Card title="Payouts" icon="hand-holding-dollar" href="/features/commissions/payouts">
    Set how and when payouts run.
  </Card>

  <Card title="Multi-currency" icon="language" href="/features/localization/multi-currency">
    Define the currencies partners are paid in.
  </Card>
</CardGroup>

## Headless

<Headless
  prompts={[
"How is commission calculated for referrals versus resale?",
"What currency are our commissions reported in?",
"What rate tiers and installments does each active plan use?",
]}
/>

## Going deeper

<CardGroup cols={2}>
  <Card title="How to" icon="screwdriver-wrench" href="./technical">
    Setup, configuration, and all how-to guides.
  </Card>

  <Card title="API reference" icon="code" href="/general/introduction">
    Integration surface and code.
  </Card>
</CardGroup>
