Save the client logins
Add each client login, or register a passkey for it, inside Coauth.
← CoauthFor MSPs and IT teams
Share client logins with your team, without pasting passwords
You manage logins for dozens of clients. Coauth lets your techs sign in without pasting passwords around, and re-keys the team the moment you remove someone who rolls off an account.
The problem
The credential sprawl every MSP knows
Client passwords end up in spreadsheets, password-protected docs, and chat threads. Onboarding a tech means forwarding a pile of credentials. Offboarding means changing all of them and hoping you caught every copy. And the moment a client turns on phishing-resistant MFA, a shared password stops being enough on its own.
Per-client sharing
Share one client login into a team, sealed individually to each tech. Group by client or by pod.
Clean offboarding
Remove a tech and the team key rotates, so they cannot read anything shared from then on. Change any password they saw, since they could have copied it.
Zero-knowledge
Client passwords are encrypted on your techs' devices before they sync, so the server stores them only as ciphertext and cannot read them.
No per-seat cost
Free for up to 3 people, then $5 a month flat. No license per tech and no suite to roll out for every client.
How it works
Set it up in three steps.
Share with your techs
Share each login with a tech by email. They get a link and join, and the login is sealed to every member of that team.
Techs sign in, you revoke on exit
Techs autofill or use the shared passkey from their own browser. When one leaves, remove them, the key rotates, and you change any password they saw.
FAQ
Common questions.
Do techs need to see the password to sign in?
No. Coauth autofills the login on the site, or uses a shared passkey, so nobody pastes the password around. A team member can still reveal and copy a shared password if they choose, so change it when someone leaves.
What happens when a tech leaves?
Remove them from the team and the team key rotates, so they cannot read anything shared from then on. Change any password they could have seen, as with any password manager.
Is it safe to store client credentials in an extension?
Client passwords and passkey keys are encrypted on the device before they sync, so the server cannot read them. It does store readable details such as each login's site and username. Removing a member rotates the key, and every night the encrypted database is copied to storage outside Supabase.
Does this cost per client or per tech?
Neither. Free covers 1 team of up to 3 people. Pro is $5 a month flat for unlimited teams and members, so a team per client costs nothing extra.
See it work
A look at Coauth.
Share one login. Free for 3 people.
Install Coauth and share the login with your team, free for up to 3 people. When someone leaves, remove them and the team key rotates.