We kept sharing passwords internally. Someone needed to test a project, so one of us sent them the login. A few days later, someone else needed it. By then we had a second question to answer: was that the staging password or the production one?

What bothered me was how ordinary the interruption felt. A teammate could have the site open, know exactly what they wanted to test, and still have to wait for another person to reply.

Global Login extension icon

That’s the problem I built Global Login to solve. It gives our team a shared place for project accounts and brings the right choices into the browser when someone needs to sign in.

Start with the project

Say you’re checking a fix before it goes live. You know the project name and you know you want staging. Those two details should be enough. On the dashboard, each project keeps its accounts together, so you can give the test account a label that the next person will recognize.

Global Login dashboard showing the project grid

Meet people at the sign-in field

Here’s my favorite part. Open the project site in Chrome and click the sign-in field. The extension shows matching accounts. Pick the one you need and it fills the form. If you’re starting in the extension, Open & Fill takes you to the saved site.

The Global Login browser vault with its saved accounts

That changes the handoff. I can tell a teammate “use the staging account in Global Login,” and that answer still makes sense after the password changes. When the extension suggests saving an update, someone gets to review it first.

Leave room for the things that belong to one person

Building a shared vault raised a very human question for me: if I put something here, who can see it? Project accounts belong in the team workspace. My private vault is for things like my own API credentials and secure notes. Even a file I attach to a shared login stays private to me. That’s a small distinction I’d want to understand before uploading anything.

My private vault in Global Login

What you can do with Global Login

When you need to… Here’s what you can do
Find the right environment Keep local, staging, and production accounts under one project. Tag and sort logins, group projects into collections, and refresh their website icons individually or in bulk.
Sign in to a project site Pick a matching account in the sign-in field, search other logins with the keyboard, or use Open & Fill. Review suggested saves and updates. Exclude a site or switch off the floating prompt when you want to.
Test a new signup Generate a fresh password, fill identity fields from a saved profile, or open the external temporary-mailbox shortcut.
Keep personal details handy Use your private vault’s 21 item types for things like API credentials, identities, cards, SSH keys, and secure notes.
Attach a file Upload, rename, download, or delete files up to 50 MiB each. A document can reference a file. Attaching one to a shared login still leaves access with its owner.
Bring a teammate onboard An administrator approves membership and controls edit and backup permissions. A view-only teammate can still use shared logins for testing.
Find out what changed A login’s activity history shows who updated it and when, including changes made through an AI client.
Automate housekeeping Connect an AI client through the Model Context Protocol (MCP) using a personal token. It can organize collections, refresh icons, or manage vault items and files within your permissions.
Back up or self-host Authorized members can export shared projects and accounts. Imports require backup and edit permissions. You can also run the workspace on your own Cloudflare account.

What happens to a password when I click Save?

Saving a project password requires edit access before encryption and storage. Autofill checks membership before decryption and delivery to the browser.

The server encrypts each project password with AES-256-GCM before writing it to the database. It uses a fresh random value each time and binds the encrypted password to its account ID. Someone who gets a copy of the database would also need the server’s encryption key to read those passwords. Moving an encrypted password to a different account record would fail the integrity check. Read the encryption code.

Access matters just as much as encryption. A workspace administrator approves new members. Approved teammates can use shared accounts, while the server checks ownership for personal vault items. The server can decrypt passwords to deliver them for autofill, so the people running the workspace and protecting its encryption key are part of the trust model. See the private vault implementation.

One detail matters when you make a backup. An authorized export contains readable shared passwords, so whoever holds the exported file can read them. The encryption shown above protects the database copy.

The tech stack behind it

I used TypeScript across the project and React for both the web dashboard and the extension interface. Vite builds the dashboard, and WXT packages the Chrome extension. The backend is a Hono API running on Cloudflare Workers. It stores records in Cloudflare D1 using Drizzle ORM, and keeps file attachments in Cloudflare R2.

Try it 🔑

Install Global Login from the Chrome Web Store and choose Add to Chrome. The listing is currently unlisted, so use that direct link to find it. I plan to make it public and searchable soon. Once your workspace administrator approves your account, open the extension and sign in with Google.

For a manual install, the Chrome ZIP is also available on GitHub Releases.

The source code and self-hosting guide are available if you’d like to run it for your own team.

If someone joined your team tomorrow, which login would they have to ask you for first? That’s the one I’d start with.