Please allow us to define our own metadata for members. For instance, I have a specific need to assign a 10-bit ID (1-1023) to each surveyor for reasons that would unlikely apply to anyone else, while I have no desire to include their mobile number. I would also like to include a record of their account activation / deactivation history (for seasonal work) and special flags for editing privileges in specific apps that are too cumbersome to manage through roles.

I'd like the metadata to be accessible to data events with a function like USERDATA(user_field_name) that returned null if the named field did not exist. I'd be content with a text editor to create JSON / JavaScript objects for each user, e.g. {short_id:367, history:"created 2019-05-18, deactivated 2019-10-01", privileges:"none"}. However, it would clearly be safer to have a little metadata editor where we give names and types to our metadata fields and then a form (similar to Fulcrum web app) and CSV importer to populate the data for each member.

PS: Perhaps an easy way to achieve this would be to allow us to link an app to the members table. It would be automatically populated with one record for every member, with a matching _record_id for the member's user_id. It would be editable via the Fulcrum web app, both to define the fields and edit records. (You could disable adding/deleting records, or make that equivalent to adding/deleting a member.) Or you could not enforce the links, so that the metadata would only count as linked if a special field existed (e.g. user_id) that matched a member's user_id. That's effectively what I do now, but I'm unable to access the user metadata in data events, which I would really like to do.