There is a gap between "send someone your notes" and "share a note", and most friction comes from not deciding which you meant.
Sending is a one-time transfer: they get a copy, you keep yours, and the two immediately diverge. Sharing is ongoing access to the same object, with permissions and a history. They solve different problems and people reach for the wrong one constantly — usually sending when they should share, and occasionally the reverse, which is worse.
The four ways, and when each is right
1. Send a copy. Export to PDF, paste into an email, screenshot. Correct when the content is finished, the recipient does not need to edit, and you do not want it to change. Also correct when you want a record of exactly what you sent, which matters more often than people expect. Its weakness is that it goes stale instantly.
2. Share the live note. Apple Notes, Notion, Google Docs and most modern apps allow this in one action. Correct for collaboration and anything that will keep changing. Its risk is that you have granted ongoing access to something you will keep editing, possibly forgetting it is shared.
3. Publish. A public or semi-public page — Obsidian Publish, a Notion site, a digital garden. Correct when the audience is undefined or large. See what is a digital garden.
4. Rewrite it for them. Underrated and usually the right answer. Ten minutes turning notes into something readable beats sending twenty minutes of raw shorthand that costs the recipient more to decode than it saves them.
Your raw notes are not a document
This is the mistake worth naming clearly, because it causes both embarrassment and confusion.
Notes are written for an audience of one who has all the context. They contain abbreviations, private shorthand, half-formed judgements, "ask X about this — seems off", and things you thought and did not mean. They are a thinking artefact, not a communication artefact.
Two consequences:
They are less useful to others than you assume. What reads as a clear record to you reads as fragments to someone who was not in the room. The cost of decoding lands on them.
They frequently contain things you would not say. A note recording your first impression of a colleague, a doubt about a client's competence, or a blunt assessment of a plan is fine as private thinking and damaging as a shared document. This is the most common regret in note sharing, and it is entirely avoidable by reading before you send.
The rule: read the whole note before sharing it, every time. Not the part you meant to share — all of it, including whatever is at the bottom from three weeks ago.
Check the permissions, then check them again
Sharing defaults vary and are not always what you expect. Before sharing anything sensitive:
- Who exactly gets access? A named person, anyone in your organisation, or anyone with the link? The last is effectively public — links get forwarded.
- Can they edit or only view? Default to view.
- Does it expire? Most sharing is permanent by default, and revocation is a thing you must remember to do.
- Are you sharing a note or a folder? Sharing a parent folder shares everything you later put in it, which is how material leaks accidentally.
- Can they see the history? Some tools expose version history to collaborators, including the sentence you deleted.
The folder one causes more accidents than any other, because it is invisible: you share a project folder in March, and in July you drop something confidential into it without thinking.
Sharing in a team
A few practices that prevent the usual mess:
- Shared notes need an owner. A collaboratively-edited document with no owner becomes stale and nobody feels able to delete it.
- Separate the shared record from your private notes. Keep your own observations in your own space and publish the agreed version. Trying to make one note serve both purposes means either censoring your thinking or over-sharing it. This matters most in 1:1 notes, where the distinction is the whole skill.
- Put decisions in the shared doc, reasoning in yours. The team needs the decision; the reasoning is what you will want next year.
For the tooling side of this, see best notes app for teams.
What not to share, ever
- Anything containing someone else's confidential information. It is not yours to pass on, even in a note about a meeting.
- Credentials, keys or personal data. Notes apps are not secret managers. See encrypted notes.
- Notes about people. If you keep records on colleagues, clients or friends — see personal CRM — those are private by construction. The test is whether you would be comfortable with the subject reading it.
- Anything under NDA, into a personal account. Common, casual, and a genuine contractual problem.
The honest default
For most requests, the best response is not to share a note at all. It is to write three lines: what was decided, what it means for them, and what you need. That is what they wanted, it takes less of their time than your notes would, and nothing leaks.
Your notes stay what they are for — thinking. See how to write a summary.
More in how to take meeting notes, export your notes, and how to take notes.