---
title: Share people and find warm intros in Venom People
description: Share a person, a selection or a whole circle with a team or the organisation, search who in the org knows someone at a company, see the warm-intro paths ranked by strength, and ask a colleague for an intro. Colleagues see that you know someone, never your notes.
section: cloud
order: 163
audience: [user, operator, agent]
sources: ["services/nodejs-cloud/app/(people)/people/network", services/nodejs-cloud/components/people/Network.tsx, services/nodejs-cloud/components/people/Share.tsx, services/nodejs-cloud/lib/people/network.ts, services/nodejs-cloud/lib/people/network-model.ts, services/nodejs-cloud/lib/people/mcp-network.ts, services/nodejs-cloud/lib/people/tools-network.ts, services/nodejs-cloud/migrations/0167_people_network.sql, docs/adr/0057-venom-people.md, services/nodejs-cloud/components/org/ShareTeamSelect.tsx]
features: [cloud.page-people]
---

[Venom People](/docs/cloud/people.md) is personal by default. Your network gets useful when colleagues can see who each other
knows. Sharing is how: you decide per person, per selection or per circle, and a colleague then finds out that you know
someone, never what you know about them.

## What sharing shows

Share a person with **a team** (one of your own teams, or a subteam under one) or with **everyone in the organisation**. A
colleague who may see them gets:

| Colleagues see | Colleagues never see |
|---|---|
| name, role, company, location, tags, photo | handles (email, phone, WhatsApp, Telegram), how you met, the event |
| that **you** know them, your strength with them and when you last touched | your notes, the context card, the interactions, relationships |

Search over a shared person reads only those public fields. The words in your private notes find nothing for anyone
but you, and your semantic search never ranks someone else's people. An org owner or admin has no back door: a
private person is private from them too. Another organisation sees nothing.

## How to share

- **One person:** open them and press **Share**. Choose *Only me*, *A team* or *Everyone in the organisation*. The team
  picker shows the org's tree of teams; you can pick your own teams and the subteams under them, and the rest show
  greyed out with the reason.
- **Several:** tick the boxes on the **People** list (or press `x` on the highlighted row) and press **Share…** in the
  bar that appears.
- **A circle:** on **Today**, each circle has a **Share…** link that shares everyone in it.

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)).

Choosing *Only me* takes sharing back; the person leaves colleagues' searches and intro paths straight away. Only the
owner's rows ever change, so you cannot change a colleague's sharing and they cannot change yours.

Sharing needs the owner, admin or developer role. With the billing or viewer role the **Share** buttons are disabled
and say why, and the share dialog offers only *Only me*, so you can still take back a person you shared earlier.

## Who knows someone at …

Open **Network** (`/people/network`) and search a company, a topic or a name: *Acme*, *cold storage*, *Dewi Putri*.
Venom searches your own people (your private notes count for you) and everything colleagues shared, then groups the rows
that are the same real person. Each result shows who knows them and, below it, the **warm-intro paths**:

> You → **Ann** → Sarah Lee · strong · last touched 3 weeks ago

Paths are ranked by the colleague's **strength** with the person (the same score as on Today, 0 to 100). A recent touch
only breaks a near tie. You are never a path to yourself: if you know them, the card says so. A shared person's page
shows the same paths under *Ways to reach them*.

## Ask for an intro

**Ask for intro** on a path asks that colleague to introduce you. Say why: a specific reason gets a yes. The request
lands in the colleague's **bell** and under **Network → Intro requests**. One request is open per person at a time;
asking again updates your message. You can withdraw a pending request.

The colleague chooses:

- **Accept and draft the intro:** Venom writes a short message to the person, in the colleague's voice, from what the
  colleague knows about them and the reason you gave. It is one call through your organisation's own gear under People's
  daily AI limit (default $1 a day). At the limit, or with no chat model, the request is still accepted and the page says
  why there is no draft.
- **Accept:** write it yourself; **Decline** with an optional note.

The colleague reads and edits the draft, then sends it from their own WhatsApp, Telegram or email with the buttons on
the card (Telegram cannot prefill text: copy first). **Venom never sends the intro, and never writes to the person.** You
see the colleague's answer in your bell: that they said yes, or passed, and their note. You never see the draft.

You can add a **note to forward** (**Draft from my pitch** fills it from your one line and your reason). Once accepted,
either side can mark it **Introduced**. Your sent requests also show under **Network → My asks**, next to the asks you
make of your own contacts ([Ask for an intro](/docs/cloud/people-intros.md)).

## Agents

The same actions are tools on the [workspace MCP server and REST API](/docs/cloud/people-mcp.md): `people_person_share`,
`people_network_search`, `people_intro_path`, `people_intro_request`, `people_intro_list`, `people_intro_respond`. They
use the caller's own member, so the privacy line above holds for an agent exactly as for you.
