If you have an existing template for those email notifications (which OOTB, you should), you can add an email layout which is configured to have a header/footer. There is a default Email Layout that you can work off of and duplicate for your own effo...
Are there other elements of the record which would work as identifying info for the user signed in? I would suggest avoiding any reporting off of journal fields/text fields since there isn't an inherent way to dynamically filter based off the 'Me' op...
The 'sys_update_xml' table is your 'Customer Updates' table. I'd start there. Here's some documentation to further elaborate on why you would want to search that table for information regarding modifications to OOTB functionality.
I would start with the following:
<g:ui_reference name="user" completer="AJAXTableCompleter" id="user_name" table="sys_user"/>
From there, you can add the columns attribute to the UI reference by doing the following:
<g:ui_reference name="user" compl...
Well, the idea is that you don't want to load a large number of records on one page. The additional records in a list view = longer load times which creates a bad UX. If I know that I want to look at a list for all records assigned to a group, I'm ok...
