Registering a security key with one account does not register it everywhere. A single physical authenticator can support several services, but each registration creates a credential for a particular service. That distinction matters when you are checking which accounts a key can actually unlock.
| What you need to know |
|---|
| A physical authenticator can be used with more than one supporting service. |
| WebAuthn credentials are scoped to a particular relying party. |
| Adding a key to one account does not enrol it with unrelated accounts. |
| Keep an account-by-account record of completed registrations. |
The W3C WebAuthn specification describes public-key credentials as scoped to a relying party: the service using the authentication system. The authenticator helps create and use that credential. The plastic object on your desk and the credential registered by a website are different parts of the arrangement.
Consider two hypothetical accounts, one for email and another for a document service. You finish registering the key with email. That says nothing about the document account. It needs its own supported enrolment process. A successful email sign-in is evidence for that email registration, rather than a test of every account you use.
Check the account, not the keyring
The FIDO Alliance’s passkey guidance distinguishes credentials that can be synchronised from device-bound passkeys, including those held on security keys. Neither description promises that every bank, exchange or workplace application supports your chosen device. Check the service’s own authentication options before buying or enrolling hardware.
A useful private inventory records the service, the account identifier and whether enrolment was completed. It can also record the service’s available recovery route, without copying passwords or recovery secrets into the inventory. If you have two physical keys, establish which accounts have each one registered. Similar-looking devices are easy to mix up.
Test a registration using the service’s normal sign-in process while your existing access still works. A test should answer one narrow question: can this authenticator sign in to this account? Keep recovery checks separate, since a working key does not prove that a lost-key procedure will succeed.
This is also why removing a key from one service should not be treated as a global revocation. Review the other registered accounts individually. The manageable unit is the account’s credential record; a single hardware purchase does not replace that record.






