{{variable_name}} placeholders that are automatically replaced when rendering a policy preview or generating a PDF. Missing values appear as highlighted [VARIABLE NAME] markers in draft previews so you can easily identify what needs attention.
How Variables Work
1
Auto-Resolution
When you preview or download a policy, LowerPlane fetches your organization details, security roles, and active integrations to fill in placeholders automatically.
2
Manual Overrides
Any auto-resolved value can be overridden per-policy via the policy editor metadata. Overrides take precedence over auto-resolved values.
3
Missing Value Handling
Unresolved placeholders appear as
[VARIABLE NAME] highlighted in yellow during draft preview. In approved documents and PDFs, they appear as plain text without highlighting.Organization Variables
These are resolved from your organization settings (Settings page).Framework & Integration Variables
Date & Version Variables
These are set automatically and always have values.Security & Compliance Defaults
These always have hardcoded defaults and will never show as missing. Override them per-policy if your organization uses different values.Security Role Variables
These are resolved from your Security Roles assignments (Personnel > Security Roles). If a role is assigned to a person, their full name is used. If not assigned, the variable shows as a highlighted placeholder.Custom security roles are also supported. Any role added to Security Roles automatically generates a variable using the pattern: role name in lowercase with spaces replaced by underscores, followed by
_name. For example, Network Engineer becomes {{network_engineer_name}}.Overriding Variables Per-Policy
You can override any auto-resolved variable for a specific policy:- Open the policy in the editor
- Go to Policy Settings or Metadata
- Add custom placeholder values
- These overrides take precedence over the auto-resolved defaults