As part of the header section, the Yonder Content Manager depicts the current status of the document (1) and allows selected users to trigger context-specific actions related to revisions and approval procedures (2).

The currently available action (2) that can be triggered depends on the current status of the document and your organization's specific workflow. Possible actions include:

• Request Approval: Typically available when a new document was created, allowing selected users to ask for the initial approval once the document is ready. Clicking on the “Request Approval” button triggers the next step in the document-specific approval workflow that allows the corresponding stakeholder(s) to approve the newly created document via the Yonder Reader Online.
• New Revision: Allows selected users to open a new revision for the document. Remark: Doing so automatically transfers change requests from the “Waitlist” to “Active”, if applicable.
• Close / Reject Revision: Allows selected users to formally close a document revision. Remark: Only possible if all of the issued change requests for the document have been resolved. Closing a revision automatically triggers all of the module- or document-specific notifications, thereby explicitly informing users about those changes (via the Yonder Reader My Tasks section).

General remark / reminder: Keep in mind that all of the revision and approval steps are tracked in an irreversible compliance and audit trail. It's therefore reasonable to apply caution before triggering any of the above-mentioned actions.