Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 36 ยท Getting Started

The Admin Role, Salesforce Releases and Certifications

Understand the daily work of a Salesforce administrator, the three yearly releases, sandbox testing, change management and the Administrator certification path.

Salesforce administration is part technical job, part business analysis, and part support desk. This lesson describes what the job really consists of, how Salesforce updates your org three times a year, how to test and release changes safely, and how to prepare for the Administrator certification.

A day in the life

A typical admin's week mixes small requests with planned projects:

  • Requests: "Please add Mexico to the Country picklist." "Why can't Dana see this report?" "Can we get an alert when a deal passes $50,000?"
  • Operations: onboarding and offboarding users, resetting passwords, watching email and storage limits, reviewing failed flows.
  • Projects: a new sales process, a data clean-up, integrating a billing system.
  • Governance: deciding what is worth building and how to document it.

The skill that separates good admins is requirements gathering: turn "I need a button" into "what decision does the user make, and what information do they need at that moment?" The answer is often a field, a validation rule or a report, not a button.

The admin as translator

Admins sit between business users and developers. Learning vocabulary on both sides helps: sales talk about pipeline and quota, while developers talk about triggers and APIs. You speak both.

The three releases a year

Salesforce updates every org on a fixed schedule: Spring, Summer and Winter releases (roughly February, June and October). You do not install anything; Salesforce upgrades the service for everyone, and features arrive in your org according to the release schedule.

What an admin does around a release:

  1. Preview: sandboxes are usually upgraded earlier than production. Test your key processes there.
  2. Read the release notes: look for items that affect your org, such as retirements and new defaults.
  3. Watch for "Release Updates": Setup > Release Updates lists changes that are optional for a while and then get enforced by a date. Test them in a sandbox before the deadline.
  4. Enable new features deliberately: some arrive turned off, so you choose when to adopt.
  5. Communicate: tell users what changes.

Subscribe to the release notes for your clouds and keep a simple checklist of the five or six processes that must work on Monday morning (create a lead, convert it, log a case, run the pipeline report). Run that checklist in the preview sandbox.

Sandboxes and safe change management

Never experiment in production. A sandbox is a copy of your org's configuration (and sometimes data) where you can test. Types, from smallest to largest:

Sandbox Contains Refresh interval Typical use
Developer Metadata only, small storage Daily Building and unit testing
Developer Pro Metadata only, more storage Daily Larger development and testing
Partial Copy Metadata plus a sample of data Every 5 days User acceptance testing
Full Metadata plus all data Every 29 days Final staging, performance tests

The exact allowances depend on your edition and contract, and refresh intervals can change, so check Setup > Sandboxes in your org.

A simple, safe change process:

flowchart LR
    R["Request"] --> D["Design and document"]
    D --> B["Build in dev sandbox"]
    B --> T["Test and user acceptance"]
    T --> P["Deploy to production"]
    P --> V["Verify and tell users"]

Even a small team benefits from a build-test-deploy path. Chapter 8 covers the deployment tools.

Each step is cheap compared with fixing a mistake in production.

A tiny change log

Keep a log. This stand-in shows a changelog that refuses entries without a reason, a habit worth copying in a spreadsheet or wiki.

Python Stand-in: a change log that requires a reason

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Release timing helper

Because three releases arrive every year, you can predict where you will be. This stand-in lists the release names in order and finds the next one for a given month. The months are the usual pattern, not a promise: always check the official release schedule.

Python Stand-in: which release comes next?

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Certifications

Salesforce offers role-based certifications. For admins the foundation is the Salesforce Certified Administrator exam. Typical facts (confirm on the official certification page, because details change): it is a proctored, multiple-choice exam with a time limit of about two hours, a passing score of roughly 65 percent, and domains such as Configuration and Setup, Object Manager and Lightning App Builder, Sales and Marketing Applications, Service and Support Applications, Productivity and Collaboration, Data and Analytics Management, Workflow/Process Automation.

Later paths include Advanced Administrator, Platform App Builder, Sales Cloud Consultant, Service Cloud Consultant, Platform Developer I and others. Maintenance is done through short online modules on a yearly basis.

Study advice:

  • Do the hands-on work in your own org; the exam asks "which tool do you use" questions, and you answer better after doing it once.
  • Learn the order of execution and the differences between profiles, permission sets, roles and sharing rules.
  • Practice reports: summary vs matrix, filters, bucket fields, joined reports.
  • Use Trailhead trails and the official exam guide as your syllabus; this course follows the same areas.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. How often does Salesforce deliver major releases?

    Salesforce ships Spring, Summer and Winter releases each year.
  2. 2. Which sandbox type copies metadata plus all of the production data?

    Only a Full sandbox contains all data, which also makes it the slowest to refresh.
  3. 3. Why test in a preview sandbox before a release reaches production?

    Sandboxes upgrade earlier, so you can run your key processes and fix surprises ahead of time.
  4. 4. What is Setup > Release Updates used for?

    Release Updates let you opt in early and test before a change becomes mandatory.

Summary

  • Admin work is requirements gathering, configuration, operations and governance.
  • Salesforce upgrades every org three times a year; preview in a sandbox and read the notes.
  • Use sandboxes and a build-test-deploy habit, and keep a change log.
  • The Administrator certification is the standard starting goal; practice in a real org.

Next: CRM Fundamentals: Sales, Service and Marketing