Using Views

Views save a table configuration: filters, sorting, visible columns, their order, and widths. You access saved views from the dropdown in the top-right corner of a record list, which shows Default View until you create your own.

​

Open a record list

Views are supported on these record tables:

• Candidates
• Jobs
• Companies
• Contacts
• Opportunities
• Lists
• Job Candidates and Speculative Presentations, the two application tables on the Jobs page

Views on the application tables mean a pipeline review no longer starts from a blank table. Save one view with the stage, owner, and last activity of every open application, another with the source and the date someone was added to the job, and switch between them from the same dropdown.

​

Moving through the list without going back

Opening a record from a table opens it as an overlay on top of the list, and the header carries ˄ ˅ arrows with a counter such as 6 of 141 candidates. The arrows step to the next and previous record in the order the table is currently sorted and filtered, so a view is also a worklist: filter to the twenty people you want to review, open the first, and arrow through them without returning to the table between each one.

​

Apply filters and sorting

Use the Filters button to narrow down your list (for example by stage, location, or activity date), adjust sorting, and add or hide columns via View Settings. Every location filter offers Set area as well as a radius: on jobs, companies, contacts (their own location and their company’s), and applications, as it already did on candidates. An area is a place you search for, from a town to a region, a country, or a continent, so “everyone in Flanders” is one filter rather than a radius you have to tune. See location filters. Columns are not limited to fields on the record. Two that are worth turning on:

• Campaigns on Candidates and Contacts, showing the campaigns that are in draft or ongoing for each record, so you can see who is already being approached before you approach them again.
• Job board postings on Jobs, showing which postings are live.

Both work as a column in the table and as a row on the cards in board view. The Job Candidates and Speculative Presentations tables carry Job Status and Job Users as columns and as filters, so you can cut a list of applications down to the jobs that are still open, or to the ones a particular colleague is on, without going to the Jobs table to work out which those are. Contacts have a LinkedIn column as candidates already did. The application tables, Job Candidates, Applicants, and Speculative Presentations, also filter and sort on the custom attributes you added to applications, so a field such as notice period or salary expectation becomes something you can cut a list on rather than read row by row. Most attribute types do both; checkbox, currency, multi-select, and user attributes filter but do not sort, timestamps and durations sort but do not filter, and date ranges do neither. From the Job Candidates table you can also put a selection on another job: select the rows, open Candidate Actions, and choose Add to job. Pick the job, the Stage they should land in, and optionally a Label; they arrive at the top of that stage. Anyone already on the job is skipped and listed, so nobody ends up there twice. It works on Speculative Presentations too, for up to 1,000 rows at a time. The Candidates table can also show the companies a candidate is a contact at, for the people who are both. On a desk where a former placement is now the person doing the hiring, that is the column that tells you before you send the wrong email.

​

Relative dates

Date filters take relative values as well as fixed ones. Instead of pinning a filter to a calendar range that goes stale the day after you save it, pick a window that moves with today: Today, This week, This month, Last 24 hours, Past, or Future. Custom time builds your own window: a direction (Last or Next), a unit (Hours or Days), and a value. Custom date still gives you a fixed range when that is what you want. This is what makes a saved view stay useful. A view filtered on “last interaction in the last 30 days” keeps meaning the same thing every morning, where a fixed range quietly becomes a report about the past.

​

Leave a period out

A date filter can also exclude a period, which is how you build “everyone I have not called this week” or “jobs that do not close this month”. There is no separate “not this week” value; you pick the operator and the value:

• not between with This week, This month, Next 7 days, Next 30 days, Next 90 days, or a custom range
• is not with Today or a single date

It works on every date filter, your custom date fields included, on candidates, contacts, companies, jobs, placements, opportunities, tasks, and notes. The rolling presets, such as Past or Last 24 hours, cannot be turned around this way. A record with no date at all counts as outside the period, so it shows up in a “not this week” filter. A list of people “not called this week” therefore includes people you have never called. Reports are the exception: there, an empty date never matches. One thing to know before you save it as a view: This week is stored as the dates of the week you saved it in. The next Monday, the view still leaves out last week rather than the new one, so check the dates when you reopen it.

​

Create a new view

1. Click the current view name in the top-right corner (for example Default View).
2. From the dropdown, select + Create New view. The new view starts as a copy of the one you are on.

3. Give your view a name, for example Law, Recent Activity, or Open Roles in UK.

Your filters, sorting preferences, and visible columns are all saved in the view.

​

Access your saved views

Your custom views appear in the same dropdown. Click a view name to switch instantly between saved configurations. You can create as many views as you like, each tailored to a specific workflow or segment.

​

Edit or delete existing views

1. Open the dropdown again.
2. Click the three dots next to a saved view to rename or delete it.

Deleting a view only removes the saved configuration. Your underlying data stays safe. Views are personal: other users in your workspace create and manage their own views independently.