How Nysa keeps private email private while sharing what the team needs

In Nysa, raw email stays private to its owner. The team sees only the facts drawn from it, and each agent sees only what its teammate can see. Your colleague's agent can learn that a customer asked for a Q4 start without ever reading the email thread it came from.

The problem with shared email

Email is where much of a team's knowledge lives, and also where much of its privacy lives. A sales thread, a hiring note, a message from a lawyer. A team brain that pulls everything in and shows everyone everything is a liability, and people rightly refuse to connect their inbox to one.

The opposite fails too. If email stays fully locked away, the team loses what it contains: the customer's request, the date, the commitment. Each person ends up re-explaining it to their own agent. We covered that failure in saved isn't searchable and shared memory is not shared access.

Nysa takes a middle path: share the facts, keep the email.

What stays private, and what is shared

When you connect Gmail, Nysa imports your email history and keeps new mail flowing in. From that mail it draws facts about the people and companies you work with, each with its quote, date and source.

• Private to you: the raw email. Other teammates and their agents do not get it.
• Shared with the team: the facts drawn from it, subject to the same scoping rules as everything else in the brain.

This is the line Nysa's site draws, and it is one of the differences listed on its comparison pages.

Scoped automatically, per person

Every fact is scoped automatically, so each agent sees only what its teammate can see. You do not tag each item or manage a permissions spreadsheet.

Agents connect over MCP, signed in as their teammate. That is the key to the model. An agent has no standing of its own. Claude sees only what your Nysa account can already see, and the same goes for ChatGPT. The connect pages also say each call is audited. Details for each are on the Claude page and the ChatGPT page.

So two teammates can ask their agents the same question and get answers that reflect what each of them is allowed to see.

Projects

Nysa also organizes knowledge by project, so a team can share what is relevant to a piece of work without opening everything. Scopes and projects are part of how Nysa decides what each agent can see, so the right people get the right facts.

What agents can and cannot do

Agents can read from and write to the brain. They cannot send email or edit your calendar. Nysa updates only on request. The MCP tools that read people, companies, meetings and the brain are listed in Nysa's MCP tools, explained. Note that calendar tools return the signed-in account's own events.

The trust basics

• Not for sale, not for training. Your data is never sold or used to train AI.
• Independently assessed. An authorized lab tested Nysa's security to CASA Tier 2, and Google approved its Gmail and Calendar access.
• Visible recording. The meeting notetaker joins the calls you choose as a visible participant. See how Nysa turns meetings into facts.

What to know

• Google accounts today. Gmail and Google Calendar are supported, for personal Gmail and Google Workspace. Outlook and Microsoft 365 are not supported yet.
• The email stays with its owner. Only the owner's own agent can reach the exact wording of a private message. Everyone else gets the facts.
• Every fact can be checked. Each fact keeps its quote, date and source, so you can verify it before you act on it.

Why this design

Teams that run agents need two things that pull in opposite directions: shared context and personal privacy. A system that picks one fails the other. Sharing the facts and keeping the source material private lets an agent give useful answers about a customer while the inbox stays with its owner. For why this matters beyond email, see same company context for every agent.

Setup takes under 5 minutes: sign in with Google, invite your team, and connect your agents.

FAQ