Release notes for version 3.1.0.0
Version 3.1.0.0 extends DocuKlaud along three axes: signing and approval outside the organization, finer document governance, and operations. It is a backward-compatible update (with no breaking changes to what already exists).
Unless otherwise stated, these improvements are available on all plans; features marked with PRO plan require a PRO plan subscription.
What's new and improvements
- External approvals: add approvers who do not belong to your organization within a workflow, without Microsoft 365 licenses. They receive by email a link scoped to the task, and their approval or rejection has the same traceability as an internal approver. See Approval Workflows · Electronic Signature.
- DocuSign integration PRO plan: delegate a workflow's signing stage to DocuSign from within the process itself, with status tracking per recipient (sent / viewed / signed / rejected). Requires a customer DocuSign account. See DocuSign Integration.
- Change Requests: formalize and control requests to modify already published documents. The request is linked to the current version and is resolved by the document owner, leaving a record of the decision. See Change Requests.
- Main and secondary folder approvers: define approvers at the folder level (main and subfolder); documents inherit them automatically, and the subfolder can override the main folder when the area requires a different owner. See Folder Management · Approval Workflows.
- Document type and workflow restrictions in subfolders: each subfolder can limit which document types are allowed and which workflows can run within it, reducing classification and approval-circuit errors. See Folder Management.
- Corporate email branding: personalize system notifications (task assignments, reminders, approvals, rejections, and publications) with your organization's logo, colors, and header/footer, with a preview before applying. See Email Branding.
- Stuck workflows screen: a new operational view that lists processes that are stopped or in an inconsistent state, so the administrator can identify the cause and take action. See Stuck Workflows.
Update
The update is backward-compatible: all workflows, documents, versions, and tasks created in version 3.0.0.0 keep operating without conversion. The only subsequent action is deploying the list required for Change Requests, which DocuKlaud detects automatically and guides a site administrator to complete in a single step.