Teaching Clara
Clara arrives knowing how to be safe. You teach her how your business works: your house rules, your how-to steps, your legal obligations. Bring a document and she reads it, or write one rule in plain words. Nothing applies until you review it and press publish, and nothing you add can ever switch off her built-in protections.
This page is for everyone. No technical background needed.
What Clara can learn
| You add | Clara treats it as | Example |
|---|---|---|
| House rules | What is allowed and what is not | "Refunds only within 30 days" |
| How-to steps | The way your team handles things | "New customers get a welcome pack in one business day" |
| Compliance obligations | What the law requires of you | "Keep conversation records for seven years" |
Everything you teach her sits on top of a baseline that Paresium maintains. If one of your rules would loosen a baseline protection, Clara refuses it at the door and tells you which protection she kept. Your rules can only make her stricter, never looser.
Three ways to add knowledge
Open Knowledge in the portal and press Add knowledge.
Bring a document is the usual path. Upload your employee handbook, refund
policy, or compliance manual. Clara accepts PDF, Word (.docx), Excel, PowerPoint,
CSV, Markdown, plain text, HTML, and images. Scanned pages are read for you when
that capability is enabled on your environment. Older Word .doc files need a
re-save as .docx first. Clara reads the text with an AI model and proposes
rules, each one shown next to the exact sentence it came from. The reading step
is metered to your credits and you see the held amount before anything runs. You
keep, drop, or edit every proposed rule before it goes anywhere.
Bringing everything at once
Drop a pile of files (or a zip) onto Knowledge. Clara checks each file first and tells you in plain words which ones she can read and which need a fix. Readable files get one combined credit price. Batches under your auto-run limit start on their own; larger ones wait for your confirmation. You can leave the page while she reads. Finished documents land in Needs review on the Knowledge page.
Review and publish stay one document at a time. Nothing applies until you approve the rules. There is no bulk publish. You are only charged what the run actually uses. Nothing you add can weaken Clara's built-in protections.
Change the auto-run limit under Settings → Knowledge.
Write a rule in plain words is best for one rule at a time: when it applies, what Clara should do, and how serious it is.
Paste structured items is for developers who already have rules as JSON.
The safety check before publish
Every path runs the same test step: Clara checks your new knowledge against her baseline protections without saving anything. If a rule conflicts, you see it in plain words and that rule cannot be published as written. Publishing is always an explicit button, every publish creates a new numbered version, and imported rules keep a link back to the document they came from.
Company-wide or one assistant
When you publish, you choose who follows the knowledge: the whole company, or only named assistants. A rule scoped to your support assistant never binds your internal HR assistant, and the run records show which rules applied.
Keeping documents in sync
Connect a Google Drive folder under Knowledge, Connected sources and Clara keeps read-only copies of its documents. Share the folder with your workspace's Clara service account (the portal shows the address), then press Sync now whenever the documents change. Synced copies cannot be edited or deleted in the portal: change them in Drive and sync again. If a document changes after you imported rules from it, Clara flags those rules as possibly out of date so you can re-import.
SharePoint support is built and arrives when Microsoft 365 connections are switched on for your plan.
Where Clara had to ask a human
The Knowledge page also shows repeated questions Clara could not answer on her own. Each one has an Add knowledge for this button that opens the wizard with the situation already filled in. Adding knowledge there turns tomorrow's "let me check with the team" into an immediate, correct answer.
From the command line
Everything above also works in the paresium console:
paresium knowledge list
paresium knowledge list --review
paresium knowledge import employee-handbook.pdf --title "Employee handbook"
paresium knowledge import ./handbook-pile/ --structure policies --yes
paresium knowledge versions kn_1a2b3c4d5e6f
paresium knowledge scope kn_1a2b3c4d5e6f --to company
paresium knowledge delete kn_1a2b3c4d5e6f
Document imports quote the metered reading step first and ask before running
it (pass --yes to skip the prompt in scripts). Folders, globs, and zips use
the same batch lane as the portal: one price, then Needs review. Nothing
applies until you publish.