-
Notifications
You must be signed in to change notification settings - Fork 15
Command Palette
Every so often you know exactly where you want to be β a ticket, an asset, the Change module β and the slow part is getting there: open the launcher, find the module, wait for a list, scroll, click. The command palette removes all of that. One keystroke, type a few letters, press Enter.
It's the same idea as the launcher in VS Code, Slack or Linear: a single box that searches everything and takes you straight to it, without your hands leaving the keyboard.
Press βK on a Mac, or Ctrl-K on Windows or Linux, anywhere in FreeITSM. A search box drops down over the middle of the screen with the cursor already in it β start typing immediately.
- Esc closes it. So does clicking the dimmed area behind it.
- Press βK / Ctrl-K again to close it too.
It's there on every analyst page β the header carries it β so the shortcut works the same whether you're in Tickets, buried three levels into CMDB, or on a settings screen.
Open it and, before you've typed anything, you'll see Go to β every module you have access to. Type a few letters of a name (chan, cmdb, know) to narrow the list, then Enter to go. It's the waffle launcher without the reach for the mouse.
Start typing and FreeITSM searches your data as you go, grouped by kind:
| It searches | By |
|---|---|
| Tickets | reference or subject |
| Changes | title, or the CHG-0042 reference |
| Problems | reference or title |
| Knowledge | article title |
| Contracts | reference or title |
| Assets | hostname or service tag |
| Configuration items | name |
Pick a result and it opens the record itself β the ticket in its reading pane, the asset with its detail showing, the article open to read β not just the module it lives in.
π‘ Search by reference works too. Half-remember a number? Typing
CHG-42,PRB-17or part of a ticket reference finds it as readily as typing words from the title.
The palette also lists a couple of Actions you can trigger from anywhere:
- Toggle dark mode β flip between the light and dark theme.
- Sign out.
You never need the mouse:
| Key | Does |
|---|---|
| β / β | Move up and down the results |
| β΅ Enter | Open the highlighted result (or run the highlighted action) |
| Esc | Close the palette |
The highlighted row is always the top one as you type, so for most searches it's type, glance, Enter.
- It only shows you what you can already reach. A module you don't have access to never appears under Go to, and its records never appear in search. Search is scoped to your active company exactly as each module's own list is β so on a multi-company install you see that company's tickets, assets and so on, never another's. (Knowledge follows its own rule: an article shared with every company stays visible, because that's what "shared" means.)
- Two letters minimum. Searching on a single character would match half the database and help nobody, so results start once you've typed two.
- A handful per kind. Each group shows the most relevant few β enough to recognise the one you want, refined by typing more, rather than a wall to scroll.
- It follows your theme. Light or dark, the palette matches β it borrows the same colours as the rest of the app.
- Analyst side only. The palette is for the staff app; the self-service portal doesn't have it.
- It navigates and searches β it doesn't yet act on a record. Assigning a ticket to yourself or closing it from the palette (when you're looking at one) is a planned next step, not something it does today.
- Its search covers the modules in the table above. Other areas (Software, Tasks, Formsβ¦) aren't searched yet; they can be added to the same search over time.
- Tickets β the busiest place the palette takes you
- Theming & Dark Mode β the palette follows whichever theme is active
- Command palette β Developer Guide β how it works under the hood, and how to add a search source
FreeITSM β an open-source IT Service Management platform Β· github.com/edmozley/freeitsm Β· MIT licence
- Installation
- β° Scheduled tasks (cron jobs)
- Architecture
- AI Providers
- Internationalisation (i18n)
- Timezones & Time Handling
- Theming & Dark Mode
- β¨οΈ Command palette (βK)
- π Searching inside tickets
- π Attached documents
- MobileβFriendly
-
Security
- Layer 1 β which modules you can enter
- β³ π§© Module Access Control
- β³ π οΈ Module Access β Developer Guide
- Layer 2 β what you can administer
- β³ π Roles & Permissions
- β³ π οΈ Roles β Developer Guide
- β³ π€ Why capabilities are constants
- Layer 3 β the System module
- β³ π Admin Access Control
- Hardening
- β³ π Security review response 2026-08
- β³ π‘οΈ Security hardening 2026-08
- β³ π οΈ Security hardening 2026-08 β Developer Guide
- β³ π‘οΈ Round three β plain English
- β³ π οΈ Round three β Developer Guide
- Single Sign-On (SSO)
- ποΈ LDAP & Active Directory
- Browser Extension
- API Reference
-
π REST API β how it works
- β³ π« REST API: Tickets
- β³ π» REST API: Assets
- β³ π΄ REST API: Problems
- β³ π REST API: Changes
- β³ π REST API: Knowledge
- β³ β REST API: Tasks
- β³ ποΈ REST API: CMDB
- β³ π REST API: Contracts
- β³ ποΈ REST API: Calendar
- β³ πΏ REST API: Software
- β³ π¦ REST API: Service Status
- β³ βοΈ REST API: Morning Checks
- β³ π REST API: Forms
- β³ βοΈ REST API: Workflow
- β³ πΊοΈ REST API: Network Mapper
- β³ π§ Using the API docs page
- β³ π OpenAPI specification
- β³ β OpenAPI: kept correct
- β³ π οΈ Maintaining the catalogue
- Watchtower
-
Tickets
- β³ Mailbox Authentication
- β³ π€ Email send log
- β³ Basic IMAP mailboxes
- β³ Email rendering & images
- β³ SLA Management
- β³ WhatsApp channel
- β³ π¬ Web chat channel
- β³ π£ Slack channel
- β³ π Linking tickets
- β³ ποΈ Canned responses
- β³ βοΈ Limiting replies to particular senders
- β³ βοΈ Email signatures
- β³ π The public web address
- β³ π Raising a ticket for someone else
- β³ π Merging tickets
- β³ β Splitting tickets
- β³ β Selecting several tickets
- β³ π οΈ Snoozing tickets β Developer Guide
- β³ π₯ Collision detection
- β³ β±οΈ Time tracking
- Problem Management
- Tasks
- Assets
- Knowledge
- Change Management
- Calendar
- Morning Checks
- Reporting
- Software
- Forms
- Contracts
- Service Status
- π Notifications
- π¨ War Room
- Self-Service Portal
- LMS
- Process Mapper
- CMDB
- Network Mapper
- Workflows
- Issue trackers (Jira, Azure DevOps)
- System
-
Overview
- β³ π Progress tracker
- β³ Concepts & vocabulary
- β³ Email routing & mailboxes
- β³ Settings: global vs per-company
- β³ Users & self-service
- β³ Staff cross-company access
- β³ Worked examples
- β³ Pitfalls & gotchas
- β³ Scope: what it's for
- β³ π οΈ Developer Guide (make a module multi-company)
- β³ ποΈ Case study: CMDB (a linked graph)
- β³ π§ͺ Test harness (prove it's isolated)