Browser-saved passwords are not a business control

The Save password prompt in Chrome is not a security program. It is a convenience feature that happens to sit in the same window as your payroll portal. Those are not the same job.

I am not arguing that Google Password Manager, Edge password storage, or Apple Passwords are “insecure” in the cartoon sense. They encrypt, autofill, and warn about reused passwords. Chrome and Edge can also be managed by company policy. The problem is fit: a per-user browser store is not a shared vault with deliberate ownership, recovery, and item-level access for payroll, banking, and infrastructure.

This is the companion to 1Password for home and work. That piece is the product call. This one is why the browser is not a substitute.

What these stores actually are

Chrome / Google Password Manager saves credentials to your Google Account when you are signed in, then uses them across devices and some apps. If you are not signed in, Chrome keeps them locally on that machine. Google documents both modes in Manage passwords in Chrome. A company can manage Chrome and disable new password saving with PasswordManagerEnabled, but Google notes that previously saved passwords still work. That is a browser control, not a retroactive secret recall.

Microsoft Edge supports both personal Microsoft accounts and managed Microsoft Entra profiles. Microsoft’s enterprise sync guidance says managed profiles can sync passwords and other browser data, and admins can restrict sync types. That is materially better than a personal profile: the identity and policy can belong to the company. It still gives each user a synced password store; it does not turn a firewall login into an organization-owned shared vault.

Safari / Apple Passwords sit on iCloud Keychain. Apple’s Passwords app syncs passwords, passkeys, and related data across approved Apple devices tied to that Apple Account. Sharing is Shared Groups for family and other trusted contacts, or AirDrop. You can even pull those passwords into Chrome or Edge on a Windows PC via iCloud for Windows.

The important distinction is not “browser equals consumer.” It is per-user autofill versus organization-owned secret sharing. A managed Edge or Chrome profile can be governed. A personal Google, Microsoft, or Apple account cannot. Neither model should become the only owner of a shared administrative credential.

Why this fails at work

There is no shared company vault. A browser entry belongs to one profile. Even when that profile is company-managed, it does not provide the same vault membership, item history, recovery roles, and intentional sharing model as a business password manager. With a personal profile or local-only store, IT may not own the identity at all.

Offboarding the identity does not rotate the secret. Disabling a managed Entra or Google Workspace account is useful and should stop future cloud access. It cannot make a password unknown after someone has viewed, autofilled, or exported it. Personal profiles and unmanaged devices are worse because your tenant controls may never reach them. Shared high-impact credentials still need rotation when access changes.

Sharing is the wrong shape. Google shares with a family group. Apple shares with friends, family, and AirDrop. Neither is “the two people who need the firewall this week, and nobody else, with an audit trail.” Pasting the password into Teams is what happens next. That is how shared admin secrets end up living in chat.

Sync scope must be configured, not assumed. A personal Chrome profile or iCloud Keychain can put credentials on home devices by design. Managed Edge can restrict enterprise sync in supported unmanaged-device scenarios, but platform support varies and the control only helps if you configure it. Review the browser profile and sync policy; a company logo in the title bar is not proof.

Recovery follows the profile, not the shared service. A company can recover a managed identity; it cannot use that fact to decide who should inherit a locally saved firewall password, see its item history, or separate one department’s secrets from another. With a personal account, recovery may be the person’s inbox and trusted devices rather than anything IT controls.

Export exists. Chrome will download a file of saved passwords. That is a migration hatch, not a control. A CSV on a desktop is the spreadsheet problem with extra steps.

A force-installed password manager extension is a policy. Chrome’s built-in save prompt is not.

Do this / don’t do that

Do treat browser password saving as a personal convenience setting. Shopping, streaming, the dentist portal — fine.

Do put payroll, banking, Microsoft 365 / Google Workspace admin, DNS, PSA/RMM, and firewall secrets in a business password manager with shared vaults. The product decision is in 1Password for home and work, and the sharing model is in the vault tutorial above.

Do ignore the Save prompt on work browsers for those high-impact sites, so staff are not trained to dump company secrets into a personal profile.

Don’t use a signed-in personal Google or Microsoft account on a work PC as the place company credentials live. Profile sync is the feature. It is also the leak.

Don’t share the firewall login by AirDrop, family group, or “just save it in Chrome on the front desk PC.” The front desk PC is not a vault.

Don’t dismiss managed Edge or Chrome profiles as useless. They are real controls for browser sign-in, sync, extensions, and password-saving policy. Use them. Just do not confuse managed per-user autofill with a team vault.

Bottom line

Browser-saved passwords are per-user autofill, sometimes personal and sometimes company-managed. Managed browser profiles are worth configuring, but they are not a shared company vault and disabling the identity does not rotate a credential the person already knew. Keep individual low-impact convenience in the browser if policy allows it. Put shared payroll, banking, and administrative secrets in a business password manager.