Salesforce implementation key points
The CRM project first aligns Sales Cloud and Platform licensing boundaries; sandbox Dev/Test/Prod and change sets or CI/CD need to be finalized in the first Sprint.Integrate with ERP/marketing stack to prioritize lead/account master data attribution.MiCount provides Lightning delivery lists and governance templates.
Salesforce · Administrator
Identity · Sandbox · Change · Governance · Recommendations 2–3 weeks
Introduction to Org Administrators and Architects: Identity, Profile/Permission Set, Sandbox Policies, Change Sets vs DevOps Center, and Field Audit and Event Monitoring basics.Can be compared directly Admin Help Center step by step.
learning path
Identity and permissions
User, Role, Profile, Permission Set Group, Minimum Permission.
Environment and application life cycle
Sandbox type, Refresh, Change Set, App delivery list.
Compliance and monitoring
Setup Audit Trail, Login History, Health Check, Backup Export.
official document comparison
| theme | Learning points | Link |
|---|---|---|
| Manage Users | SSO, MFA, Permission Set allocation | Users |
| Sandboxes | Developer / Partial / Full Selection and Refresh | Sandboxes |
| Change Sets | Outbound/Inbound, dependencies and Profile do not include field level | Change Sets |
| Security Guide | Sharing Rules, OWD, Shield concepts | Security |
arithmetic · Org governance list
Before Go-Live
- My Domain, MFA, IP restriction strategy; integrated user independence + minimal profile.
- OWD and sharing rule documents; prohibiting large numbers of "View All Data" Profiles.
- Sandbox Refresh calendar; UAT account and production data desensitization specifications.
runtime
- Monthly Health Check; Storage, API Limit, Async Apex Queue.
- Release: Change Set or CI list + rollback plan (Metadata backup).
- Disable user within 24h of resignation; periodic Permission Set audit.
Hands-on Tasks (Acceptance Criteria)
Task: Complete a Sandbox → Production simulation release
- Create a new Permission Set "Sales-Analytics" in the Developer Sandbox that only contains report permissions.
- Deploy to another sandbox using Change Set or DevOps process and UAT sign.
- Write Release Note: list of components, affected users, verification steps, rollbacks.
- Enable the Setup Audit Trail to export the sample and indicate who has access.
Arithmetic delivery includes the "Org Permission Matrix" template; see developer.html for integration with ERP.