Your table (or TO) names are quite confusing.
It seems what you have here is an Audit Log and you only want to see changes recorded during the current login of the user.
So if you have a Login table, you can relate that by ID; then use a relationship to the Audit table by ID, and filter a portal with
AuditTable::dateChanged > GetAsDate ( Max ( Login_byID::timeStampLogin ) ), or, if you just have a login date,
AuditTable::dateChanged > Max ( Login_byID::dateLogin )
(in short: make sure you compare the same data types)
or – less flexible, but with better performance for a large number of records – create a calculation field with that expression in the User table and use it as second predicate in a relationship.
If you just want to see the changes during a specific session, than IMO the cleanest way would be to add a foreign key field to the Audit table where you auto-enter the primary key of the current Login record.
Then you could create a field in the User table to hold a login ID (that you can set via clicking a portal row) and use that as relationship predicate (where now the userID wouldn't necessary).