Academic databases log out after 20 minutes of inactivity. That is the plain answer, and it is the part users feel first. A session that sits still will often end on its own, and the screen will ask for a fresh sign-in.
I keep coming back to the gap between a database and a browser tab. Many people think they are still “in” a source if the page is open. In practice, the system is watching for activity. If nothing happens for long enough, the session ends. In one common example, Factiva’s help page says it times out after 20 minutes of browser inactivity, and that setting is controlled by the provider. Other library help pages and vendor guides show the same basic pattern, though some systems use longer or shorter limits.
That is the main fact a reader needs. The logout is usually not a sign that something broke. It is a normal session limit. It exists because the service treats idle time as a closed or abandoned session. In some systems, that also helps release access for another user. In that sense, the logout is part of how the platform manages shared use.
The detail that matters most is that the timeout is not always identical across all databases. Some library guides say 30 minutes. Some say 15 minutes in tighter settings. Some systems are set much longer. So the headline is true in a general sense, but it is not a universal rule for every academic database at every site. The exact number depends on the platform and on local setup.
For research work, this feels small until it is not. A long reading session can end in the middle of note taking, and an unsaved search string can disappear. The problem is not only inconvenience. It can also break a chain of thought. That is why timeouts matter in database teaching. They are part of the user experience, even if no one thinks about them at first.
I treat this as a design fact, not a moral failure. A timeout can protect shared access and reduce stale sessions. It can also frustrate careful work. Both things can be true at once. The useful part is knowing that the logout is built into the service, not just into the browser or the user’s mood.
The hard limit here is coverage. Public help pages can show the timeout rule, but they do not always show every edge case. A database may behave one way through a library portal and another way through a direct vendor page. Settings may also change without much public notice. So I can say the 20-minute pattern is real and common, but I cannot say it applies to every academic database in the same way.
For me, that is the kind of detail Beyond Citation should name plainly. A source can be solid and still have a small but important friction point. Session timeout is one of those points. It is not a flaw in the scholarship inside the database. It is a limit in the way access is managed.
The Source List tries to stay faithful to that kind of plain fact. One digital source worth knowing, one search tip, and one honest limitation. That is the right frame for a logout rule too, because the useful answer is simple, and the limit is simple as well.