Lesson 10 of 23 · All lessons
Salesforce Platform Administrator II
0 of 23 complete
1Exam Overview
  1. 1.1Platform Administrator II Complete Exam Overview
2Security and Access20%
  1. 2.1Sharing architecture: records, fields, and inherited access
  2. 2.2Profiles, permission sets, delegated administration, and
  3. 2.3Person accounts and complex account-contact models
3Objects and Applications19%
  1. 3.1Object relationships, record types, and schema design
  2. 3.2Applications, Lightning App Builder, Dynamic Forms, and
  3. 3.3Record types, page layouts, and related-list experience
4Auditing and Monitoring10%
  1. 4.1Debug logs and Setup Audit Trail
  2. 4.2Sensitive data, sandbox controls, and security review
  3. 4.3Reviewing security changes and pending access updates
5Cloud Applications11%
  1. 5.1Sales lifecycle: products, price books, schedules, orders, and
  2. 5.2Forecasting and Enterprise Territory Management
  3. 5.3Knowledge, entitlements, and service channels
  4. 5.4Salesforce product suite and platform extension choices
6Data and Analytics Management13%
  1. 6.1Data quality, validation, duplicates, enrichment, and archiving
  2. 6.2Complex reports, dashboards, and analytic design
  3. 6.3External data, backup and restore, and import methods
7Environment Management and Deployment
  1. 7.1Sandboxes, packages, and metadata movement options
  2. 7.2Change set composition, validation, and deployment practice
  3. 7.3Sandbox selection, refresh, and data protection
8Process Automation20%
  1. 8.1Choosing Flow, approvals, formulas, and legacy automation
  2. 8.2Order of execution, recursion, and automation interaction
  3. 8.3Automation troubleshooting, testing, and fault handling

Section 4 · Auditing and Monitoring · 10% of exam

4.3 Reviewing security changes and pending access updates

4 min read Updated Nov 17, 2026

Exam objective

Explain how to review and troubleshoot security settings, including pending changes that can alter system access.

Effective access is the result of multiple current settings and sometimes pending operations. A user may receive access from a profile, permission set, permission set group, role, territory, queue, team, sharing rule, manual share, or implicit relationship. Before changing a setting, identify the object, field, record, user, action, and time at issue. Compare a successful user with an affected user to find the smallest relevant difference. Avoid assuming that the profile alone explains access.

Pending work can change access after an administrator begins a configuration change. Role hierarchy or territory updates may require recalculation; group membership and sharing changes may take time to propagate; deployments can change permissions or automation; and asynchronous jobs can alter records that users can access. Review setup status, deployment results, and relevant job completion rather than repeatedly saving the same setting. Keep a record of the expected final state and verify it after the operation completes.

Use access diagnostics and record sharing details to determine why a user can see or edit a record. Inspect object and field permissions separately. For a sensitive field, verify field-level security and any report or dashboard exposure. For a record, inspect ownership, hierarchy, sharing rules, teams, territories, and other grants. If a user can log in but cannot open an app or record, check authentication, app visibility, object permission, and record access in order. This layered sequence prevents broad permission changes that hide the real issue.

Security review should include the impact of both granting and revoking access. Removing a permission set may not remove the same capability granted by another assignment. Changing a role or territory can affect many users and records. A sharing-rule change may expand access to a group that includes external or cross-functional users. Before deployment, enumerate impacted users and records, test in a representative environment, obtain the required approval, and communicate any temporary recalculation window.

For an incident, preserve timestamps, user identity, record identifiers, and relevant configuration history. Setup Audit Trail can show setup changes; login history can help with authentication; debug logs can explain an execution path; and sharing diagnostics can explain record access. These tools are complementary. Protect exports and log files because they may contain sensitive data. If exposure is confirmed, follow the organization's incident process and avoid ad hoc edits that destroy evidence.

Exam focus: determine whether access is absent, excessive, or still recalculating. Check additive grants and pending operations before changing the baseline. Distinguish authentication from authorization and field security from record sharing. State what you would verify after a deployment or access recalculation. The least-privilege solution should be tested with the affected user, not only with an administrator.

Extra concept: Access review is a lifecycle control. Include assignment expiry, role changes, vendor offboarding, and periodic recertification so temporary grants do not become permanent.

When a deployment changes access, capture a before-and-after result for a user who should gain access and one who should remain excluded. Include a record the first user owns and one owned by someone else. Check both the user interface and reporting path. If access is unexpectedly broad, trace the source of the grant and remove the narrowest unnecessary path. If access is missing, add only the required permission or share and repeat the same checks. This comparison helps catch a setting that solves one user's issue by exposing records to an entire role. Check the access change for every relevant entry point, including list views, reports, dashboards, APIs, and mobile pages. A successful check in Setup does not prove that a downstream user can complete the workflow, and a hidden button does not prove that the underlying data is secure. Capture expected access in a short matrix and rerun that matrix after the change is fully applied.

Practical scenario

After a territory model update, a seller cannot see accounts expected in the new region. Check whether the model is active, the territory assignment rules ran, the user belongs to the territory, and any recalculation completed. Then inspect account access details and confirm the seller's object permissions. Do not grant View All as a temporary workaround; it would obscure whether the territory design is working and expose unrelated accounts.

Extra concept

A permission set assignment may be asynchronous or one of several additive grants. Record the intended access and validate the final effective permissions after the operation, including whether removing one assignment actually removes the capability.

Key takeaways

  • Inspect additive grants and pending recalculation before changing baseline access.
  • Compare effective access for users who should gain and remain excluded.
  • Recheck reports, dashboards, APIs, mobile, and record sharing after the change.
  • Official references: https://help.salesforce.com/s/articleView?id=005298969&language=en_US&type=1 https://help.salesforce.com/s/articleView?id=sf.security_sharing_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.admin_monitorsetup.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.users_profiles.htm&type=5

Check your knowledge

Answer exam-style Auditing and Monitoring questions with answers and explanations.

Practice Auditing and Monitoring
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Platform Administrator II simulator: same number of questions, same time limit.

Get Complete Access