Every version, approved by the people you choose.
Request approval of a specific version from 1 to 20 people. They approve or reject from their inbox, with a comment — and while the request is open, that version can’t be published or sent for signature.
You choose the approvers. NexDok handles the rest.
Any active workspace member can be an approver, whatever their role. Requesting approval takes the Editor role; publishing afterwards takes Admin or Owner.
From a version under review to a publishable version — with the trail intact.
An editor requests approval of a specific version from 1 to 20 workspace members, with a note.
Every approver gets an email and sees it in “Needs My Action”: Approve or Reject, with a comment.
The request is approved only when everyone approves. One rejection closes it as “Rejected”.
While it’s open, no one publishes v4 or sends it for signature. Once closed, an admin can publish it.
Decide as each approver. See when publishing is released.
“Clínica Andina” · SOP-014 Sterile Field Preparation · v4 · 3 approvers.
Approved · Oct 21 10:12
Pending
Pending
Approved · Oct 21 10:12
Approved · Oct 21 15:40
Pending · the outcome depends on her
Rejected
Rejected · Ana receives “Approval rejected: SOP-014…”
Blocked: an approval request is pending for this version.
Cancelled · pending decisions become “Voided”
“Approval cancelled” email to approvers and requester
Sample data. Requesting approval requires the Editor role.
While it’s being decided, that version isn’t published.
The request is about v4. If someone uploads v5, v4’s approval doesn’t change and v5 needs its own.
All approvers decide at once, in no order. Two simultaneous votes are recorded one after the other, with no conflicts.
With the request open, publishing v4 returns an approval-pending notice.
No signature request with an open approval, and no approval with an active signature.
Every request, decision and cancellation is kept with who and when, and the requester and approvers are notified by email.
An approval is a decision by people, not an automatic formality.
Publishing doesn’t require approval. What an open request does is hold publishing back.
No automatic approvals by type or collection: every request names its approvers.
Publishing is still an explicit act by an admin or owner.
No automatic deadlines or reminders: each approver decides from their inbox.
Everything waiting for your decision, in one place.
“Needs My Action” shows only what’s waiting for you, with filters by state, type and collection and each request’s progress. “Submitted” collects what you requested.
Approve the version. Then sign it with SignDok.
Once the request closes, the version can be published or sent for signature. Every step stays on the same document.
Approved · 3/3 · Oct 22 2026
Signed · new version Signed (v5)
1 to 20 active workspace members, of any role.
Editor role or higher.
Admin or Owner role.
Email on request, on close and on cancel.
Which document needs approval this week?
Tell us what you review and who approves it. We’ll show it to you in NexDok.