---
title: Venom People
description: Remember everyone you meet in Venom Cloud. Keep who they are, how you met, what you talked about and an AI context card per person, search by what you remember, and share people with your team without sharing your notes.
section: cloud
order: 160
audience: [user, operator]
sources: ["services/nodejs-cloud/app/(people)", services/nodejs-cloud/components/people, services/nodejs-cloud/lib/people, services/nodejs-cloud/lib/people/member-link.ts, services/nodejs-cloud/components/people/PersonLink.tsx, services/nodejs-cloud/migrations/0164_people.sql, docs/adr/0057-venom-people.md, services/nodejs-cloud/components/org/ShareTeamSelect.tsx, services/nodejs-cloud/migrations/0220_org_teams_people_funnel_outreach.sql, services/nodejs-cloud/lib/people/filter-model.ts, services/nodejs-cloud/lib/people/explore.ts, services/nodejs-cloud/lib/people/derive.ts, services/nodejs-cloud/lib/people/derive-model.ts, services/nodejs-cloud/migrations/0282_people_derived.sql, services/nodejs-cloud/migrations/0283_people_views.sql, services/nodejs-cloud/migrations/0284_people_interactions_contact.sql, services/nodejs-cloud/migrations/0285_people_companies_name_trgm.sql, services/nodejs-cloud/components/people/DeriveNow.tsx, services/nodejs-cloud/lib/people/outbound.ts, services/nodejs-cloud/lib/people/outbound-model.ts, services/nodejs-cloud/components/people/OutboundLink.tsx, services/nodejs-cloud/migrations/0342_people_link_titles.sql]
features: [cloud.page-people]
---

Venom People is a relationship memory, at `/people`. You meet people at conferences, swap a WhatsApp contact or a
card, and months later you need to remember who they were and what you talked about. People keeps that for you:
who they are, how you met, every touch since, and a short card that sums it up. `g r` opens it from any app, and
⌘K finds people by name, company or tag (type `@` to search only people).

Every member of an organisation has it. Agents use it through the [workspace MCP server and REST API](/docs/cloud/people-mcp.md). When
interest becomes real, **Create deal** on a person or company opens a deal in [Venom Funnel](/docs/cloud/funnel.md).

## Network and imports

Share people with a team or the organisation, search who knows someone at a company, and ask a colleague for a warm intro:
[Share people and find warm intros](/docs/cloud/people-network.md). Bring in contacts from files you already have (Google, iCloud,
LinkedIn, WhatsApp, Telegram, HubSpot, Pipedrive): [Import contacts](/docs/cloud/people-import.md).

## People

A person has a name, a role, a company, a location, tags, a photo URL, handles (email, phone, WhatsApp, Telegram,
LinkedIn, X, a website), how you met, the event where you met, a circle, and private notes. Add one with **Add person**
(or `c`): paste their handles one per line and Venom guesses each kind (an email, a phone number, an `@handle`, a
LinkedIn URL). "What did you talk about?" becomes the first interaction.

The form helps you fill it in:

- **Fill from a screenshot.** At the top of **Add a person**, pick, drop or paste an image (on a phone, take a photo):
  a business card or badge, a WeChat, WhatsApp, Telegram or LINE profile or chat, a phone's contact book, a LinkedIn
  profile or an email signature. Your organisation's own vision model reads it and fills the empty fields; they are
  highlighted so you see what came from the image, and you edit before you press **Add person**. A chat's gist goes
  into "What did you talk about?". An image with several people (a contact list, a group chat) shows a short list: open
  one in the form, or add the ticked ones as drafts. If the person looks like someone you already have, the form says so
  and offers to update them instead. The image is read and not kept. See [Capture people](/docs/cloud/people-capture.md#fill-from-a-screenshot).
- **Country and city.** Country is a searchable list with flags: type a name, an ISO code or a dialling code (`sing`,
  `SG`, `+65`); the countries you use most come first. City is optional. A person saved with a free-text location still
  shows it, and an obvious country in it (`Jakarta, Indonesia`) is split into the two fields when you edit.
- **Phones with their country code.** A phone or WhatsApp handle has a flag and dialling code on the left, starting at
  the person's country (else your browser's), and formats as you type. It is stored as an international number
  (`+6591234567`). Pasting `+65 9123 4567` picks the code for you.
- **Tags as pills.** `Enter`, a comma or `Tab` makes a pill, `Backspace` removes the last one, and your existing tags
  autocomplete. **Suggest tags** asks your organisation's gear for a few tags from the role, company, how you met and
  notes, preferring tags you already use; you click the ones you want and nothing is added by itself.
- **A LinkedIn URL** pasted in Handles is added as the LinkedIn handle, and fills the name from the address
  (`linkedin.com/in/sarah-chen-1234` is "Sarah Chen") when Name is empty. Venom never opens LinkedIn for you (no
  outbound call, and LinkedIn blocks them anyway): to fill role, company and location, paste or drop a screenshot of
  the profile.

When you add someone who looks like a person you already have (the same email or phone, or the same name at the same
company), Venom tells you. **More → Merge** on the person's page folds a duplicate in: empty fields are filled, tags and
handles are joined, and interactions and relationships move over.

Handles open your own apps: an email opens your mail, a phone number calls, WhatsApp opens `wa.me`, Telegram opens
`t.me`. Venom never sends a message for you.

## The list and search

The list holds everyone you may see, however many: the first 200 come with the page and the rest load as you scroll.
The order is fixed when you start scrolling, so nobody is skipped or shown twice even when a person changes meanwhile.
Each row shows the person, their seniority (a small bar mark, `?` when unknown), warmth (a dot), outreach (an arrow
mark), their country's flag, sector or function on wide screens, tags, and every company they worked at that People
knows, current first, then fainter the longer ago they left. A person of yours in a Funnel deal also gets a deal-stage
chip ("Proposal"), coloured by whether the stage is open, won or lost, that opens the deal; on a phone it is the
outreach arrow instead. Every chip is a link: click a country, a tag or a company to filter by it.

Search as you type by name, company, tag or anything you wrote: "the cold-storage founder from Jakarta" works. When
your organisation has an embedding model on its gear, the search also matches by meaning over your own people (the
**By meaning** switch); otherwise it matches words.

Matches by words show first, with no model call, a moment after you stop typing; people found by meaning and each
filter's counts fill in right after ("adding matches by meaning…"). While the next answer is on its way the rows you see
stay, dimmed, and the ones that still match on their face (name, role, company, place, tags) stand in for it; an answer
for an older query never replaces a newer one, and going back to a query you just typed (backspace) answers at once.
The first 50 matches come with the answer and the rest load as you scroll. The address bar keeps the query, so a
reload or a shared link opens the same search.

### Filters

Each filter is a pill. It opens a list of its values, each with how many people you would get by adding it to what is on
now (the counts are over every other filter, so they always add up to the rows you see), and you can tick several: they
match any of them. **Unknown** is always a value of its own with its count, so a filter never hides the people it knows
nothing about unless you leave Unknown unticked.

| Filter | Values |
|---|---|
| **Country** | the person's country, with **+ nearby** for its neighbours (Singapore + nearby adds Malaysia, Indonesia, Thailand, Vietnam, the Philippines and Brunei) |
| **Seniority** | 1 student or intern … 6 C-level or founder, or unknown; a word such as `seniority=vp` matches what AI classification said, as [Insights](/docs/cloud/people-classification.md) counts it |
| **Company** | anyone who works there now or worked there before ("34 now · 51 ever"); **Only where they work now** narrows it |
| **Tag** | your tags |
| **Warmth** | hot, warm, cooling, cold, never in touch (below) |
| **Outreach** | never contacted, sent with no reply, talking, replied then quiet, in a sequence, in a deal (below) |
| **Deal stage** | **No deal**, then each stage of your Funnel pipelines in order ("Consulting · Proposal"); a person counts under one stage, their deal's (below) |
| **Pipeline step** | targets, reached out, talking, in a deal, won: each of your people in one step at most, the furthest they reached, as [Insights](/docs/cloud/people-classification.md#insights) counts them (`step=deal`) |
| **More filters** | region, city, function, sector, persona, gender (a guess), school, topic, personality, circle, relevance, opportunity, event, whose |

**Needs warming** keeps people who are cooling off, or cold and senior (manager or above) or highly relevant. Sort by
most recently changed, name, last touch, relevance, seniority, warmest first, or most in need of warming. **Group by**
country, region, seniority, function, sector, persona, warmth, outreach, deal stage (no deal first, then the stages in
their pipeline's order), relevance, company or event puts a header with the
group's count over each run of people, and **Board** shows them as columns.

Everything is in the URL (`/people?country=sg,my&nearby=1&seniority=5,6`), so a filtered list is a link you can keep.
A value a filter does not know (a country by name, a typo, a stale link) matches nobody; it never drops the filter and
shows everyone. Agents get an error instead.
**Views → Save this view…** keeps the filters, sort and grouping under a name; only you see your views.
**Open in graph** opens the [graph](/docs/cloud/people-graph.md#filters) with exactly these filters (your own people), and its
**Open in list** comes back; the graph's **Views** opens a saved view as a graph.
To ask who to contact about a topic in a territory, ranked with a route for each, use [Reach](/docs/cloud/people-reach.md). A saved
Reach view can run every night and leave its picks, with drafts, on Today: [the overnight queue](/docs/cloud/people-overnight.md).

Warmth and outreach are worked out from your own interactions. A note to yourself and LinkedIn's "connected" marker are
not contact. **Outreach**: in a deal (an open Funnel deal), in a sequence (active in Outreach), talking (they wrote within
30 days), sent (your last touch was outbound and nothing came back), replied (they wrote, longer ago), never. **Warmth**:
hot or warm (strong enough and in touch within 90 days, not overdue for their circle), cooling (strong, or in touch within
a year), cold, never.

**Deal stage** is the stage of a person's Funnel deal: their furthest open deal (the latest stage of its pipeline), or,
with none open, the deal changed last. Someone in two deals is under one stage everywhere, never counted twice. Only
deals you can see count (your organisation's and your teams'), so a colleague's deal in a team you are not in never
shows, and like the derived fields it is shown and filtered for your own people only. The chip, the filter's counts, the
group and **At a glance** on the person's page always agree.

### Derived fields

Seniority, function, sector, country (with region and city), gender and personality are worked out for each of your own
people, without a model: from the job title, the company name, the location, a phone's country code, an email or website
domain, the headline and the notes. With [AI classification](/docs/cloud/people-classification.md) on, its answer beats these rules;
what you set by hand beats both. A person's page shows them under **At a glance**, each with where it came from ("from the
job title", "a guess from the first name", "set by you"); **Edit** there sets one by hand or gives it back to the rules
(**Back to automatic**). Gender is only a guess, labelled as one, and only you ever see it. It comes from pronouns the
person declares the usual way, in brackets ("Jane Tan (she/her)"), after their name, at the start or end of their
headline ("she/her | Product") or as "Pronouns: he/him", or else from the first name. Pronouns written about something
else ("Speaker on she/her pronouns in tech") and pronouns in your notes are never read. Unknown stays unknown: nothing is
filled in to look complete.

Seniority comes from the role, not the people around it: "Assistant to the CEO", "Founder's Associate" and "Office of the
CEO" do not rank as a CEO, and an intern, assistant, associate, coordinator, secretary, PA or EA stays at that level. A
role an intern, trainee, student, participant or volunteer holds ranks as a student at most, whichever side of a comma the
word is on ("Intern, CEO Office"), and so does an officer of a club, society, union, council or chapter ("President of
Toastmasters Club"). A senior word naming what a team works on is not the person's rank: "Head of Founder Success" is a
head.

Sector by rules comes from a list of well-known employers by name (banks, payment networks, big tech, telcos, airlines,
government agencies, universities, investors: "DBS", "Visa", "Airwallex", "Grab", "GovTech Singapore", "NUS", "Singapore
Airlines"), then from words in the company's name ("…Payments", "…Telecom", "…Technologies"), then from a few title
words ("Lawyer", "Professor", "Pilot"). Beyond the classification's sectors, the rules also answer technology, telecom
and aviation-travel. A name that says nothing on its own ("Summit", "Pollen") stays unknown. **At a glance** says which
of the three found it.

The person's company is their current job. Every other employer is now, past or **dates unknown**, by one rule the
chips, the company filter, the counts, Reach, the graph and the person's page share: a job with an end date, or one you
marked ended, is past; a job read from a profile with no start date (an "at export" or history line, even one the
profile marks current) has its dates unknown; anything else is now, so a job you add by hand without dates is current,
and so is one dated "2021 – Present". A job with its dates unknown counts in "ever" but not in "now", and its chip is
drawn dashed with "dates unknown". Names of one company written differently are one company in the chips, the
counts and the company filter: case, punctuation, a legal suffix ("Pte. Ltd.", "Inc", "GmbH", "Sdn Bhd", "K.K."),
Indonesia's "PT", or a native-script name beside the Latin one ("그린랩스 Greenlabs" and "Greenlabs"). Two companies with
the same Latin name and different native names stay apart: "삼성전자 Samsung" and "삼성생명 Samsung" are two companies, and
plain "Samsung" stays with each. The company records themselves stay as they are.

A person is worked out when you add or change them. After an import, the rest are worked out in the background, never
while a page waits: the list and **Insights** say "Deriving 3,200 of 6,415" until they are done, and **Derive now** next
to it finishes the job while you watch. Until someone is worked out, the graph and "who do I know in…" use what is known
about them so far. They come from your own notes and handles, so these filters match only your own people: a person a colleague
shared with you shows in the list but never under a country or seniority filter. A country guessed from a phone, an email
or your notes stays yours everywhere; only one read from the company's name or website, or their headline, can relate
them to others in the graph and in "who do I know in…".

Keys: `/` search, `c` add a person, `j`/`k` move, `Enter` open, `n` add a note to the focused person. On a person's
page, `n` (or `l`) jumps to the note box, `e` edits, `Escape` goes back.

## Select and edit many

Tick people in the list to act on all of them at once:

- The checkbox at the top of the list picks everyone in view (with your search and filters). It shows a dash when only
  some are picked. When the list has more than it loaded, **Select all N matching** picks every match, up to 10,000.
- **Shift**-click picks the range from the last person you clicked. **⌘**-click (**Ctrl**-click on Windows and Linux)
  adds or removes one person.
- Keys: `x` picks the focused person, `Shift`+`↓`/`↑` (or `Shift`+`J`/`K`) extends the pick, `⌘A` (`Ctrl+A`) picks
  everyone in view, `Escape` clears.
- On a phone, press and hold a person to start picking. While you are picking, a tap adds or removes someone.

The bar at the top of the list then offers:

| Action | What it does |
|---|---|
| **Tags** | add tags to everyone picked, or remove tags some of them have |
| **Circle** | put them in the inner circle, active, long tail, or no circle |
| **Set company**, **Set location** | the same company or location for everyone; leave it empty to clear it |
| **Set seniority, country, gender, sector** | set by hand for everyone picked (kept over the guesses), clear, or back to automatic. The unknown counts on [Insights](/docs/cloud/people-classification.md#insights) open exactly the people to set |
| **Share** | who may see them, as on a person's page ([the network](/docs/cloud/people-network.md)) |
| **Sequence** | add them to an Outreach sequence |
| **Merge 2 people** | with exactly two of yours picked: pick the one to keep, and the other folds into it |
| **Export CSV** | a spreadsheet of the people picked: name, role, company, location, tags, circle, last touch and strength; for your own people also emails, phones and other handles, seniority, function, sector, country, gender (a guess), warmth, outreach and past companies |
| **Enrich N people** | when your organisation turned [enrichment](/docs/cloud/people-enrichment.md) on: asks its providers about each of your people picked, with progress and cost; what they find comes back as suggestions on each person |
| **Delete** | moves them to the trash after you confirm. **Undo** in the message that follows brings them back with their notes, interactions and images |
| **More → Add to pipeline**, **Mark reached out**, **Keep warm** | a Funnel deal per person or per company, an outbound touch logged on each, or a circle and cadence, as in [Reach](/docs/cloud/people-reach.md#act-on-many) |

An action changes everyone it can and tells you about the rest, for example "Tagged 12 #investor; 2 are shared with
you and only their owner can change them". People a colleague shared with you are theirs to change. A contact you
shared with a team or the org needs a role that writes in People (owner, admin or developer); deleting your own is
always yours to do. One action changes at most 10,000 people, 500 at a time; the bar says how far it got ("Changing
2,000 of 6,500…"), and if something stops it part way, the message says how many changed and that the rest did not.
**Undo** after a delete goes in the same steps. An agent's `people_person_bulk_update` works for about 20 seconds and
answers with the people it did not reach yet (`left`), to send again.

On a phone the bar shows the count and an **Actions** menu with the same choices.

Agents do the same with `people_person_bulk_update` ([People for agents](/docs/cloud/people-mcp.md)), or
`POST /api/v1/people/bulk`.

## A person's page

The buttons sit at the top right: **Add note**, **Add snapshots**, **Create deal**, **Brief**, **Share**, **Edit**, and **More**
for **Merge** and **Archive**. On a phone they get a row of their own under the name, and **More** also
holds **Create deal**, **Add snapshots** and **Enrich**.

- **Context**: a short card with three parts, how you met, what they care about, and open loops (things you promised).
  Every line cites the interactions it came from; click a citation to jump to it. It is rebuilt after you log an
  interaction, and on **Refresh**. It uses your organisation's own gear, under a daily limit (below).
- **Add note** (the button, or `n`): one box for a note or a meeting. Pick a kind (note, met in person, call, message,
  meeting, email), a date (today by default), where, and what happened. `⌘↵` saves it, and the context card is rebuilt
  in the background and shows the new note a few seconds later.
- **Timeline**: every note and interaction, newest first, each with its date, kind, place and event. **Edit** changes
  one (kind, date, where, text) and the **x** deletes it; only you can, because only you can read them.
- **Mentioned in**: the notes you can read that mention this person with `@`, with their title and date. **Log as
  a meeting note** adds a meeting to the timeline that links to the note (once per note). See
  [Notes mentions](/docs/cloud/globe-mentions.md).
- **Mentioned in** also lists your own People notes that link this person: how you met someone else, or a note on
  their timeline (see [Linking people](#linking-people)). Only your own: nobody else's notes are read.
- **Reach**, **Details** and **Notes**: handles, where and how you met, circle, last touch, strength, private notes.
- **Relationships**: who they know, and who introduced you.
- **Who knows them**: colleagues who know the same person (the same handle, or the same name at the same company) and
  shared them with you.
- **Brief**: one page on them before you meet, every line a stored fact with its date. See
  [Meetings in People](/docs/cloud/people-meetings.md#the-brief).

## Linking people

**How we met**, **Notes**, **What did you talk about?** (when adding), the note box on a person's page, a note's
**Edit**, and the "what you talked about" box in **Capture** all link people. Type `@` and a name: the menu lists the
contacts you may see. Use `↑`/`↓` to move, `Enter` or `Tab` to pick, and `Esc` to close. The last row, **Add "name" as a
person**, makes a new private contact with that name and links it. A linked person shows as a pill.

- **Click a pill** to open the person's page. `Cmd`-click (`Ctrl`-click on Windows and Linux) opens it in a new tab,
  `Tab` then `Enter` opens it from the keyboard, and hovering shows a card with their role and company, when you last
  talked, and **Open in People**.
- **While you edit** a field, a click on a pill opens a small menu instead, so the form you are filling in stays open:
  the card, **Open**, **Copy link**, and **Remove link**, which turns the pill back into plain text. `Cmd`-click opens the
  page in a new tab. `Backspace` on a focused pill removes it.
- **Names you typed**: when the text holds the full name of a contact you can see and it is not a pill yet, the field
  offers **Link Joel Yarbough?** underneath. When a name follows "introduced by", "intro from" or "via" and no contact has
  it, the offer is **Add Joel Yarbough as a person**. Only whole names count, and no AI is involved.
- **Introductions**: a pill right after "introduced by", "intro from", "via", "through", "thanks to" or "referred by"
  in **How we met** (or before "introduced us") records **Introduced by** under Relationships, by the person's id, when
  both people are yours. A link that already exists keeps its note and date. A pill anywhere else links nothing.
- **What a pill shows**: the person's current name, so it follows a rename. A pill of someone you can no longer see shows
  the name as it was written, as plain text, and nothing more. These fields are private to you, so nobody else sees the
  pill or its name.
- **Everywhere else**: search, the context card, drafts, tag suggestions, Ask, intros and agents read the plain name. A
  person is found by the name of the person you linked in their notes.

The text is stored with each pill as `@[Name](person:<id>)`, the shape Notes comments use for members. The REST and MCP
`how_met` and interaction fields carry this text as stored; the MCP tools' answers show the plain name.

## Links

A web address (`http://` or `https://`) in **How we met**, **Notes** or a timeline note is a link. It has a dotted
underline and a small arrow-out icon, opens in a new tab, and shows the full address when you hover over it. A meeting
synced from Granola gets a link to its Granola note under it. Punctuation that ends the sentence (a full stop, a comma, a
closing bracket) is not part of the link, and nothing else in the text becomes one: `javascript:`, `data:` and a bare
`example.com` stay text.

- **Page title** (the default): a link shows the title of the page it points to. Until the title is known, or when the
  page has none, it shows the site and a short path, such as `notes.granola.ai/d/1a2b…`. A Granola note shows the
  meeting's title from your [Meetings sync](/docs/cloud/people-meetings.md), or **Granola note** when there is none.
- **Full URL**: a link shows the whole address.

Choose in **People → Settings → Links**. The choice is yours alone and applies to every People page.

Titles come from Venom's server, not your browser. When you view a person, it asks once for the titles of every link on
the page, then reads each page's `<title>`: only public `https` addresses, never following a redirect, at most 4 seconds
and 256 KB a page, 4 pages at a time and 20 links a request. Each title is kept for your organisation for 30 days, and a
page with no title (or one that could not be read) for a day, so a page is read at most once per organisation in that
time. Granola notes are never read this way, because they need your Granola sign-in. Without a network the links keep
their short form. Links with `http://` addresses always show the short form.

## Opening a person

Clicking a person anywhere in Venom opens their page in People: a pill, a mention in Notes, Tasks or Chat, an assignee,
a deal's owner or people, an incident's commander, a support conversation's assignee or customer, a calendar booking's
invitee or team host, and a row in **Settings → Members**. Every link is focusable, `Enter` opens it, and `Cmd`-click or
`Ctrl`-click opens it in a new tab.

A contact opens their page directly. An org member (an `@joel` mention, an assignee, a comment's author) is matched to
the people you can see, at `/people/member/<id>`:

1. By the member's email, then by the phone they verified for paging in Incidents.
2. Your own record wins. With none, a record shared with the organisation or one of your teams is used.
3. A colleague's private record is never used, even when it matches, so you never see their notes.

When nobody matches, the page shows the member (name, org role, email) and asks **Add Joel to your People?**. Nothing is
saved until you click **Add to People**, which makes a private person with their name, email, verified phone and role
and opens it. The next click on Joel opens that person. **Not now** goes back. Membership itself is never changed here.

Agents do the same with `people_person_search` (by the member's email) and `people_person_create`.

## Companies and events

Companies and events belong to the organisation: everyone sees them. A company appears when you add someone who works
there. The companies list says how many people you may see there now and ever ("34 now · 51 ever": past employers of
your own people count in ever) and sorts by either; a person promoted there counts once. A company's page lists the
people there now that you may see, then those of yours who worked there before with when, latest leavers first, and its
domain, location and shared notes. Its counts are always the true ones; past 500 people the page shows the first 500 by
name and links to the list, which has them all. Past jobs read from a snapshot's profile follow the profile: one it no
longer lists goes, while jobs you added by hand stay. Add events at
**Events → New event**; an event's page lists the people you met there. Who you met at an event stays yours.

The pages are `/people` (the list), `/people/{id}` (a person), `/people/companies` and `/people/companies/{id}`,
and `/people/events` and `/people/events/{id}`.

## Who sees what

People are private by default. On the person's page, **Edit → Who can see them** shares them:

| Setting | Who sees them |
|---|---|
| Only me | you |
| My team | you and the members of one of your teams, including the members of the teams above it |
| Everyone in the org | every member of the organisation |

A colleague who can see a person you shared sees who they are (name, role, company, location, tags, photo), that you
know them and how strongly. They never see the handles, how you met, notes, the context card, interactions or
relationships, and search by meaning never ranks someone else's people. Outreach keeps to this too: a colleague who
enrolls someone you shared never reaches them through your handles, only through addresses they hold on a contact of
their own ([Outreach](/docs/funnel/outreach.md#sharing-a-sequence-with-a-team)). Only you can change a person you own. Owners and
admins of the organisation have no way around this.

Sharing needs a role that writes in People: owner, admin or developer ([who can do what](/docs/cloud/teams.md)). With the billing
or viewer role you keep your own private contacts and every control on them, but the controls that reach other members
are disabled, and hovering one says why:

- **Share** on a private person, **Share…** on the list's selection bar and on Today's circles, and *My team* and
  *Everyone in the org* in **Who can see them**;
- **Edit** on a person you shared earlier (make them private with **Share → Only me** first);
- **Edit** on a company page, since a company's details are everyone's.

Team membership flows down to subteams: a member of Engineering is also a member of Platform under it, at any depth.
So a person shared with Platform is seen by Platform's members and by the members of Engineering above it, while one
shared with Engineering is not seen by someone who is only in Platform, and a sibling team sees neither. Teams are made
in **Settings → Teams** ([teams](/docs/cloud/teams.md)).

### Org webhooks {#webhooks}

People is each member's own memory, so the org's webhooks (Settings → Webhooks) see only what every member already
sees: a person shared with **Everyone in the org**. `people.person.created` says one became org-wide (added that way,
or shared later), `people.person.updated` that one changed, and `people.person.removed` (with the id only) that one was
archived, merged away, or made private or team-only again. They carry the id, name, role, company and the member who
owns the record, never handles, how you met, notes, the card or interactions. A private or team-only person never
leaves. These events are not ticked by default on a new endpoint.

## AI and limits

The context card and search by meaning use your organisation's own gear (its providers, keys and budgets), never
anything else. Every People AI call (photo and voice capture, context cards, recall, Today, drafts, intros, signals,
classification, the overnight drafts) counts against one daily limit per organisation, **People's daily AI limit**:
$1 a day by default, from $0 to $100. At the limit, or without a gear, the card says it is waiting and capture asks you
to add the person by hand or share a vCard.

### People's AI gear {#ai-gear}

Under the limit, **Gear for People's AI** picks the gear that photo, voice and typed capture, context cards, recall, People
chat, meeting notes and topics run on. **Org default** (named with the gear it is now) is the first option; then every gear
of your organisation and venom's built-ins unless your organisation allows only its own. A gear that cannot run now is
greyed out with the reason. The line under it names the model photos are read with (the gear's `vision` role, else its
main model), or says the gear has none that reads pictures. Signals and classification keep their own gear settings.

**If this gear's provider is out of credit, use another gear**: when a call fails because the provider account behind the
gear cannot pay (HTTP 402, or a 429 such as `insufficient_quota` or `credit_balance_exhausted`; never an ordinary rate
limit), People tries once more on the next of your organisation's own gears that can do the same kind of call (for a
photo, one whose model reads pictures) and that another provider serves, within the daily limit; never on a built-in. It is on by default for **Org default**
and off by default for a gear you chose, so an organisation that picked a provider on purpose is never moved off it.
It never moves from a model your own daemons serve to a cloud provider. When the call still fails, capture says which
provider, which gear and what to do (code `provider_out_of_credit`), with a link to People → Settings.

The gear and the switch are changed by the same people as the limit, with `people_aisetting_set` (`gear`, `fallback`)
too, read with `people_aisetting_get` (`gear`, `fallback`, `gears` with each one's availability, `model`, `vision_model`),
and recorded in the audit log as `people.ai.gear` with the old and new values. They are stored as `people_ai` in the
organisation's settings.

An owner or admin changes the limit in **People → Settings**, at the top of the page, or with the
`people_aisetting_set` tool. Every member can read it there or with `people_aisetting_get`. The change is recorded in
the audit log as `people.ai.limit`, with the old and the new value. An agent acting for a member (a quick chat, or an
agent's run on a computer) cannot change it. The value is stored as `people_ai_daily_cap_usd` in the organisation's
settings.

### Today's AI spend

The top of **People → Settings** shows today's spend against every daily cap People has, one bar each:

| Bar | What it counts | Where its cap is changed |
|---|---|---|
| People AI (overall limit) | every People AI call | this section |
| Signals | signals' assessments | the Signals section ([signals](/docs/cloud/people-signals.md)) |
| Classification | classification runs and category scans | the classification section ([classification](/docs/cloud/people-classification.md)) |
| Enrichment (paid providers) | paid data providers (People Data Labs, Apollo) | the enrichment section ([enrichment](/docs/cloud/people-enrichment.md)) |

Signals and classification sit under the overall limit: each stops at its own cap or at People's limit, whichever comes
first, so one of them can stop while its own bar is not full. Enrichment's cap counts what paid providers charge, not
AI, so it is separate. A bar says **Limit reached** when the spend reaches its cap, **Limit is $0** when the cap is 0
(nothing runs), and **Off** for a feature that is turned off. Every figure is a UTC day and starts again at midnight
UTC. The sections below hold each feature's own cap. The same bars, with every other product's daily AI limit, are on
the [AI spend](/docs/cloud/ai-spend.md) page (**See all limits**), where owners and admins can change each one too.

Venom does not look anyone up on the web: no scraping, no enrichment, and a LinkedIn URL is kept as text.

## What's next

People is the first part of a plan ([ADR 0057](https://github.com/elishahbiz/venom/blob/main/docs/adr/0057-venom-people.md)):
capture in ten seconds (card photos, vCards, voice notes, a Telegram bot), an event debrief and keep-warm with circles,
strength and "five people today", the Funnel CRM on top, and warm-intro paths across the team.
