Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
steve28
3 years agoOccasional Contributor
Autofill... domain matching choices?!? O. M. G.
Holy crap. It's here! Mostly!
It would be awesome if you had ONE more choice:
domain only: match as long as domain.com matched
host: the full host needs to match (i.e., sub.domain.com) ...
wagnerone
3 years agoDedicated Contributor
wagnerone interesting, thanks for explaining. I wonder if the “archive” feature found in 1Password 8 would help your use case. Archived items remain perfectly intact for an indefinite time, but they never get suggested in the browser. Anyone in the team can access them at any point via the app.
Secondarily (although I know you mentioned you prefer not to edit existing items), 1Password 8 has a password history feature that lets you keep track of all the password a specific item’s ever had. You can see them by using the drop-down next to the password field. I imagine the workflow your team has is already fairly set, but I wanted to mention this possibility.
I’m curious if any of these approaches would work for you.
@ag_Gabriele Thank you for reply!
The Archive feature could be useful, yes. I never really understood what it might be used for. Right now it seems like, in our case, a "pre-Trash" area. We could reconsider (or, consider) how we're using that vs the trash.
I know all about the password history. ;) It's a thorn in my side and IMO a security gap to not let us "clear" that password history on an item. My issue with it is I often have the need to duplicate complex records with various unique data items in them, but I cannot do so because of the password history being forever retained in the record.
Anyway, it's not just the password we want to track for historical reasons, but all the notes, additional Section and field items we add throughout that records actual lifetime.