Is there a user guide to available item types? I'm new and want to design/plan before implementing.

Thanks, Brenty!

I had seen the first two links you sent before writing. What helped most here is your clarification that there are only four types that do filling and that the other "types" you have provided are templates for storing personal information but are not used for automated online form filling.

Would it be fair to say that the other 14 types** currently listed in the item creation drop down are essentially custom information types that you have provided as optional templates and that we, as users, can customize those or replace them with our own customized versions of information types (and that all of these - yours and any that we customize) can not used for filling forms except by manual copy and paste actions?

Assuming I am understanding that close to correctly, then is it possible to edit the type list to customize it for our family (i.e. to either edit or delete any or all of the provided information types, aside from the four that are use for filling, and to add our own custom types and have them show up in the drop down for users in our family group)? If not, how do custom types work - how do users access them - once they are established?

I did come across multiple references in your forum posts to not being able to customize information types so it seems you have upgraded 1Password with the capability for user-defined custom types fairly recently. I am happy to have access to the functionality, however it works, for sure!

Regarding the references to user guides and manuals that I found scattered in forum posts: is there a manual available at all? I noticed references to separate manuals for PC vs. Mac users, etc. Do these no longer exist? Or a listing, in one place, of whatever documentation is currently available, something like a table of contents? If guides like those you sent me links to are all that is available for documentation now is there a listing of all available guides in one place?

[**to be completely clear about which types I am referencing above, in addition to the main four fillable types of Login, Credit Card, Identity, and Password, the other fourteen types listed are: Secure Note, Wireless Router, Server, Email Account, Document, Bank Account, Database, Driver License, Membership, Outdoor License, Passport, Reward Program, Social Security Number, Software License]

Thanks again for your help!

Awesome sauce! I feel like I'm significantly up the learning curve to knowing how I want to set up our family plan and I haven't even started playing within my own account as a family sandbox yet!

On another subject, I came across some older posts** in your forum yesterday that discussed the idea of crowd sourcing templates for users by creating a repository of templates that users can contribute to. I LOVE that idea (and actually found myself hoping to find something like that when I started my process with 1Password...)

It would be so useful for at least two dilemmas users have: 1) starting up as a newbie user and wanting to jump start the process of tailoring for individual needs; and 2) sharing ideas and insights among experienced users to improve templates over time in the pursuit of best practices, including, particularly, in niche applications; this could include the ability to rate and comment on submitted templates to add to the peer-to-peer information in the repository.

To those ends four suggestions I have if you do ever pursue crowdsourcing functionality would be to:

a) add a checkbox inline in the final step of customizing a template to ask the customizer if they would like to share their custom template with others (perhaps with a choice to share "as is" or to mask or anonymize any element that may contain identifying or other sensitive information (e.g. by manually highlighting any included proper nouns); This could include a brief pitch on why sharing is of value with a link to the respository; I believe this would increase the frequency of sharing significantly - once someone shares once they will find the checkbox triggers a natural, automatic go/no-go decision on every template they create;

b) to offer the option, to the sharer, of selecting relevant category tags from a dropdown that capture the obvious uses for the to-be-shared template to help organize the template repository (among categories defined by an AgileBits curator or community advisory board?);

c) to include community support for repository users to rate and comment on shared templates so that, over time, peer-to-peer guidance emerges; and

d) organize something like curators (permanent paid experts on what's in the repository - also acting as moderators?) and guest reviewers (invited outside experts, paid or voluntary, with valued perspectives?) who would create collections of templates selected for particular use cases and post their collections with a narrative about their choices and envisioned uses.

These last two suggestions would address the challenge of how to communicate best practices and offer jumpstart advice to newbies and power users alike in as fine-grained niche usage cases as emerge within the community (N climbers who are global high altitude "peak baggers" and want to share how they use 1Password to manage the business side of basecamp support internationally? M parents of multiples -twins, triplets, quads- who want to share how they use 1Password to organize their babies' medical accounts and records? P entrepreneurs who want to share how they use 1Password to address security and privacy needs while using co-working spaces? With the right community supports those in the niche will be able to find each other...)

**older post cited above: https://discussions.agilebits.com/discussion/19520/if-custom-categories-were-available-how-would-you-use-them

Thanks, Lars. Makes perfect sense. In fact, regarding what you wrote here:

While we'll never say never to altering or adding to the list of pre-populated categories in 1Password, it has to be a really compelling case for us to consider any changes there.

...it seems to me that you might want to consider reducing the number of baseline pre-populated categories and increasing your emphasis on and documentation of the fields that are the building blocks of categories so that users can become better customizers.

I live in SoCal now but as a former Wisconsinite who grew up in "north woods" close(r) to AgileBits home locale of Canada I get the reasons you have a lot of people wanting to add "Outdoor licenses" to 1Password, but now that you have custom category support it seems a bit odd to see that (and other) categories on your baseline pre-populated list.

Between that and the fact that [ 1Password = data repository/sharing + stellar security ] in this age of massive security breaches your ongoing success will inevitably lead to proliferation of data types well beyond what you envision (and probably already has.) I have really enjoyed reading about the thinking those of you on the AgileBits team are doing to figure out where to draw the box around what 1Password is and what it isn't. (The visibility on this kind of thing is another benefit of your openness within the forum, in addition to what someone in some post I read described as a policy of openness to promote trust in a product that, by its nature and mission, requires we trust it.)

I think the support challenge in helping users becoming adept at customizing would be greatly helped by crowdsourcing category templates and supporting peer-to-peer community growth centered around customization. Add my vote to the "Yes on crowdsourcing" tally!

Just a footnote to say thank you to both Lars and Brenty for pointing out that the existing category types don't get in our way if we don't use them - e.g. they don't show up as we use 1Password in our implemented user configurations unless they are selected components we choose to include. This was also a helpful bit of guidance for this new user - it helped me stop worrying about the distinction between existing and custom categories. Even the four main types that are important to distinguish because they get used for filling forms online don't need to be bothered about if they aren't used. This type of input from the AgileBits team members was very helpful to continue wiring in my mental model. I'm looking forward to getting more clarification on what customization is possible with the categories that do include form filling functionality. That part of my mental model is still pretty sparse...