Sharing contexts and folders

Beyond raw sources, you can share an individual context or a whole folder with Viewer or Editor access. Use Viewer access for a finished writeup, or Editor access when a working brief or project folder should become a collaborative space that people and agents refine together.

Share a context or folder

1. In your Library, select the context or folder you want to share
2. Open its Private or Share control
3. Choose Personal access for one person, or a team audience - everyone, admins only, or a specific teammate
4. Choose Viewer or Editor
5. Save, then copy the private link when you want the recipient to open the exact item

What recipients get:

• Viewer access: recipients and their agents can open, search, and read the current context or folder tree
• Editor access: recipients can edit context Markdown, title, and emoji with live presence and synchronized cursors; because shared contexts are enrolled in collaboration, their CLI and MCP agents update that same collaborative document
• Folder inheritance: everything inside a shared folder inherits that folder's audience automatically unless a child or intermediate folder has a direct override or exclusion
• Mixed ownership: Editors can create or move their own contexts and folders into the shared tree. The containing folder becomes collaborative, but every contributed node keeps its original owner
• Provenance: a shared context shows its actual owner, any applicable team scope, and the source attribution it carries

Overrides and unsharing:

• Change one inherited context from Viewer to Editor, or Editor to Viewer, without changing its siblings; Nessie creates a direct context rule and excludes the parent rule for that audience on that context
• Unshare one context or nested folder to remove inherited access to only that item or subtree while leaving the broader folder shared
• A separate personal, team, or direct child grant can still supply access after another grant is removed
• Re-sharing an excluded child restores it without rebuilding the parent share

Folder operations:

• Editors can add or move only nodes they own; they cannot take ownership of a teammate's contribution
• Viewer destinations reject creates and moves
• Moving or deleting a contribution requires Editor access to its current shared-folder ancestry
• A folder must be empty across every contributor before it can be deleted

Manage from the CLI

Use nessie sharing add ... --access viewer|editor to grant access to a context or folder. The CLI can also inspect and remove direct grants; inherited access and overrides continue to follow the rules above. See the CLI reference for audience and removal examples.

A context inside a shared folder shows the inherited audience in the shared column when you browse through the CLI or MCP.