The users that are counted towards the client limit of a DocFetcher Server instance are not identified by IP addresses, but by browser sessions. This has the following non-obvious implications: Accessing the server from two different browsers on the same computer -- counts as 2 users. Accessing the server from a private and a non-private tab in the same browser -- counts as 2 users. From a user perspective, this is admittedly not ideal, since accessing the server from the same computer in multiple ways is still really only one \\"seat\\". However, the alternative, counting by IP addresses, is technically infeasible because IP addresses are generally not a reliable way to identify users. In particular, if two users access a server from behind a NAT firewall or a proxy server, the server being accessed would see both users as having the same IP address. Thus, DocFetcher Server's client limit could easily be circumvented by using a proxy server. For an extended technical discussion of the IP addresses vs. browser sessions issue, please see this page and this page on Stack Overflow. DocFetcher Server offers a workaround called session stealing that makes switching between different browsers on the same computer as well as switching between different computers more convenient. Session stealing means that when the client limit is reached, new users are able to take over existing sessions, thus kicking their previous owners out of the web interface. The intended use is for users to kick themselves out in order to more easily switch between browsers and/or computers. For instances of DocFetcher Server with a client limit greater than 1, session stealing is off by default and must be enabled in the Admin Area on the Access tab.