Salesforce admin services: what an outsourced administrator actually does each week

"Salesforce admin services" is one of the most searched phrases that lands on Micronetbd, and the people searching usually want one thing explained: what does the administrator actually do, week to week, when the role is on a retainer rather than a desk?

Monday: the queue

Requests sit in a ticket queue with turnaround by priority. Access and blocking issues (a user locked out, a report that will not run for the sales meeting) are handled the same business day. Configuration changes are scheduled into the weekly plan. Larger enhancements are estimated and put on the monthly backlog for you to prioritise.

Users, roles and security

User and license management, profiles and permission sets, role hierarchy and sharing rules, login and MFA policy, and deactivations done on the day someone leaves. It is unglamorous and it is where most audit findings come from.

Configuration and automation

Fields, page layouts, record types, validation rules, Flow builds and fixes, approval processes, and retiring the automation nobody remembers building. A retainer admin keeps a change log in your org so every change is traceable.

Data, reports and releases

Duplicate rules, imports and mass updates, field cleanup and backup checks. The reports leadership asks for, built on fields people actually fill in. Sandbox testing before each of the three Salesforce releases, managed package upgrades, and an eye on what each release deprecates, including API version retirements that break integrations quietly.

The backlog

A named admin, a weekly plan and a monthly backlog you prioritise, so the org improves every month instead of slowly rotting. When a request turns out to be development, integration or architecture work, it is estimated at agreed rates and started only with your approval, by the same Micronetbd team.