← Help centre

AI assistants

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

Settings > Integrations > AI assistants is where an admin decides how AI assistants (Claude, ChatGPT, Copilot and the like) connect to your agency's Lovelio: who may connect one, what it can do, and how many candidates it has looked at. Admins only. Pausing a person sits on Settings > Workspace > Users. There is nothing to set up: the settings below are already on.

The page has three parts: "Waiting for you" (only when someone has asked to connect), "Team settings", and "People".

What counts

On screen never counts. Reading profiles and CVs in Lovelio is the job, and nobody monitors it.

Leaving Lovelio always counts. A candidate counts as accessed when a copy exists outside Lovelio:

  • a CV or document file downloaded in the app;
  • a row exported to CSV from the candidates list;
  • any candidate returned to an AI assistant or API key, because that record now sits on a machine outside Lovelio. For an assistant, a read is a download.

Each candidate counts once per person per day, whichever door it left through and however many times. Fifty downloads of the same CV in one day is one candidate. A profile and its CV are one count; the "Of which CV files" column says how many of them included a file.

The daily limit

An assistant or API key acting for a consultant (anyone who is not an admin) can take out 200 candidates a day unless you change "Daily limit per person" in Team settings. At the limit it is refused with: "You have reached today's limit for candidates accessed. Ask an admin if you need more." Candidates it already took out today do not count again, so re-reading the same records is free. The limit resets with the person's own day. Keys held by an admin have no limit.

"When limit reached" decides what happens at the limit:

  • Stop until tomorrow (the default): further candidates are refused until the next day.
  • Keep going and email me: nothing is refused; it keeps counting and every admin gets an email.

You can give one person a different limit from their panel.

Who can connect an assistant

A consultant connects their own assistant from the assistant's own app. They sign in to Lovelio, see exactly what it will get, and ask to connect. Two switches in Team settings decide what happens next:

  • Team can connect assistants: On or Off. Off means only admins can connect anything.
  • I approve each one: On means a new connection waits for an admin; Off means it goes live straight away.

You get an email and a notification when someone asks. They get an email when you approve or decline.

What it can do

"What it can do" in Team settings sets the level for everyone. Three levels:

  • Look only: reads records. Changes nothing. Candidates, CVs, jobs, clients, pipeline, submissions and interviews.
  • Recruiter (the default): adds notes, moves stages, updates candidates. Cannot submit, book or email.
  • Full desk: also sends to clients, books interviews and sends email as the consultant. Also reads placements without fees, talent pools, forms, quotas and analytics.

"Fine-tune" then "Show each area" opens one row per area of Lovelio with None, See or See and change. Changing a row makes the level "Fine-tuned"; picking a level again resets it. Candidates and their CVs can always be seen: an assistant that cannot read the CV cannot screen, so the daily limit is the control. Fees and money, recruiter DNA, integrations, marketplace, webhooks and account details sit under "Show more" and are off in every level. Assistants never touch users, settings, API keys, billing or deleting records.

The assistant uses the connected person's current role and record access. Granting an area does not make a consultant an admin. Manage role permissions in Settings > Workspace > Permissions. Personal connections cannot create API keys; create these yourself in Settings > API.

Giving more requires the person to reconnect and agree again. An existing connection never gains extra access from a settings change. Taking access away narrows the next request.

Each person in the People table has their own "What it can do" menu: Team setting, Look only, Recruiter, Full desk, or Turned off. Team setting follows the team level when it changes; any other pick pins them. Click a person to open their panel, where you can also change their daily limit or fine-tune their areas. Every change saves straight away.

Waiting and connected

A request shows under "Waiting for you": who wants to connect which assistant, and when they asked. Choices:

  • Approve: the assistant gets the person's level and anything extra it asked for is dropped. This is the one to use.
  • Approve everything it asked for: shown only when the assistant asked for more than the level allows; grants the extras too.
  • Decline: nothing is connected.

While it waits, the assistant stays connected but answers every request with "This connection is waiting for an admin at (your agency) to approve it." The person does not need to reconnect: once you approve, they get an email and it works on its next request.

The person's panel lists their assistants, each with Connected and when it was last used, and a Disconnect button. Disconnecting takes effect on the next request.

Pausing someone

Pausing lives on Settings > Workspace > Users: the pause icon on the person's row. This page shows a red "Paused" tag when somebody is paused, and the person's panel links across.

Pausing signs them out everywhere, stops them signing back in, and disconnects every API key and AI assistant acting for them. Nothing they own is deleted or reassigned: their candidates, jobs, notes and their name on the timeline stay exactly as they are. Restoring lets them sign in again; their keys stay disconnected and they reconnect their assistant, which is the safe way round.

Removing someone from the workspace does the same revocation automatically.

When someone is far above their usual

Every admin gets one email and one notification a day when a person's week or month goes past three times their usual. It is a nudge, not an accusation, and the same threshold colours the cells on this page. One alert per person per day, whatever else happens.

Candidates looked at

  • People shows each person, their assistants (live, or "waiting"), their "What it can do" pick, and how many candidates they took out this week. The number becomes an amber pill when the week is three times their usual and red at ten times, saying how many times usual it is.
  • Click a person for their last eight weeks as bars, coloured the same way. Usual is the average of their completed weeks so far. Small numbers never colour: a week under 15 candidates is never amber.
  • "Download CSV" gives the whole history for everyone, split by door: pulled by an assistant, downloaded in app, exported to CSV. The CSV link in a person's panel gives just theirs. Company API keys with no person behind them are in the CSV only.

History is never pruned. The suspicion is often found weeks later, so the download looks back as far as the data goes.

CSV export

Export CSV on the candidates list is for admins and team leaders only, and every exported row counts as a candidate accessed.

What it cannot see

A person paging the candidates table with their browser's developer tools gets profile text without CV files, and nothing counts it. Screens can be photographed. The page makes bulk copying slow, visible and attributable; the access history is what turns a suspicion into evidence.