Ensure secure access to PeopleForce while minimizing friction for users and following best security practices.
Enable automatic sign-out after inactivity
Why: Reduces risk if someone forgets to log out on a shared or public device.
How: Go to Settings → Security, and set the system to automatically sign out users after 120 minutes of inactivity.
✅ Best practice: Set to 120 minutes to balance security and convenience.
Enforce two-factor authentication (2FA)
Why: Adds an extra layer of protection for employee accounts beyond passwords.
How to set it up:
Go to Settings → Security.
Enable Enforce Two-Factor Authentication (2FA).
Once enabled, employees will see a prompt when logging in:
“Wait, before continuing you need to enable Two-Factor Authentication. Your company has enabled forced 2FA on your account. In order to continue, you must enable 2FA.”Users will not be able to access PeopleForce until they set up 2FA.
✅ Best practice: Make 2FA mandatory for all users. Combine with strong password rules (e.g., minimum length, numbers, and special characters).
Turn on IP Tracking
Why: Helps detect unusual activity like unauthorized logins.
How: Enable IP Tracking to notify employees when their account is accessed from a new IP address.
✅ Best practice: Enable this for all accounts. It’s a passive but effective way to increase security awareness.
Use SSO (Single Sign-On)
Why: Centralizes access management and improves login security across company tools.
How: In the SSO provider section, choose your company’s provider — Google, Microsoft, SAML, or LDAP .
✅ Best practice: SSO ensures that user access is managed through one central system, making onboarding, offboarding, and access control more secure and efficient.
Enforce Single Sign-On (SSO) Login
Why: Centralizes access control and enhances security by requiring users to log in only through your company’s identity provider (Google, Microsoft, SAML, or LDAP).
Go to Settings → Security
Under Single Sign-On (SSO) provider, choose your provider (e.g., Google Authentication, Microsoft Authentication, etc.)
Enable Enforce SSO login
🔒 Once enabled, users will no longer be able to log in with their PeopleForce passwords — they must authenticate through SSO.
✅ Best practice: SSO ensures that user access is managed through one central system, making onboarding, offboarding, and access control more secure and efficient.
Set strong password requirements
Why: Protects accounts that still use email + password login.
How: Set the following password rules:
Minimum length: 12 characters
At least 1 number
At least 1 uppercase letter
Encourage special characters (optional)
✅ Best practice: Combine strong password rules with 2FA for accounts that don’t use SSO.
Enable password expiry
Why: Reduces the risk of long-term password exposure. This applies only to companies using login and password authentication (not SSO).
How: In Security settings, set passwords to expire every 2–3 months. Users will be prompted to create a new password after expiry.
✅ Best practice: Set password expiry to 60–90 days to ensure regular updates. Notify users in advance to avoid disruptions, and encourage the use of strong, unique passwords with each reset.
