Is Nod team context available to everyone?

No. Team context is early access for approved teams, not a generally available self-service workspace. Individuals can still use Nod without joining an organization.

What gets shared when I join a Nod organization?

Nothing is shared by membership alone. Team context appears only when you deliberately share a finished conversation or folder, and you can remove that share. A public summary link is a separate, revocable action.

Can a team administrator read conversations I kept private?

No. In the current early-access workflow, administrators can manage team membership but cannot open, export, or search private conversations. Forced organization ownership and administrator-read access are future, unreleased controls.

Team context

Early access

The context is in someone's head. Nod puts it where the team can ask.

Every call your team takes ends as dated decisions, commitments and open questions, in the words people used, and they stay yours until you share them. Share one conversation or a whole folder with a team, and the next person reads the memory instead of booking a meeting with you. No bot joins the call, no audio is kept, and joining an organization makes nothing visible on its own.

Download for macOS Book a team demo

Team context is early access for approved teams. Individual Nod has a 14-day trial, no card. macOS only.

In your memory

9 sessions this week · 4 decisions · 3 open commitments

Team context lets an approved early-access team share selected conversation memory without turning every personal meeting into a company archive. Joining an organization shares nothing by default. A person chooses a finished conversation or folder to share, colleagues can read and ask across that material, and the owner can remove access later.

By Vlad Kampov, Nod co-founder · Published September 1, 2026

Product evidence: The early-access workflow supports deliberate conversation and folder sharing while private meetings remain private by default.
Limits: Team context is early access, not a generally available self-service workspace. Nod does not currently claim SSO, SCIM, or organization-wide administration.
Method: The workflow separates what the user does, what Nod produces, and what still needs human judgment. Product behavior is checked against current Nod documentation; no customer outcome is generalized.

Sources and related reading

The problem

Your team's memory is spread across five people's notes.

What was promised to a customer lives in one person's head. Why billing works the way it does lives in a Slack thread nobody can find any more. So every handoff and every new hire costs a meeting to reconstruct something that was already said out loud, and the person who said it is usually the one with the least time for that meeting.

Six situations

Where the team's memory would otherwise be a meeting.

Walk into every call already briefed

Situation: The account has spoken to three people on your team since you last spoke to them, and each of them wrote it up somewhere different.
What Nod does: Ask Nod what your team promised this account and what's still open. The answer is built from the calls your colleagues shared, and each line points back to the conversation it came from.
Result: You open the call knowing what the last person said, instead of digging through five people's notes first.

Decisions stop getting re-litigated

Situation: Three months on, someone asks why the pricing changed. The person who decided has moved on, and the thread that explained it is gone.
What Nod does: Every conversation ends with its decisions and open questions written down, with the date and the wording from the call. Share the conversation and those decisions become team context.
Result: When someone asks “why did we change this?”, the answer has a date on it.

Handoffs without a handoff meeting

Situation: Sales to onboarding, founder to first hire, dev to support. The receiving side needs everything the last person heard, and the last person is busy.
What Nod does: File the account's calls into a folder and share it with the team taking over. They can read the summaries, transcripts and action items, and ask questions across all of them.
Result: The receiving side reads the memory instead of booking 30 minutes.

New hires ask the team, not the team's calendar

Situation: It's week one. “What did we promise Acme?” “Why is billing built this way?” Each answer costs a senior person half an hour they didn't have.
What Nod does: Someone added to a team can ask across what the team has shared from their first day, and check each answer against the conversation it came from.
Result: Answered from real conversations rather than tribal knowledge, and without booking time with the one person who knows.

Customer promises don't leak

Situation: “I'll get you the security doc by Thursday” was said on a call. By Thursday it's in nobody's list, and the customer remembers.
What Nod does: A commitment can become action-item text that records what was promised, to whom, and by when, when those details were said aloud. Review the text against the call, then share the conversation if the team should see it.
Result: The promise outlives the call. Nod does not currently file it into Linear, Jira, HubSpot or Notion, so the confirmed task still belongs in the team's system of record.

Your 1:1s stay yours

Situation: A performance review, a candidate's salary, a call with the board. Some of what you record should never become team context.
What Nod does: Every conversation is private by default. You choose, per conversation or per folder, what the team can read, and removing a share ends their access immediately.
Result: Nothing becomes visible because you joined a team, and nothing stays shared once you change your mind.

Control

You decide what becomes team context.

Joining an organization shares nothing. Team context appears only when you deliberately share a folder or one finished conversation, and you can reverse either share. A public summary link is a separate, revocable action and never exposes the transcript.

Control	Privatedefault	Shared with a team
Who can read it	Only you. Not your team and not your admin.	Whoever is on that team at the time they look, or everyone in the organization if that's the audience you chose.
What they see	Nothing.	The summary, the transcript and the action items. Nothing Nod read from your screen.
Ask Nod	Answers from your own conversations.	Colleagues can ask across it, alongside everything else shared with them.
Taking it back	Nothing to take back.	Remove the share. Access ends immediately.
What an admin can do	Nothing to the recording itself. Current early access has no admin view, forced organization ownership, or administrator-read switch for meetings you kept private.	Manage who is on the team, so adding someone lets them read what was shared with it. Every membership change is written to an audit log.
When you leave	Still yours, unchanged.	Access ends both ways, at once.

The full wording, in the Privacy Policy

Sources

Where team context comes from.

Calls and meetings

Zoom, Meet, Teams, Slack huddles, or a phone on speaker, captured from your Mac's own audio. No bot joins and no audio is kept.

Conversations in the room

The decision made across a desk counts too. Nod hears through the Mac's microphone, and it's written up the same way.

Voice notes

The thought straight after a call, spoken into Notepad. Any finished session can be filed into a folder or shared on its own.

A finished conversation shared on its own

Share one completed conversation without filing it into a folder. The team can read its summary, transcript and action items until you remove the share.

Never your screen

Ambient context feeds your own Ask Nod and nothing else. What Nod read from a window you had open never ends up in a summary, a share or a colleague's answer.

Nothing becomes visible because you joined

Membership shares nothing. Your meetings stay exactly as private as they are for an account in no organization.

Admins can't open what you kept

There is no administrative view of another member's recordings and no export of them. Sharing is always your own act.

Audio is never stored

Sent to hosted transcription, then discarded by Nod when text returns. Notes are encrypted at rest in the EU, inference may occur outside the EU, and nothing is used to train a model. Groq may retain transient error or abuse logs for up to 30 days unless Zero Data Retention is enabled.

What Nod stores, and what it refuses to Security & privacy

Frequently asked questions

Is Nod team context available to everyone?: No. Team context is early access for approved teams, not a generally available self-service workspace. Individuals can still use Nod without joining an organization.
What gets shared when I join a Nod organization?: Nothing is shared by membership alone. Team context appears only when you deliberately share a finished conversation or folder, and you can remove that share. A public summary link is a separate, revocable action.
Can a team administrator read conversations I kept private?: No. In the current early-access workflow, administrators can manage team membership but cannot open, export, or search private conversations. Forced organization ownership and administrator-read access are future, unreleased controls.

Bringing a team on

Start alone. Share when there's something worth sharing.

Nod signs in with any Google account, so one person can start today without a rollout. When the rest of the team should be able to ask too, we'll set up the organization with you and walk through what sharing looks like for your accounts.

Book a team demo Or write to us

The same memory through one role's week: founders, sales, product managers, engineers, recruiters, consultants, researchers, coaches and claims adjusters. For what is stored and where, see private by default; for asking across it, see Ask Nod.

Useful on day one. Hard to work without by month three.

Start free on macOS, no card. Every conversation you capture today is one you can still ask about a year from now.

Download for macOS