Loading tutorials…
Loading tutorials…
Salesforce is the most powerful CRM on the market and the easiest to misconfigure in week one. Most owners blow past the org-wide sharing settings, hand out System Administrator profiles like candy, and end up rebuilding 90 days in. Here is the setup sequence that holds up.
Who this is forFounders, RevOps leads, and operations owners standing up a new Salesforce org — or anyone who bought Sales Cloud licenses 60 days ago and is staring at a blank Lightning Experience wondering where to start. If your org already has 5+ users and you cannot remember which profile each got, this tutorial is for you.
What you'll need
Step 1
Default Time Zone, Default Locale, Currency, and Fiscal Year are org-wide. Changing them after data exists creates years of reporting drift.
Open Salesforce → Setup (gear icon, top-right) → Company Settings → Company Information.
Edit and set: Organization Name, Primary Contact, Default Locale (controls date/number formats), Default Language, and Default Time Zone. Time Zone is the one that bites later — it controls how every report rolls up days, weeks, quarters.
Setup → Company Settings → Fiscal Year. Pick Standard or Custom Fiscal Year, then set the month your fiscal year starts. This drives every quarterly forecast. Default is January — change if your fiscal year does not match.
Setup → Company Settings → Manage Currencies (if multi-currency is on). Set the corporate currency. If you sell in multiple, enable Multiple Currencies first — but only if you genuinely need it, because it cannot be cleanly turned off.
Setup → Company Settings → Business Hours. Used by Service Cloud SLAs, escalation rules, and approval reminders. Set your default business hours even if you do not use Service Cloud yet.
Step 2
Setup → Security → Sharing Settings. Pick Private vs Public Read Only vs Public Read/Write for each object. This is the single hardest-to-change decision in Salesforce.
Open Setup → Quick Find → "Sharing Settings."
For each standard object (Account, Contact, Opportunity, Lead, Case), set the Organization-Wide Default (OWD).
Most B2B sales orgs run: Account = Public Read Only, Contact = Controlled by Parent, Opportunity = Private, Lead = Private, Case = Private. Private means only the owner + their management chain see the record; sharing rules and roles open it up from there.
If you set OWD too permissive (Public Read/Write everywhere) you cannot tighten later without breaking existing access. If you set it too restrictive (Private everywhere) reps will complain they cannot see anything — but you can open it up with sharing rules.
Document your sharing model in a one-page doc that lives outside Salesforce. Future-you in 12 months will not remember why Opportunity is Private and Account is Public Read Only.
Step 3
Role Hierarchy drives record visibility upward. Profiles control object/field permissions. Permission Sets layer additional access. Use all three deliberately.
Setup → Users → Roles. Build a Role Hierarchy that matches your real org chart: CEO at the top, then VP Sales, then Sales Manager East/West, then AE/SDR underneath.
Role Hierarchy controls "rollup" record visibility — a manager sees everything their reports own, automatically. This is independent of Profile permissions.
Setup → Users → Profiles. Clone the Standard User profile to create custom profiles: Sales Rep, Sales Manager, RevOps, Marketing, Read-Only. Never give standard System Administrator to anyone except 1-2 actual admins.
For each custom profile: Object Settings → set Read/Create/Edit/Delete per object. Tab Settings → control which tabs the profile sees. App Permissions → toggle major capabilities.
Setup → Users → Permission Sets. Create reusable permission bundles that add capability on top of a profile: "Export Reports," "Modify All Data — Opportunity," "API Access," "View All Forecasts." Assign Permission Sets to individual users rather than embedding all that capability in a Profile.
Rule: minimum-viable Profile + targeted Permission Sets > one mega-Profile per role. Permission Sets are easier to audit and revoke.
Step 4
Setup → Users → New User. Match each user to their actual license, profile, and role. Salesforce licenses are expensive — get this right.
Setup → Users → Users → New User.
Enter First Name, Last Name, Email, Username (usually email + a suffix), Profile, Role, and License Type.
License Type matters financially: Salesforce (Sales Cloud) is the full license. Salesforce Platform is cheaper but cannot see Leads/Opportunities/Cases. Identity is sign-on only. Pick deliberately — at $80-150/user/mo for Sales Cloud Pro, picking wrong on 5 users is $400-750/mo wasted.
Assign the Profile you built. Assign the Role from the hierarchy. Set Time Zone, Locale, Language per user.
Save. The user receives a welcome email and must verify within 7 days. Stale invites do not consume the license until activated, but the seat is reserved.
After activation, log in as the user (Setup → Users → user record → Login link, if available with your edition) and verify their access. Look for over-access (they can see Opportunities they should not) or under-access (they cannot create a Lead).
Step 5
Setup → Object Manager → object → Page Layouts. This controls what reps see when they open an Account, Contact, Lead, or Opportunity. Defaults are noisy.
Open Setup → Object Manager → Account → Page Layouts → Account Layout.
Drag the most-used fields to the top of the layout: Account Name, Account Owner, Industry, Annual Revenue, Number of Employees, Phone, Website, Type.
Remove fields nobody uses. The default Account layout has ~40 fields most teams never touch — half of them inherited from older Salesforce versions.
Setup → Object Manager → object → Compact Layouts. This controls what shows in the highlights panel at the top of the record. Pick 4-7 fields max: Name, Owner, Phone, Industry, Annual Revenue.
Repeat for Contact, Lead, and Opportunity. Each object needs deliberate Page Layout + Compact Layout work, or reps drown in noise.
If you use Record Types (multiple Lead processes, multiple Opportunity sales motions), assign different Page Layouts per Record Type per Profile. This is the right pattern for B2B + Channel mixed motions.
Step 6
Setup → User Interface. Salesforce ships with Chatter, Quick Actions, and a dozen optional features enabled. Turn off what you do not use; enable Trailhead-recommended defaults.
Setup → Feature Settings → Chatter → Chatter Settings. Decide: are you actually going to use Chatter for internal communication? If no, you can disable Chatter feeds on records to reduce noise. Most B2B orgs leave Chatter on but disable Email-to-Chatter.
Setup → User Interface → Quick Actions. Configure the global publisher actions (Log a Call, New Task, New Event, New Note) and the object-specific actions (New Opportunity, Convert Lead).
Setup → User Interface → Themes and Branding. Upload your company logo and set brand colors. This shows in the Lightning header for every user.
Setup → User Interface → Lightning App Builder. Configure the Sales Console app or build a custom Lightning App for your sales team — different sales motions need different navigation tabs.
Setup → Feature Settings → Sales → Activity Settings. Enable Shared Activities (a contact can be linked to multiple Opportunities via Activity), enable Email Tracking, enable Activity Timeline. These are off by default in some editions and they matter for adoption.
Step 7
Setup → Identity → Identity Verification. MFA is mandatory for all Salesforce orgs since 2022. Configure login IP ranges and session timeouts intentionally.
Setup → Identity → Identity Verification. Enable Multi-Factor Authentication for all users. This is required by Salesforce contractually — non-MFA logins are blocked.
Setup → Security → Session Settings. Set session timeout (default 2 hours; most teams use 4-8 for productivity, but tighten for finance/admin users). Enable "Force logout on session timeout."
Setup → Security → Network Access. If your team works from fixed offices or VPN, add Trusted IP Ranges. Logins from outside these ranges require Identity Verification every time.
Setup → Security → Password Policies. Set minimum password length (12+), complexity requirements, password expiration (90 days is common), and account lockout after failed attempts.
Document the security model. SOC 2 / ISO audits will ask for evidence of password + session policies. Easier to document at setup than reconstruct later.
Common mistakes
Inviting users with System Administrator profile to "just get started"
What goes wrong: Every rep can delete fields, archive records, and modify validation rules. Within 60 days someone deletes a custom field that 3 reports depend on. You are paying $1,500/mo for 10 Sales Cloud Pro seats and the data trust is already broken.
How to avoid: Build custom profiles (Sales Rep, Sales Manager, Marketing, RevOps) before inviting users. Reserve System Administrator for 1-2 actual admins. Use Permission Sets for incremental capability.
Leaving Org-Wide Defaults at Public Read/Write
What goes wrong: Reps can edit each other's Opportunities. AE-East accidentally changes AE-West's Close Date to next quarter. Forecast accuracy drops to 60% because nobody trusts the numbers. Reports show a 30% revenue gap due to data being silently overwritten by the wrong owner.
How to avoid: Setup → Sharing Settings → set Opportunity and Lead to Private. Use Sharing Rules to open visibility where genuinely needed. Document the model.
Skipping fiscal year configuration
What goes wrong: Default fiscal year is January-December. Your company runs July-June. Every quarterly report is wrong for 4 quarters before someone notices. Board meetings reference numbers that do not match accounting. Rep adoption drops to 20% after 90 days because they stop trusting the dashboards.
How to avoid: Setup → Company Settings → Fiscal Year → set Custom or change start month. Do this BEFORE any Opportunity data exists, or recalculations are messy.
Buying Sales Cloud licenses for users who only need Platform
What goes wrong: You give 8 marketing/ops/exec teammates Sales Cloud Professional at $80/user/mo 'just in case.' That is $640/mo extra. Most never touch Opportunities. Six months later you have spent $3,840 on unused capability.
How to avoid: Audit who actually works Opportunities daily. Move marketing/ops users to Salesforce Platform license ($25/user/mo) or Identity. Save the Sales Cloud seats for AEs/SDRs.
Customizing Page Layouts inconsistently per user
What goes wrong: Every rep sees a different field order. Trainings break ("the Close Date field is third from the top" — but it is seventh for half the team). New hires onboard 40% slower because the UI is non-standard.
How to avoid: Setup → Object Manager → object → Page Layouts. Assign one layout per Profile + Record Type. Users can collapse sections but not reorder fields.
Enabling Multi-Currency without needing it
What goes wrong: You toggle Multi-Currency on because 'we might sell internationally one day.' Every Opportunity, Quote, and Product now requires a Currency value. Reports become harder to read. Disabling Multi-Currency requires a Salesforce support ticket and is not always possible.
How to avoid: Leave Multi-Currency OFF unless you genuinely transact in 2+ currencies today. Add it later — it is enableable on demand, but very hard to remove.
Recap
Done — what's next
How to set up Salesforce Leads, Contacts, and Opportunities without confusing your reps
Read the next tutorial
Hand it off
A clean Salesforce setup pays dividends for years. A messy one creates a Saturday-cleanup job every quarter and a 60-day rebuild every time you switch admins. A vetted Salesforce-capable specialist will run the entire setup — org defaults, OWD, profiles, page layouts, security — typically as a $400-800 one-shot engagement, or ongoing admin support at $400-1,200/mo at $14-16/hr.
See specialist rates
Professional ($80/user/mo) covers most B2B teams under 25 reps: standard objects, basic automation, basic forecasting. Enterprise ($165/user/mo) adds: advanced workflow (Flow Builder full capability), more custom objects, advanced reporting, Web-to-Lead, and unlimited Roles in the hierarchy. Most teams hit Enterprise around 30-50 reps or when they need API access for integrations. Start Professional; upgrade when a specific feature gates real work.
Lightning Experience is the modern UI Salesforce ships as default since 2019. It is the same underlying data model and platform — same Accounts, Contacts, Opportunities, same Apex backend — but with a redesigned UI, Lightning App Builder (drag-and-drop record pages), Lightning Components, and Einstein AI integration. Classic is sunset; new orgs are Lightning-only. If you inherit a Classic-only org, plan a Lightning migration — Trailhead has a Lightning Experience Readiness Check tool.
Sales Cloud is built around Leads → Opportunities → Closed Won (the sales motion). Service Cloud is built around Cases → SLAs → Resolution (the customer-support motion). Both share Accounts and Contacts. Most teams start with Sales Cloud and add Service Cloud licenses for support reps when they need ticket queues, SLAs, knowledge base, and omnichannel routing. The data model is unified; the licenses are separate.
Yes. Salesforce's Data Import Wizard (Setup → Data → Data Import Wizard) handles CSV imports for Accounts, Contacts, Leads, and Custom Objects up to 50,000 records. For larger or more complex migrations (100,000+ records, lots of history, custom fields), use Data Loader (free desktop tool) or a partner. DIY migration over 10,000 records typically loses 5-15% of data quality without careful field mapping and dedup discipline.
A solo founder with a 1-2 person team can finish org-level setup in 8-12 hours. A 10-person sales team with custom profiles, Page Layouts, and integrations is 1-2 weeks of focused work. A 50-person organization with multiple sales motions, Record Types, and Apex automation is a 2-3 month project — usually run by a certified Salesforce admin or consultancy.
Salesforce
The Lead-Contact-Opportunity distinction is the single most-confused concept in Salesforce. Get it wrong and your reports double-count revenue, your reps work duplicate records, and Marketing keeps emailing people who already closed. Here is the discipline that holds up at scale.
Salesforce
A Salesforce pipeline is the most-referenced screen in the entire platform. Set up wrong, the forecast is fiction and reps stop trusting it. Set up right, the CRO walks into Monday with a real number. Here is the discipline that holds up.
Salesforce
Salesforce automation has had three eras: Workflow Rules, Process Builder, and now Flow Builder. As of 2026, Workflow Rules and Process Builder are being retired — Flow Builder is the only path forward. Most owners are still building Process Builders that will break in 12 months. Here is the discipline.
HubSpot CRM
HubSpot's Smart CRM is free, fast to spin up, and easy to break in the first month. Most owners skip the account-level defaults, invite users with the wrong permission sets, and end up rebuilding 60 days in. Here is the setup sequence that holds up.
Salesforce
DIY Salesforce admin is a great idea — until it is not. This is the honest framework: when the cost of self-managing exceeds the cost of hiring, and how to tell which side you are on.