Working only in iOS: creating new fields for entries; getting 1PW to eat logins from Safari.
Hullo, I'm working only in iOS as 1PW won't run on my desktop. I'd be grateful for advice regarding the following:
I need to add custom fields to your items for things such as additional info needed for logins.
I'd really like to add even more custom fields, such as emergency contact numbers (national and international) for credit card entries, postal addresses for banks and so forth. After using Firebox it's going to be a total pain switching between Address Book and 1PW.
(Perhaps you could add some 'blank for your own personal message' fields to your ready-made entries?
How to use '1PW for Mac' describes a way of automatically creating new logins - including custom fields - in 1PW from Safari; is it possible to do this in iOS? If so, can you talk me through it?
Comments
-
Hello @colddrake ,
You can do this in iOS now. Custom fields is part of the Pro Features. If you go to Settings > Pro features, you can purchase them, and then when you edit an Item, you can add new sections and new fields, including different field types such as text, passwords, email, etc. More information is here: https://guides.agilebits.com/1password-ios/5/en/topic/pro-features
Cheers.
0 -
Thanks, hayesk. But this leaves me feeling particularly dense: I've been trying to work out how to create new fields in the Pro version all morning; searching the Pro features FAQ for terms such as 'create"new fields"' doesn't come up with any obvious instruction. This page (https://guides.agilebits.com/1password-ios/5/en/topic/create-login?q=create+"new+fields") is said to tell me how to create new items 'and more', but there's no guide to adding fields to an existing item.
Also, can I record logins from Safari on the iPhone? If so, how?
0 -
Further to this: I've now found the 'edit' button and worked out that I have to add a section in order to add a field. Why the distinction?
0 -
Hi @colddrake,
All custom fields belong to a section, no matter what version of 1Password they're created in. Now maybe it was a reason of space that on the Mac there is a blank section ready to add custom fields to (which if it remains blank disappears when you click on Save) in contrast to the much smaller workspace of the iOS devices. That answer would require the devs and/or the designers but space considerations seems a reasonable enough cause.
I do apologise that it took a while to figure out this particular feature, obviously the goal is for an intuitive UI.
Regarding your other question. Extension are new in iOS 8 and while we jumped on to their power straight away this is still our first attempt at an iOS extension. So at the moment the extension can fill using an existing Login item but it doesn't have quite the power that the Mac or Windows extension has. In some regards it never will, extensions are strictly controlled and may be terminated at any time by iOS. As a result we have to keep things very simple and quick. We do want to add saving a Login item for the obvious reasons but we have to be very careful. The last thing we want to ever happen is have a partially created Login item just as iOS terminates the extension. All it means is we're being careful as to how we move forward.
If you have any follow up questions do please ask :smile:
0