Share files with your team
Use /hq-share to grant teammates access to a narrow vault prefix through a single-use, expiring link instead of copying files around.

Scoped grant
Sharing grants access to a vault prefix; it does not hand out a copy.

Pick a narrow prefix
A share grant targets a vault prefix, such as companies/{co}/knowledge, not your whole HQ.
Confirm the files exist in your synced vault, then identify the narrowest prefix that covers them.
Mint and send the link
/hq-share mints an encrypted, single-use, fifteen-minute share-session link and opens a browser ACL picker for the prefixes and people you choose.
Run /hq-share with the prefix, pick the recipients in the browser picker, and send only the generated link.


Confirm and manage access
Accepting the link adds an ACL grant for the prefix, so the recipient gets access to your files, not a copy of them.
Have the recipient open the link and accept the grants in the browser, then inspect and revoke grants with /hq-files.
Keep the chapter executable.
Mints a single-use, expiring share-session link and opens the browser picker to grant access to chosen vault prefixes.
Inspects and revokes ACL grants on vault prefixes after a share.
What goes wrong, and the fix.
Sharing too broad a prefix so the recipient sees more than the task needs.
Share the narrowest path that does the job, then widen only if required.
Pasting the share-session URL into chat, notes, or commits to use later.
Treat the link as a single-use capability that expires in fifteen minutes and re-mint a fresh one when needed.
Confusing share with sync and expecting /hq-share to move files.
Use /hq-share to grant access and /hq-sync to move your own copies.
What to keep in mind.
Share vs sync
Sharing grants access to your files; sync moves your own copies. Use /hq-share to grant access and /hq-sync to move what you own.
Link is a capability
The share-session link is single-use and expires in fifteen minutes, so never paste it into notes, chat, or commits; re-mint instead.
