Variables
Store values such as your legal name, the incident hotline or a retention period once, and mention them in policies, so a change updates every document.
A variable is a value with a name, for example Access review cadence with the value Quarterly for privileged access, semi-annually otherwise. You mention it in policies and records with :. The policy PDF prints the value. When the value changes, you edit the variable once, and every policy that mentions it prints the new value.
To import, archive or delete variables, see Collections. Scripts and integrations: see API below.
Add a variable
- Open Collections, then Variables, and choose Add variable.
- Enter a Name that says what the value is, for example
Access review cadence. - Enter the Value, for example
Quarterly for privileged access, semi-annually otherwise. Write it so it reads well inside a sentence. - Choose Create.
Good candidates are values that appear in several policies or may change: legal name, register number, hotline, retention periods, patch deadlines, password rules.
A policy template adds the variables it uses. Its proposed value stands in square brackets, and the list marks it To confirm until you change it and remove the brackets. A policy that mentions it can't be approved before then.
Use it in a policy
- Open the policy in the editor and click where the value belongs.
- Type
:and the first letters of the variable name. Choose the variable. - Choose Save.
In the editor, the mention shows the variable's name. Click it to see the value.


Change a value everywhere
- Open Variables and open the variable.
- Click the Value on the Detail tab, or choose Edit, and enter the new value.
- Save.
Every mention of the variable now has the new value. Its card shows it, and PDFs of a policy's latest state print it. A version that was already approved keeps the value it was approved with. To record the new value in a published policy, approve the policy again: the approval dialog lists what changed.
Reference
| Field | Required | Notes |
|---|---|---|
| Name | yes | 2 to 255 characters. |
| Value | yes | Plain text. |
| Slug | yes | Made from the name. See Collections. |
Every member and auditor can read variables. Do not store passwords or other secrets in them.
CSV columns
The template from Download CSV template has these columns. Leave slug empty to make it from the name.
slug,name,value
access-review-cadence,Access review cadence,"Quarterly for privileged access, semi-annually otherwise"API
The calls are the same for all collections; see the Collections API. The path is /variables/.
| Field | Type | Required |
|---|---|---|
organizationId | string | on create |
name | string, 2 to 255 characters | yes |
slug | string, lowercase with hyphens | yes |
value | string | yes |
{
"organizationId": "<organization id>",
"name": "Access review cadence",
"slug": "access-review-cadence",
"value": "Quarterly for privileged access, semi-annually otherwise"
}How is this guide?
Schedules
Define your recurring cycles once, such as "every quarter", and use them for policy reviews, evidence reviews, trainings, vendor assessments and automated checks.
Risks
Keep a risk register an auditor can follow. Rate each risk against your own criteria, decide its treatment, have the owner accept what remains, and review it on a schedule.