Settings map

Settings is a separate area. Entering it replaces the ordinary sidebar with a dedicated settings menu — "Back to the app" at the top, and below it every screen grouped into seven categories.

Two ways to reach a screen

The landing page shows one card per screen, grouped by category, with a search box at the top; Enter opens the first result.

The settings menu stays on screen while you work. It has its own search, and it also reaches sub-pages — which the landing page does not, because a sub-page has no card of its own.

Both searches understand English terms (SMTP, session, LDAP) as well as Hebrew spelled without vowel letters, so a shortened spelling still finds the screen.

Who sees what

A screen you do not hold the permission for simply does not appear — not as a card, not as a menu row. A category whose screens are all hidden disappears with them, so a content administrator does not look at seven categories with nothing in six of them.

The Personal category is the exception: it is open to every signed-in user, because everything it stores belongs to that user.

The screens

Category	Screen	What it decides	Permission
Personal	Personal preferences	Language, theme and display	Every signed-in user
General and appearance	General settings	System title, default calendar view, items per page, scheduling cadence and external links	settings.system
General and appearance	Sidebar	Item order, names, groups and hiding	Every user (their own) · settings.nav (the default)
General and appearance	Page descriptions	The sentence behind each page's hint bulb	settings.system
General and appearance	Custom fields	The fields on servers, systems, equipment and databases	settings.fields
Scheduling and events	Update types and templates	Color, server requirement, message template and contacts	settings.types
Scheduling and events	Checklist forms	The form operators fill in on an event	settings.checklists
Scheduling and events	Task templates	Recurring tasks, for the wizard and the event editor	tasks.manage
Scheduling and events	Configuration freeze	Periods in which no change may be scheduled	settings.freeze
Scheduling and events	System memory	The contacts and notes kept per system	memory.manage
Scheduling and events	System manager email	The "send to the system manager" template and its table columns	settings.mail
Scheduling and events	Suggestion weights	How much each term contributes to the score on the suggestions page	settings.system
Activity planning	Workflows	Which flows appear on the activity board, and their field mapping	The workflows permission
Activity planning	Memory scenarios	The questions an operator answers when work on one system caused a fault in another	settings.scenarios
Users and permissions	Access management	Who may sign in and who gets administrator rights	settings.access
Users and permissions	Roles and permissions	Custom roles, the permissions in each, and who holds them	roles.view
Users and permissions	Change log	Who changed what, when, from which value to which	audit.view
Users and permissions	Security and sign-in	Session length and lockout after failed attempts	settings.system
Users and permissions	Access tokens	Tokens for scripts and automated systems	tokens.create
Connections and delivery	Integrations and connections	The source-system catalog, configured connections and data sources	settings.integrations
Connections and delivery	Message channels	Which provider messages go out through, and what the request to it looks like	settings.integrations
Connections and delivery	Enterprise identity (SSO)	The connection to the corporate identity provider	settings.sso
Connections and delivery	Alert rules and delivery	Which alerts are raised, where they are delivered and what is actually sent	alerts.manage
Connections and delivery	Scheduled reports	Which reports are mailed, to whom, in which format and when	reports.manage
Connections and delivery	Recipient groups	Standing distribution lists, with a to/cc role per recipient	recipients.manage
Connections and delivery	Acknowledgment reason wording	The words in the alert acknowledgment dialog	settings.system
Connections and delivery	Alert thresholds	The vulnerability severity at which the bell raises an alert	settings.system
System and advanced	Environment configuration (env.)	The settings fixed at deployment, and the connection status board	settings.system
System and advanced	Capacity management	Capacity, redundancy and overhead thresholds — each with its source	settings.system
System and advanced	Simulation and dev tools	Test a ticket, a mail and a message	settings.simulate
System and advanced	API documentation	The system's OpenAPI document, with in-browser call testing	docs.api

Three screens — Integrations and connections, Alert rules and delivery, and Scheduled reports — carry sub-pages. They open as indented menu rows while the screen is active, and get no separate card on the landing page.

The permission that does not look like the right one

Six screens require settings.system even though their subject is something else entirely: suggestion weights, alert thresholds, acknowledgment reason wording, capacity management, security and sign-in, and page descriptions.

There is one reason. Each of them writes a single value into the same system-settings group, and on the server that write is always behind that one permission. Filing a screen under a narrower permission — alert-rule management for the alert thresholds, say — would open it for whoever holds that one, and then fail on save. The rule here is to keep the permission the server actually enforces, and file the screen wherever it reads best.

Old links

Addresses from the previous layout, when settings were tabs on a single screen, still land on the right screen. An old bookmark or a link quoted in a support ticket does not break.