---
title: Share a note and publish it to the web
description: Invite people in your org to read one note, and publish a note as a read-only public page that search engines skip by default.
section: globe
order: 13
audience: [user]
sources: [services/nodejs-cloud/components/globe/ShareMenu.tsx, services/nodejs-cloud/lib/globe/share.ts, services/nodejs-cloud/lib/globe/publish-pure.ts, "services/nodejs-cloud/app/(globe)/p/[token]/page.tsx"]
features: [cloud.page-p]
---

Open a note and press **Share** in its header. The panel has two tabs.

## Share

- **Invite** someone in your org by email, or a whole group (one of your organisation's teams: its members and the
  members of the teams above it), and pick what they can do:
  - **Can view** reads the note, live.
  - **Can comment** reads it too; it is the level the comments feature uses.
  - **Can edit** changes the text and properties of the note, live with others. Where the note lives, its name and
    deleting it stay with its owner (or an org admin).
  A shared note shows up in the invited person's sidebar under **Shared with me** and nowhere else: not in their tree,
  search or graph, and not with your other notes around it. Change someone's level from the list, or remove them with ×;
  it takes effect at once.
- **People with access** lists you (or the org's admins), the people and groups invited, and their levels.
- **General access** says who else can see it. A note in your own vault is "Only people invited". For a note in the org's
  vault, org admins can switch between **Everyone in your organization** and **Only people invited**.
- **Copy link** copies the note's address in Notes. People still need access to open it.

### Restricting an org note

Choosing **Only people invited** on an org note takes it out of the org's vault lists. Nobody finds it in the tree,
search, the graph, a database, the loop's suggestions or MCP's lists, not even by its title. Only the people and groups
you invite (at view, comment or edit) and org admins can open it, by its link or from **Shared with me**. Choosing
**Everyone in your organization** puts it back where it was, with its links working again; if another note took its name
meanwhile, rename one of them first. Org admins always keep access to restricted notes, so a note is never locked away.

Invites are for notes in your own vault and for restricted org notes. The org's open notes are already shared with the org.

## Publish

The **Publish** tab turns the note into a public page at `/p/{token}` (the token starts `vgp_`) that anyone with the link can read, with no
sign-in. You can publish a note you own, or an org note if you are an org admin.

- The page is read only and drawn in the Reading view's style, without the panes of Notes. It shows the note's title, icon,
  cover and text, and the date it was last updated. It never shows who wrote it.
- To keep the rest of your org private, the page shows only the note's own words. `[[Links]]` to other notes become plain
  text, `![[embeds]]` and inline databases are left out, and links that point into Venom (a note, a task) lose their
  address. Links to other websites stay.
- **Search engines may index this page** is off. The page asks search engines to skip it, and the setting is yours to
  turn on.
- **Make a new link** gives the page a new address; the old link stops working. **Unpublish** ends the page at once.
  Deleting the note ends it too.
- The link is a long random string. Venom keeps only a hash of it to look the page up, and, where the cloud has a vault, a
  sealed copy so you can copy the link again later.

Every share, unshare, publish, unpublish, new link and indexing change is written to the org's audit log.
