Managing a Salesforce org is an ongoing operational discipline that spans Setup configuration, sandbox refresh planning, user management, customization promotion, and limits monitoring. The workflow below covers the standard tasks every admin should perform regularly to keep the org healthy.
- Confirm and document org identity
From Setup, open Company Information. Record the org ID, edition, address, default fiscal year, default currency, and language. Document this information in the org's runbook for support tickets and partner conversations. Also note which Salesforce data center or Hyperforce region the org is in, which affects URLs, IP ranges, and disaster recovery characteristics. Refresh the documentation annually because some details (org edition during a contract upgrade, region during Hyperforce migration) change over time.
- Plan and execute sandbox refreshes
Build a sandbox refresh schedule based on the development cycle: Full Copy refreshes after each major release, Partial Copy monthly, Developer Pro per sprint, Developer ad-hoc. Communicate refresh dates to all stakeholders so they can save and preserve in-progress work. Run the refresh through Setup, then immediately apply the sandbox-specific configurations that get reset: email deliverability, named credentials, integration endpoints, sandbox-only user passwords. Document the post-refresh checklist so a new admin can repeat the process.
- Monitor limits and storage
Schedule a monthly review of the org's limit consumption. Open the Limits page (Setup > System Overview) and the Storage Usage page. Note any limit category trending toward the ceiling. For data storage, identify the biggest contributing objects and consider archival strategies. For API calls, identify the noisiest integrations and consider caching or rate-limiting. For Apex governor limits, identify any code consistently approaching limits and refactor. Without monthly monitoring, limits become an emergency rather than a planning input.
- Govern deployment and change management
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 simple legacy orgs, SFDX with Git for modern setups, or DevOps Center for managed pipelines. Document the process in the team's wiki. Train every admin and developer on it. The single biggest source of production incidents in mature orgs is uncontrolled changes that bypass the deployment process, and a written process plus consistent enforcement is the antidote.
- Org IDs are not portable across orgs. Migrating from one org to another requires re-mapping every external reference that used the old org ID.
- Sandbox refresh overwrites existing sandbox data and metadata. Any in-progress work that has not been deployed back to production is lost.
- Some org settings are irreversible: enabling Person Accounts, enabling Multi-Currency, enabling certain features. Sandbox-test before enabling in production.
- Edition affects available features and limits. An Essentials edition org cannot use many enterprise-tier features, regardless of admin configuration.
- Storage and API limits hit during business hours produce real outages. Monitor consumption monthly to catch trends before they cause downtime.