
Open the editor
Open Templates

Click Create new → Assistants
Name your Assistant

The Assistant Configuration panel
None of these change how the Assistant answers. They determine how you and your colleagues find it in a library that has grown to thirty Assistants.Language versions
An Assistant can carry more than one language version. The configuration panel has a Language field showing the one you’re editing; open it and you get the list of versions the Assistant already has, plus Manage languages at the bottom. That switches the menu to a searchable list of every language Libra supports — tick the ones you want and click Apply selections. Name, description, prompt instructions and conversation starters are all held per language. Switch the active language and the Setup & Instructions tab shows that version’s content. Every language you add needs its own name and prompt instructions before the Assistant will save; press Save with one incomplete and a Fill required fields badge marks the offending language in the Language field and its menu.Setup & Instructions
Prompt instructions
The system prompt, and the one field that genuinely matters. A four-part structure works well:Identity: who the Assistant is
Identity: who the Assistant is
Task: what the Assistant does
Task: what the Assistant does
Format: how the output is shaped
Format: how the output is shaped
Constraints: what the Assistant never does
Constraints: what the Assistant never does
Conversation starters
Optional example prompts that appear as clickable buttons when someone opens a chat with the Assistant. Click Add for each one; every row has its own Improve with AI and remove buttons. Starters are the fastest way to show a colleague what the Assistant is actually for.Resources
Model
The base model that answers the prompt, default Libra AI. Leave it alone unless you have a specific reason to pin the Assistant to a particular model.Research sources
Pre-selecting research sources is what turns a generic Assistant into a jurisdiction-specific one. When someone picks the Assistant in chat, Libra switches Research on automatically with exactly those sources — nobody has to remember which databases the question needs.
Open the Resources tab

Choose the jurisdictions
Toggle the sources you want
Save the Assistant
Knowledge
Knowledge documents are the reference material the Assistant draws on. Think of them as the onboarding pack you’d hand a junior associate.Find the documents

Select and add
Save, run, share
In a new Assistant the primary button reads Save. Once it exists, the primary button becomes Run — which drops you into a chat with the Assistant attached — and Save moves alongside it. Saving is blocked until every configured language has both a name and prompt instructions. Duplicate, Share, Delete and the favourite toggle only appear in the toolbar once the Assistant has been saved, and only for Assistants you have the rights to. If you’re the only member of your team, Share either disappears or turns into an upgrade prompt, depending on your plan.Click Share
Set General access
Add people or groups
Set the permission level
Test before you trust
Don’t validate an Assistant on one trial.Run it on three real prompts
Read each output critically
Iterate on the instructions
Managing existing Assistants
Tips for instructions that work
Be specific about the task
Be specific about the task
Define the output format explicitly
Define the output format explicitly
Provide examples for judgment calls
Provide examples for judgment calls
Set guardrails the Assistant should never cross
Set guardrails the Assistant should never cross
Say what to do when the knowledge runs out
Say what to do when the knowledge runs out

