Expand custom fields feature to add custom headings and file attachments as a custom field

The current identity feature is nice but I feel lacks the functionality required to effectively keep track of your Identity documents through it. I end up with an unwieldy number of custom fields to record everything I need and think the feature would be better (along with the platform more generally) if the below changes to custom fields were implemented.

I think it would be good to create custom headings and group custom fields under them.
In the below images you can see how the predefined fields have descriptive headings (highlighted in yellow) and names while custom fields are all thrown together. While this doesn’t have much impact for passwords I find in the identities section of the platform I have an endless wall of custom fields to record licence numbers, card numbers and expiry dates for my various IDs that I need to keep track off. If I could have a heading for say “Forklift License” and then put the relevant custom fields under there it would make it far easier to find the items.


The other change I thought would be good would be adding an “attachment” custom field. That way if you have a complex identity record (or password record for that matter) you can attach specific files under specific headings (i.e. a copy of your visa or passport under your passport section).

The final two alterations I would consider are the following:

  • Adding a date custom field (not necessarily important as the text field works, may have some benefit to users)
  • Allowing people to hide a custom heading and its contents (can be achieved by using the hidden field for all data, this would be cleaner and could have access governed by policies or roles for use in an enterprise setting)

Let me know what people think about this. If I get time one day I could try implementing these changes, not that familiar with UI dev so might be a bit messy tho.

@Scotch7870 Welcome to the forum!

Please split your two requests in two separate feature requests (and search for possible duplicates first for each).

Reason: it’s not possible to count votes in a meaningful way if there are two requests within one feature request. – Simple example: how should one vote for your feature request, who really would like your changes to custom fields, but doesn’t want any changes to the way attachments work at all?