I think this.

How to manage user session timeouts in v7 and higher with Syracuse (sage.com)

or 

(+) Timeout settings for PU9 - Sage X3 General Discussion - Sage X3 - Sage City Community

Note: This article only applies to X3 v7 and higher. For X3 v6 and lower, see knowledgebase article 18654 below.

1. Have all users exit Sage X3.
2. On the Syracuse server, browse to ..\Syracuse\syracuse\bin\ and locate a file called nodelocal.js
3. Make a copy of the nodelocal.js file.
4. Once a copy has been made, right-click the nodelocal.js file and select Edit (or open it with Notepad if this option is not available).
5. Change the timeout value from 20 to the desired duration:
   • The nodelocal.js file will have a section similar to what's below. Edit the 20 to something higher, such as 480. The value 20 represents 20 minutes. The 20 is two character digits. Do not exceed more than 5 character digits as doing so may cause problems with Syracuse.
   • session: {
       timeout: 20, // minutes
        checkInterval: 60, // seconds
        "auth": "basic"
     },
6. Save the file.
7. Restart the Syracuse service.
   • If the Syracuse service does not start or if logging into Sage X3 generates errors, this generally means the nodelocal.js file was edited incorrectly. Restore the copy and attempt steps in this KB again, making sure not to exceed 5 character digits in the value and no extra characters are added or deleted.

Note: The timeout is unique to each Web browser tab. If you are working on the first Web browser tab in X3, and open a second tab and continue to work on the second tab without going back to the first tab, the first Web browser tab will time out. You will not see the timeout message until you click back on the first tab.

Special considerations for multi-Syracuse servers

If after following all these steps above and you are still seeing wildly different timeout durations, you must then verify if you have multiple Syracuse servers running, and thus different nodelocal.js files with different settings. To do this:

1. Have affected users log into X3. (i.e. users who have the wrong timeouts)
2. Have unaffected users log into X3. (i.e. users who have the correct timeouts)
3. Log into X3 as an admin who has access to the Administration menu.
4. Locate the menu item "Web client sessions" and click to open that screen.
5. Look for a column called Server name. This is the Syracuse server. If there are multiple Syracuse servers, you will see the different server names.
6. Log into the affected server, and perform the steps noted above to change the timeout setting to make it active.
7. Users must log out of Sage X3 and log back in for changes to take effect.