Knowledge (sources & tools)

The Knowledge page determines what the assistant is allowed to use during chat. These are preferences, not extra permissions.

Important:

• preferences are stored locally in your browser;
• switching products gives you a different knowledge configuration;
• in project chat, project documents remain the main context even if you enable extra sources.

Knowledge page layout

The Knowledge page is organized into four top-level sections, selectable from the top of the page:

• Sources — public and external sources, grouped per legal domain. Each card has its own on/off toggle. A filter bar and per-tab tooltips help you find what you need; attention indicators flag sources you probably want to enable for your practice.
• Tools — capabilities such as retrieving legislation, using case law, managing tasks, starting research, and generating Word review suggestions.
• Personal — your personal knowledge base, your uploaded files, and your long-term Memory store with automatic keyword extraction.
• Organization — shared organizational knowledge bases and linked public knowledge bases, plus organization-wide policy switches for OWNER and ADMIN.

The choices you make here are mirrored in your browser so they take effect in chat immediately. If the public-source catalog changes, the page quietly drops unknown ids — no reset needed.

Vakgebied (specialization)

The Vakgebied stepper tells the assistant which area of law you practice. That drives the filtering of sources and suggestions.

The stepper has three steps:

1. Legal domains — pick one or more legal areas from the grid. One click to add, one click to remove.
2. Role — pick your role (for example lawyer, paralegal, in-house counsel). One roleSlug per profile.
3. Branches — optionally pick one or more industry specializations; this step auto-saves.

If your profile is still empty, a one-shot hint walks you to the stepper. During onboarding the Knowledge page opens automatically on the relevant section.

Product matrix from the code

This is the current functional matrix for LEO, VERA, and ZIA.

Source or tool category	LEO	VERA	ZIA
Project, personal, and shared knowledge bases	Yes	Yes	Yes
Dutch laws and regulations (Wetten.overheid.nl)	Yes	Yes	No
Omgevingswet by location (IPLO/Ozon)	Yes	Yes	No
Official publications (KOOP)	Yes	Yes	No
Case law (Rechtspraak / ECLI)	Yes	Yes	No
EU law (EUR-Lex)	Yes	No	No
German law	Yes	No	No
Disciplinary law	Yes	No	No
SKGZ / Scheidsgerecht Gezondheidszorg	Yes	No	No
Kifid	Yes	No	No
Raad van Arbitrage	Yes	Yes	No
Regulators (AP, ACM, UWV, NZa, Belastingdienst)	Yes	No	No
Personal-injury & FMS guidelines	Yes	No	No
BIG register, Kadaster BAG, KVK trade register	Yes	No	No
European law (ECHR, EUR-Lex, CORDIS, LIT/OpenAlex)	Yes	No	No
ONS (Nedap care)	No	No	Yes, if integration is active
Calculator	Yes	Yes	Yes
Tasks (kanban)	Yes	Yes	Yes
Word review	Yes	Yes	Yes
Research jobs	Yes	No	No
LiDO ECLI positioning map	Yes	No	No
SharePoint documents	Yes, if integration is active	Yes, if integration is active	No

Nuance for LEO lite:

• only Dutch laws and regulations, Case law, and EU law;
• no research jobs, SharePoint toggle, tasks toggle, calculator, or Word-review toggle.

How to read this matrix

LEO

LEO is the broadest legal variant:

• general legislation,
• case law,
• domain sources such as Kifid/SKGZ/disciplinary law/RvA,
• research jobs,
• optional SharePoint.

VERA

VERA is narrower but focused:

• mainly environmental and public-regulatory sources;
• plus Rechtspraak and RvA;
• no EU law, German law, disciplinary law, SKGZ, or Kifid.

ZIA

ZIA is document-first:

• works from your project, personal, and shared documents;
• includes helpers such as Tasks, calculator, and Word review;
• has no public legal source families;
• can optionally connect to ONS (Nedap) for care organizations that use it.

Shared and public knowledge bases

Use them for:

• templates, memos, manuals, and internal policy materials;
• organization-wide source sets next to your matter context;
• public knowledge bases linked by your organization.

What the toggles do:

• on = the assistant may search that KB;
• off = the assistant ignores that KB for new answers.

Knowledge library and admin roles

The Knowledge page usually has two management levels:

Temporary browser-level selection

Every user can decide per knowledge base:

• on or off for the current browser/device;
• fewer sources for less noise;
• more sources when broader retrieval is useful.

Organization-wide public KB linking

In the Knowledge library, usually only OWNER and ADMIN can:

• link public knowledge bases to the organization;
• unlink them again.

Members without that role can browse the catalog but not change it.

Practical effect:

• linked public KBs then appear in the normal knowledge-base list;
• unlinked public KBs disappear there for everyone.

Non-public knowledge bases

Some public knowledge bases are marked as non-public. These are sources that contain licensed or proprietary content, such as standard conditions from industry organizations.

Why the distinction?

Non-public sources contain material that may require a license or subscription. Your organization is responsible for verifying that it holds the required rights before enabling these sources. PrudAI has included a supplement for this in the terms and conditions.

How it works

• Non-public knowledge bases are recognizable by an amber “Non-public” badge in the knowledge library.
• When linking a non-public knowledge base, or when enabling it, a confirmation dialog appears. It explains that your organization must have valid access rights and that the terms must be accepted.
• The “Enable all sources” action deliberately skips non-public knowledge bases: they stay off by default and must be confirmed one by one.
• Unlinking and re-linking will prompt for confirmation again.

Who can link non-public knowledge bases?

Only users with the OWNER or ADMIN role can link or unlink public knowledge bases. Regular members can browse the catalog but cannot make changes.

Organization-wide policy switches (admin mode)

Owners and admins see extra switches on the Knowledge page to disable sources organization-wide. A source disabled this way is unavailable in chat for everyone in the organization, regardless of their own preferences. Use this to temporarily block a source during an audit or to hide a legal domain that your organization does not cover.

Creating organizational knowledge bases

If your environment allows it, OWNER and ADMIN users can continue into the RAG Dashboard to create an organizational knowledge base.

Use that for:

• internal templates;
• guidelines;
• memos;
• other shared document collections.

More: Account & RAG dashboards.

SharePoint

If SharePoint is enabled in your environment:

• a dedicated SharePoint tool category appears;
• the assistant may use linked SharePoint documents;
• availability still depends on your organization’s integration status.

More: SharePoint.

How this affects chat

Your Knowledge choices act as a practical allowlist for new chat answers.

Practically:

• if you disable a source family, the assistant stops using it for new answers;
• if you disable a knowledge base, it will no longer be searched;
• in project chat, project documents still remain the main context.

Practical settings by task

Matter analysis on your own documents

Turn on:

• project documents;
• optionally Tasks.

Often leave off:

• extra external sources that add noise.

Source-grounded legal answer

For LEO:

• legislation,
• case law,
• relevant domain sources.

For VERA:

• Omgevingswet,
• IPLO,
• official publications,
• plus Rechtspraak/RvA where needed.

For ZIA:

• work from your own document layer; there are no public legal toggles.

Writing in Word

Turn on:

• relevant knowledge bases;
• Word review if you use the Word add-in.

Verifiability still comes first

Even with the right knowledge selection:

• ask for citations;
• open source drawers;
• verify critical articles, cases, and amounts yourself.