Why connection strings are worse than passwords
A database connection string bundles everything an attacker needs in one line: host, port, database name, username, and password. Unlike a forgotten password, a leaked connection string often works from anywhere on the internet until someone notices and rotates it.
That is why emailing a DATABASE_URL or pasting it into a group chat is riskier than most people assume. Mail archives, chat exports, and notification previews all create quiet copies that outlive the project.
A workflow that limits exposure
Start by reducing what needs to travel. Create a dedicated user with minimal privileges instead of sharing admin credentials, and prefer short-lived access where the database supports it.
When the credential must be sent, encrypt it in the browser before it ever reaches a server, attach an expiration, and use a one-read link if the recipient only needs it once. After onboarding completes, rotate the password. The goal is simple: the credential should be useless to everyone except its intended recipient, and only for as long as necessary.