Getting started

This walkthrough takes about fifteen minutes and ends with something real: a document of yours in a knowledge base, and an answer from Klu that cites it.

Before you start you need an account. Accounts are created by invitation, so if you don’t have one, ask your administrator to invite you — or read Administering your organization if you are the administrator.

You also need a document you don’t mind uploading. A PDF or Word file of a few pages is ideal — a contract, a policy, a protocol. Something you know the contents of, so you can tell whether the answers are right.

Go to your product’s address and add /hub/:

Lex — lex.klusai.com/hub/
Med — med.klusai.com/hub/
razorBridge — razorbridge.eu/hub/

You’ll be sent to the sign-in page. Enter your Email and Password and press Log in. If your organization uses Google, Microsoft or another identity provider, use the Continue with… button instead — it’s faster and there’s no password to keep.

If you belong to more than one organization you’ll see Select organization: pick one and press Continue. You can switch later from the sidebar.

Lex and Med open in Romanian. If you’d rather work in English, use the small RO | EN toggle at the bottom of the sidebar — one click, and it sticks.

2. Get your bearings

You’re on Home. Spend a minute here rather than clicking straight into something:

Your workspaces — a card per area you have access to. This is the honest answer to “what do I actually have?” — if a section isn’t here, you don’t have it.
Recent activity — what your colleagues have been working on.
Quick actions — the two shortcuts you’ll use most: Search Knowledge Base and Ask the assistant.

Now try the two navigation tools, because they’ll save you the most time later:

Press ⌘K (Ctrl K on Windows or Linux). A palette opens listing every page you can reach. Type a few letters — know, say — and press Enter. This is faster than the sidebar for anything you can name.

Set your timezone. Go to Account (in the sidebar), find Timezone under Your details, set it, and press Save changes. Every date and time in the Hub is displayed in it, so this is worth doing before you look at a single deadline or appointment.

While you’re on this page: Answer style controls how the assistant formats its replies. Leave it for now — come back once you’ve seen a few answers and know what you’d prefer.

3. Ask Klu something

Click Ask Klu in the sidebar (it reads Ask Lex or Ask Med in those products).

You’ll see a greeting and a row of suggestion cards. Click one — they’re ordinary prompts, and they’re a good way to see what the assistant is set up to do. In Lex, Status of active cases; in Med, Today’s appointments.

Watch what happens as the answer arrives. Klu tells you what it’s doing: Thinking, then Calling a tool, then Used that tool with a result count. If your organization has data behind that question you’ll get a real answer; if it’s a fresh tenant with nothing in it yet, Klu will say so — which is the correct answer, and worth seeing once.

Now type something of your own. The composer takes plain language — “which of my cases have a deadline this month?” works better than trying to guess a command syntax. Enter sends, Shift+Enter adds a line.

If the answer used your records or documents, a sources list is attached. Open one. You’ll get a panel with the exact passage, the page it came from, and a link to the original. This is the habit worth forming now: read the claim, open the source, confirm the source says it. An answer with no sources attached is the model’s general knowledge, not your data.

4. Create a knowledge base

Now let’s give Klu something of yours to work with.

In the sidebar, open Knowledge and click Databases. Press or expand Create new knowledge base and fill in:

Name — something specific. Client contracts or Clinic protocols, not Documents. You’ll want more than one of these eventually, and retrieval works better when each holds one kind of thing.
Description — optional; a line on what belongs in it.

Press Create base. It appears in the list, marked Active, with no documents yet.

5. Upload your document

Go to Knowledge → Upload.

Under Knowledge Base, select the one you just created.
Drag your file onto the drop zone, or click browse and pick it. You can select several files at once.
Press Upload & Process.

You land on the Documents list with a confirmation, and your document showing a status. It starts as Pending, then shows a progress badge naming the step it’s on — for a PDF, the page it has reached — and finally Ready. The list refreshes itself every few seconds, so just watch. A few pages of text take moments; a long scanned document takes longer.

Once it says Ready, click it. Expand Extracted Text and read a few lines. This is the text kOS actually read out of your file — and it is the single most useful thing to check when an answer later seems to have missed something. If the text is garbled or empty, the file was unreadable, and no amount of rephrasing your question will help.

6. Ask about your document

Back to Ask Klu, and New conversation.

Ask something whose answer you already know from the document — a specific figure, a date, a clause, a named party. Something like:

What notice period does the agreement require?

Klu searches your knowledge bases on its own; there’s no base to select. The answer arrives with a source attached: your document, the page, the section heading, and the passage it used.

Open the source and check it against what you know. If it’s right — you’ve now seen the whole loop, and everything else in kOS is a variation on it.

If it’s wrong, use Flag as incorrect and pick a category. That is genuinely the most useful thing you can do with a bad answer.

Try the other way round

For a contrast, drag the same file directly onto the conversation and ask about it. Klu reads it from the message rather than searching your library. That’s the right tool for a document you’re looking at once; the knowledge base is for documents your whole team will ask about repeatedly.

Where to go next

The Hub — the rest of the navigation, notifications, and your account settings.
The Klu assistant — commands, plans and approvals, assistants, and how citations work in detail.
Knowledge bases — supported formats, managing documents, searching a base directly.
Privacy tiers — the lock in the composer, and what it changes.
Your product’s own section: Lex, Med, razorBridge.