> For the complete documentation index, see [llms.txt](https://docs.nexos.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexos.ai/workspace/settings/organization/guardrails.md). # Guardrails **How guardrails work** * **Company guardrail** – Applied to all models by default, unless a custom or excluded guardrail is set. * **Custom guardrail** – Applies to specific models and has higher priority than the company guardrail. * **Excluded models** – Models in the exclusion list are not affected by any guardrail. *Priority order:* Excluded → Custom → Company {% stepper %} {% step %} ### Name your guardrail Use descriptive names that indicate purpose (e.g., "PII-Protection-Customer-Data" or "Content-Filter-Internal-Use") {% endstep %} {% step %} ### Add validators Select from the validators library based on your security requirements. \ [Click here for more info on Regex](#regex-match-validator). \ [Click here for more info on No PII](#no-pii-validator). {% endstep %} {% step %} ### Configure each validator Set specific parameters for detection and response behavior {% endstep %} {% step %} ### Test configuration Validate settings before deployment. Note: you can edit guardrails anytime. {% endstep %} {% endstepper %} ### Regex match validator Controls content based on pattern matching. Configure as follows:

Configuration	Meaning
Name	Assign a descriptive identifier for the rule
When Regex matches	Search: looks for pattern existence in content Extraction: identifies and extracts specific pattern matches
Regex rule	Define the pattern to match (e.g., credit card numbers, internal codes, sensitive identifiers)
Trigger on	Input: validates user prompts and requests Output: validates AI model responses Both: validates both input and output
Guardrail behavior	Fix: automatically removes or replaces sensitive data Filter: removes sensitive content with generic replacement Exception: blocks the request entirely and returns error

### No PII Validator Detects and anonymizes Personally Identifiable Information. Configuration includes:

Configuration	Meaning
Name	Assign identifier for the PII protection rule
Entities	Select specific PII types to detect (credit card numbers, crypto addresses, etc)
Trigger on	Choose Input, Output, or Both
Guardrail behavior	Fix: Replaces PII with generic placeholders Exception: Blocks content containing PII

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nexos.ai/workspace/settings/organization/guardrails.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.