Team → Settings is the index of every configuration screen. Most can wait. Four are worth doing on day one, and doing them in this order saves rework.
Day one, in order
1. Company settings
Name, logo, address, currency and timezone. The last two are not cosmetic: currency formats every monetary value in the product including conversion values sent to Google and Meta, and timezone decides what "today" and "overdue" mean everywhere.
Setting the timezone wrong means task reminders fire at the wrong local time and your dashboard's "today" is somebody else's. Do this before anyone starts using the CRM in anger. See company settings.
2. Pipeline stages
Not strictly under Settings, but it belongs in day one. Your stages define what every conversion rate in the product means and which lead movements report conversions to your ad platforms. Changing them later is possible; changing them after you have three months of data is a nuisance. See pipeline stages.
3. Users and roles
Add your team and give each person a role. Roles decide what people can see and do from the moment they log in — there is no separate onboarding step. See adding team members.
4. SMTP
Connect your own mail provider so the CRM sends from your domain. Without it, receipts, reminders and password reset codes go out through a shared path that spam filters increasingly distrust — including the reset code you will eventually need. See configuring SMTP.
The one people skip and regret: SMTP. It feels optional right up until somebody is locked out and the reset email is in a spam folder nobody checks. Ten minutes on day one.
Configure when you need them
- Custom fields — extra fields on leads. Add them before you start capturing data you care about, so it lands in a real field rather than the unstructured bucket.
- Storage — where uploads live. Local works fine; move to S3 when disk becomes a constraint.
- WhatsApp — sending messages from a lead record.
- Integrations — analytics and pixel IDs for your own site.
- Google Ads / Meta — conversion reporting. Worth doing early if you run ads, since it is the thing this product exists for.
- Webhooks and API keys — for pushing leads out or letting other systems push them in.
- Billing — plan, invoices, payment history.
A note on order
The temptation is to start with the integrations, because they are the interesting part. It is worth resisting: conversion reporting depends on your pipeline stages being right, and connecting Google Ads before deciding what "Won" means produces a working integration reporting the wrong thing.
Stages first, then integrations. It is fifteen minutes either way, and only one order avoids doing it twice.