Share a project

A ThoughtBridge project can have more than one person capturing into it. Sharing works without accounts, invitations, or a separate permissions system: the owner mints a key scoped to the project, and whoever holds that key can link it on their own account. It’s built on the same API keys that power scripts and agents - project sharing is just a key handed to a person instead of a machine.

Share your side

1. In the app, open the project you want to share and choose Sharing from its menu.
2. The panel shows Shared with: everyone the project is already shared with, when each share was created, when it was last used, and a Revoke button for each.
3. Under New share, give the share a name - this is how their contributions will show up on thoughts they capture (e.g. “Captured by Sander”), not their real identity, so pick something you’ll recognize.
4. Choose Create key and copy the secret immediately. It’s shown once: ThoughtBridge stores only a hash, so if it’s lost you revoke it and create a new one.
5. Send the key to the person you’re sharing with, the way you’d share a password - a password manager or a secure message, not a public channel.

Link it on the other end

1. In the app, choose New project, then the Link a shared project tab.
2. Paste the key. ThoughtBridge checks it and shows what it unlocks before anything is linked.
3. Confirm to link. The project appears alongside your own, marked as linked and shared by another account.

What a linked project can do

A linked project is a full content-writing participant, not a read-only mirror:

• View existing thoughts, tasks, notes, and media.
• Capture new thoughts into the project.
• Tick tasks, add notes, attach context links, and upload media.

What stays with the owner, whichever side creates the share: renaming or deleting the project, adding or changing its destinations, chatting with Bridget, and any Bridge-it run - claiming, answering questions, approving a merge, or cancelling. A linked project’s build and PR history stays on the owner’s runner and repo, so a shared key can never spend the owner’s runner or agent time, or merge into the owner’s code.

Every thought captured through a shared key carries a “Captured by” byline in the destination file, naming the share (e.g. “Captured by Sander”) using whatever the owner called it - so it’s clear at a glance who added what, without exposing anyone’s account details.

Revoking access

Revoke a share any time from the project’s Sharing panel (or Settings > API keys - it’s the same key either way). Revocation is immediate: the key stops authenticating on its next request, and the linked copy on the other side shows as revoked until they remove the link. Thoughts already captured through the share stay exactly where they were filed.

Honest notes

• The key is the access. Anyone who has it can link the project - there is no separate approval step and no way to tell who is actually using a given key beyond the label you chose. Treat it like a password.
• Shared captures count toward the owner’s plan, not the sharer’s. Someone contributing to your project uses your monthly capture quota.
• A share is a read_write key scoped to one project. If you’d rather automate a project than share it with a person, see API keys for scoping a key to several projects at once, or capture thoughts from anywhere for driving it from a script.

A note on profiles

Sharing labels are separate from Settings > Profile, where you set your own display name and photo (shown across the app on web and the apps). A share’s “Captured by” byline always uses the name the owner gave that share, never the recipient’s profile - so someone can link a project without ThoughtBridge ever learning who they are.