TABLE OF CONTENTS
Purpose
Custom Filters are used in different areas of the platform, from data grid views to dashboard widgets. Filters allow users to apply conditions that can narrow down a search in a dataset (e.g. Risks that are active AND high).
- Ability to set filters per module: This allows admin users to create filters per module for use in dashboards and data grid views.
- Ability to share filters: Allows admin users to share filters with the organisation.
- Ability to mark a filter as favourite: This feature allows admin users to mark a filter as favourite for all users. A favourite filter will appear by default when the user opens a filter panel in the platform.
- Conditional Logic: Filters allow users to apply logic between condition statements [AND, OR, NOT], facilitating simple to complex data queries.
Important Notes
- System Administrator access is required to configure filters via admin.
- Filters by themselves, if not applied to anything, do not change anything.
- End Users can access the filters they created, or that were shared with them via the “My Filters” page. This is accessible when the user sees the filter panel [shown below from a dashboard widget] and they click the 'cog' icon.

Step by Step Guide To Create or Edit a Filter
- Navigate to Admin > Filters.
- Click Blue 'Add'.
- From the dropdown, select the module you want to create the filter for.

- The 'Add' form will now appear.
| Fields | Description |
| Title | 256 character limit, the name of the filter. |
| Conditions | Create the filter conditions |
| Share with all users | Selecting checkbox will give all users access to the filter. |
| Favourite for all users | Selecting checkbox will have the filter appear under Favourites for all users on the relevant module. |
| Sub-filter | Selection will change the filter so it can be applied to other filters as a sub-filter This will mean users can’t use this filter outside of other filters. |

Building conditions
When you click into conditions, you will see a list of fields and linked modules available to filter on. We will focus first on the fields.
| Logic | Definition |
| AND | All conditions must equal TRUE |
| OR | Only one of the conditions needs to equal TRUE. If two equal TRUE, it returns FALSE |
| NOT | Condition must equal FALSE to return TRUE |
- Start by selecting the logic that will wrap ALL conditions. The platform defaults to ‘AND’ but can change by selecting the ellipsis (…) at the bottom of the AND on the left hand side.
- Select the field you would like to use as a condition to filter. This will automatically populate the available fields/relations for the selected module. See the below table for condition options.

- Conditions can be ‘Nested’ (ie an OR statement inside an overall AND statement). To do this, select the ellipsis (…) on the right hand side of the first of the condition statements.
Please note: You cannot add a condition to the left of another; new conditions must be added within the current condition. - Save the filter once completed.
To test the filter, apply it to a widget on a dashboard. You can find more information about dashboards and advanced dashboards.
| Condition | Description | ||
| Generic | |||
| Is equal to | Must be exact to single value to return TRUE | ||
| Is not equal to | Must not match single value to return TRUE | ||
| Is blank | No value in the field | ||
| Matches filter | To be used with Sub filter | ||
| User field specific | |||
| Reports to | If Supervisor on users is enabled, will filter to all users that has the supervisor as the selected user | ||
| Is myself | User fields only Equals TRUE when the current user is the user in the field | ||
| Reports to me | Similar to ‘Reports to’ but will filter for anyone that has the current user in the supervisor field. | ||
| Number specific | |||
| is less than | Field is lower than specified value (i.e. less than 5 is 4 and less, including negatives). | ||
| Is less than or equal to | Field is lower or equal to the specified value (i.e. less or equal to 5 is 5 and less, including negatives). | ||
| Is greater than | Field is higher than specified value (i.e. greater than 5 is 6 and higher) | ||
| Is greater than or equal to | Field is higher or equal to the specified value (i.e. greater than or equal to 5 is 5 and higher) | ||
| Date specific Working with dates uses the same conditions as Number, however with more options. | |||
| is less than | a specific date | Select from calendar | Selected value (i.e. date or date relative to today) is treated as 0. Anything in the past from that is ‘less than’ i.e. -1 for the previous day |
| A date relative to today | Enter integer first (positive number = future, negative = past) Then toggle day/year/month | ||
| Is less than or equal to | a specific date | Select from calendar | Selected value (i.e. date or date relative to today) is treated as 0. Anything in the past from that is ‘less than’ i.e. -1 for the previous day |
| A date relative to today | Enter integer first (positive number = future, negative = past) Then toggle day/year/month | ||
| Is greater than | a specific date | Select from calendar | Selected value (i.e. date or date relative to today) is treated as 0. Anything in the past from that is ‘less than’ i.e. -1 for the previous day |
| A date relative to today | |||
| Is greater than or equal to | a specific date | Select from calendar | Selected value (i.e. date or date relative to today) is treated as 0. Anything in the greater than is anything after then. i.e 1 for the following day |
| A date relative to today | Enter integer first (positive number = future, negative = past) Then toggle day/year/month | ||
| Occurs in month | Specific month | Month/Year value from calendar | Selected value (i.e. month or month relative to selection) is treated as 0. Anything in the future of the month is considered greater than and is a higher number (i.e. following month is 1) |
| Month relative to today | Enter integer first (positive number = future, negative = past) | ||
| Occurs in year | Specific month | Year value from calendar | Selected value (i.e. year or year relative to selection) is treated as 0. Anything in the future of the month is considered greater than and is a higher number (i.e. following year is 1) |
| A year relative to today | Enter integer first (positive number = future, negative = past) | ||
| Occurs in financial year ending | A specific financial year | Year value from calendar | Selected value (i.e. financial year or financial year relative to selection) is treated as 0. Anything in the future of the month is considered greater than and is a higher number (i.e. following financial year is 1) |
| A financial year relative to today | Enter integer first (positive number = future, negative = past) | ||
| Relation specific | |||
| All match filter | Select a sub-filter. All related items must meet the sub-filter condition to return TRUE If blank, no sub-filter is available for the selected relation | ||
| Any match filter | Select a sub-filter. At least 1 related item must meet the sub-filter condition to return TRUE If blank, no sub-filter is available for the selected relation | ||
| Overlaps with | Similar to ‘is any of’ however selects specific items of the relation | ||
Sub-Filters
Sub-filters allow you to filter an item further based on values of its related items. In order to use them, you need at least two filters: the sub-filter and the filter that will use the sub-filter. To build a filter, follow the above guide on creating a filter, but select ‘Sub-filter’. To apply, use the conditions within ‘Relation specific’ in the table above.
Sub-filter use example:
- Create a sub-filter for material risks using your criteria, and mark it as a sub-filter.
- Create a second filter, now for actions, and select Risks instead of a field from the condition list:

Then select one of the following: all match filter OR any match filter (as per your filtering needs). This will enable the last field to be filled in which will list the available sub-filters.

Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article