Your Mesh team
Invite teammates, manage roles + access, and keep an audit trail. Seats are set by your plan.
Sign in
Paste your client token (run mesh status in your joined vault, or it is in .mesh/credentials).
Seats
Write-back flywheel
Reuse counts fetches served by the hosted MCP index; members on mesh mcp --http record reuse in their own local index.
Invite a teammate
Members
Folder access
Restrict a folder to a role, group, or user. A folder with no rule is readable + writable by all members (viewers read only). Most specific prefix wins.
Scopes
A scope partitions who can read and write which notes. A note's scope: (absent = dev) decides. Devs have full access; a scoped member (sales, marketing, ...) reads + writes only their own scope and can never touch dev docs. Assign each member a scope on the Members tab.
Cross-scope read access
Scopes are isolated by default. Open one scope for reading by another group here (e.g. let marketing read dev). Grants READ only, never write.
Integrations
Pull from where your team already keeps knowledge into the vault. Add a source and paste its token right here (it is encrypted on the hub, never shown again, and never sent back to the browser). The hub imports on a schedule and on demand. Prefer env tokens? Leave the field blank and set MESH_INGEST_<TYPE>_TOKEN on the hub instead. Imported notes appear under imported/ and sync to everyone.
Audit trail
Export my contributions
Download a zip of the notes you authored plus your audit rows (GDPR access).
Download my dataErase a member (admin)
Revoke a user's access. Optionally delete the notes they authored.