Write and govern organizational documents

Organizational documents keep policy or procedure text alongside ownership, review decisions, references, and lifecycle records. Reading or changing a document requires project access and active Platform and Autopilot Organizational Documents licenses. Changes require a project Contributor, Admin, or Owner role; Readers can read, follow discussion, and download an export. See access and licenses if the document is unavailable.

Create the documentCopy Anchor Link

1. Open the Projects Hub, select the project, and choose New artifact, then Organizational document.
2. Enter Document title, choose Document type, Classification, and Review frequency, and add the purpose.
3. Choose Create document. Sorena opens its workspace, where you can add sections and governance details.

If creation fails, correct any highlighted fields and try again. If you cancel after entering details, choose Keep editing to retain them or Discard details to leave without saving.

Add and organize sectionsCopy Anchor Link

1. Choose Add section in the section rail, enter the heading details, and choose Add section to save.
2. For nested content, open a section's action menu and choose Add subsection. Repeat within a subsection to build a deeper outline, up to the depth allowed by the control.
3. Select a section, open its content editor, and write the Markdown text. Check the preview, then choose Save changes.
4. Use the section's menu to rename it or Move up and Move down. Expand parent sections to reach their children.

Search and refine the outline to find a section. If a move is unavailable, read its explanation; a filtered outline or the section's position can limit the action.

Clear content removes a section's saved body while retaining the section. Delete section permanently removes the section and its content, including nested sections. If Sorena asks again because the section contains children, Delete section and contents confirms removal of every descendant. Check the branch before proceeding.

If content cannot be saved, the editor keeps your draft and shows the failure beside the action. Correct the problem and retry. Cancel leaves the editor; when prompted, keep editing or discard the unsaved changes deliberately.

Assign reviewers and record decisionsCopy Anchor Link

Select a section and use its reviewer control to Assign a reviewer. Search project members, select a person, and confirm the assignment. A reader can be assigned but may need wider access to record a verdict; assignment does not grant that access. Use Load the rest if the member list is incomplete.

To record a reviewer's verdict, select the section, choose Manage reviewers, and change the review status beside the person's name. Wait for the update to finish and check the saved status. Contributor access is required for these changes, even when the assigned person is a Reader. Reviewer controls remain available on locked documents when your role permits them.

Choose Show past reviewers to inspect removed reviewers and their last decisions. To end an assignment, choose Remove, add an optional reason, and confirm Remove reviewer. The section leaves their review queue, while their earlier contributions remain in the record. If removal fails, the panel stays open with the error so you can retry.

Open Review in the rail. Waiting on me opens your assigned sections and highlights those awaiting your review; Everyone shows the wider queue and reviewer roster. For Readers, the personal scope is labelled Assigned to me and allows inspection; a Contributor must record the verdict. Select a row to read the section before acting. Clear filters if an expected section is missing. When a section has active reviewers, its queue Decision says Set by reviewers. Update reviewer verdicts from the section's reviewer controls.

Keep each reviewer's verdict, the section decision, and the document's overall lifecycle distinct. Where manual section-decision controls are available, they offer Approve, Ask for changes, and Decline. Asking for changes or declining requires confirmation. Changing an approved section to another decision withdraws its recorded approver and approval date. Add a comment explaining what must change so the author can act on it.

Use the section discussion and reviewer-management controls to follow comments, update assignments, and record the review actions available to your role. A document lock protects text and details; it does not by itself remove reviewer and discussion tools.

Maintain details and supporting recordsCopy Anchor Link

Choose View details to inspect configuration or Edit details to change it. Set the title and identity, ownership, classification, review timing, effective date, and retention or disposition fields that apply. Supersedes document links an earlier organizational document in the same project. Choose Save configuration after reviewing the changes.

If another change or lock prevents a save, use Refresh and reconcile when offered. Sorena loads the latest configuration and retains your unsaved values for review. Check the resulting fields before saving again; the message may report that identity fields were already saved.

Open More document actions for Stakeholders, References, Control mappings, and Activity. These records identify the people responsible, supporting documents or external sources, linked framework controls, and governance history. Use the add, edit, or remove controls within the relevant record panel when your role allows it. Review removal confirmations before changing those links.

To add a reference, open References, choose Add reference, and select Relationship. Choose Parent policy, Linked procedure, or Related to link an organizational document, or External to enter an outside source. Add notes and choose Save reference. Use Edit reference to change the relationship or target later.

With an additional Research Copilot license, choose Ask Copilot to discuss the document with its context attached. Check any resulting content and governance details before recording approval.

Change the lifecycle and understand locksCopy Anchor Link

Use the document's lifecycle control to choose an available destination. Review the consequence screen before confirming. The lifecycle includes Draft, In review, Approved, Published, Superseded, and Retired.

Approving records approval evidence and locks the details and section text. Publishing marks the document as published and protects it against edits. Superseded marks it as replaced; retired takes it out of use while keeping it for reference. Locking transitions require acknowledgement. Supply signature evidence when approving if requested.

Returning an approved, published, superseded, or retired document to Draft releases the lifecycle lock but deletes the approval record, including its approver, date, and signature evidence. That record is not restored by moving forward again. Leaving Retired also clears its retirement date. To preserve a published version's approval, create its replacement and mark the old document superseded instead.

For a manual lock, ask a project admin to review it. Read the lock notice before trying to edit. Reading and exporting remain available. When a scheduled review is complete, use the review-completion action when offered; it schedules the next review date.

Export or permanently deleteCopy Anchor Link

Choose Export, then Download Markdown for a copy on your device. Contributors can also save Markdown to the project drive: choose a destination, check the collision choice, and save. Review the Saved to the project drive result and open the saved file when needed.

To delete the document, choose Delete document from More document actions. Wait for the deletion preview and inspect the related records it lists: sections, stakeholders, references, control mappings, requirement links, and activity events can be removed with the document. Enter the displayed document name exactly, then choose Delete document permanently. Deletion stays unavailable if the preview fails or is blocked. Keep or export the document instead while you resolve the reported reason.