Metadata
The metadata node carries template bookkeeping — who authored the policy, its version, timestamps and searchable tags. It is stored with the policy set but not applied to sessions.
Editor Advanced → Metadata JSON · JSON
metadataProperties
| Property | Type | Notes |
|---|---|---|
author | string | Who created or owns the template. |
version | string | Free-form version label (distinct from the top-level numeric revision). |
created | string | ISO 8601 date-time. |
updated | string | ISO 8601 date-time. |
tags | string[] | Searchable labels, e.g. finance, contractors, high-security. |
Sample
"metadata": {
"author": "Security Team",
"version": "2.0",
"created": "2026-01-15T09:00:00Z",
"updated": "2026-06-01T14:30:00Z",
"tags": ["finance", "restricted", "audited"]
}
Note
Because metadata is not applied to sessions, editing it never changes runtime behaviour. Use tags to keep a growing library of policy sets organised and searchable, and keep updated current as a change marker. The numeric revision field on the policy set itself (see Policy Sets & the Editor) is what drives built-in upgrade prompts.