Login History and Access are essential security and monitoring features within Salesforce that help administrators track and manage user authentication activities.
Login History provides a comprehensive record of all login attempts made to your Salesforce organization. Administrators can access th…Login History and Access are essential security and monitoring features within Salesforce that help administrators track and manage user authentication activities.
Login History provides a comprehensive record of all login attempts made to your Salesforce organization. Administrators can access this feature by navigating to Setup and searching for 'Login History.' This log captures critical information including the username, login time, source IP address, login type (such as Application, API, or Partner Product), browser type, platform, and whether the attempt was successful or failed.
The Login History data is retained for six months and can be downloaded as a CSV file for further analysis or compliance requirements. This feature is invaluable for security auditing, troubleshooting user access issues, and identifying suspicious activities such as unauthorized login attempts or unusual login patterns from unexpected locations.
Administrators can also view login history at the individual user level by accessing the user record and scrolling to the Login History related list. This provides a focused view of a specific user's authentication activities.
Access management in Salesforce encompasses several components that control how users interact with the system. Session Settings allow administrators to configure session timeout values, login IP ranges at the organization level, and login hours restrictions. These settings help enforce security policies and limit access based on time and location parameters.
Network Access settings enable administrators to define trusted IP ranges, ensuring users can only access Salesforce from approved network locations. When combined with profile-level login IP restrictions and login hour limitations, organizations can create robust access control frameworks.
The Identity Verification History tracks multi-factor authentication events, providing additional visibility into security verification activities. Together, Login History and Access controls form a comprehensive approach to maintaining security, ensuring compliance, and protecting sensitive organizational data within the Salesforce platform.
Login History and Access - Salesforce Administrator Exam Guide
Why Login History and Access is Important
Login History and Access is a critical security and auditing feature in Salesforce that helps administrators monitor user authentication activities. Understanding this topic is essential for the Salesforce Administrator exam because it relates to security controls, user management, and troubleshooting access issues. Organizations rely on this feature to maintain compliance, investigate security incidents, and ensure only authorized users are accessing the system.
What is Login History?
Login History is a record of all login attempts made to your Salesforce organization. It captures both successful and failed login attempts, providing valuable data for security monitoring and user support. Salesforce retains login history data for six months, and you can download it for longer retention if needed.
Key information captured in Login History includes: • Username - The user attempting to log in • Login Time - Date and timestamp of the attempt • Source IP Address - The IP address from which the login originated • Login Type - How the user authenticated (UI, API, Partner Portal, etc.) • Status - Success or failure, with reason codes for failures • Browser and Platform - Technical details about the client • Application - Which connected app was used, if applicable
How to Access Login History
There are multiple ways to access Login History in Salesforce:
1. Setup Menu (All Users): Navigate to Setup → Security → Login History. This shows login history for all users in the organization.
2. Individual User Record: Go to a specific user's record and click the "Login History" related list to see that user's login attempts.
3. Reports: Create custom reports using the Login History report type for more detailed analysis and filtering.
4. API: Query the LoginHistory object for programmatic access to login data.
How Login History Works
Every time a user attempts to authenticate with Salesforce, the system creates a LoginHistory record. This happens regardless of whether the attempt succeeds or fails. The system records:
• Failed attempts due to invalid passwords • Failed attempts due to IP restrictions • Successful logins via various methods (SSO, username/password, API) • Session timeout and re-authentication events
Administrators can filter and sort this data to identify patterns, such as repeated failed attempts that might indicate a brute force attack or unusual login locations that could suggest compromised credentials.
Key Features and Limitations
• Login History is read-only - records cannot be modified or deleted • Data is retained for six months within Salesforce • You can download login history data as a CSV file for archival • The View Setup and Configuration permission is required to view all users' login history • Users can view their own login history from their personal settings
Exam Tips: Answering Questions on Login History and Access
Tip 1: Remember the Retention Period Salesforce keeps login history for six months. If a question asks about viewing login data older than six months, remember that you would need to have previously downloaded and archived that data.
Tip 2: Know the Access Points Questions may ask where to find login history. Remember the three main locations: Setup → Security → Login History, individual user records, and custom reports.
Tip 3: Understand Use Cases Common exam scenarios include: • Investigating suspicious activity • Troubleshooting why a user cannot log in • Auditing user access for compliance • Identifying inactive users
Tip 4: Differentiate from Related Features Do not confuse Login History with: • Setup Audit Trail - tracks configuration changes, not logins • Field History Tracking - tracks data changes on records • Session Management - shows active sessions, not historical data
Tip 5: Know Permission Requirements Regular users can see their own login history. Administrators with the "View Setup and Configuration" or "View All Users" permission can see login history for all users.
Tip 6: API vs UI Login Types Understand that login history distinguishes between UI logins (browser-based) and API logins (integrations, data loaders). This is relevant for troubleshooting integration issues.
Practice Question Approach
When you encounter a question about Login History: 1. Identify what the scenario is asking (viewing, reporting, troubleshooting) 2. Consider the timeframe involved (within or beyond six months) 3. Think about who needs access and what permissions they have 4. Eliminate answers that confuse Login History with other audit features