Teams & billing
Sharing a connection securely
Hand a working connection to someone end-to-end encrypted, after verifying it is really them.
Sometimes a teammate needs a connection that actually works, credentials included. Rather than pasting a password into chat, AddisDB can seal one so only the person you chose can open it.
How it works
- Choose what travels. Every value is masked on this screen — you are picking which fields to include, not reading a credential dump.
- Choose who, and verify their fingerprint. This is the step that makes the encryption mean anything; comparing the fingerprint out of band is what proves you are sealing it to the right person.
- Send it — either through AddisDB, or as a block of text you deliver however you like.
What the recipient gets
They open it in AddisDB and the connection lands in their sidebar, ready to use. If it was sent through AddisDB, the delivery is one-time: the half of the key AddisDB holds is destroyed once the share is opened or once it expires, so the same link cannot be replayed later.
Do not confuse it with team sharing
Sharing a connection with your team syncs the connection details only — every person still supplies their own database password. This feature is the deliberate exception, for when the credential itself has to move.