Send production keys to my co-founder, not the whole vault

The whole-vault temptation

Early teams often share trust before they build process. A co-founder needs access, so someone exports a file, pastes a key, or shares the whole password manager collection.

It works because the team is small. It fails because the boundary is too large.

The person needed one production credential. They did not need every draft note, every old test token, or every unrelated personal record that happened to live in the same place.

Sharing should have a smaller shape

NT² is designed around a narrower idea: share the item, not the vault.

A production key belongs in a Credential item. When another trusted vault needs it, the share should carry that item under rules you choose. The recipient should see a clear request in Inbox, understand what arrived, and accept or decline.

That model changes the habit:

• one item instead of a full export;
• one recipient instead of a group thread;
• a share passphrase or vault-to-vault trust path, not your master password;
• a record that feels like a handoff, not a leak you hope is okay.

This is still human trust. NT² does not decide whether your co-founder is trustworthy. It gives that trust a better container.

Collaboration without surrender

The product value is simple: collaboration should not require surrendering the whole vault.

Founders, contractors, family members, and accountants all create moments where another person needs a narrow piece of sensitive information. A structured vault can make that moment explicit. What is being sent? To whom? Is this a Credential item, a Bank item, or a Document item? Is this a one-time disclosure or a lasting shared record?

Those questions are much healthier than "which chat should I paste this into?"

For the other side of the API-key habit, read You pasted the API key in Slack. Follow new posts through the RSS feed.