Know who can see your chats and memory

People hesitate to give an AI teammate real work until they know who else is reading it. This is the honest answer.

Nobody else sees your Talent's work

Your conversations, your personal memory, your runs, your approvals, your connections, and the suggestions your Talent makes to you are visible to you and to nobody else in your workspace.

That includes admins. It includes your manager. An admin who queries for your conversations gets the same empty result as any other member. This is not a filter someone remembered to apply, it is how the data is stored and indexed, so a new screen cannot accidentally expose it.

The three narrow exceptions

There are exactly three things about your Talent that reach an admin, and each one deliberately stops short of content.

1. What a run cost. An admin can see the credits a run spent, when it happened, whether it succeeded, and which model lane it used. They cannot see what it said, what it read, or what it produced. The workspace pays one bill, so the people who pay it can see what it is made of. A Routine name appears only if that Routine is published to the whole workspace. Anything private shows as "Private routine".
2. That you have a Talent. An admin sees your Talent's name, its mascot, and whether it is active on the Team page. Nothing it has ever done.
3. Bounded support data about nudges. Whether a proactive check spoke or stayed silent, and when. No message content, no destination, no conversation.

What your Talent itself can reach

Your Talent works with:

• Your own connected accounts. Not a teammate's.
• Your personal memory.
• Approved company memory, plus approved memory for your one active department.

A department manager seat is a governance role over shared work. It does not widen anyone's view into a report's private Talent, and it does not widen what a model sees.

A worked example

Mina asks her Talent to analyze a sensitive renewal and draft options. Her workspace admin can see that Mina used credits and that the run completed, but cannot open the conversation, draft, source material, personal memory, or connection. Mina shares the finished recommendation herself when it is ready.

In shared Slack channels

When your Talent replies in a channel other people can read, it treats that audience as real. It will not volunteer your memories, notes, documents, schedules, private conversations, or anything it read from your connected accounts. If the honest answer needs private detail, it keeps the channel reply short and takes the rest to your direct message. See reaching your Talent from Slack, Telegram, or iMessage.

Your credentials

When you connect an app, the secret behind that connection is never shown again to anyone, including you. You see the connection and its status. You never see the secret itself, and neither does anyone else.

Sharing on purpose

Nothing private becomes shared by accident. Work reaches your workspace only when you explicitly publish it, for example by promoting something into a Routine and having it published to the Marketplace. Until then it is a private draft.

The Copy private link on a conversation is navigation, not sharing. Sending that link to a colleague gets them nothing.

What to check

• You expected a teammate to see your work and they cannot. That is correct behavior. Publish it to the Marketplace, or share the output itself.
• An admin asked you for a transcript. They cannot pull it. Paste or export what you want to share yourself.
• Your Talent will not answer something in a channel. Ask again in your direct message. Channel discretion is doing its job.
• A connection shows as connected but your Talent says it cannot act. The connection exists but the action may need your approval, or the account may have lost access on the provider's side. Reconnect it in Connections.