Managing a Salesforce organization is an ongoing operational discipline. The workflow below covers the standard tasks every admin should perform regularly to keep the org healthy, secure, and aligned with business needs.
- Document org identity and key configuration
From Setup, open Company Information and document the Organization ID, edition, address, default fiscal year, default currency, primary contact, and active feature licenses. Document the org's region (Hyperforce or legacy data center), URL pattern (My Domain), and active sandboxes. Maintain this documentation in the team's runbook so anyone joining the team can orient quickly and so support cases have the key information ready.
- Maintain the sandbox refresh schedule
Build a documented refresh schedule for each sandbox: Full Copy quarterly aligned with major releases, Partial Copy monthly, Developer Pro per sprint, Developer ad-hoc. Communicate refreshes to all stakeholders in advance so they can save in-progress work. Run each refresh through Setup and immediately apply the post-refresh checklist (email deliverability, named credentials, integration endpoints, sandbox-only data resets). Document the checklist so a new admin can run a refresh from the runbook alone.
- Monitor limits and capacity
Schedule a monthly review of the org's limits consumption. Open the Limits Console and any custom monitoring dashboards. Track data storage, file storage, API calls, Apex governor consumption, and any package-specific limits. Identify any metric trending toward its ceiling and plan remediation: archive old data, optimize chatty integrations, refactor inefficient Apex, or purchase additional capacity. Without monthly monitoring, limits become urgent capacity crises rather than planned upgrades.
- Govern change and deployment
Define the org's deployment pipeline: which environments customizations flow through, who approves each promotion, how rollbacks happen if something breaks. Use Change Sets for legacy orgs, SFDX with Git for modern setups, or DevOps Center for managed pipelines. Document the process in the team's wiki and train every admin and developer on it. Consistent enforcement of the deployment process is the single biggest predictor of production stability over time.
- Organization IDs are not portable across orgs. Org-to-org migration requires re-mapping every external reference that used the old ID.
- Sandbox refresh overwrites existing sandbox data and metadata. In-progress work that has not been deployed back is lost.
- Some organization settings are irreversible: Person Accounts, Multi-Currency, certain feature enablement. Sandbox test thoroughly before enabling in production.
- Edition affects feature availability. An Essentials edition org cannot use many Enterprise-tier features regardless of admin configuration.
- Limits hit during business hours produce real outages. Monitor monthly to catch trends before they cause downtime.