Section 2 · Configuration and Setup · 15% of exam
2.4 Organization security and identity controls
Exam objective
Explain identity verification, login methods, login hours, Setup Audit Trail, session settings, and agent access controls.
Authentication establishes who is logging in; authorization determines what that identity can do after login. Orgs can use supported login methods and identity verification controls. Login hours restrict when users assigned to the relevant profile can log in, while session settings govern aspects of authenticated sessions such as session behavior and security.
Setup Audit Trail helps administrators review recent setup changes, including who made a change and when. It is useful when investigating unexpected configuration changes, but it is not a replacement for all security monitoring or data-change history. For an access issue, inspect authentication, user status, profile restrictions, and session controls before assuming a record-sharing problem.
Additional concepts
Authentication, verification, and authorization
Login methods such as a company identity provider concern how a user authenticates. Identity verification adds a check that the person is authorized to use that login. Object, field, and record permissions govern what the authenticated user can do afterward. Troubleshoot these layers separately instead of granting broader data access to solve a sign-in problem.
Time and session restrictions
Login hours limit when users in scope can log in; session settings govern aspects of the active session. Setup Audit Trail is useful for tracing setup changes, while record history and other monitoring features address different events. Choose the control that matches the incident being investigated.
A user can authenticate but is repeatedly blocked outside approved hours. Check the user’s assigned profile and login-hour schedule, then confirm whether the behavior is expected before altering org-wide authentication controls.
Agent or integration access should be scoped to the required data and actions. Authentication alone should never be treated as sufficient authorization.
Key takeaways
- Authentication, session controls, login hours, and permissions address different security layers.
- Use Setup Audit Trail to investigate setup changes.
- Apply restrictions to the intended users and validate the resulting login experience.
