Overview
URI match detection is how Vault decides which of your saved logins match the website or app you are on, so it can offer the right autofill suggestions.
Match detection options
| Option | What it matches |
|---|---|
| Base domain (recommended) | Any address on the same base domain (a login for example.com matches app.example.com, example.com/login, etc.) |
| Host | The hostname and port exactly (sub.example.com:443) |
| Starts with | Pages whose address begins with the saved URI |
| Exact | Pages whose address matches the saved URI exactly |
| Regular expression | A custom pattern you provide |
| Never | The login is never offered for autofill |
The default is Base domain, which works well for most sites.
Setting the default
In the browser extension: Settings > Autofill > Default URI match detection. On Android and iOS the same default lives under the autofill settings. (Your organization can enforce this default, in which case the option is hidden.)
Overriding it for a single login
- Edit the login item
- Open the options for the URI you want to change
- Under Match detection, choose an option
- Save
A note on advanced options
Starts with and Regular expression are advanced options that carry an increased risk of exposing credentials to the wrong page. Vault warns you when you select them. Use them only if you understand the implications.
Tips
- Use Exact or Host for sites that host several separate logins under one domain.
- Use Never for entries you never want autofilled (for example, notes saved as a login).
