Hello @Samuel Vitales
I agree with Kaio and Phaneendra - and honestly, how could I not? They are the best! Hahaha
One way to validate this would be to test it with a small group instead of waiting for your own session to be disconnected.
According to the current Resource Center documentation, the inactivity timeout can be configured for the whole organization, for specific user groups, or both. When both are configured, the group-specific timeout overrides the organization-wide value for users in that group.
So, if this option is available in your org, you could create a small test group, apply a shorter inactivity timeout to that group, and leave one of the users inactive to confirm that the session is logged out and the presence changes to Offline.
I don't believe there is a dedicated Operational Console view or report that specifically shows "user disconnected due to inactivity timeout," so a controlled test group may be the easiest way to validate the behavior.
Resource Center references:
------------------------------
Arthur Pereira Reinoldes
------------------------------