Salesforce Admin Tasks: A Daily, Weekly and Monthly Checklist

Calendar-style checklist of daily, weekly and monthly Salesforce admin tasks, with automated tasks marked by a gear icon

Salesforce admin tasks are the recurring jobs that keep an org secure, clean and ready for the next release: reviewing who changed what in Setup, checking logins, managing users, backing up data and preparing for each Salesforce release. The short answer to "what does an admin do every week?" is a checklist split by cadence, where some tasks run on a schedule inside Salesforce and others need a person to read the results and decide.

This guide gives you that checklist. Each task names the Setup page to use, the limit Salesforce documents for it, and whether you can automate it with a tool Salesforce already ships. Use it as a starting point and trim it to the size of your org.

Why a cadence beats a to-do list for Salesforce admin tasks

Most admin work arrives as requests: a new user, a picklist value, a broken report. The maintenance work never arrives as a request, so it slips. A cadence fixes that by tying each check to a day, a week or a month, and it also protects you from limits that quietly delete history. Salesforce keeps some records only for a set time, so a check you skip for too long can become a check you can never run.

Two examples show why timing matters:

  • Setup Audit Trail. The SetupAuditTrail object reference says it "represents changes you or other admins made in your org's Setup area for at least the last 180 days." Salesforce's Security Guide adds that after 180 days, setup entity records are deleted.
  • Login History. The same guide says the Login History page shows up to 20,000 records of user logins for the past 6 months, and that you can download the information to a CSV or GZIP file to see more records.

If you only look at either page when something goes wrong, the evidence may already be gone. A monthly download keeps it.

Daily Salesforce admin tasks

Daily tasks are short. The goal is to catch problems while they are small.

  • Work the request queue. Password resets, locked users and access questions come first, because they block people from working. The Trailhead user management unit starts from Setup: in the Quick Find box, enter Users, and then select Users. From there you can reset passwords for selected users. Automatable: partly. The steps repeat, but access decisions stay with a person.
  • Check failed scheduled work. If your org runs scheduled Apex or batch jobs, open Scheduled Jobs and Apex Jobs from Quick Find. The Apex Scheduler documentation points to the Scheduled Jobs page to monitor or stop a scheduled job. Automatable: the jobs are automated; reading the failures is not.
  • Glance at API usage. Integrations that run out of API calls stop working. The Salesforce limits quick reference says you can see usage in the API Usage section of the System Overview page in Setup. Automatable: no native schedule is documented, so this stays a quick manual look.

Weekly Salesforce admin tasks

Weekly tasks look for changes you did not expect and data that is drifting.

  • Review the Setup Audit Trail. The Security Guide gives the path: from Setup, in the Quick Find box, enter View Setup Audit Trail, and then select View Setup Audit Trail. The page shows the 20 most recent setup changes. To see the full history for the past 180 days, click Download. Look for changes nobody told you about, especially to profiles, permission sets and sharing. Automatable: no. Reading the trail is judgment work.
  • Confirm the weekly backup ran. Trailhead's Export Data unit gives the path: from Setup, enter Data Export in the Quick Find box, then select Data Export and Export Now or Schedule Export. It allows an export once every 7 days for weekly export or 29 days for monthly export, and the zip files are deleted 48 hours after the email is sent. Weekly exports are available in Enterprise, Performance and Unlimited Editions. Automatable: yes, with Schedule Export. Downloading and storing the files before they expire is still your job.
  • Clean up data hygiene exceptions. Open opportunities with past close dates, leads with no owner activity and records missing key fields all pile up. This is the best candidate for automation, and the worked example below shows how.
  • Review new and changed users. Check who joined, who changed role and who left. Trailhead explains the difference between freezing and deactivating: both actions prevent the user from logging in, "but freezing user accounts doesn't make their user licenses available in your organization." Freeze when you need to stop access right away, then deactivate when the person has left. Trailhead also notes that you can deactivate users, but you can't delete them.

Monthly Salesforce admin tasks

Monthly tasks look at security posture, history you could lose, and the next release.

  • Run Health Check. The Security Guide path is: from Setup, in the Quick Find box, enter Health Check, and then select Health Check. Your score compares your security settings with a baseline of recommended values for High-Risk, Medium-Risk, Low-Risk and Informational settings. If you change settings to be less restrictive than the baseline, the score and grade decrease. Our post on signs your Salesforce org needs a health check covers what to do when the results look bad. Automatable: no documented schedule. Fix Risks does not cover every setting, so some changes are manual.
  • Download Login History. Because the page covers six months and 20,000 records, a monthly download gives you a complete record. Look for logins from unexpected places and accounts that should be inactive. You need the Monitor Login History or Manage Users permission.
  • Download the Setup Audit Trail. Do this at least every few months so nothing ages past 180 days without a copy.
  • Review release updates. The Salesforce Admins blog post Be Release Ready warns that release updates are not optional forever: each one flips automatically after its enforcement date. Test the ones due soon in a sandbox, then activate them on your schedule rather than Salesforce's.
  • Check field history coverage. The Security Guide says that when Field Audit Trail is turned off, Salesforce retains field history data for up to 18 months, and up to 24 months through the API. If you need older history for audits, export it before it ages out.
  • Check storage and licenses. Compare data and file storage and active user licenses with what your contract allows, so a renewal or a large import does not surprise you.
  • Replace Optimizer reviews with Org Check. Older checklists still tell admins to run Salesforce Optimizer. The Salesforce Admins blog post Optimizer Is Sunsetting: Learn How To Use Org Check says Optimizer was retired in the Winter '26 release and walks through the alternative.

Quarterly and release-cycle tasks

Some admin work follows the release calendar rather than the month. Before each release, refresh a sandbox, read the release notes for the features you use and run your most important processes end to end. When you move tested changes to production, a step-by-step change set deployment keeps the release repeatable. Once a quarter, also review permission sets and profiles against what each team actually needs, and remove access nobody uses.

How to automate a weekly admin task with a schedule-triggered flow

Data hygiene checks are the easiest Salesforce admin tasks to hand to Salesforce itself. A schedule-triggered flow runs on a timetable and works through the records that match its conditions. Trailhead's Schedule a Flow unit says these flows can run once, daily or weekly, and that they are based on your org's default time zone.

Here is a weekly flow that gives sales reps a task for every open opportunity whose close date has passed. Build it in a sandbox first.

  1. In Flow Builder, create a new Schedule-Triggered Flow.
  2. In the Start element, set the start date, a start time outside business hours, and the frequency to Weekly.
  3. Choose the Opportunity object and add the condition IsClosed Equals False, so the flow only looks at open deals. Filtering here keeps the record count down.
  4. Add a Decision element with one outcome whose condition is a Boolean formula resource, shown below, that equals True. It checks whether the close date is before today.
  5. On that outcome, add a Create Records element that creates a Task with the Subject "Update close date or close this deal", the Related To field set to the opportunity Id, and the Assigned To field set to the opportunity owner.
  6. Debug the flow in the sandbox, check the tasks it created, then activate it and move it to production with the rest of your release.

The Decision outcome can use a formula resource like this one:

{!$Record.CloseDate} < TODAY()

Know the limits before you scale the idea. The Salesforce Admins post What Is a Schedule-Triggered Flow? says the maximum number of schedule-triggered flow interviews per 24 hours is 250,000, or the number of user licenses in your org multiplied by 200, whichever is greater. It also says a schedule-triggered flow can only query up to 50,000 records before hitting the governor limit, that the Automated Process user runs these flows, and that you can monitor and manage them from the Scheduled Jobs page in Setup. Because the Automated Process user creates the tasks, check that your assignment and notification settings behave the way reps expect.

Which Salesforce admin tasks can you automate?

Use this rule of thumb: automate the collection, keep the judgment.

  • Automate with Salesforce's own tools: scheduled data exports, recurring data hygiene checks with schedule-triggered flows, and reminder tasks for record owners.
  • Automate the routine, review the result: user setup, deactivation and permission set assignment follow the same steps every time, so they are good candidates for a documented process or an AI assistant that works inside your Salesforce permissions.
  • Keep manual: reading the Setup Audit Trail, reviewing Login History, deciding what to do with a Health Check score, and choosing when to activate a release update. These need someone who knows the business.

AI tools can take on more of the middle group. Cirra AI is building Cirra Admin to take routine Salesforce requests like these off an admin's plate, with the admin still making the judgment calls. Today, Cirra AI's Salesforce Admin MCP Server handles setup work such as creating users, assigning permission sets and adding fields from the AI client you already use, working as the connected user within that user's permissions. You can read more about how Cirra AI works with Salesforce admins. Whatever you use, keep Salesforce's documentation as the source for limits and paths, because menu names and limits can change between releases.

A printable Salesforce admin task checklist

  • Daily: request queue, locked users and password resets; failed scheduled and batch jobs; API usage on the System Overview page.
  • Weekly: Setup Audit Trail review; weekly export ran and files saved within 48 hours; data hygiene exceptions; new, changed and departed users frozen or deactivated.
  • Monthly: Health Check; Login History download; Setup Audit Trail download; release updates due soon tested in a sandbox; field history exported if you need more than 18 months; storage and licenses; Org Check in place of Optimizer.
  • Each release or quarter: sandbox refresh; release notes; end-to-end tests; access review of profiles and permission sets.

Frequently asked questions

What are the most important Salesforce admin tasks?

The most important Salesforce admin tasks are user management, security reviews, data backups and release preparation. User requests keep people working, the Setup Audit Trail and Login History show who changed or accessed what, the Data Export service protects your data, and release updates must be tested before Salesforce enforces them.

How often should a Salesforce admin review the Setup Audit Trail?

Review it weekly and download it at least every few months. Salesforce keeps setup changes for at least the last 180 days, and after 180 days setup entity records are deleted, so a regular download is the only way to keep an older record.

Which Salesforce admin tasks can be automated?

You can automate scheduled data exports with Schedule Export, and recurring data hygiene checks with schedule-triggered flows that run once, daily or weekly. Reviewing the Setup Audit Trail, Login History and Health Check results still needs a person to judge what the findings mean.

What is the difference between freezing and deactivating a Salesforce user?

Both actions prevent the user from logging in. Freezing does not make the user license available in your org, while deactivating does. Freeze an account when you need to stop access right away, then deactivate it once the person has left. You can deactivate users, but you cannot delete them.

How long does Salesforce keep login history?

The Login History page shows up to 20,000 records of user logins for the past 6 months. To see more records, download the information to a CSV or GZIP file. A monthly download keeps a complete history.

Is Salesforce Optimizer still part of an admin checklist?

No. The Salesforce Admins blog says Salesforce Optimizer was retired in the Winter '26 release and shows admins how to use Org Check instead. Replace any Optimizer step in an older checklist with Org Check and Health Check.

Share the Post:

Related Posts