Setup

Working effectively in Setup is more about navigation habits and audit hygiene than about a specific configuration. The four-step routine covers: learn Quick Find as the primary navigation tool, organize Setup access by permission set, use the Setup Audit Trail for change tracking, and document Setup conventions in the org admin runbook. Each habit compounds: an admin who navigates Setup quickly, grants access correctly, audits changes regularly, and documents conventions explicitly does substantially more useful work per hour than one who improvises each step.

1. 1
   Learn Quick Find as the primary navigation tool

   Open Setup once and confirm Quick Find is the search box at the top of the sidebar. Practice navigating to common pages by typing partial names: Profiles, Permission Sets, Object Manager, Flow, Sharing Settings, Company Information, Health Check. Within a week, every navigation should be through Quick Find rather than tree browsing. Document the canonical Quick Find searches in the team onboarding doc so new admins learn the keystrokes too. The 5-second navigation saving per page compounds across the admin workday.

2. 2
   Organize Setup access by permission set

   Create permission sets that reflect the team Setup access needs. View Setup permission set for release engineers and business analysts who need read-only Setup. Modify All Data plus standard admin permissions for full admins. Narrower permission sets (Manage Users, Manage Sharing, Manage Profiles) for users with scoped admin responsibilities. Assign permission sets through permission set groups so onboarding and offboarding flow through the standard user lifecycle. Avoid granting blanket System Administrator profile assignment to anyone who does not truly need it. Audit Setup access quarterly through the org security review.

3. 3
   Use the Setup Audit Trail for change tracking

   Open Setup, Security, View Setup Audit Trail at least weekly. Review the changes since the last review. Flag any unexpected activity: configuration changes by users you did not expect, sharing rule modifications outside business hours, permission set assignments to non-admin users. The Audit Trail retains 180 days of history by default. For longer retention, enable Field Audit Trail on specific objects. Document the review cadence in the admin runbook and rotate the reviewer across the team so the discipline persists even when individual admins are out.

4. 4
   Document Setup conventions in the admin runbook

   Maintain a single source of truth for how the org configures Setup. Document conventions: naming standards for permission sets and profiles, sharing rule patterns, layout assignment rules, custom field naming conventions. Document one-off decisions: why this specific validation rule exists, why this sharing rule was added, why this permission set has these contents. Without documentation, future admins reinvent decisions or, worse, undo them without understanding the original intent. The runbook is the admin equivalent of a developer README; treat it as a living document.