diff --git a/content/docs/api-reference/errors.mdx b/content/docs/api-reference/errors.mdx
index bf02744..d3cbe75 100644
--- a/content/docs/api-reference/errors.mdx
+++ b/content/docs/api-reference/errors.mdx
@@ -2,7 +2,7 @@
 title: Errors & Troubleshooting
 description: All API error codes, their causes, and how to fix common integration problems.
 kind: reference
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 > **Beta** — The Affitor SDKs and CLI are in active development. The documented happy-path works; edge cases may change. Report issues on GitHub.
@@ -193,7 +193,7 @@ The JSON body also gains a `warnings` array. No existing field is removed or ren
 
 This body is the [typed envelope](#the-typed-envelope): no `data` key, and an `error.code` to branch on.
 
-**Fix:** In your Affitor dashboard, go to **Settings** → **API keys** and regenerate the key, then update `AFFITOR_API_KEY` on your server with the new value. See [Rotate your API key](/docs/brand/settings#step-3-regenerate-the-key) for the full walkthrough.
+**Fix:** In your Affitor dashboard, open the program menu and choose **Program settings**. Under **Developers** → **API keys**, regenerate the key, then update `AFFITOR_API_KEY` on your server with the new value. See [Rotate your API key](/docs/brand/settings#step-3-regenerate-the-key) for the full walkthrough.
 
 ---
 
@@ -437,7 +437,7 @@ An expired session is not an error on `/auth/poll`: it answers `200` with `"data
 |----------|--------|---------------|---------|-----|
 | both | `401` | `Missing or malformed Authorization header. Expected: Bearer <api_token>` | The `Authorization` header is missing or does not start with `Bearer ` | Send `Authorization: Bearer YOUR_PROGRAM_API_KEY` |
 | both | `401` | `Missing API token` | The token is empty after `Bearer ` | Check for an empty env variable |
-| both | `401` | `Invalid API key. To get a working key for the program you already have, ask a workspace owner of that program to open Affitor → Settings → API Key and click Regenerate, then replace the key you are sending with the new one.` | The key matches no program | Do as the message says. Running `affitor init` does not help: it creates a second program |
+| both | `401` | `Invalid API key. To get a working key for the program you already have, ask a workspace owner of that program to open Affitor → Settings → API Key and click Regenerate, then replace the key you are sending with the new one.` | The key matches no program | Do as the message says: the key is under program menu → **Program settings**, then **Developers** → **API keys**. Running `affitor init` does not help: it creates a second program |
 | both | `401` | [`api_key_rotation_required`](#api_key_rotation_required) | The key is retired | Create a new key |
 | `GET /status` | `500` | `Failed to get status (request_id: <id>)` | Status lookup failed on our side | Retry with backoff |
 | `POST /test-event` | `400` | `Invalid event_type: <value>. Valid: click, lead, sale` | Single-event mode got a missing or unknown `event_type` | Send `click`, `lead` or `sale`, or `{"type": "chain"}` for the full chain |
diff --git a/content/docs/api-reference/integrations/fastify.mdx b/content/docs/api-reference/integrations/fastify.mdx
index fcecfee..55be4de 100644
--- a/content/docs/api-reference/integrations/fastify.mdx
+++ b/content/docs/api-reference/integrations/fastify.mdx
@@ -2,7 +2,7 @@
 title: "Fastify"
 description: "Server-side Affitor integration with @affitor/sdk/server — track signups and sales from your Fastify backend, including a raw-body Stripe webhook."
 kind: guide
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 This guide wires Affitor into a Fastify app. Because Fastify is a pure server runtime, the click is captured by a frontend script tag, then the `affitor_click_id` is forwarded to your server so all tracking calls — lead and sale — happen server-side with `@affitor/sdk/server`. The sale is tracked from your Stripe webhook handler, which needs the **raw request body** for signature verification.
@@ -15,7 +15,7 @@ The `@affitor/sdk` package is **Beta**. The documented happy-path works; report
 
 ## Prerequisites
 
-- Your **program ID** (**Settings** → **Program settings** → **Business**)
+- Your **program ID** (program menu → **Program settings** → **Business**)
 - A **program API key** for server-side calls (dashboard → API keys)
 - `@affitor/sdk` and `stripe` installed in your backend
 
diff --git a/content/docs/api-reference/integrations/nextjs-clerk.mdx b/content/docs/api-reference/integrations/nextjs-clerk.mdx
index 91d74e0..1993d2c 100644
--- a/content/docs/api-reference/integrations/nextjs-clerk.mdx
+++ b/content/docs/api-reference/integrations/nextjs-clerk.mdx
@@ -2,7 +2,7 @@
 title: "Next.js + Clerk"
 description: "Add Affitor tracking to a Next.js (App Router) app that uses Clerk for authentication."
 kind: guide
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 This guide covers the auth-specific parts of an Affitor integration when your Next.js app uses Clerk. Steps 1 (capture the click) and 3 (track the sale) are identical to the [base Next.js guide](/docs/api-reference/integrations/nextjs) — this guide focuses on **Step 2: tracking the signup** with Clerk's identity model.
@@ -15,7 +15,7 @@ The `@affitor/sdk` package is **Beta**. The documented happy-path works; report
 
 ## Prerequisites
 
-- Your **program ID** (**Settings** → **Program settings** → **Business**)
+- Your **program ID** (program menu → **Program settings** → **Business**)
 - A **program API key** for server-side calls (leads and sales)
 - A Next.js App Router app with **Clerk** configured
 
diff --git a/content/docs/api-reference/integrations/nextjs-nextauth.mdx b/content/docs/api-reference/integrations/nextjs-nextauth.mdx
index 7bd29e5..c344978 100644
--- a/content/docs/api-reference/integrations/nextjs-nextauth.mdx
+++ b/content/docs/api-reference/integrations/nextjs-nextauth.mdx
@@ -2,7 +2,7 @@
 title: "Next.js + NextAuth"
 description: "Add Affitor lead tracking to a Next.js app using NextAuth (Auth.js) — handle the click-id cookie gap correctly."
 kind: guide
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 This guide covers the signup step when your Next.js app uses **NextAuth (Auth.js)** for authentication. Steps 1 (capture click) and 3 (track sale) are identical to the [base Next.js guide](/docs/api-reference/integrations/nextjs) — this page focuses on what is different: wiring the lead call to NextAuth's auth lifecycle without losing the click attribution.
@@ -15,7 +15,7 @@ The `@affitor/sdk` package is **Beta**. The documented happy-path works; report
 
 ## Prerequisites
 
-- Your **program ID** (**Settings** → **Program settings** → **Business**)
+- Your **program ID** (program menu → **Program settings** → **Business**)
 - A **program API key** for server-side calls
 - A Next.js App Router app with NextAuth (Auth.js) configured
 
diff --git a/content/docs/api-reference/integrations/nextjs-supabase.mdx b/content/docs/api-reference/integrations/nextjs-supabase.mdx
index cb52e09..362c0aa 100644
--- a/content/docs/api-reference/integrations/nextjs-supabase.mdx
+++ b/content/docs/api-reference/integrations/nextjs-supabase.mdx
@@ -2,7 +2,7 @@
 title: "Next.js + Supabase Auth"
 description: "Add Affitor tracking to a Next.js app that uses Supabase Auth — clicks, signups, and sales."
 kind: guide
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 This guide covers the Supabase-specific signup step. Steps 1 (capture the click) and 3 (track the sale) are identical to the [base Next.js guide](/docs/api-reference/integrations/nextjs) — refer there for full detail.
@@ -15,7 +15,7 @@ The `@affitor/sdk` package is **Beta**. The documented happy-path works; report
 
 ## Prerequisites
 
-- Your **program ID** (**Settings** → **Program settings** → **Business**)
+- Your **program ID** (program menu → **Program settings** → **Business**)
 - A **program API key** for server-side calls (leads and sales)
 - A Next.js app with **Supabase Auth** configured
 
diff --git a/content/docs/api-reference/integrations/nextjs.mdx b/content/docs/api-reference/integrations/nextjs.mdx
index 639605e..fc25a70 100644
--- a/content/docs/api-reference/integrations/nextjs.mdx
+++ b/content/docs/api-reference/integrations/nextjs.mdx
@@ -2,7 +2,7 @@
 title: "Next.js"
 description: "Add Affitor tracking to a Next.js (App Router) app — clicks, signups, and sales."
 kind: guide
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 This guide wires Affitor into a Next.js App Router app with the three moves every integration needs: **capture the click**, **track the signup**, **track the sale**.
@@ -15,7 +15,7 @@ The `@affitor/sdk` package is **Beta**. The documented happy-path works; report
 
 ## Prerequisites
 
-- Your **program ID** (**Settings** → **Program settings** → **Business**)
+- Your **program ID** (program menu → **Program settings** → **Business**)
 - A **program API key** for server-side calls (leads and sales)
 - A Next.js app on the **App Router**
 
diff --git a/content/docs/api-reference/integrations/node-express.mdx b/content/docs/api-reference/integrations/node-express.mdx
index 562f689..876bd1a 100644
--- a/content/docs/api-reference/integrations/node-express.mdx
+++ b/content/docs/api-reference/integrations/node-express.mdx
@@ -2,7 +2,7 @@
 title: "Node / Express"
 description: "Server-side Affitor integration with @affitor/sdk/server — track signups and sales from your Express backend."
 kind: guide
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 This guide wires Affitor into a Node.js / Express app. Because Express is a pure server runtime, the click is captured by a frontend script tag, then the `affitor_click_id` is forwarded to your server so all tracking calls — lead and sale — happen server-side with `@affitor/sdk/server`.
@@ -15,7 +15,7 @@ The `@affitor/sdk` package is **Beta**. The documented happy-path works; report
 
 ## Prerequisites
 
-- Your **program ID** (**Settings** → **Program settings** → **Business**)
+- Your **program ID** (program menu → **Program settings** → **Business**)
 - A **program API key** for server-side calls (dashboard → API keys)
 - `@affitor/sdk` installed in your backend
 
diff --git a/content/docs/api-reference/integrations/polar.mdx b/content/docs/api-reference/integrations/polar.mdx
index 20b8924..ae4a18f 100644
--- a/content/docs/api-reference/integrations/polar.mdx
+++ b/content/docs/api-reference/integrations/polar.mdx
@@ -2,7 +2,7 @@
 title: "Polar"
 description: "Canonical recipe for attributing Polar payments to Affitor partners — one-time, subscriptions, renewals, and refunds. No Stripe account needed."
 kind: guide
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 This guide is the **canonical reference for the Polar sale path**. Polar is a merchant of record, so there is no Stripe account to connect — instead, your app hosts a small webhook route that reports every paid order to Affitor.
@@ -15,7 +15,7 @@ The `@affitor/sdk` package is **Beta**. The documented happy-path works; report
 
 ## Prerequisites
 
-- Your **program ID** and a **program API key** (run `npx affitor init`, or **Settings** → **Program settings** → **Business** for the ID and **Developers** → **API keys** for the key)
+- Your **program ID** and a **program API key** (run `npx affitor init`, or, in the program menu, **Program settings** → **Business** for the ID and **Developers** → **API keys** for the key)
 - A Polar organization with checkout working in your app
 - Access to your Polar organization's webhook settings. Sandbox is a separate environment with its own tokens and its own webhook endpoints (`sandbox-api.polar.sh`).
 
diff --git a/content/docs/api-reference/integrations/stripe.mdx b/content/docs/api-reference/integrations/stripe.mdx
index 1f8a2f3..2333a01 100644
--- a/content/docs/api-reference/integrations/stripe.mdx
+++ b/content/docs/api-reference/integrations/stripe.mdx
@@ -2,7 +2,7 @@
 title: "Stripe"
 description: "Canonical recipe for attributing Stripe payments to Affitor partners — one-time and recurring."
 kind: guide
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 This guide is the **canonical reference for the Stripe sale path**. Other framework guides (Next.js, Express, etc.) link here for Step 3. If you need click capture or signup tracking first, start with the [Next.js guide](/docs/api-reference/integrations/nextjs) or the framework guide for your stack.
@@ -15,10 +15,10 @@ The `@affitor/sdk` package is **Beta**. The documented happy-path works; report
 
 ## Prerequisites
 
-- Your **program ID** (**Settings** → **Program settings** → **Business**)
-- A **program API key** (dashboard → program settings → API keys)
+- Your **program ID** (program menu → **Program settings** → **Business**)
+- A **program API key** (program menu → **Program settings**, then **Developers** → **API keys**)
 - Stripe Checkout or Stripe Billing already working in your app
-- Affitor receiving your Stripe webhooks (dashboard → program settings → Stripe connect)
+- Affitor receiving your Stripe webhooks (program menu → **Program settings** → **Payments**, **Connect Stripe**)
 
 ## 1. Capture clicks and track signups
 
diff --git a/content/docs/api-reference/mcp.mdx b/content/docs/api-reference/mcp.mdx
index dc20aa2..a4eee9a 100644
--- a/content/docs/api-reference/mcp.mdx
+++ b/content/docs/api-reference/mcp.mdx
@@ -2,7 +2,7 @@
 title: Affitor MCP server
 description: Connect Claude, ChatGPT, Cursor, VS Code, Perplexity, Claude Code, Codex and other AI apps to your Affitor program or partner account at https://mcp.affitor.com/mcp. Sign in with your Affitor account; access is read-only.
 kind: reference
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 The Affitor MCP server lets an AI app read your Affitor data: a brand's program, partners, applications, commissions and billing, or a partner's programs, links, earnings, commissions and payouts. It is a hosted [Model Context Protocol](https://modelcontextprotocol.io) server. You sign in with your Affitor account, no API key needed, and the connection is read-only: it cannot change data or move money.
@@ -38,7 +38,7 @@ https://mcp.affitor.com/mcp
 
 ## Connect your AI app
 
-In the Affitor dashboard, **Connect an AI tool** shows the server URL and steps for Claude, Cursor, Claude Code and Codex. Brands find it in **All settings** › **Developers** › **AI agents**, and on the program's **Tracking** step under **Your agent** › **Connect your AI**. Partners find it in **Settings** › **Integrations**.
+In the Affitor dashboard, **Connect an AI tool** shows the server URL and steps for Claude, Cursor, Claude Code and Codex. Brands find it in the program menu under **Program settings**, then **Developers** › **AI agents**, and on the program's **Tracking** step under **Your agent** › **Connect your AI**. Partners find it in the **⋯** menu next to their name, at the bottom of the left menu, under **Integrations**.
 
 <CodeGroup items={[
   {
@@ -175,8 +175,8 @@ To give an app a second program, connect again and pick that program. Each conne
     "Your AI app lists the Affitor tools: `get_program` for a brand connection, `list_my_programs` for a partner connection",
   ]}
   dashboard={[
-    "Brands: the connection appears under **All settings** › **Developers** › **AI agents**, with **Added** and **Last used**",
-    "Partners: the connection appears under **Settings** › **Integrations**",
+    "Brands: the connection appears on **Developers** › **AI agents** (program menu › **Program settings**), with **Added** and **Last used**",
+    "Partners: the connection appears on **Integrations**, in the **⋯** menu next to your name",
   ]}
   ifNotWorking={[
     "**This request has expired**: start the connection again from your AI app",
@@ -210,7 +210,7 @@ Every tool is read-only, and the server declares it so on each tool: `readOnlyHi
 | `list_my_links` | Your referral links, newest first, with lifetime clicks, leads and sales. | `partner_program_id`, `status` (`active`, `inactive`), `limit`, `cursor` |
 | `get_my_earnings` | Your earnings per program and in total for the window: earned, ready, arriving, paid and pending. | `from`, `to` |
 | `list_my_commissions` | Your commissions across your programs, newest sale first. | `status`, `from`, `to`, `partner_program_id`, `limit`, `cursor` |
-| `list_my_payouts` | Your payout requests, newest first: amount, status, method type and dates. Bank and PayPal details are never included. | `limit`, `cursor` |
+| `list_my_payouts` | Your payout requests, newest first: amount, status, method type and dates. Payout account details, such as bank or Wise details, are never included. | `limit`, `cursor` |
 
 ### How results look
 
@@ -264,8 +264,8 @@ The server cannot approve an application, change a commission, create a link or
 
 ### Remove access
 
-- **Brands:** **All settings** › **Developers** › **AI agents** lists the program's connections under **Connections** with **Client**, **Connected by**, **Added**, **Last used** and **Access**. Click **Remove** on your own connection. A program owner can remove any member's connection to that program.
-- **Partners:** **Settings** › **Integrations**, then **Remove**.
+- **Brands:** program menu › **Program settings**, then **Developers** › **AI agents**, lists the program's connections under **Connections** with **Client**, **Connected by**, **Added**, **Last used** and **Access**. Click **Remove** on your own connection. A program owner can remove any member's connection to that program.
+- **Partners:** the **⋯** menu next to your name › **Integrations**, then **Remove**.
 
 Removal is immediate: the app's tokens are deleted and its next request gets `401`.
 
diff --git a/content/docs/brand/api-keys.mdx b/content/docs/brand/api-keys.mdx
index 1b36ddb..2864c1e 100644
--- a/content/docs/brand/api-keys.mdx
+++ b/content/docs/brand/api-keys.mdx
@@ -2,7 +2,7 @@
 title: API key reference
 description: Which credential each Affitor call needs, where the program API key lives, how to replace it, and how mandatory rotation is signalled.
 kind: reference
-last_updated: 2026-10-15
+last_updated: 2026-10-17
 ---
 
 Affitor has one self-serve credential: the **program API key**. It authenticates server-side tracking calls for a single program, you manage it yourself from the dashboard, and it is the key the integration guides, the SDKs, the CLI's tracking setup, and the agent skill all refer to. CLI commands that create or list programs are different: they act as your account, so they authenticate with your CLI login rather than with this key.
@@ -46,7 +46,7 @@ Keys issued before the short prefix was introduced do not start with `aff_`. Aut
 
 ## Where to find it
 
-1. In the program menu (your program's name at the top of the left menu), choose **All settings**.
+1. In the program menu (your program's name at the top of the left menu), choose **Program settings**.
 2. Under **Developers**, select **API keys**.
 
 A program is given a key the moment it is created, but creating a program does not hand that value back to you. To get a key you can put in an environment variable, a workspace owner selects **Generate** — or **Regenerate**, if one was generated before — on the **API keys** page. The full value appears in the response to that action, and only there. Copy it then and store it server-side:
@@ -136,7 +136,7 @@ Send a test-mode call with the key in hand: it goes through the same authenticat
     "Read the status before the body: a 200 with no warnings array means this key is not flagged for mandatory rotation. A flagged key that is past its deadline returns 401 and carries no warnings array either, so warnings alone never proves a key is unflagged",
   ]}
   dashboard={[
-    "Settings → API keys shows a masked value whose visible characters match the key your server sends",
+    "The **API keys** page (program menu → **Program settings**, then **Developers** → **API keys**) shows a masked value whose visible characters match the key your server sends",
   ]}
   ifNotWorking={[
     "On a 401, read error.code first. api_key_rotation_required means the key passed its rotation deadline — regenerate it, because re-copying the same key will not bring it back. Any other 401 means the header is malformed or the key matches no program: check the Authorization: Bearer prefix and your environment variable for trailing whitespace",
diff --git a/content/docs/brand/cli/commands.mdx b/content/docs/brand/cli/commands.mdx
index cd742f6..94eeeab 100644
--- a/content/docs/brand/cli/commands.mdx
+++ b/content/docs/brand/cli/commands.mdx
@@ -2,7 +2,7 @@
 title: CLI Command Reference
 description: Complete reference for all npx affitor commands, flags, and options.
 kind: reference
-last_updated: 2026-10-12
+last_updated: 2026-10-17
 ---
 
 Every `npx affitor` command, flag, and option in one place.
@@ -96,7 +96,7 @@ Create a **new** affiliate program and generate config files. Requires a login s
 npx affitor init
 ```
 
-`init` always creates a new program. It does not adopt a program you already have and it does not issue a replacement key for one: if a program's key stopped working, a workspace owner regenerates it in Affitor under Settings → API Key. Running `init` in a directory that already has `.affitor/config.json` stops without changing anything.
+`init` always creates a new program. It does not adopt a program you already have and it does not issue a replacement key for one: if a program's key stopped working, a workspace owner regenerates it in the Affitor dashboard (program menu → **Program settings**, then **Developers** → **API keys**). Running `init` in a directory that already has `.affitor/config.json` stops without changing anything.
 
 | Flag | Description | Default |
 |---|---|---|
@@ -222,7 +222,7 @@ A readiness poll that succeeds after a failed chain still reports `integration_v
 
 ## `affitor setup stripe`
 
-Stripe is connected from the Affitor dashboard, not from the CLI: open the program, go to **Settings**, and use **Connect Stripe**. Affitor's own webhook then records sales, renewals and refunds for that account; nothing needs to be created on your Stripe account. To attribute each sale, add Affitor metadata to your Checkout Session, as described in the [Stripe integration guide](/docs/api-reference/integrations/stripe).
+Stripe is connected from the Affitor dashboard, not from the CLI: open the program menu, choose **Program settings**, open **Payments**, and use **Connect Stripe**. Affitor's own webhook then records sales, renewals and refunds for that account; nothing needs to be created on your Stripe account. To attribute each sale, add Affitor metadata to your Checkout Session, as described in the [Stripe integration guide](/docs/api-reference/integrations/stripe).
 
 ```bash
 npx affitor setup stripe
@@ -358,8 +358,8 @@ Two gaps are worth knowing before you build on this output:
 | Invalid event type | `invalid_event_type` | `test` | `affitor test` takes `click`, `lead`, or `sale` |
 | No API key | `no_api_key` | `onboard` | Pass `--api-key`, set `AFFITOR_API_KEY`, or run from a directory with `.affitor/.env` |
 | API rejected the call, account session | `error` is the API message, `status` the HTTP status | `init` | `init` authenticates with your account session, not a program key. A `401` here means the session is invalid or expired — run `affitor login` again. Do **not** regenerate a program key for this: it will not fix the session, and it breaks whatever is still using the old key |
-| API rejected the call, program key | `error` is the API message, `status` the HTTP status | `status`, `test` | On a `401`, the key matches no program or was replaced. Compare it against the value you stored when it was issued; if you no longer hold that value, ask a workspace owner to regenerate the key under Settings → API Key and deploy the new one |
-| Stripe is connected elsewhere | `stripe_setup_moved` | `setup stripe` | Connect Stripe in the dashboard: program **Settings**, **Connect Stripe** |
+| API rejected the call, program key | `error` is the API message, `status` the HTTP status | `status`, `test` | On a `401`, the key matches no program or was replaced. Compare it against the value you stored when it was issued; if you no longer hold that value, ask a workspace owner to regenerate the key (program menu → **Program settings**, then **Developers** → **API keys**) and deploy the new one |
+| Stripe is connected elsewhere | `stripe_setup_moved` | `setup stripe` | Connect Stripe in the dashboard: program menu → **Program settings** → **Payments**, **Connect Stripe** |
 | No usable response | `network_error` | `init`, `status`, `test` | See below |
 | Anything else | `unexpected_error` | `init`, `status`, `test` | Re-run with `--verbose` and keep the output |
 
diff --git a/content/docs/brand/cli/quickstart.mdx b/content/docs/brand/cli/quickstart.mdx
index db70aca..26d9a0e 100644
--- a/content/docs/brand/cli/quickstart.mdx
+++ b/content/docs/brand/cli/quickstart.mdx
@@ -2,7 +2,7 @@
 title: CLI Quickstart
 description: Set up your affiliate program in 3 commands with npx affitor.
 kind: quickstart
-last_updated: 2026-10-15
+last_updated: 2026-10-17
 ---
 
 Get your affiliate program running in under 5 minutes -- program creation, Stripe webhooks, and live tracking all from your terminal.
@@ -104,7 +104,7 @@ Choose your payment tracking method: **Server-side tracking vs Stripe integratio
 
 ### Option A: Stripe integration (automatic)
 
-Connect Stripe in the Affitor dashboard: open the program, go to **Settings**, and use **Connect Stripe**. Affitor's own webhook then records sales, renewals and refunds. Add Affitor metadata to your Checkout Session so each sale is attributed; see the [Stripe integration guide](/docs/api-reference/integrations/stripe). The CLI does not connect Stripe (`affitor setup stripe` only points you to the dashboard).
+Connect Stripe in the Affitor dashboard: open the program menu, choose **Program settings**, open **Payments**, and use **Connect Stripe**. Affitor's own webhook then records sales, renewals and refunds. Add Affitor metadata to your Checkout Session so each sale is attributed; see the [Stripe integration guide](/docs/api-reference/integrations/stripe). The CLI does not connect Stripe (`affitor setup stripe` only points you to the dashboard).
 
 ### Option B: Server-side tracking — your backend calls POST /api/v1/track/sale (any payment provider)
 
diff --git a/content/docs/brand/quickstart/setup-program.mdx b/content/docs/brand/quickstart/setup-program.mdx
index 025c7b3..ca13b59 100644
--- a/content/docs/brand/quickstart/setup-program.mdx
+++ b/content/docs/brand/quickstart/setup-program.mdx
@@ -2,7 +2,7 @@
 title: Set Up Your Program
 description: Complete the five setup steps (Business, Commission, Tracking, Payments, Go live) and publish your program on the marketplace.
 kind: quickstart
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 Setup takes your program from created to live in five steps: **Business**, **Commission**, **Tracking**, **Payments** and **Go live**. It opens at the Business step as soon as you [create your program](/docs/brand/quickstart/create-account), at `affitor.com/brand/setup/business`.
@@ -28,7 +28,7 @@ Setup takes your program from created to live in five steps: **Business**, **Com
 
 The top of each step shows **Step N of 5** and **Save and exit**. **Continue** saves the step and opens the next one. **Save and exit** saves Business or Commission first, then opens that page in Settings; the other steps have nothing to save and open their Settings page directly. On a wide screen the step list sits on the left, where a done step shows a check (Business also shows your website, Commission your rate), and **What partners see** previews your program card on the right.
 
-The same five pages are also **Settings** → **Program settings**, so anything you set here stays editable there. Until the program is live, Program settings shows how many of the five steps are done. After launch the pages have no **Back** or **Continue**: **Business** and **Commission** have **Save**, **Payments** has nothing to save, the **Partner link parameter** on **Tracking** saves when you pick it, and **Go live** is named **Status**.
+The same five pages are also **Program settings** (open the program menu and choose **Program settings**), so anything you set here stays editable there. Until the program is live, Program settings shows how many of the five steps are done. After launch the pages have no **Back** or **Continue**: **Business** and **Commission** have **Save**, **Payments** has nothing to save, the **Partner link parameter** on **Tracking** saves when you pick it, and **Go live** is named **Status**.
 
 ## Step 1: Describe your business
 
@@ -41,7 +41,7 @@ The **Business** step (**Your business**) sets what partners see first.
 | **Program URL** | Yes | Your public program page, `affitor.com/marketplace/<handle>`. Lowercase letters, numbers and dashes, up to 48 characters. You can change it later |
 | **Program ID** | Shown, not edited | Used by the tracking script, the API and AI agents. **Copy** copies it |
 | **Logo** | No | PNG, JPG or SVG, square, under 5 MB |
-| **Tagline** | No | In Settings only (**Program settings** → **Business**): one line on your marketplace card, up to 160 characters |
+| **Tagline** | No | In **Program settings** → **Business** only: one line on your marketplace card, up to 160 characters |
 
 **Continue** saves only the fields you changed and moves on once every save succeeds; an error shows under its field. The step is done once the program has a business name and a website.
 
@@ -191,7 +191,7 @@ Once live, the page says your program is live and shows its link with **Copy lin
 
 ## Verify it worked
 
-Open **Settings** → **Program settings** and check that each page kept what you saved:
+In the program menu, choose **Program settings** and check that each page kept what you saved:
 
 <VerifySuccess
   dashboard={[
diff --git a/content/docs/brand/settings.mdx b/content/docs/brand/settings.mdx
index a4e8e81..f20ed4d 100644
--- a/content/docs/brand/settings.mdx
+++ b/content/docs/brand/settings.mdx
@@ -2,7 +2,7 @@
 title: Manage program settings and your API key
 description: Edit your program's terms after launch and find, copy, or regenerate the per-program API key that authenticates your tracking integration.
 kind: guide
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 Everything you configured in the [setup wizard](/docs/brand/quickstart/setup-program) stays editable after launch, and Settings also hold the API key that every server-side [tracking call](/docs/api-reference/overview) authenticates with. This guide shows where each setting lives, how to change terms safely, and how to rotate the key with the shortest possible gap in tracking.
@@ -18,13 +18,13 @@ Everything you configured in the [setup wizard](/docs/brand/quickstart/setup-pro
 
 ## What lives in Settings
 
-Settings belong to the program selected in the program menu. Open the program menu (your program's name at the top of the left menu, or in the top bar on smaller screens) and choose **All settings**. Everything on the Settings pages applies to that program.
+Settings belong to the program selected in the program menu. Open the program menu (your program's name at the top of the left menu, or in the top bar on smaller screens) and choose **Program settings**. The same menu also has **Members** (only for people who can manage members) and **Billing**. Everything on the Settings pages applies to that program.
 
-![The program menu, opened from the program name at the top left: your programs with their status, Create program, then All settings, Team, Billing and Refer a brand](/docs/brand/program-menu.png)
+![The program menu, opened from the program name at the top left, with your programs, their status and Create program](/docs/brand/program-menu.png)
 
 **Program settings** are the same five steps as setup, one page each:
 
-![Settings for one program: the left menu groups Program settings, Developers (API keys), Team (Members), Billing (Invoices), Personal (Your account) and Explore (Refer a brand); Program settings opens Business, Commission, Tracking, Payments and Status, with the Business form on the right](/docs/brand/settings.png)
+![Settings for one program: the left menu with Program settings selected, its pages Business, Commission, Tracking, Payments and Status beside it, and the Business form on the right](/docs/brand/settings.png)
 
 | Page | What you edit there |
 |---------|--------------------|
@@ -41,14 +41,15 @@ The rest of the Settings menu:
 | **Developers** | **API keys** | The per-program secret key for server-side tracking calls, and the line for an AI coding agent |
 | **Team** | **Members** | Who can work on the program |
 | **Billing** | **Invoices** | Platform-fee invoices |
-| **Personal** | **Your account** | Your own profile and sign-in, shared with the partner side |
 | **Explore** | **Refer a brand** | Your link for referring brands to Affitor, **Invite via email**, and the brands you referred ([how it works](/docs/partners/quickstart/get-your-referral-link#refer-a-brand-to-affitor)) |
 
+Your own settings are not part of a program. To change your profile, sign-in or payout details, open the **⋯** menu next to your name at the bottom of the left menu and choose **Your account**: it has **Profile**, **Login and security** and **Payouts**.
+
 ## Step 1: Edit program terms after launch
 
 Programs evolve — rates get adjusted, branding gets refreshed, approval policies tighten or loosen. None of this requires recreating the program.
 
-1. In the program menu, choose **All settings**.
+1. In the program menu, choose **Program settings**.
 2. Open the page you want to change: **Commission** for the rate, hold period and how new partners join, or **Business** for the business name, website, logo and branding.
 3. Make the change and save. On **Commission**, once terms are saved, select **Set new terms** before you change them.
 
@@ -62,7 +63,7 @@ The **Commission** page sets your program-wide default. To pay different rates t
 
 Every server-side call to the tracking API — sales, refunds, and server-mode leads — authenticates with a Bearer token that is unique to your program. Integrations, SDKs, the CLI's tracking setup, and AI agents all use this same key. CLI commands that create or list programs act as your account instead, and authenticate with your CLI login.
 
-1. In the program menu, choose **All settings**.
+1. In the program menu, choose **Program settings**.
 2. Under **Developers**, select **API keys**.
 
 The dashboard displays the key masked, and no read returns the full value. It is revealed exactly once — in the response to an owner's **Generate** or **Regenerate** action on the **API keys** page. If you no longer have the current key stored anywhere, you can't recover it from the dashboard; regenerate it instead (Step 3).
diff --git a/content/docs/brand/tracking/quickstart-integration.mdx b/content/docs/brand/tracking/quickstart-integration.mdx
index e07d75c..09b07f2 100644
--- a/content/docs/brand/tracking/quickstart-integration.mdx
+++ b/content/docs/brand/tracking/quickstart-integration.mdx
@@ -2,7 +2,7 @@
 title: 3-Step Integration Guide
 description: Get Affitor tracking live with the supported click, signup, and server-side tracking flows
 kind: quickstart
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 Three steps get Affitor tracking live: clicks → signups → sales. Steps 1 and 2 establish attribution; step 3 records revenue.
@@ -50,7 +50,7 @@ Once the tracker is live on your public site, Affitor detects it automatically,
 </script>
 ```
 
-Replace `YOUR_PROGRAM_ID` with your program ID (**Settings** → **Program settings** → **Business** → **Program ID**, **Copy**).
+Replace `YOUR_PROGRAM_ID` with your program ID (program menu → **Program settings** → **Business** → **Program ID**, **Copy**).
 
 ### What this does
 
diff --git a/content/docs/faq/index.mdx b/content/docs/faq/index.mdx
index 765bab8..ee023a3 100644
--- a/content/docs/faq/index.mdx
+++ b/content/docs/faq/index.mdx
@@ -2,7 +2,7 @@
 title: "Frequently Asked Questions"
 description: "Common questions about Affitor's pricing, tracking, commissions, and integration options."
 kind: faq
-last_updated: 2026-10-14
+last_updated: 2026-10-17
 ---
 
 Quick answers about Affitor's pricing, tracking, commissions, and payouts, with links to the full guides where you need more depth.
@@ -27,7 +27,7 @@ Affitor differentiates on:
 ## Accounts
 
 ### Can I use a personal email address to sign up?
-Yes, but a business email is recommended for team management — a shared address like `partnerships@yourcompany.com` keeps access simple as the team grows. You can update your email later in account settings.
+Yes, but a business email is recommended for team management: a shared address like `partnerships@yourcompany.com` keeps access simple as the team grows. Your sign-in email is shown read-only in **Your account** → **Profile** (the **⋯** menu next to your name).
 
 ### Is there a cost to create an advertiser account?
 No. Creating an account is free. The platform fee is $0 until your program earns its first $10,000 through affiliates, then 3.5% on affiliate-driven sales only.
diff --git a/content/docs/support/glossary.mdx b/content/docs/support/glossary.mdx
index 7afabe1..1aa3b80 100644
--- a/content/docs/support/glossary.mdx
+++ b/content/docs/support/glossary.mdx
@@ -2,7 +2,7 @@
 title: Glossary
 description: Common terms used across Affitor docs — server-side tracking, Stripe integration, invoice billing, and more
 kind: reference
-last_updated: 2026-10-16
+last_updated: 2026-10-17
 ---
 
 ## A
@@ -58,7 +58,7 @@ A pricing model where fees are tied to partner-generated revenue rather than a m
 Affitor's fee on partner-generated revenue: $0 until a program's affiliate-driven revenue reaches $10,000, then 3.5% of each affiliate-driven sale. The threshold is counted per program.
 
 ### Program ID
-The identifier for your Affitor program. It is used in tracker setup, test flows, and Stripe metadata. Find it under **Settings** → **Program settings** → **Business**, where **Program ID** is shown with **Copy**.
+The identifier for your Affitor program. It is used in tracker setup, test flows, and Stripe metadata. Find it in the program menu under **Program settings** → **Business**, where **Program ID** is shown with **Copy**.
 
 ## R