Start a Salesforce permissions audit by asking who can see, export or delete data and why they need that access. Review System Administrators, integration users, permission assignments and sharing paths. Record what you find in your own org rather than relying on an industry percentage.
Use these 38 checks to organize a manual review. For a product-assisted review, start the 14-day Platform trial, no card, and run an access review of your production org yourself. These checks are review prompts, not a certification test or a promise that the product automatically scores every item.
Profile hygiene (8 checks)
- Inventory profiles and their purposes. Identify overlap and document why each profile is needed.
- Review every System Administrator assignment. Confirm the business need with an accountable owner, rather than using a universal percentage target.
- Review temporary admin grants. Check whether project or contractor access should end.
- Investigate profiles with no assigned users. Confirm dependencies before proposing removal.
- Review View All Data and Modify All Data. Document why each broad permission is needed and where it is granted.
- Review API Enabled assignments. Confirm which human users and integrations need API access.
- Review View All Users. Check its purpose against the user's responsibilities.
- Review Manage Users. Confirm each holder has an approved user-administration responsibility.
Integration users (6 checks)
- Identify each integration account and owner. Document shared accounts and how actions are attributed.
- Review integration users with admin-level access. Test narrower permissions with the integration owner before changing production.
- Review credential handling with the security owner. Document how integration credentials are protected and rotated. Do not put secret values in the review workbook.
- Document each integration's authentication method. Have the security owner confirm the applicable authentication requirements.
- Review integration network restrictions. Confirm which restrictions apply to the actual connection method.
- Confirm the available activity evidence. Identify what each log records and any gaps; do not assume Setup Audit Trail records all integration activity.
Permission set hygiene (8 checks)
- Permission sets are used in place of profile customization for one-off access grants. Profile for baseline, permission sets for everything else.
- Investigate unassigned permission sets. Confirm their owner, purpose and dependencies before proposing removal.
- Permission set names follow a documented convention. No "Sarahs_Test_PSET" in production.
- Review Permission Set Groups where applicable. Confirm that each grouping matches a documented job function.
- Each permission set has a documented owner and purpose. Description field populated, not blank.
- No permission set grants "Modify All Data" without an explicit business justification documented.
- Agree on an assignment review schedule. Set it with your security and compliance owners and document when reviews occur.
- Review combined access from profiles and permission sets. Evaluate the resulting permissions, not just each grant in isolation.
Role hierarchy + sharing (6 checks)
- Role hierarchy has no orphan nodes. Roles with no users and no children below them.
- Role hierarchy reflects organizational reality. Not the 2021 org chart.
- Review organization-wide defaults for sensitive objects. Document why each baseline access setting meets the business need.
- Sharing rules do not silently grant broad access. Each rule reviewed for unintended scope.
- Manual record sharing is logged or restricted. Otherwise records can be shared in ways nobody knows about.
- Review external-user access separately. Test whether external users can reach only the intended records.
Sensitive field protection (5 checks)
- Review protection of personally identifiable information. Confirm encryption requirements and available controls with the security owner.
- Review field-level access to personal information. Restrict visibility and editing to documented business needs.
- Financial fields (revenue, contract value, custom fields with $ data) have field-level security audited.
- Review protected health information with your compliance owner. Agree on access, integrity and evidence requirements for your use case.
- Custom fields holding sensitive data have explicit Description field documentation noting the classification.
Login security (5 checks)
- Verify MFA for human users. Review actual sign-in paths and applicable requirements with the identity owner.
- Login IP ranges restrict access to corporate networks and VPN where applicable.
- Review session timeout settings. Document the policy and any exceptions based on the user's responsibilities.
- Review authentication methods for elevated roles. Confirm approved methods with the identity owner.
- Review failed-login handling. Confirm lockout, monitoring and escalation settings with the security owner.
Record your findings
For each check, record the affected user or permission, the access path, business justification, owner, evidence and proposed action. Mark items as reviewed, needs investigation or not applicable, with a reason.
| Status | What to record | Next step |
|---|---|---|
| Reviewed | Current access and approved business need | Set the next review date. |
| Needs investigation | Missing owner, unclear need or unexpected access | Assign an owner to investigate. |
| Change proposed | Intended access and affected users or integrations | Test, obtain approval and keep an undo plan. |
| Not applicable | Why the check does not apply | Revisit if the org or use case changes. |
Completing the checklist does not establish SOC 2, ISO 27001 or HIPAA compliance. Agree on evidence and acceptance criteria with your auditor. Nothing changes in your org without your approval.
Run a self-serve access review
The Clientell Platform includes access review and is $500 a month after the 14-day trial, no card required. The trial starts when you connect your first org. Run an access review of your production org yourself, then review proposed changes before approving them.
For the manual steps, see the access review guide. You can also use the Salesforce Audit Workflow Playbook to organize follow-up work.