Skip to main content

2.42 Release overview

Summary of all features and improvements we're announcing in this release

🚀 This release brings a wide range of improvements across Core HR, Perform and Time (Attendance) to help you manage your HR processes with greater control, security, and efficiency. From more flexible access settings and enhanced document protection to improved reporting and streamlined configuration, these updates are designed to reduce manual work, provide deeper visibility into system activity, and make everyday tasks easier for HR teams, managers, and employees alike.

👥 People-level visibility in the “All people” role

The “All People” role now includes visibility settings that let you control who users can see in the system.

You can choose:

  • Everyone (default) — no changes, users can see all people as before

  • Specific people — limit visibility based on legal entity, division, location, or team.

This helps ensure employees only see the people relevant to them. For example, a regional team can view only their own location, sensitive departments can stay hidden from other parts of the company, and managers can focus on the teams they actually work with. More here.

This feature is currently released behind a feature flag while we continue expanding and refining visibility coverage across the platform.
If you notice any unexpected visibility behavior after enabling the feature, please contact our support team.

📋 Audit log becomes System log with more detailed event data

The Audit log has been renamed to System log and now provides more detailed information about actions performed across employee records. A new IP address column helps identify where each action was performed from, while the new Open button displays additional event details in a side panel. Depending on the event, this may include device and browser information alongside the date, user, and affected employee.

All of this information is also available in exports, making it easier to investigate changes, track user activity, and support internal security audits. More info here.

🏖️ Improved leave policy assignment

Managing leave policies is now more transparent and easier to control, whether you assign a policy to an individual or update it in bulk.

The updated interface includes a cleaner layout, advanced filtering options, and a step-by-step review process that helps you confirm exactly how policy changes will be applied before saving them.

When selecting employees in bulk, filters such as current leave policy, department, division, team, location, work type, and other custom fields make it easier to identify the right group and transfer them to another policy.

When assigning or editing a leave policy, you can choose when the new rules should take effect:

  • Hire date – recalculates accruals from the employee’s start date

  • Specific date in the past – applies the policy retroactively from the selected date

  • Today – replaces the current policy immediately and recalculates today’s accruals under the new rules

  • Future date – keeps the current policy active until the selected date, then switches to the new one automatically

A visual timeline explains how the selected policy will be applied and what happens to existing balances based on the chosen date. This makes it easier to understand the impact before confirming the change. More details here.

🔐 Require Sign-In Before Signing Documents

Organizations that work with sensitive documents can now add an extra layer of security to the eSignature process.

A new Sign in to sign option is available in Settings → Security → Authentications. When enabled, employees must sign in to PeopleForce before they can open and sign documents received by email. This setting applies to documents signed through PeopleSign. If an employee has an active preboarding process, they can continue opening and signing documents without signing in to PeopleForce first.

This helps ensure that only the intended signer can access the document. If someone else opens the signing link, PeopleForce verifies their identity and blocks access. More details.

🌙 Continuous overnight shifts in Attendance

Attendance now supports continuous shifts that cross midnight. Employees can clock in late at night and clock out the next morning without the shift being automatically split at midnight.

When a shift ends on the next day, the system displays a warning and a small “next day” indicator, but still allows the entry to be saved as one continuous shift.

This behavior now applies to both manual time entries and clock-in/clock-out actions.

In exports, the full shift is displayed under the day the shift started, including both start and end times.

Improved assignment logic for employed employees only

Starting from release 2.42, several assignable objects in PeopleForce are now scoped only to Employed people instead of both Employed and Hired statuses.

This change affects announcements, polls, knowledge base articles and categories, surveys, calendar events, and performance review cycle collaborators. Previously, employees in the Hired status (for example, people in preboarding before their official start date) could also receive or participate in these items. After the update, they will no longer be included automatically.

The reason for this change is to better align assignment logic with real-life usage. In most cases, these workflows and communications are intended for active employees rather than candidates or future joiners who have not yet started working in the company. This helps reduce accidental access, unnecessary notifications, and situations where preboarding employees see content or participate in processes that are not yet relevant to them.

Additionally, release 2.42 changes the default assignment behavior for custom roles, competencies, and surveys. Previously, newly created items were automatically assigned to all Employed and Hired people by default. Now, the default value is set to Nobody, and administrators can explicitly choose the audience before saving.

This update is designed to give admins more control and prevent situations where roles, permissions, competencies, or surveys are unintentionally applied to the entire company. Since these objects are usually created for specific groups of employees, the new default behavior provides a safer and more predictable setup experience.

🛠️ Other updates

In addition to the major enhancements, we've also rolled out several other updates to improve your overall experience with PeopleForce. Here's a quick overview of these:

Core HR

  • We added a new Knowledge Base permission to give companies more flexible control over content management access. The “Create and manage articles and categories shared with them” permission allows users to create, edit, and organize Knowledge Base content, but only within items explicitly shared with them. This is ideal for team leads, department owners, or contributors responsible for specific sections of the Knowledge Base.

  • We improved how assignment rules work across PeopleForce by replacing the always-visible rule builder with a simple two-step choice: Everyone or Specific people. This removes unnecessary complexity when no filtering is needed.

    When “Everyone” is selected, the item applies to all employees with no conditions shown. When “Specific people” is selected, admins can define filters like department or location and see how many people match.

    This makes setup clearer, faster, and more intuitive across policies, reviews, surveys, tasks, forms, and other assignment-based features.

  • PeopleForce now separates the ability to request eSignatures from the broader permission Manage employee documents within the company. Users who have permission to edit documents in specific folders under the People section can now send those documents for eSignature directly. This applies only to the employees and document folders they already have access to, helping teams delegate document signing securely without granting unnecessary administrative access.

  • New hire forms now support table-based fields. Instead of adding each field one by one, you can select Position, Work, or custom tables and choose which fields to include in the form, making configuration faster and more consistent with other forms in PeopleForce.

  • System search now supports partial matches across multi-part first names, allowing users to find employees regardless of the order in which first and middle names are entered.

  • Under Employee profile → Compensation → Additional compensation, the existing table has been split into two separate tables based on payout type.

    One table shows once-off compensation items only, with no status icons. Items are sorted with the most recent first. The second table shows recurring-fixed compensation items and includes status indicators: yellow for future items, green for active items, and no icon for historical items. Items are also sorted with the most recent first.

  • A new mobile SMS login option is now available, allowing employees to sign in using their phone number and a 6-digit one-time code sent by SMS.

    This feature can be enabled in Settings → Security → Authentication by selecting the Enable mobile SMS login checkbox. It provides a simpler and more convenient login method, especially for employees who primarily use mobile devices.

  • A new unified integration for Slack is now available under a feature flag. It combines previous Slack tools into a single bot and allows companies to create custom notifications for specific channels, teams, or departments, helping reduce unnecessary notifications for employees.

  • Headcount reports now automatically hide items with zero values. For example, divisions, locations, or categories without employees will no longer appear in charts, making reports cleaner and easier to read.

  • The Instructions field in leave policy settings now includes a rich text editor. You can add formatted text and clickable links to internal policies, compliance documents, or HR portals, making it easier for employees to access relevant information when submitting leave requests.

  • The Leave Balance report now includes a Usable balance column that displays balances after applying the rounding rules configured in the leave policy. The existing Ending balance column has been renamed to Calculated balance to indicate the raw value stored in the system. This helps HR and accounting see the same rounded balances that employees see in their profiles.

  • Documents with an Expired eSignature status can now be sent for signature again using the new Retry eSignature action. This option is available both from the document menu and in bulk actions, making it easier to resend unsigned documents without deleting and uploading them again.

  • Email action in the workflows now supports the placeholder. This makes it possible to include the employee’s system ID or build direct profile links in automated emails, helping connect PeopleForce workflows with external onboarding and automation tools.

  • The My tab in Requests now includes filters and a Current Approver column. This makes it easier to track who is responsible for the next approval step and quickly find specific request types.

  • Custom Reports now support custom fields from the Position and Work tables. This allows you to include your own organiszational attributes alongside employee data in a single report.

Perform

  • A new Badges feature is now available behind a feature flag. It allows administrators to assign visual badges of honor to employee profiles to recognize milestones and achievements.

  • The Review Cycles page now includes a Finished filter, making it easier to find completed review cycles and review past performance assessments.

API

  • The Get Employee API endpoint now returns the full department hierarchy for each employee, making it easier to understand their exact position within your organizational structure.

  • GDPR-compliant future-recruiting consent now is supported in the candidate API.

Did this answer your question?