Skip to content

Guidance

Guidance injects system-prompt text into requests — for example, a house system prompt targeted at a specific group. There is no standalone Guidance surface in the shipped admin console. The legacy per-group model_guidance domain was retired: its objects were migrated into the org’s pinned Guidance pack, and guidance is now authored as inject-guidance chain entries under Security & DLP → Policy Packs / Chain.

Author guidance as an inject-guidance entry in the pinned Guidance pack: open Security & DLP → Policy Packs, edit the Guidance pack, and add an entry with the system prompt to inject (optionally targeted at a group). The Chain panel controls where the Guidance pack sits relative to your DLP packs. See those pages for the current step-by-step.

The former standalone Guidance panel in the admin console, listing groups with a preview of their system prompt and an Enabled badge.
Historical capture — the former standalone System → Guidance surface, now folded into the Guidance pack on the ChainCitadel synthetic data on a non-production Arbitex demo instance. Never client data.

The legacy /api/v1/admin/models-routing/model-guidance/{set,list} routes and the model_guidance config domain are retired. Guidance entries now live on the Guidance policy pack, so they are authored through the policy-pack authoring seam — see Policy Packs → API equivalent and Chain for the current calls and the inject-guidance entry shape.

Guidance authoring is available on every plan.

On a Hybrid Outpost, guidance packs are authored and synced the same as on the cloud admin console, scoped to that deployment. In an air-gapped deployment, authoring works fully offline.

  • Policy Packs — where the Guidance pack’s inject-guidance entries are composed.
  • Chain — where the pinned Guidance pack is ordered relative to your DLP packs.
  • Groups & roles — where the groups a guidance entry can target are created and managed.