People records

Signed in? Ask Lovelio this question inside the app - it answers from this same page.

People is the agency's database of people, and it is called People in the left menu because it holds two kinds: candidates, and the contacts at your clients. Both are one record type - see the People record section of the company identity card. Every person belongs to the agency, never to a client: a candidate can be submitted to three different clients and each client only ever sees what the agency chooses to send them. The People page is where you search, browse, and open those records.

"Candidate" is still the right word for a role, not a place: the tab on a job, the pipeline stages and an application all stay candidate-worded, because that is what someone in a hiring process is.

What a record holds

A candidate record stores name, email, phone, location, LinkedIn URL, current job title, current employer, skills, the CV, referees, a 1-5 star rating, an open-to-work flag, a do-not-approach flag, and a preferences section (below). When the CV on file could not be read, the record header, the CV tab, the deal file and the list rows all show "CV not read" with the reason (scanned, password-protected, empty, wrong file type); search, matching and the assessment never saw that CV, so upload a readable copy and the flag clears on its own. Automatic retries stop when a CV is unreadable. Uploading a replacement CV or an improved document reader gives it another attempt. Temporary service failures still retry. Source is recorded (how they entered the system) and shows on the record header: Imported, Careers page, Found by web search, or the source of the first job they were added to. Anyone found on the web always shows Web search as their source on a job, so you know you may never have spoken to them. The deal file header also reads Source for that one job. To tell a candidate how you found them, check this line. Someone added from a job's On the web tab also has a Public profile section on the CV tab: their public profile exactly as they wrote it, labelled as their own words. Edit these on the Details tab: click "Edit", change fields, then "Save changes" or "Cancel". Placing a candidate updates their current job title and current employer to the placed role automatically.

The name comes from the CV and is always written "Firstname Lastname": "LAUREN GOLDSMITH" on a CV becomes "Lauren Goldsmith". The full CV read decides the name, never a heading or a place on the page ("Candidate Profile", "Auckland NZ"). A name you typed is never changed by a CV read.

Location always reads as suburb and state, or city and state: "Balmain, NSW". A candidate's street address is never shown on the grid, the record, an export, or anything sent to a client, even when a CV parse captured one.

Star rating

The star rating is your agency's own opinion of the candidate: one shared rating per candidate, 1 to 5 stars, blank until someone rates them. The stars sit at the right-hand end of the facts strip in the record header, under the contact details. Click a star to rate - there is no edit mode and no save button. Click the same star again to clear the rating. Nobody rated yet shows one star and the word "Rate"; point at it and the full row of five opens. Rated candidates show a small star badge next to their name on the candidate grid and in search results.

AI search filters on it: "5 star candidates", "developers rated 4 and up", "3 stars or below". Candidates nobody has rated never match a rating search - nothing is guessed. The rating never moves anyone up or down a result list on its own; it filters, like a tag.

Candidate preferences

The Preferences section on the Details tab captures what the candidate WANTS, separate from what their history says: preferred roles (for example "Head of Sales"), preferred locations with an open-to-relocation flag, work types (permanent, contract, temp, part-time), a seniority preference, salary expectation in their own words (annual figures and day or hour rates both work, for example "145k plus super" or "850/day"), notice period, an available-from date, and work rights. Edit it with its own "Edit" button: roles and locations are added as chips, work types are toggles, and everything saves with "Save changes" or backs out with "Cancel".

Every preference is searchable. AI search understands asks like "marketers open to contract work who want to move to Sydney", "open to relocation", "wants a director role", "available within a month" (a stated notice period or an available-from date both count), and "on under 120k". Preferred locations are place-aware the same way normal locations are: a candidate who wants "Manly" matches a search for candidates wanting Sydney. Candidates with no captured preference simply do not match preference filters; nothing is guessed from the CV.

"Extract from notes" in the section header reads the candidate's recent call notes and timeline notes and proposes preference updates. Nothing is written until you review the playback and click "Apply". Extraction only adds to preferred locations, never removes what is already stated, and it never invents a preference the notes do not state.

Opening a person on the list

The People page is the search. Type who you are looking for in the one box. Under the box, tick where to search: My database, The web, LinkedIn, any one on its own or together (one always stays ticked); the ticks stay in the address, so a shared link keeps them. Your recent searches sit in a list below the box, each with how many it found; click one to run it again on whichever sources are ticked. "Recent candidates" beside the heading lists the people you touched lately, and "Import CVs" opens the bulk import. The page keeps the same shape before and after a search: the heading above the box becomes the search you ran, in your words and with each phrase clickable, whichever sources you ticked, and the ticks stay under the box. Tick another source after a search and it joins that search; the results update below. A search of more than one source shows a tab for each (My database, The web, LinkedIn), one on screen at a time, so the page stays short. Each source's results sit under a coloured header (blue for My database, amber for The web, green for LinkedIn) that says how many it found. My database is a full-width table: Name, Current job, Employer, then the match score after a search, Location, Owner, Last contact and Added. Click a row and the person's full record (below) opens as a panel on the right, with "1 of 50" and arrows at the top to walk the list without closing it. The web and LinkedIn are full-width tables too, and a row opens a panel on the right the same way (more below).

While a search on My database, the web or LinkedIn is still running, the page shows your own sentence and the requirements Lovelio read from it, above a wall of faces with a lens moving across it. The faces are decoration, not results: they are not the people your search found, and nothing on the wall is a count or a match. The real results replace it the moment they are ready.

Each row on Your database shows the name, with the star rating, the off limits sign and Placed beside it, then their current job and employer in their own columns, the location, the owner (the consultant the person belongs to), when they were last contacted and the date they were added. Last contact is the latest email you sent them, call you logged or interview they had; "Never" means none of those has happened yet. It is the same date the "never contacted" search filter uses, so the two always agree. A note on its own does not count as contact. After a search the Match column shows the score; hover it to see why they matched, or click it to keep that open. People whose CV only mentions the employer sit under their own heading at the end of the table, with "Why" instead of a score. Hover a row for the heart (Ask Lovelio) and the "..." menu of row actions.

Every row has a tick box, and the box at the top of the table selects everyone on the page, for the bulk actions bar. Click a column heading to sort by it (Name, Current job, Employer, Match, Location, Owner, Last contact, Added); click it again to flip the order. Page numbers sit under the table. The Cards view works the same way: a click opens the full record.

"Add to a job or pool" opens one box with two fields you type into. Job: type to search every open job by title, then pick one; it sits in the field as a chip, and its x removes it so you can pick another. The job you used last is labelled "Last used" and sits first, but is never picked for you. Talent pools: type to filter and pick as many as you like; each becomes a chip, and Backspace in the empty field removes the last one. Pools they are already in show as "Already in" and cannot be picked. Arrow keys and Enter work in both lists, and Escape closes the list. A line at the bottom says exactly where they will go, for example "Priya goes into the funnel for Sales Manager at Are Media and the Sydney sales leaders pool"; two or more pools are counted ("and 2 pools"). "Save" stays greyed out until you pick something. After it saves, a green line says where they landed. A Stage control picks where they start on the job: Funnel (the default), Yes, Screen or Submitted, and the green line names it ("In the Screen stage for Sales Manager at Are Media"). Someone already on the job moves up to the stage you picked, or stays where they are if they are already there or further on.

On the web

The web section searches the web for the same search you typed in the box. There is one search box: tick The web under it and the web runs the same search. It needs a job title, a place or an employer to search on, for example "account managers in Sydney"; a search with none of them says so. Everything else you typed goes to the web too: a skill, an industry, employers (now or at any time) and years in the current job that you say you must have are filters the web applies, so only people whose profile shows them come back, and years of experience in all or a degree are checked on each person who arrives. Nice-to-haves only change the order, and so does work you name ("with capital raising"): people whose profile says it come first. A suburb also searches the city it sits in, because most profiles name the city (Clayton searches Clayton and Melbourne); a city stays as typed. Places typed with "or" or "/" are searched as separate places. A search with no place searches your agency's own country, shown as a place chip; change the chip to search somewhere else. An industry is searched under the web's own names for it: IT services, cyber security, manufacturing, robotics, REITs and property funds all have one, and commercial property or a property fund never searches estate agencies (ask for "real estate agents" or "residential property" for those). When the web has no name for an industry you typed, a line under the count names it and the search covers every industry instead. A client you name ("for Sentinel") is who the search is for, not where people work; ask for people who work there to search the client's own staff. A long list of titles joined by "or" runs each title as its own search, so one common title never fills the page. Before the web searches, Lovelio reads the job's ad, or what you typed, and writes several searches the way a recruiter who knows the market would: the titles these people hold today (the job's own title is often rare), the industries their employers sit in and the kinds of employers that produce them. The strongest searches run first and the next ones run as you scroll; when they run out, the fallback searches carry on. Every person is still checked against your requirements and ordered by the same search engine. The top of the web results says how many people the web has for the search ("Up to 340 people on the web"), and the requirements sit above them as the same chips as on Your database, so you can edit them without typing the search again. With more than one source ticked, each source has its own tab with its own count. When nobody in your database matches but the web has people, the page opens on The web, and Your database says it found nobody there. A tab you click stays where you put it. Nothing is searched on the web until you tick it. Searching the web is free; adding a new person from it uses credits. The web search starts as soon as Lovelio has read what you asked, about two seconds in; it does not wait for your database results. While it searches, the section shows what it is searching for and which step it is on; the first page usually lands in a few seconds.

Web people are a full-width table: Name, Current job, Employer, Match and Location. Someone the web found who is already in your database carries an "In your database" badge beside their name. Hover the match score to see why they fit. The order comes from the same search engine that orders your database, never from AI; requirements a public profile cannot show, like salary or notice period, are listed as not part of the ranking, and when nobody matched the exact search a line says how Lovelio widened it. A title with an industry in front ("insurance broker") carries on into related titles once the exact ones run out, and a line says so. When few people match, the list carries on into groups, each under its own coloured heading. "Held this job title before" is people who did the job before their current one; with an industry named, they work in it now or did the job in it. Those who held it more recently rank higher, all else equal. "Could be anywhere in New Zealand" (for a search in Auckland) is people whose profile names only the country, so they may live there. Nobody whose profile names another town or region is ever shown. The web search always keeps a job title, a company or a skill in a place: it never falls back to everyone in an area. More people load as you scroll to the end, up to 50 a search. When a search stops at 50 and the web has more, the end of the list says so: "The search stops at 50 people on the web. Narrow it to see others." Add a requirement or a smaller place and the search starts again. When the web has no more, the end of the list reads "That is everyone on the web who matches this search."

Click a row and the person opens as a panel on the right, with "1 of 50" and arrows at the top to walk the list without closing it. They are not a record yet, so the panel is their public profile: their name and role at the top, then their location, years in work and LinkedIn link, and Why they fit as green ticks with the match score beside them. Hover or tap a tick to see the proof, taken from the search itself; nothing shows until you search for something. The proof is also marked where it already sits on the profile: a tick on their location (with the distance), a tick on their current job, matching skills in green, and the matching words highlighted in their summary. Then their public profile as they wrote it, their career, Skills and Education. The button is "Add to the database". It opens the same add box, so you can also put them on one job and in any talent pools in the same click. At the top, "Find their" picks which contact details Lovelio looks up: Email (their work and personal email) is ticked to start, and Mobile is ticked only when an admin has turned mobiles on in Settings, Hiring, Web Sourcing. Each shows its price in credits, and you are only charged for what is found. Untick both and nothing is looked up. Once they are added the row's badge reads "Added", the button becomes "Add to a job or pool", and "Open record" opens their new record. Someone already in your database gets "Open record" straight away. The lookups run in the background. Adding someone who is already on file looks up only the details you picked that their record does not hold yet, and only when Lovelio has their LinkedIn link.

The LinkedIn section runs the same search on your own LinkedIn. There is one search box: tick LinkedIn under it and the search stays. Like The web, it starts as soon as Lovelio has read your search, without waiting for your database results. Pick the LinkedIn you use (LinkedIn, Recruiter Lite or Recruiter; Lovelio remembers it, here and on a job's Find candidates) and press "Search LinkedIn". Plain LinkedIn opens with the search already typed and lists the filters to add by hand, like the location. Recruiter and Recruiter Lite open with the search copied, ready to paste. It needs a job title or a skill; a search with only a place says so. It is the same search a job's LinkedIn tab builds, so the same words give the same LinkedIn search everywhere.

Lovelio never reads LinkedIn's results. Capture anyone you like with the Chrome extension and they land in your database; without the extension the tab says so and links to it. Under the button the tab lists the people already in your database who came from LinkedIn and match the search, in the same order as Your database, with a count, in the same table as Your database. They are already records, so a row opens their full record, with arrows to walk the list.

The full record (slideout)

The full record opens as a right-side panel over the list, so the flow stays "click, glance, close, click next". The header leads with the name, then the current role and location; its buttons sit top right in the same order and the same size on every record panel in Lovelio: "Add to job", "Email", the "..." menu, "1 of 50" with arrows for walking the list, then close at the far right. There is no initials circle; the name is the heading. Under it come the contact details, then a facts strip: the role chips (Candidate, Contact at a client, Placed and when), "Needs you on 2 jobs" when any of their jobs is waiting on your Yes, No or Maybe, "Open to work" when it is set, and the star rating at the right. Nothing sits above the name. Anything that changes what you are allowed to do - off limits, do not approach - drops into an amber band across the bottom of the header instead of competing with the chips, and a flag that is off draws nothing at all; set one from the "..." menu. When the person is also a client contact, the role chips become a switch: click the "Contact at ..." segment and the panel flips to their contact record in place (details, documents, timeline for that role); click "Candidate" to flip back. The same switch sits on their contact record inside the client, so from either side the other record is one click away. The Roles tab's contact entries flip the same way. The segments show how each role was recorded: a contact somebody put on the client shows in colour, a role Lovelio derived because the person's own record says they work there ("works here") shows quiet, and a role their record says has ended shows quiet too, labelled "Past" - so a person who has moved on still shows both the client they left and the one they are at now. The "..." menu carries the rest of the candidate actions. A person who is only a client contact has no Float (or Spec) or Share to marketplace in that menu, and cannot be submitted: add them to a job first, which makes them a candidate.

Under the header the record is built like the deal file: a list down the left and the page on the right. The list starts with Profile. A contractor then gets a Working group: every contract they are on or about to start, with the role, the client and "until 30 Jan 2027" or "starts 14 Oct" (a green dot while it runs, amber before it starts). Click one and the contract opens over the record, the same panel the Contractors page opens, with "<- [name]" at the top to come back. Then every job the person is on. Live jobs come first, each with the job title, the client and the stage, and a coloured dot: pink when the job is waiting on your Yes, No or Maybe, amber while it is moving, green once placed. Closed jobs (No, rejected, withdrew, placed) sit in their own Closed group underneath, with a red dot when it ended badly. Click a job and its deal file opens over the record, the same deal file the job's Candidates tab opens, with "<- [name]" at the top to come back to the person. A placed job's "Open placement" opens the placement file the same way, without leaving the person. On a phone the list becomes a row of buttons across the top. Profile opens on one plain-English sentence: for a contractor with nothing waiting on you, where they are working and until when ("Jane is working at Acme until 14 Nov 2026."), with a button to open the contract; otherwise how many jobs the person is live on with you and which one needs your decision, with a button to open it; or, when they are on no job, that they are not on a job with you. "Add to job" in the header adds them to one. Under it, the tabs, in order: Details, CV, Documents, Referees, Roles, Timeline, Ask Lovelio. The same tabs appear in the same order wherever a candidate opens. Details holds preferences, tags, contracting and skills. CV holds their summary, cover letter, experience and education exactly as they wrote them. The AI assessment of a job lives in that job's deal file, not on the person. Ask Lovelio is a Q&A tab where you ask questions about this specific candidate. The Timeline shows the full history as single-line rows that expand on click, with filter chips (emails, stage moves, AI activity, notes, changes) and a search box. Emails include inbound replies, not just what the agency sent.

Row actions and the "..." menu

The candidate grid row "..." and the slideout header "..." draw from one shared menu, so they never drift: Add to job, Spec (or Float) to a client, Share to marketplace, Add to talent pool, Assess against role, Email candidate, Log call, Add note, and Delete. Share to marketplace appears when the marketplace module is turned on (Settings > Integrations). The record's own menu adds the two flag toggles - "Mark as open to work" and "Mark as do not approach", which read "Remove ..." once they are set - because the header no longer draws a chip for a flag that is off. Grid rows also offer "Select for bulk actions"; on a talent pool members grid, "Remove from pool" appears too. Reject never appears on a candidate menu: only applicants who applied to a job can be rejected, on the job side.

The deal file on the job (applicants, not candidates)

Pipeline moves live on applications, not the candidate record. The deal file is the one way an application opens, from every door: an applicant row, a job in the list on a person record, the calendar, notifications, emails, Slack and Ask Lovelio links all open the same panel, and an old link ending in ?application= still lands there. Its header carries Email, Add note and the applicant "..." menu, which never repeats the two buttons beside it: Email opens the email window over the deal file, and Add note jumps to the Review step's Timeline with the note box ready. Clicking an applicant row on a job's Candidates tab opens the deal file: the same panel a row on the home page's money belt opens, and the same one a candidate dot or face opens on the jobs list's Race Track and Deal Board views, so every dashboard reads identically. It is a right-side panel like every other record panel (drag its left edge to resize - it remembers your width), with a list of steps down the left and the selected step's own pane on the right. The list shows every step of the deal, top to bottom, never hiding one: Float, Review, Screen, Submission, Client interview, References, Offer, Placement, each with a coloured dot (green done, red went wrong, pink your move, amber waiting on someone, hollow not started), a one-line state and a date. Clicking a rung shows that step's pane on the right; opening a candidate opens the step that needs you, or else the step for the stage they sit at now, so a candidate moved back to Yes opens on Review, not on the interview they once had. Every pane opens on one plain-English sentence (the verdict card) with the step's verbs on the card, and the step's content split behind tabs.

The Review rung is the triage step. Its card states where the human decision stands ("Sarah needs a decision.", "You marked Sarah Maybe.", "You marked Sarah Yes.") and, while the decision is open, carries the same Yes / Maybe / No triage buttons as the grid rows - pure stage moves, no emails, no other side effects, and the mark they already carry is hidden. While no human has acted on an AI verdict, the card notes the suggestion in so many words ("Lovelio suggests Yes - job fit 82."); the AI never decides. Below the card, "The assessment" tab holds the scorecard: their current role and phone number as a clickable link (a click opens your phone or VoIP app's dialler), the AI assessment's Job fit and Client fit scores (plus Screen once a phone screen has a score) with its summary, a "View full assessment" link that expands the per-criterion detail in place, and an "Our history with [name]" panel. The history panel is what your agency already knows about this person rather than what the AI thinks of them: a past placement, a contact role at a client, the last time somebody here was in touch, their star rating - each line only appears when there is something to say, and the whole panel is absent for a candidate you have no history with, which is most of them. "Employment history" is its own tab: the roles from their CV in their own words, each expandable.

The review queue rides along: the header shows where you are in the list ("3 of 14") with prev/next arrows, the left and right arrow keys walk the list, and on a Funnel or Maybe candidate's Review step the keyboard decides - Yes (Y or Enter), Maybe (M, funnel only), No (N). Deciding moves straight to the next candidate still waiting on you; when nobody is left, the panel shows "All reviewed" with the pass's tally. Every other rung works exactly as it does on the home page: a consultant can run the whole deal from here - screen, submit, book the interview, follow up referees, log the offer, create the placement - each start action opening the same popup windows the rest of the app uses. Backing out of one of those windows (the Back button or Escape) puts the deal file straight back where it was - nothing to reopen by hand.

Finishing an action closes its window and puts you back on the grid - it never drops you back on a card you had already read. Actions move stages, so if you were looking at one stage on the funnel strip the grid follows the candidate to their new one - finish a screen on a Yes candidate and the grid shows the Screen stage, with them in front of you. On the Active pipeline or All views nothing is re-filtered: the row is already on screen and just moves along. The strip never sends you to No or to a stage off the strip, so a rejection leaves you where you were. Triage decisions are the exception, and always were: marking Yes, Maybe or No walks straight to the next candidate waiting on you.

The Yes and Screen grid rows keep their verb buttons (Screen / Interview / Submit, and Interview / Submit / References), and DO NEXT still carries the recommended action - those open the action's own window directly, skipping the deal file, so a consultant who already knows the move loses no clicks.

The applicant "..." menu (the same nine, everywhere except triage rows and Yes)

Wherever you reach a job application - the applicants grid row or the deal file header - the "..." menu opens with the same nine actions in the same order: Screen candidate, Book client interview, Request references, Create placement, Email candidate, Add note, Add to talent pool, Mark as No, Candidate withdrew. They never move and never disappear. An action you cannot do yet is greyed with the reason underneath it (for example "Log the offer first" on Create placement, or "Shortlist them first" on Request references). Anything else that is available right now - Shortlist, Submit to client, Run interview, Log offer, Record offer outcome, Reject, Move back to Maybe - is listed underneath those nine. Grid rows add one extra item at the bottom, "Full profile & CV", which opens the person's full record. Two kinds of row are the exception, both because the row itself already carries those actions as buttons. Funnel and Maybe rows on the applicants grid carry Yes, No and Maybe, so their "..." menu holds only Email candidate, Add note and Add to talent pool - everything else on that row belongs after the Yes, and clicking the row itself opens the deal file, whose header name opens the full candidate record. Yes rows on the applicants grid carry Screen, Interview and Submit as buttons, so the Yes row's menu is five items - Request references, Email candidate, Add note, Add to talent pool, Mark as No - with nothing greyed, no extras underneath and no Full profile item. The deal file has no such buttons, so its menu at Yes is the full nine plus Submit to client. Submit is offered once: on a Yes or Screen row whose candidate a submission has already carried to the client, the Submit button is greyed with "They are already with the client".

Selecting rows on the applicants grid gives the bulk bar the same words for the actions that work on many people at once: Submit to client, Email candidate, Add note, Add to talent pool, Mark as No, Candidate withdrew.

Saved searches

After a search, the search panel offers "Save this search and tell me when someone matches", which stores the search as a saved view (a search with no results offers the same as "save this search to be notified"). Saved views appear as clickable entries (up to 8 shown) in the list under the search box and rerun the search. That list, with your recent searches, shows while the box is empty and goes away as soon as you type. A personal saved search with a query carries a bell toggle to alert you when new candidates match. A settled AI search also stamps the URL, so copying the address shares the exact filtered view.

Open to work

Whether the candidate is in the market right now. The Chrome extension sets it automatically when it spots the open-to-work badge on their LinkedIn profile, and any consultant can set or clear it from the record's "..." menu ("Mark as open to work"). When it is set, a green "Open to work" chip shows in the header's facts strip; when it is not, the header stays quiet about it. AI search filters on it: "engineers open to work".

Do not approach

The off-limits flag. When set, the candidate is excluded from search, matching, and suggestions by default; "Do not approach" appears in the amber warning band across the bottom of the record header, and a marker shows on grid rows. Searching with an explicit do-not-approach filter is the one way to see flagged people; bookkeeping surfaces (duplicate checks, a job's existing pipeline) still show the record. Set or clear it from the record's "..." menu ("Mark as do not approach"), in the Details tab's edit mode, or via the API.

Merging two people

Two ways in, one popup. The duplicates banner on People suggests pairs it thinks are the same person; click "Merge" on a pair. To merge any two people yourself, tick exactly two on People, Recent or a talent pool, then pick "Merge" under "More" on the bar at the bottom. Merge only shows with exactly two ticked, and only for roles allowed to merge candidates. The popup shows both side by side; click a card to choose which record to keep (it starts on the one with more applications, or the older one), then "Confirm merge". The kept record takes the other one's applications, notes, tags, pool memberships and history, takes the other one's job title, employer, email, phone, location, LinkedIn or CV where its own is blank, and the other record is deleted. Nothing already on the kept record is overwritten.

Deleting and GDPR

"Delete" soft-deletes the record and closes any marketplace listing for that candidate. Deletion is blocked while the candidate has any application, from every door: the app, the API, the assistant and connected agents all refuse and name the jobs. Remove them from their jobs first. On a bulk delete of a mixed selection, the free candidates are deleted and the attached ones are skipped. Once a candidate, client or contact is deleted, nothing that links to them shows who they were: a job, placement, submission, interview or call keeps the link, marks it deleted, and shows no name, email or phone. Separately, GDPR right-to-erasure permanently removes all candidate data: applications, interviews, assessments, talent pool memberships, call recordings, the marketplace listing, and every stored file. Erasure skips the 30-day file trash and removes the off-site copies too. It is irreversible. It exists only as an API call (DELETE on the candidate's gdpr-delete endpoint, needs an API key with candidates write scope); there is no button for it in the app. Both delete and GDPR erasure are locked capabilities: a company admin cannot grant them to other roles.

Common questions

Why did clicking a row not open the full record? On Your database a row opens the full record. On the web and LinkedIn a row opens the person in the panel on the right; click "Open record" for the full record.
Why can I not delete this candidate? They have an application on a job. Close out their applications first.
Why is there no Reject on the candidate menu? Reject is an application-level action; it lives on the applicant menu on a job.
Why is an action missing from the applicant menu? It is not legal at the current stage; for example "Run interview" needs a booked interview first.
Why does a candidate not appear in search? Check the do-not-approach flag; flagged candidates are excluded by default.
How do I merge two people? Tick exactly two on People, then More, then Merge. Pick which record to keep and confirm.
Can a client see my candidate database? No. Clients only see the candidates the agency sends them in a submission.