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
Former Member
4 years ago1PW 8 feature requests: Vault Navigation, Template/editor improvements, Shortcuts integration.
Hi! I'm holding off on fully moving to the new beta for the time being until I decide what to do with my iCloud and Dropbox vaults (on Teams, don't have my own personal/family account, only a standal...
JohannesKnust
3 years agoNew Contributor
I agree on all comments in section 2, to make 1Password for Business more usable with custom templates!
- Templates Custom Templates have been in "Beta" for years, and there haven't been any improvements to them since release from what I can tell. In our workflow, we extensively use a copy of the "Membership" template (as it was just about the only one that didn't contain a bunch of uneditable fields that we wouldn't be using) to store all the credentials that we manage for an individual end-user, rather than have a dozen "login" items per user in a Client's vault (John's O365, John's Webmail, John's GSuite, etc). The following improvements would be very much appreciated:
Allow us to create our own templates from scratch, specifying whatever sections and fields we want, rather than having to copy an existing item type that only approximates our use case.
Let us upload our own icon for the template, like we can with Vaults
Right now, if a template is being created, once a section or field has been added there's no way to rearrange them to change their order. If I realize I forgot to add a certain section to the beginning of the template, I have no choice but to delete every other field and section after place I want to add a new section to. Please improve the editor so fields and sections can be added anywhere.
Let us add our own selection drop-down menu fields like you have in various templates
Finally, please allow us to designate sections within our templates to server as login fields, that can be offered as auto-fill suggestions. If I have a section in an item that includes a username field, a password field, and a website, 1PW should be smart enough to realize this is a login, even if it's in a Membership template, or an Email Account template, or a Server template. And each of these "loginnable" sections should be accessible from the browser.