Settings

Admin → Settings. Live configuration — change it and it takes effect on the next request, no deploy. Values are stored in the config table (the runtime tier of the config cascade), so they can be scoped per-org, and they're a form over stored config — never a separate settings table.

What you can set

• Site name and the home page — which CMS page is served at / (or the built-in landing).
• Sessions & auto-logout — the maximum session timeout (with a human-readable readout), and the inactivity behaviour: a master toggle, the idle window in seconds, and what happens when it fires — full logout or lock screen. See Auth & sessions.
• Theme & skin defaults — the active skin (a live switcher is in the header; this is the default).

Modules add their own

Settings is a tree, not a single page. A module registers its own settings page into it from its Bootstrap (Tiger_Admin_Settings::register), ACL-filtered live — so Docs, System, and any module you install appear here without touching a core file. That's the same mechanism you'd use for a module you write — see Building an admin screen.