Web dashboard

Find help

Search the guides by what you are trying to do, narrow them to where you are working, and read one.

Sound is off

The Knowledge Base holds the written guides for the product. It is built to be searched by the thing you are trying to do, not by the name of the page you are on — so plain words work: "how do I approve timesheets" finds the timesheet approval guide whether or not those words appear in its title.

Two searches run at once. One reads the meaning of what you typed and ranks the guides by how well they answer it; the other matches the words themselves. The ranked answers lead, and the plain word matches follow, so a phrase that reads like a question and a single keyword both get you somewhere.

The platform chips are worth setting. A guide is tagged for the Web dashboard, the Mobile app, both or neither, and the steps genuinely differ between the dashboard and the phone. A guide with no platform tag applies everywhere and carries no badge.

Results appear as you type. Enter sharpens them — the list shows Ranking… while it re-orders by meaning.

Step 1
Open the Knowledge Base
Knowledge Base in the side menu. It opens on the browse view, with the guides grouped into categories and sub-categories — worth a look when you do not yet know what to ask for. Searching replaces that grid with results; clearing the search puts it back.
Step 2
Ask it what you want to do
Type the task rather than the page name. Search reads the meaning of the phrase, so "record who turned up" gets you to the attendance guide without matching a single word in its title.
Step 3
How the results are ordered
The best-matching guides come first, ranked on meaning, and a ranked row can show the passage it matched on. Plain keyword matches that the ranking missed follow underneath.
Step 4
Narrow to your platform
The Web dashboard and Mobile app chips filter to guides for that platform. The filter applies to the search results too, not just the browse view.
Step 5
Why the platform matters
The same task is often done differently on the dashboard and in the app. A guide tagged for one platform shows a badge saying which; a guide with no badge applies to both.
Step 6
Check the badge, then open it
Read the platform badge on the guide before you follow it — following mobile steps on the dashboard is the common way to get stuck.
Step 7
Read it in steps
Guides are written as numbered steps, and many carry the demo video for the same task alongside the words.
Step 8
Three different places to look, and which is which
It is easy to lose twenty minutes searching the wrong one.

The Knowledge Base is guides about the product — how a feature works, written by us, the same for every organisation. The Library is your own organisation's documents: policies, procedures, the care plan template your team actually uses. Star Beam answers from your organisation's content — records, form responses, and library documents that have been indexed for chat — and not from these guides.

So "how do I record a medication" is a Knowledge Base question, "what is our policy on administering one" is a Library question, and "what did we record for this client last Tuesday" is a question for the assistant.
Step 9
Why a colleague's search finds something yours does not
Almost always the platform chip. A guide tagged for mobile is filtered out of a web-filtered search even when it is the guide that answers the question — which is the right behaviour when you are at a desk and the wrong one when you are writing instructions for somebody who is not. Clear the chip before concluding a guide does not exist.
Step 10
If the search finds nothing useful
Try describing the outcome rather than the control — "stop a form going to everyone" rather than "visibility setting". Then clear the platform chip: you may have filtered out the guide that answers it. And if the answer genuinely is not there, the assistant can answer from your organisation's own content, which the Knowledge Base does not contain.