Salesforce Admin cheat sheet
Salesforce Admin · Keep the key ideas within reach.
Configuration and Setup
Company Information controls the org's default locale, currency, fiscal year, and storage usage.
Each user has exactly one profile; profiles set baseline object and field permissions and login restrictions.
Permission sets grant additional permissions without changing the profile; users can have multiple permission sets.
Organization-wide defaults set baseline record access: Private, Public Read Only, Public Read/Write, or Public Read/Write/Transfer for cases and leads.
The role hierarchy grants record access upward from the owner when OWD is Private or Public Read Only; it does not override Public Read/Write.
Login IP ranges and login hours are profile-level controls; trusted IP ranges are org-level and affect login challenges.
Sandbox types are Developer, Developer Pro, Partial Copy, and Full; refresh intervals and data included differ.
Delegated administration lets an admin assign selected admin tasks, such as user management, to non-admin users.
Session settings set org-wide timeout, clickjack protection, and caching; they apply to all users.
Object Manager and Lightning App Builder
Object Manager manages standard and custom objects, fields, relationships, page layouts, record types, and buttons.
Master-detail relationships make the child dependent on the parent, inherit ownership, and support roll-up summary fields.
Lookup relationships are loosely coupled; they allow reparenting, do not cascade delete, and do not support roll-up summaries.
Roll-up summary fields on a master-detail parent calculate COUNT, SUM, MIN, or MAX from detail records.
Formula fields are calculated when read, are not stored, and cannot be edited directly.
Record types control available picklist values and page layout assignments for different business processes.
Lightning App Builder builds app, home, and record pages; activation controls which users see the page.
Dynamic Forms show or hide fields based on record data and require Lightning record pages and field-level security.
Page layouts control field placement and buttons; field-level security controls whether a user can see or edit a field.
Sales and Marketing Applications
Lead conversion creates an account, contact, and optionally an opportunity; converted leads become read-only.
Web-to-Lead creates leads from website forms; CAPTCHA can be enabled and assignment rules can route leads.
Campaign members link leads or contacts to campaigns; response statuses track engagement and ROI.
Products are tied to pricebooks through pricebook entries; every product needs a standard pricebook entry.
Opportunity stages map to sales processes and carry probability and forecast category values.
Quotes and quote line items support sales pricing; syncing quotes can update opportunity line items.
Forecasting uses opportunity amounts, close dates, stages, and forecast categories; quotas set targets.
Lead assignment rules assign leads to users or queues; active rule order determines the first match.
Service and Support Applications
Case assignment rules assign new cases to users or queues; active rule order determines the match.
Escalation rules escalate cases by age or criteria; actions can reassign and notify.
Entitlements define support terms; milestones track time-based SLA targets on cases.
Omni-Channel routes cases and other work items to agents by capacity and skills.
Knowledge articles use draft, review, and published states; suggested articles can appear on cases.
Web-to-Case and Email-to-Case create cases from web forms and email; On-Demand Email-to-Case reduces email agent load.
Service contracts and entitlements link support terms to accounts and cases.
Macros and quick text speed up case responses in the service console.
Productivity and Collaboration
Chatter feeds show posts, comments, and likes; users follow people, groups, and records.
Chatter groups can be public, private, or unlisted; membership controls feed visibility.
Tasks and events are activities; shared activities let one activity relate to multiple records when enabled.
Salesforce Files stores files and shares them with records, groups, and users; content libraries organize files.
Email templates store reusable content with merge fields for mass email, workflows, and flows.
The Salesforce mobile app provides Today, notifications, and record access on mobile devices.
Desktop notifications alert users to Chatter and approval items; they are configured per user.
Lightning Sync and Einstein Activity Capture connect email and calendar data to Salesforce.
Data and Analytics Management
Data Import Wizard imports up to 50,000 records and supports standard objects and simple custom objects.
Data Loader handles bulk import and export via CSV and supports insert, update, upsert, and delete.
Duplicate rules alert or block duplicate records; matching rules define how records are compared.
The Recycle Bin restores deleted records for 15 days; deleted records count toward storage until purged.
Report formats include tabular, summary, matrix, and joined; report type defines the underlying objects and fields.
Dashboards display report data in components; a dashboard can have up to 25 components.
Field History Tracking stores changes to selected fields; Setup Audit Trail tracks configuration changes.
Weekly Data Export provides a backup of org data; it must be scheduled by an admin.
Automation
Workflow rules automate field updates, tasks, email alerts, and outbound messages; actions can be immediate or time-dependent.
Process Builder uses criteria and actions; it can invoke flows and is an older automation tool.
Record-triggered flows run before or after save on create, update, or delete; before-save flows can update the triggering record without extra DML.
Screen flows collect user input; autolaunched flows run without user interaction and can be called by other automation.
Approval processes route records to approvers and can lock records during approval.
Scheduled flows run at specified times and can process batches of records.
Flow resources include variables, formulas, choices, and constants; they store and transform values.
Before-save record-triggered flows run before the record is committed; after-save flows run after commit and can access the record ID.