Browse documentation
Other settings pages
Settings holds considerably more than the pages documented in detail elsewhere. Three that aren't covered anywhere else:
Org Structure
Departments, sections and job roles. These are more than labels — task and ticket assignment can target a department or a job role rather than a named person, and change advisory boards can take them as members.
Routing by role rather than by person is what stops your assignment rules breaking every time someone changes jobs.
Features
The registry of server features and roles — the things a server can be said to run. It's what makes "this depends on that server's database role" possible rather than only "this depends on that server". See Understanding dependencies.
Integrations
Third-party connections. Currently Aruba ClearPass, for Network Access.
Everything else
The Settings landing page carries a card per area — scanning profiles, discovery, downloads, notification profiles, credentials, logs, modules, data and retention, and the per-module configuration for helpdesk, tasks, knowledge, playbooks and change management. Most are covered in their own module's section.