My Birthday Month Special: 15% off any Blazer2Role program until November 30. Get my code →
← Back to blog
salesforce admincareer growthautomationpromotion

How to Build a Promotion Case as a Salesforce Admin (Using Your Org's Own Records)

How to Build a Promotion Case as a Salesforce Admin (Using Your Org's Own Records)

When admins prepare for a promotion conversation, most write a list of what they have done: flows built, reports fixed, users trained. That list matters, but it asks your manager to take your word for it.

There is a stronger source of evidence. Your Salesforce org already records which automated work you are responsible for, by name. This guide shows where to find that record, how to compare it with your job description, and how to turn the gap into a clear proposal.

Step 1: Find the automations that report to you

Salesforce documents what happens when an automation fails: "When a process or flow interview fails, a detailed email is sent to the admin who last modified the process or flow."

That behavior is controlled by a setting in Process Automation Settings called "Send Process or Flow Email to," with two options:

  • "User Who Last Modified the Process or Flow"
  • "Apex Exception Email Recipients", where "error emails are sent to the addresses listed on the Apex Exception Email page in Setup."

What to do: search your inbox for flow and process error emails from the last six months. Each one names an automation the platform treats you as responsible for. If you find none, check which option your org uses, because the emails may be going to a shared list.

Step 2: Check the scheduled work submitted under your name

Salesforce's All Scheduled Jobs page in Setup lists "all reporting snapshots, scheduled Apex jobs, and dashboards scheduled to refresh." For each job it shows details including the "Name of the user who submitted the scheduled job" and the "Next date and time at which the scheduled job will run." Viewing the page requires the View Setup and Configuration permission.

What to do: list every job submitted under your name, with its next run date.

One detail is worth knowing: for schedule-triggered flows, "the Default Workflow User set in Process Automation Settings is the running user." The flow runs as one user, but if you last edited it, the failure email comes to you. That is a good example of responsibility that never appears in a job title.

Step 3: Compare the record with your job description

Make a simple two-column table:

What the org says you own What your role says you own
Flows and processes that email you when they fail Responsibilities in your job description
Scheduled jobs submitted under your name (or what you were told when you were hired)

The difference between the two columns is the core of your promotion case. Every line on the left can be checked, which makes it more persuasive than a list of achievements.

Step 4: Turn the gap into a proposal

A gap on its own sounds like a complaint. Turn it into a plan by sorting each item on the left into three groups:

  1. Keep: work that points toward the role you want next.
  2. Hand over: work that should belong to someone else. In Salesforce terms, that can mean a different person becomes the last to modify it, the error email setting changes, or the job is resubmitted.
  3. Retire: automations or jobs that are no longer needed.

Then present it as a scope proposal: what the platform sends you today, what your role says, what you want to own, what you would hand over, and what you would switch off. That makes the conversation about the shape of the role rather than about your merits.

What this evidence does not show

Be honest about the limits so your case holds up:

  • It records accountability, not value. It does not show whether an automation was a good idea or well built.
  • Responsibility follows the last edit. If you fixed a small thing in someone else's flow, you may now receive its errors. Say so instead of claiming the whole flow.
  • Your org may use a shared error list. If so, the inbox step will be empty, which is still useful to know.
  • The Scheduled Jobs page is not a full inventory. Read your own org instead of assuming one page shows everything.

Combine it with the usual evidence

This record works best alongside the things managers already expect: problems you solved, users you supported, and how you think about requests before you build. Our guide on why Salesforce admins must think like product managers covers that mindset, and your first 90 days as a Salesforce admin shows how to start keeping records from day one. For a picture of the wider role, see what a Salesforce admin actually does all day.

Frequently asked questions

How do I ask for a promotion as a Salesforce admin? Bring evidence your manager can check, such as the automations that report to you and the scheduled jobs under your name, and pair it with a clear proposal of what you want to own, hand over and retire.

Who receives Salesforce flow error emails? By default, the admin who last modified the process or flow, unless the org has changed the setting to send them to the Apex exception email recipients.

Where can I see scheduled jobs in Salesforce? On the All Scheduled Jobs page in Setup, which lists reporting snapshots, scheduled Apex jobs and dashboard refreshes, with the user who submitted each job.

What if the answer is not yet? You still leave with a clear list of what you own and an agreement about what to hand over, which makes the next conversation easier.

Where can I read a shorter version? Our Substack post It Runs as Someone Else and Fails to You covers the same idea in a quick read.


Blazer2Role helps career changers move into Salesforce roles, and we sell coaching and courses. Settings differ between orgs and change over time, so check current Salesforce documentation for your org. Nothing here guarantees a promotion or a salary outcome. Drafted with AI assistance under Blazer2Role's editorial direction.

My Birthday Month Special · ends November 30

Take 15% off any program this November.

Dedric's birthday month, your discount. Leave your email and we send you the code BIRTHDAY15. Use it once on any Blazer2Role program at checkout, from coaching to the full course package.

Code valid until November 30, one per person. A coach also follows up with next steps.