Safety and guardrails

Safety is a read-only record of the guardrail decisions a knowledge base made over the last 30 days: questions blocked as prompt injection, passages dropped, answers withheld. The dials that decide how readily it answers live on Settings.

What you'll need

• The Knowledge Base app in your top bar.
• This permission: Knowledge Base · Analytics - Read.
• A knowledge base people have been asking. Changing a strictness level on Settings needs Knowledge Base · Setup - Update.

If Knowledge Base isn't in your top bar, your role can't view it or your plan doesn't include it. Ask a workspace administrator, or see Permissions and module visibility.

Steps

1. Open the feed

   Open the knowledge base and select Safety in its menu.

2. Read the four counts

   The cards are Prompt-injection blocked, PII redactions, Low-groundedness suppressed and Abstentions. They count the 30 days' decisions whatever the filter below says; past 200 decisions a count ends in a plus sign.

   

   The Safety section of Northwind Supplier Handbook: Prompt-injection blocked 1, PII redactions 0, Low-groundedness suppressed 0, Abstentions 1, and two decisions by Alex Morgan, an Abstention and an Injection blocked.

   Enlarge

3. Read a decision

   Each row gives the Time, the User who asked with the start of their question, the Event and a Detail. Event is Injection blocked, Passage filtered, PII redacted, Low groundedness or Abstention, and Event (All) filters by it. Detail gives the reason, with scores where there are any, and the document a blocked passage came from. It never shows the passage text.

4. Follow one to its question

   Select the arrow under Trace (Open trace) to open the retrieval trace for that question.

5. Change how strict it is

   Nothing here is a switch. On Settings, set Relevance strictness and Groundedness strictness to Low (Lenient), Medium or High (Strict), then select Save Changes. Stricter means more questions go unanswered; more lenient means more answers on weaker evidence.

What success looks like

• The cards and the table list this knowledge base's decisions from the last 30 days.
• Open trace lands on the question behind a decision.
• After a strictness change, Settings saved successfully! appears and the next question uses the new level. Nothing is re-indexed.

What the feed does not prove

An empty feed is not a clean bill of health: it only means no decisions were logged in the window, which is fixed at 30 days with no date filter. Passage filtered means a passage was blocked but the answer still went out from the rest. PII redactions stays at zero while output PII redaction is off, and Settings has no way to switch it on yet.

If something goes wrong

Symptom	Likely cause	What to do
The table reads Nothing here.	Nothing was logged for this knowledge base in the last 30 days.	Expect this on a quiet knowledge base.
No guardrail decisions match this filter.	Event (All) is set to an event that has not happened.	Set it back to Event (All).
People report too many unanswered questions.	Groundedness strictness or Relevance strictness is stricter than the content supports.	Lower one level on Settings. Chat names the gate that stopped it, such as Stopped at: Groundedness gate.
A row has no Open trace arrow.	That decision is not linked to a question.	Find the question on Retrieval trace by its time.
Safety is missing from the menu.	Your role has no Knowledge Base · Analytics permission.	Ask a workspace administrator.

Next

• Knowledge base settings - where the strictness levels are saved.
• Reading a retrieval trace - what a single question retrieved and why.
• Who can see a knowledge base - who can reach the knowledge base and its documents.