Private notes

Not everything you know belongs in the team's workspace. Notes on a particular account, a half-formed idea for new positioning, the way you personally like your emails drafted: useful to your agent, not ready (or not meant) for everyone else's.

A private note is a page only you can see. It lives in the workspace alongside the team's pages, and your own agents get it with everything else. Nobody else in the organization sees it, not even owners and admins, and it never reaches anyone else's agent.

Making one

Anyone who can read a workspace can keep private notes in it.

• In the app: the sticky-note button at the top of the sidebar's page list makes one at the top level. Hover over a folder for the same button to make one inside it. Private notes show a lock in the sidebar.
• From your agent: ask it to save something as a private note. It uses create_page with private: true. ("Make me a private note with what I learned on this call with Harbor Health.")

You can put a private note in any folder you can see, even one you can only read. It doesn't change the folder for anyone else; they just don't see it.

Who gets it

Private notes come back only through connections that are you:

• a sign-in connection from your AI tool,
• a personal API key you created.

They never come back through a workspace key, even one with access to everything, because a workspace key isn't anybody.

When a private note is returned, it's marked as yours ("your private note") so the agent knows it's your material rather than something the team has approved. The default instructions tell agents not to present it as team-approved.

Like any page, a private note has to be published before your agents can see it. Publishing a private note sends it to your own connections and no further.

What you can do with one

A private note is a normal page in every other way. You can give it headings, tags, a usage note and an expiry date. You can also make it a rule or set it to always include, and it applies only to your own agents. That's a handy way to keep personal standing instructions ("I write in British English", "keep my emails under 120 words") without imposing them on the team.

Private notes can't be added to packs, because packs are the team's. They have no Access list, because there's no one to share them with.

Sharing it with the team

When a note is ready for everyone, open it and set Visibility to Shared with team. It becomes an ordinary page where it sits, visible to everyone who can see that folder, and the next time it's published, everyone's agents get it.

Because that's the same as creating a page there, it needs the same permission: owners and admins can share anywhere, and anyone else can share into a folder they can edit. If you only have read access where the note is, move it into a folder you can edit first, or ask someone who can.

It works the other way, too. Private to me takes a shared page back to being yours alone. It disappears for everyone else and is removed from any packs it was in, so use it with care on pages other people rely on.

Privacy details

• The request log under Activity is visible to owners and admins. When one of your private notes comes back in a request, it's listed as "(private note)" rather than by title, so nobody learns it from the log. The task your agent sent is still logged, so don't put anything in a task you wouldn't want an admin to read.
• Private notes don't count toward the workspace description agents see when they connect, and their tags don't either.
• If you delete a private note, it goes to Recently deleted where only you can see or restore it.
• If you're removed from the organization, your private notes are deleted. Share anything worth keeping first.