Overview
Advanced Filtering is now available across Confirm and this enhancement offers a consistent method for segmenting and analyzing users across various areas of the platform.
The common denominator is that filters are primarily driven by metadata stored for each person (e.g., Department, Title, Country, Manager). In addition, each section may include specialized filters that are relevant in that context (for example, ‘Calibration status’ in the Team Dashboard).
How it works
You can add one or more conditions to narrow down the dataset. Each condition consists of:
Field - either a metadata field (e.g., Department, Title, Country) or a section-specific attribute.
Operator - available options are IS / IS NOT.
Value - the filter target (e.g., “Quality Assurance”).
Conditions can be grouped:
Condition - a single filter rule
Group of conditions - multiple rules combined with AND/OR logic
Conditions can be combined with AND/OR logic. Filters can be saved for future use, bookmarked, and, in most cases, shared with other users.
Visibility rules
Visibility rules always apply:
A regular user will only see results for people or objects they normally
have access to.
An HR Admin will see results for the full population.
An HR Admin with restricted visibility (e.g., only specific departments or
people) will only see results within their scope.
A Development Plan Admin will see results limited to the plan types they
manage.
This ensures that sharing or bookmarking a filtered view never exposes
information outside the recipient’s permissions.
Key Benefits
Consistency: The filtering experience looks and behaves the same across
the product.
️Flexibility: Any metadata associated with people can be used as a filter
condition.
Composability: Multiple conditions can be combined using AND/OR logic.
Exportability: In most tables, filtered results can be exported to CSV.
Portability: Saved filters can usually be bookmarked or shared with other
users.
Section-Specific Filters
Each area of the platform supports the common metadata filters and may also include section-specific filters that provide additional context.
Surveys & Performance
>Team Dashboard
Filters are based on person metadata coming from the dataset of the selected cycle.
Includes all standard person metadata (Department, Manager, Country, etc.)
Adds calibration-related filters:
Final rating
️Calibration status
Calibration flags
Report release status
Report acknowledgement status
>Key Takeaways
Filters also use person metadata from the dataset of the selected cycle.
Includes all standard person metadata (Department, Manager, Country, etc.).
Additional filters:
Rating distribution (e.g., “Slightly exceeds expectations”).
Any attributes tied to that cycle’s dataset.
People Administration
Uses all person-related metadata as filterable fields Examples include:
Person
Manager / Manager or above
Department
Location
Level ID, Department ID, HRIS ID, DID
Hired / Terminated / Original hire date
Status (Active, Terminated, etc.)
No section-specific filters — this view is focused exclusively on person metadata.
Cycle Administration – Participants
Supports advanced filtering on basic person metadata, mainly for selecting or reviewing participants within a cycle.
Available fields include:
Person
Manager / Manager or above
Department
Location
Focused on participant management rather than detailed HR attributes
Promotion Packets
Includes standard person metadata (Department, Location, Manager, etc.)
Adds packet-specific filters, such as:
Author (the person who created the packet, formerly “Manager/MGR”).
Direct report of the candidate
Full team of candidates
Final / most recent performance rating
Requested new level
Packet status (Draft, Submitted, Approved, etc.)
Requested new title
The exact set of available filters depends on the Promotion Packet template in use, since templates define which fields and questions are collected. Certain client-specific fields (e.g., salary recommendations, custom dropdown questions) may or may not be filterable depending on implementation. Filters that are not fully supported (e.g., dropdowns that return IDs instead of values) are hidden to avoid confusion.
Development Plans
Filtering here is not based on person metadata. Only plan-specific fields are available: Candidate, Supporter, and Type (e.g., template used).
Objectives
Advanced filtering here relies entirely on person metadata (No objective-specific filters are available). Examples include:
Business unit
Department
Location
Person
Manager
Nudges
Advanced filtering is available through the Custom filter option in “Who should receive this nudge?” ✅ Only System Admins and Superusers can use it. For HR Admins, Managers, and regular users, the option is visible in the dropdown but disabled.