Settings overview

Settings has nine tabs. General, Security and Notifications are open to everyone. Buyer Portal, Email, Integrations, Developers and Team are open to owners and admins. Billing is owner-only. Tabs your role can't open don't appear at all.

Each tab has its own URL (/settings#team, /settings#billing…), so you can bookmark or share a direct link. /settings#sender-domains still works — it opens Email on the Sender domains section — and /settings#email-branding opens the other one.

Inviting teammates

Team → Invite Member, enter the email address and pick a role:

• Admin — runs the account day to day: pipelines, buyers, leads, disputes, sender domains and integrations. Sees the team list but can't change it, and can't see billing.
• Member — read-only access to all data.

Invitations expire after 7 days and count against your plan's user limit while pending, so cancel the ones that go unanswered. Owners can change a member's role from the table at any time, or remove them. The owner role itself can't be reassigned from this screen.

The organization timezone

General → Timezone is the wall clock your workspace reads its own data in. It decides where every day starts on the dashboard — cards, chart and comparisons — and how times are displayed in the activity log. Owners and admins can change it; it defaults to UTC and doesn't affect how buyers' operating hours or caps are evaluated — those keep their own timezone on each buyer.

Email branding

Email → Branding is the same card as Buyer Portal → Branding: one brand, two surfaces. The business name, logo and accent colour you set in either place dress both your buyer portal and every lead email — set them once, and a rebrand is one change, not two.

What each one does to an email: the name and the logo sit at the top, the accent colour paints the header band and the "View in portal" button. Without a logo the name is printed instead, which is also what a buyer sees when their mail client blocks images.

One field is email-only: the footer. It closes every lead email under a thin rule — a postal address, a contact line, a legal mention. Up to 2000 characters, line breaks kept, and it goes into both the HTML and the plain-text part of the message. Leave it empty and the email simply ends after its content.

The preview below the fields is rendered by the same code that sends the real thing, on a sample lead, and it updates as you type. Nothing reaches a buyer until you press Save branding.

LeadMove is named nowhere in any of it. The email is white-label, exactly like the portal.

The shared-domain banner

Until your organization verifies a sending domain, lead emails leave on LeadMove's shared address, and a banner says so on the email delivery editor and on the buyer's Settings tab. It reads the real chain, not a rough guess: a buyer pointing at its own verified domain, or a delivery method with its own From address, doesn't get the banner. Verify a domain in Email → Sender domains and it disappears on its own — full walkthrough in email deliveries and sender domains.

The account dispute window

General → Dispute window sets, in hours, how long a buyer has to contest a delivered lead. It defaults to 48 and accepts 1 to 720. Only owners can change it, and it applies to every buyer that doesn't override it on its own Disputes card — the same card that caps how often a buyer may dispute. Full precedence rules in how disputes work.

AI features

General → AI features decides which AI models may process your organization's data. Two independent switches, both on by default, both owner and admin only. Everyone can read them.

AI lead scoring — scores every incoming lead 0-100 and grades it A-D. The authenticity part of the score comes from an AI model (OpenAI) that reads the fields your pipeline collects. Turned off: no lead data reaches an AI model, new leads carry no score or grade, and score and grade leave the rule and pricing builders, the merge-code pickers and the leads-list filter. Email and phone validation keeps running — those are local checks. You cannot turn it off while an active routing rule or a buyer's price rules still read the score or grade; the card lists what to change first. Full detail in how scoring works.

AI assistant — the in-app assistant (⌘I) that answers questions about your pipelines, buyers and leads. Names, emails and phone numbers never reach the model (Anthropic); other lead fields can. Turned off: it is hidden for everyone in your organization. See the AI assistant.

Common questions

Can I rename my organization? Not from Settings — the name and ID fields are read-only. The name buyers see in their portal and on their lead emails is separate, and lives in Branding, on either the Buyer Portal or the Email tab.

I set my logo for the portal. Do I have to set it again for emails? No. It is one brand: the Branding card is the same on both tabs, and emails and the portal read the same name, logo and colour.

Why can't I see Billing? Billing is owner-only — the owner holds the payment method and the plan. If you land on /settings#billing without the owner role, you're sent back to General. The same happens on any tab your role can't open.

I'm an admin. Why can't I invite anyone from Team? By design: admins run the account, owners decide who's in it. You can see the members, roles and pending invitations, but inviting, changing a role and removing someone stay with the owner.

Team says it needs an active plan — why? Invitations are gated on an active subscription. Reactivate or change your plan in Billing, then invite.

Do teammates share my notification settings? No. Notification preferences are per user; each teammate sets their own.

Can I request an integration that isn't listed? Yes — the Integrations tab has a "let us know" link that opens chat with the team.