Search
Search or ask sits at the top of the menu on every staff page. Press it, press Ctrl K (Cmd K on a Mac), or press / anywhere outside a text field. On a phone it is the magnifying glass in the band across the top. See finding your way around.
It searches pages, people, devices, loans, repairs, tickets, products, runbooks and help articles at once. Pages answer from the first letter you type; records appear once you have typed two characters. Pick one to go straight to it.
Results are one list in sections, each with a count. Up and Down move the highlight, Home and End jump to the first and last result, Tab moves to the next section, Enter opens, and Escape closes the search and returns you to where you were. Each row says what it is with an icon or initials and a breadcrumb such as “Knowledge & reports” or “Settings”, never an address. With nothing typed, the search shows what you opened from it recently in this sitting.
Asking instead of searching
Section titled “Asking instead of searching”Every search of two characters or more also offers Ask. Words that read as a question, ending in ”?” or starting with what, which, who, how, when, why, is, are, do or does, put Ask: ”…” first, above the pages and records. Anything else offers it last.
Choosing Ask asks once. An exact answer from the desk’s own records, a count or a list, shows here in the search panel with Ask a follow-up. Anything else opens the Ask panel with the answer in it. See Ask and AI features.
Use search when you know what you are looking for. Ask when you have a question.
Search or the People page
Section titled “Search or the People page”People holds the roster and directory accounts. To reach one person, typing their name in the search is usually the faster path. When five or more people match, See all people matching opens the People page with the same words.
What you can type
Section titled “What you can type”| Type | Finds |
|---|---|
| A page name | The page: “costs” opens Costs, “submissions” opens Repairs |
| A settings page | The settings page, under the breadcrumb “Settings” |
| A name | People, matched on first, last or display name |
| A username | People |
| A serial number | Devices, and the repairs and loans against them |
| A loan number | The loan device and who has it |
| A ticket number | The ticket. #412 and 412 both work |
| A ticket subject | Tickets |
| A repair number | The repair. R-12, #12 and 12 all work |
| A product name | Stock items |
| An article title | Help centre articles, and your own runbooks |
Partial matches work. Typing broo finds Riley Brooks.
Choosing a person when your account is campus-limited
Section titled “Choosing a person when your account is campus-limited”People pickers match full names as well as partial names. If your account is limited to specific campuses, they use local people records with campus access checked. They do not fall back to a live SIS lookup or import an external ID when the connector cannot establish the person’s campus. If a person is missing, a whole-school administrator must import the record and assign its campus first.
Tickets and repairs answer as one list, under Tickets & repairs, each row marked with its queue and showing its status, because somebody ringing the desk does not know whether their laptop became a ticket or a repair. You see whichever half your permissions cover.
Repairs have their own number, separate from ticket numbers, so #412 may
be both a ticket and a repair. A repair is written R-412 on the desk, and that
finds it too. You can still find a repair by the serial number of the device it
is against.
Typing part of a page’s name offers the page itself, above the records. These
appear as you type, because they are answered by your browser rather than by the
server. One typo in a longer word is forgiven, so tickts still finds Tickets.
It also understands common alternative words: submissions finds Repairs, papercut finds Printers, jamf and intune find Fleet health, wifi finds Network, and known error finds the Problems view on Tickets. Settings pages answer to the words people used for them before, so features finds Modules, sso finds Sign-in & SSO and sites finds Campuses. Only pages your school has switched on and your role may open are offered.
Pages you have hidden from your own menu are still found, and marked Hidden from your navigation so you know why the link is not there. See your account.
From search to work
Section titled “From search to work”Most jobs at the desk start with identifying a person or a device.
- A student at the counter says their laptop is broken. Type their name, open their person page, see their devices, raise a repair against the right one.
- A serial number is on a device on the bench with no note. Type it, and you have the owner and any open repair.
- Somebody asks who has loan 14. Type
14.
What search does not cover
Section titled “What search does not cover”Audit log entries. The Logs page has its own search.
Ticket bodies. Ticket subjects and numbers are searched; the words inside a ticket are not. The tickets page has its own filtering.
Anything in another system, unless you ask. While your school moves its desk across from Zendesk or Web Help Desk, the search can reach the old desk (see below). It is off until an administrator turns it on, and it is never searched as you type.
Your external helpdesk
Section titled “Your external helpdesk”While the Zendesk or Web Help Desk connector is on, the results end with Search your external helpdesk for ”…”. Choose it and the matching tickets from that system appear in their own section, In your external helpdesk, each row named with the system it came from. Choosing one opens it in that system, in a new tab.
It is off until an administrator turns it on. In Settings, Connectors, open your Zendesk or Web Help Desk connector and switch on the federated search setting. Two things to know before you do:
- Searches run as the connector’s account, not as the person searching. Plugboard holds one credential for your helpdesk. If you restrict your agents in that system, to their own group’s tickets for example, Plugboard’s search can show a technician tickets they could not see by signing into the helpdesk themselves. Plugboard cannot tell from the outside whether that applies to you, which is why this is your decision rather than a default.
- It uses your helpdesk’s API quota, and that quota belongs to your school’s account. This is why it is a separate choice rather than something that fires as you type, and why the same search twice in a minute only asks once.
Why it is a separate choice. Your own results appear as you type and never wait for the external system. If your helpdesk is slow or unreachable, the section says so (”… did not respond, so results may be incomplete”). A system that does not answer within a few seconds is dropped for that search, and Plugboard’s own results are unaffected.
Permissions
Section titled “Permissions”Each part of the results is filtered by the permission that guards its own page. Search itself needs no permission beyond being signed in. Ask needs one of the permissions listed under asking a question.
| Results | Need |
|---|---|
| People | client.view |
| Devices | device.view |
| Loans | loan.view |
| Repairs | repair.view |
| Tickets | ticket.view |
| Stock items | stock.view |
| Help centre articles | Nothing. Published articles are school-wide |
| Runbooks | The documentation space’s own rules, including restricted spaces |
A part you do not have the permission for is left out of the results entirely, not shown empty. So a technician who works the ticket queue sees tickets and no people; somebody on the loans desk sees loans and no ticket subjects.
Search does not need client.view. If your school gave somebody that
permission mainly so the search box would work for them, revisit it: it grants
more than search does.
Two things are correctly scoped and always have been:
- Campuses. On a deployment with more than one site, search never returns a record belonging to a campus you do not administer.
- Runbooks. Documentation results respect the space’s own visibility rules, including restricted spaces.
The per-section permissions described above shipped later the same day, which
closed that gap. A school that read the old text and granted client.view on
the strength of it still has that grant in place.