​@Waqar Habib It depends on what you want to track.  If it’s aggregated counts of records that have been created or changed in a given area, some of the IFS Lobbies will have that information.  The level of granularity will depend on the area being tracked.  For example, buyers on Purchase Orders or resources on Service Tasks.

If your question is more forward looking, you can also use Lobbies to present the work that needs to be done on a given day.  

https://docs.ifs.com/techdocs/foundation1/010_overview/220_user_interface/about_lobby/default.htm

Lastly,  you can turn on History Logging for any areas of interest,.

https://docs.ifs.com/techdocs/foundation1/040_administration/270_monitoring/010_history/010_history_log/default.htm

​@Waqar Habib 

This is a very expensive operation. As ​@Tracy Norwillo  explained, there is always the option to enable history logging. 

This is advised only to use in necessary areas. The reason being this creates a lot of data. 

But there are things like customer order, purchase order etc that tracks the historical data out of the box. If the things you need are there, then all good.

If not enable history logs for the areas, you need and then use that data.

Finally, the best way to track is to create a lobby with user_id as the parameter and it will narrow things down for you. 

I’d advise to reach experts with knowledge on history logging as this has caused number of errors when not handled properly. 

If you could explain what exactly you are trying to track, I can point you in the right direction.