The Description holds the reader-facing policy text. Use it to explain the purpose, scope and requirements at the level where they belong; categories, subcategories and controls also have their own descriptions.
Edit the description
- Open the policy and select the intended element in Structure.
- Choose Edit details beside Description.
- Wait for the editor to become ready.
- Review the display code and name, then edit the description.
- Choose Save changes and verify the resulting content.
Use headings to separate topics, lists for parallel requirements and links for maintained references. Keep the hierarchy readable and avoid repeating the complete policy in every child control.
Write requirements people can follow
State who must do what, in which circumstances and how exceptions are handled. Give control descriptions enough operational context to distinguish a policy requirement from a record of implementation progress.
Keep assessment justifications and internal discussion in their corresponding fields. Readers who can see policy content may not have access to the confidential assessment layer.
Collaborate and resolve drafts
Supported text fields show collaborative changes when the connection and access permit editing. A connecting or read-only editor is not ready for new input. Check save feedback rather than relying on presence as proof that text has been committed.
Closing or cancelling the editor can retain a pending draft. Use Save changes or Discard in the page bar to resolve it before moving elsewhere. Approved, in-review and historical versions require the appropriate new or current draft for further content work.