Guardrails (portal)
/guardrails is the control-plane UI for content filters. A garden card that is not on a policy attached to a key does nothing.
Full walkthrough: Guardrails overview.
Platform admins get New policy in the page header. It opens the Create policy dialog from any tab (see Policies).
Tabs
| Tab | Purpose |
|---|---|
| Garden | Hub-style catalog: search, filters, tagged cards, multi-select (Garden catalog) |
| Guardrails | Directory of configured instances; add custom scripts or vendor scanners |
| Policies | Policy directory; open the builder to add steps and attach the policy to a scope |
| Monitor | Evaluations, blocks, pass rate and latency (Playground and Monitor) |
| Playground | Dry-run a policy against sample prompts |
Badges show the number of Garden cards, configured guardrails and policies. The selected tab is kept in the URL (?tab=).
Stat cards: Configured (guardrail instances), Policies (how many run in order vs all at once), Attachments, Enabled (and how many are off) and Requests checked (requests a guardrail checked over the last 7 days of the range, with a daily sparkline; non-admins see only their own requests).
Role restrictions
Everyone can browse. Adding garden cards, creating policies, and creating custom/vendor guardrails is a platform-admin write.