Your team may already know the people you want to reach. Sharing relationship context can help reveal those paths, but a shared contact list is not permission to use someone else's relationship.
The best team network makes two things clear: who owns the relationship and how to ask them for help.
Agree on what is being shared
Before combining context, discuss the purpose. Are you researching investors for a raise, looking for customer introductions, or exploring potential partners? Share only the information needed for that job, and respect your team's policies and the other person's expectations.
Keep these questions visible:
- Who can see the network and which details are visible?
- Who owns the relationship?
- How current is the available context?
- Who should be asked before an introduction is requested?
- What should happen if the relationship owner declines?
Use a relationship-owner-first workflow
Imagine a sales lead finds a possible path to a target account through a teammate. The lead should not treat the path as an introduction already in progress. Instead, they can share the reason the account is relevant and ask the teammate whether a conversation would be appropriate.
The teammate might have valuable context: the contact changed roles, the timing is poor, or a different person would be a better fit. They might also be happy to check whether an introduction is welcome.
| State | Meaning |
|---|---|
| Possible path | A shared connection appears relevant. |
| Owner reviewing | The relationship owner is considering the request. |
| Approved to ask | The owner is comfortable checking interest. |
| Introduction made | Both people agreed and the introduction happened. |
A team agreement that fits on one page
Write down the purpose of the shared network, who can see it, what context is appropriate to share and how to ask the relationship owner before an introduction. Include an easy way to decline. Review the agreement when the team or use case changes so the network remains useful to everyone contributing.
Try it with Aurora, Claude or Codex
Share only information you are authorized to use, and review the result before acting.
Help our team draft a simple network-sharing agreement for [purpose].
Our visibility choices and existing policies are: [details].
Include relationship ownership, a respectful request process, what to do after a decline and open questions for the team.
Share context, not pressure
Finta Networks describes read-only network sharing and a choice about whether contact email addresses are visible. Recipients can review the shared network, but the relationship owner remains part of any introduction decision.
Use Aurora to help prepare a concise request from the context you are allowed to use. Then let the people involved decide what happens next.
The warm introductions workflow shows how to move from a possible path to a permission-aware request.