Wrong wallet connected

You're connected, but as the wrong account — here's how to fix it and what PolicyVault does automatically.

#Symptom

The dashboard shows a vault, agent, or approver identity that doesn't match who you expected, or an action you expect to be available (like owner controls) is missing or disabled.

#Why this happens

PolicyVault has no separate login system — your identity is whichever account is currently active in your connected wallet (KasWare). If KasWare has multiple accounts and a different one than you intended is active, PolicyVault will correctly show you what that account can actually do — which may be nothing, if that account isn't the owner, agent, or approver on the vault you're looking at.

#What PolicyVault does automatically

Switching accounts inside KasWare while a request is in progress discards that in-progress request — PolicyVault never reinterprets an old signature under a new account, and it never silently continues a flow under a changed identity.

#What to do

1. Open KasWare and check which account is active.
2. Switch to the correct account inside KasWare.
3. Reload the PolicyVault page if the dashboard doesn't pick up the change automatically — vault state, requests, and history are always re-read fresh from the durable backend on reload, never assumed from stale browser state.
4. If you're not sure which account should be used for a given vault, check that vault's owner/agent/approver identities against the accounts available in your wallet.

See also: Connect KasWare, Owner.