Skip to main content

Prompt Store and Enforcement

V2 console

This card lives in Policy Engine > LLM Gateway at web.quilr.ai/policy. Edits join the shared draft and take effect once you review and publish a revision.

Require matching requests to use an approved system prompt from the Prompt Store. The prompts themselves are managed in the Prompt Store.

Prompt Store and Enforcement card collapsed with Configure, the Prompt Store button and the Require store prompt summary row

The Prompt Store button on the card opens the store, where you create and edit the prompts that requests reference.

Sections​

SectionWhat it doesApplies onEmpty state
Require store promptThe system prompt must include a Prompt Store reference. Text before or after the reference is allowed. Require.chat, responses, vertexNot required.

Prompt Store and Enforcement card expanded with the Require store prompt section and three per-application rows set to Required

Configuration settings​

Controls, Reads as, Severity and More options rows of the New Prompt Store and Enforcement configuration dialog

SettingOptionsDefaultNotes
Applies toEveryone, People, Smart group, Application, App tag, Requested model, Provider, API surface, Environment, Prompt complexity, Prompt text, Tool, Source network, Except...EveryoneOr pick an application directly.
Require store promptLeave as is, Required, Not requiredRequiredNot required exempts a narrower scope from a broader requirement.
SeverityNot set to Very criticalNot setReported only.

Example​

require_approved_system_promptsrequest

runs on requestpriority 600

WhenRequest metadata . environmentisproduction
Then
Require Prompt Store system promptrequired

Production traffic must use a reviewed system prompt; development traffic stays free to experiment.

Scoping and precedence​

Highest-priority configuration wins. New configurations start at 500.

Legacy app setting​

The app's Prompt Store settings. See Prompt Store.