Maintain organizational document governance
Record ownership, references, applicability, requirement links, and control mappings.
Open the Projects Hub, choose the project, and open its organizational document. Reading requires project access and active Platform and Autopilot Organizational Documents licenses. Changes require project Contributor, Admin, or Owner access. See access and licenses if a control is unavailable.
Maintain details and supporting records
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.
Record the accountable owner
To record the accountable owner, open Stakeholders, choose Add stakeholder, and set Role to Owner. Choose Person and select a project member or another person in the workspace, Business unit and select the unit, or Other contact and enter a display name and valid contact email. Choose Add stakeholder and check the saved entry. This document-owner record is separate from your project role.
Add references
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.
Record applicability and requirement links
Use Applicability on the document or a selected section to declare it Not applicable. Enter Your organization's reason, then choose Save decision and check the saved reason. Use Edit reason to correct a local declaration. This records why the content is outside your organization's scope; it leaves the text and lifecycle unchanged.
A section can inherit a Not applicable declaration from the document or an ancestor section. Choosing Applicable clears only the current document's or section's own declaration. It does not override an ancestor, so a section may remain Not applicable after you clear its local declaration. Locked documents cannot change applicability; read the lock message before proceeding. Management-system requirement applicability is a separate decision.
Section requirement mappings require active Integrated Management Systems and Autopilot Organizational Documents licenses in addition to Platform access. To connect a section to a management-system requirement, open the section's Requirements addressed area and choose Add. Select a Declared framework, choose a current requirement from that framework, and choose Add requirement. Only live requirements from a framework declared in this workspace can be selected. Use View requirements and the page controls to inspect existing links.
Removing a manual section requirement removes that link. Removing a template-provided mapping suppresses that mapping for the section. Neither action changes the requirement's applicability or establishes compliance. Review the confirmation before removing a link; locked documents cannot change these mappings.
Maintain control mappings
For a manual document control reference, open More document actions > Control mappings, choose the add action, enter both Framework and Control reference, and choose Save mapping. Control title and Notes provide optional context. These manual references are separate from controls derived from section requirement links; use the section's Requirements addressed controls to maintain those links.
Discuss the document with Copilot
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. Follow Manage the document lifecycle when the document is ready for approval or publication.