This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.

No insurance accounts

You don't have an insurance account--very important for people who aren't gen X'ers and who are over 25 (maybe not most of the folks where you work). There is a lot of information to keep track of in addition to website login info such as:

policy no.

group no.

claims address and phone number

plan name

family members covered

eligibility dates

renewal dates



Obviously we can do anything with secure notes (and do) but more of the common financial account types should really be supported with built-in types (or you could do a simple "type editor" which provides the ability to add fields, name the fields, and set the type of the field value).



Any chance of doing either?

Comments

  • DBrown
    DBrown
    edited January 2011
    [quote name='Lewis' timestamp='1296332243' post='19729']Obviously we can do anything with secure notes (and do) but more of the common financial account types should really be supported with built-in types (or you could do a simple "type editor" which provides the ability to add fields, name the fields, and set the type of the field value).



    Any chance of doing either?

    [/quote]

    All good suggestions, Lewis, and thanks for submitting them!



    We hope to add such features as customizable fields and even custom item types in a future release of all our 1Password products.



    As you can imagine, it'll require updating the entire line virtually simultaneously, not a small undertaking for a small team like ours, and there's no information about when such major features might become available.



    That said, we know they'd be useful to many of our customers.



    Thanks again!
  • You do a good job as a moderator. Custom fields and/or types has to be carefully thought through to ensure compatibility across the product line and to enable import/export/backup to work properly. Simple is good; perfect is the enemy of the good.
  • Thanks for understanding, Lewis...and for the kind remark!