Lyron
Microsoft 365

Automated Document Approvals in SharePoint

Every document follows a path it has to take: draft, review, approval, archive. Who approved it, and when, is attached to the version – and the rejected draft stays on the record instead of quietly disappearing.

Context

Why nobody knows which version currently counts

A document leaves SharePoint the moment it is attached to an email. From then on it exists in five mailboxes, three of them outside the company, and it is called contract_final_v3_JK_new.docx. The library dutifully keeps counting its versions in the meantime – except the actual work happened somewhere else. Two weeks later nobody can say which text the client received.

The real difficulty sits deeper. An approval is not a property of the file but a statement by a person about a particular text at a particular moment. Most filing systems store only the outcome: a tick in a column. If the file changes afterwards, the tick stays where it is. And whatever was rejected is silently overwritten – precisely the information that would later explain why a clause reads the way it does.

Then there is visibility. A draft should not be readable by everyone, while the approved version should. SharePoint separates the two cleanly through major and minor versions with draft item security – but only if the library, the content types and the permissions are right before the first workflow exists. So what we build here is less a process than a set of decisions: which document type takes which path, who is accountable at each stage, what happens on a rejection, and when the document is finally closed. Power Automate is the smaller part of the job.

Use cases

Which documents need a path

We start with the document type that occurs most often and has the clearest approver. Further types later share the same library logic.

Most common starting point

Contracts and quotes

The most common starting point: a draft goes to legal or the managing director, and only the approved major version may leave the building.

ContractQuoteAmendmentFramework agreement

Work and inspection instructions

Documents with a validity period: whoever reads one has to be able to trust that it is the version currently in force.

ProcedureInspection planForm

Technical documentation

Drawings and data sheets with a revision status – what is used on site should be the approved revision, not the last one printed.

RevisionData sheetDrawing

Sales and marketing material

Approved by marketing and, where needed, by legal. Expired price lists disappear from the library on their own.

Price listBrochurePresentation

HR documents

Works agreements, contract changes and references: a narrow readership, a fixed retention period, one clear approver.

ReferenceContract changeRetention

Evidence for audits

Quality manual, ISO documentation, customer audit: what gets examined is not the current file but who approved what and when.

ISO 9001Customer auditInspection record
Example

One document, seven entries, one valid version

The life cycle of a maintenance agreement: the draft that was rejected, and the stamp on the version that counts.

Maintenance-Agreement_Sample-Ltd.docx Contracts library · content type Contract · retention 10 years
  1. 1Draft
  2. 2Review
  3. 3Approval
  4. 4Archive
  1. 0.1

    DraftM. Keller · 3 Mar, 09:12

    Created from the template. Client, project and term are mandatory columns on the file.

  2. 0.2

    DraftM. Keller · 4 Mar, 16:40

    2026 rates and service window added. Visible to the author and the approver only.

  3. 1.0

    Waiting for reviewwith S. Adam, Legal · 5 Mar, 08:05

    Publishing triggers the approval: a card in Teams, three working days to respond.

  4. 1.0

    RejectedS. Adam · 5 Mar, 11:20

    Liability in clause 7 points to an annex that was deleted. Please correct.

  5. 1.1

    DraftM. Keller · 6 Mar, 10:02

    Clause 7 rewritten, annex 2 attached. The comment above stays with version 1.0.

  6. 2.0

    ApprovedS. Adam · 9 Mar, 14:07

    The valid major version, visible to every reader, file set to read-only.

  7. 2.0

    Archive scheduledautomatic · 9 Mar 2028

    Review reminder to the accountable role, then the retention label takes over.

  • draft, author and approver only
  • waiting for a person
  • rejected, kept on the record
  • approved and visible to all

The card on the right is the point: it belongs to version 2.0, not to the file. If the document is edited later, the stamp still refers to 2.0 – and the new text is a draft again.

Illustrative view of a SharePoint library with content approval. Names, deadlines and record IDs are invented.

How it works

From first draft to a locked archive record

  • Define the document type and its mandatory fields

    Each document type gets a content type with the columns the path will need later: client, project, validity, accountable role. Without those fields no workflow can decide who has to review.

  • Separate drafts from the version in force

    We switch on major and minor versions with content approval and set draft item security to author and approver. From then on everyone else sees only the most recently approved major version.

  • Ask for approval where people already work

    Publishing starts a flow in Power Automate that posts a card in Teams: file preview, document type, deadline, buttons for approve and reject. Sequential or parallel, whichever your rule says.

  • Make a rejection say why

    The flow does not accept a rejection without text. The comment is written to the version, the author receives it in Teams, and the rejected draft keeps its number and status in the history.

  • Stamp, lock and diarise

    On approval the flow writes person, timestamp and record ID into the columns of the major version, sets the file to read-only and applies the retention label. On the review date it reminds the accountable role.

Impact

What changes day to day

Today

  • The current text is called final_v3_new.docx
  • The approval sits in an email, not on the document
  • Drafts are visible to everyone in the library
  • Rejected versions get overwritten and vanish
  • Before an audit the history is pieced back together

With a managed life cycle

  • One file, one history, one recognisably valid version
  • Approver, timestamp and comment belong to the version
  • Drafts are seen by the author and the approver only
  • The rejected version stays, with the reason attached
  • The history is the evidence, not a reconstruction of it
Limits

What an approval path will not do for you

Four points we settle before quoting – two of them can lead us to advise against this product:

  • A workflow does not tidy up a library that grew by itself. If documents sit in forty folders, with inheritance broken in a dozen places and no content types anywhere, the path simply inherits that mess. Sorting it out is a separate step beforehand, sometimes a project of its own. We tell you in the intro call which of the two situations you are in.
  • With few approvals this does not pay off. If one or two documents a month need signing off, an email and a short call are faster and cheaper than any automation. The product earns its keep where several document types run through the same roles on a regular basis. Without that volume we will say no, even if you have already made up your mind.
  • An approval is not a signature. It records an internal decision with person, timestamp and version, but it is not a qualified electronic signature under the eIDAS regulation. Where written form is required, we attach a signature service at the end of the path. That works, but it costs additional licences and is a decision of its own.
  • The approver remains the bottleneck. Deadlines, reminders, escalation and a named deputy help noticeably. But if the managing director does not open Teams for two weeks, the document is not approved for two weeks. Automation makes the delay visible and addressable; it does not remove it.
Systems

Runs inside your Microsoft 365

SharePoint OnlineMicrosoft TeamsPower AutomateOutlookWord and ExcelMicrosoft PurviewEntra IDPower Apps
Scope and price

Scope and price

The entry price covers one library with one document type and one approval path. What moves the price, we say before the quote.

from €1,900 one-off
  • One document library with content type and mandatory fields
  • Major and minor versions with draft item security
  • One approval path with up to two stages and a deputy
  • Approve and reject as a card in Microsoft Teams
  • Approval stamp: person, timestamp, comment, record ID
  • Retention label and a reminder for the review date
  • Documentation, handover session and 30 days of support

What increases the price

  • Several document types with different paths
  • Approvers from a matrix rather than one fixed person, by value or client
  • Cleaning up and moving an existing filing structure
  • Connection to an ERP, a DMS or a signature service
  • Retention and deletion rules through Microsoft Purview

Several document types with an approver matrix, cleaning up the old filing structure and connecting a signature service typically land in the range of our Workflow Advanced package from €2,490. We quote the binding fixed price after the intro call.

All prices excl. VAT · operation and further development optionally via a support package

Included

What you get

  • A library that is set up

    Content type, columns, views and permissions – signed off against your real documents

  • The approval path in Power Automate

    Stages, deadlines, deputies and escalation as a flow your IT can read and change themselves

  • Evidence for audit and internal review

    Who approved which version, when and with what comment, as a view and as an export

  • Handover for authors and approvers

    What happens on publishing, how to reject properly and what applies when a deputy steps in

Questions & answers

Frequently asked questions about SharePoint approvals

It stays. In the version history it keeps its number, its status and the comment from the approver. The author continues on a new minor version, which becomes the next major version once it is published. That chain is exactly what proves later that a point was examined and changed. Nothing is deleted along the way.
Not for the standard path. Approvals in Teams, notifications and updating columns all run on the licences included with Microsoft 365. Premium only becomes necessary when we connect a system outside Microsoft 365, an ERP or a signature service for instance. We tell you which licence your path needs before the quote, not halfway through the build.
No, provided the library is configured properly. With minor versions and draft item security only the author and the approver see unpublished drafts; everyone else sees the last approved major version. This is where libraries that grew over the years most often fail, because permissions were granted one by one. We check that before building anything.
No. It documents in a traceable way who approved which version and when, but it does not replace a qualified electronic signature under the eIDAS regulation. For documents that require written form, a signature service can be attached at the end of the approval path. Whether that is worth it depends on how many such documents you have and on your licences.
Every stage has a deadline and a named deputy. Once the deadline passes the flow reminds first, then hands the task to the deputy or the next level up. What matters is that the deputy is agreed in advance: a rule that says somebody from the team cannot be modelled cleanly and ends with nobody feeling responsible.
Yes, because behind every team there is a SharePoint site. We set the path up on the document library of that team, and your people carry on working in the Files tab without thinking about the plumbing. Files from private chats are the exception: what sits in one person's OneDrive cannot be covered by a shared approval path.
Related solutions

These solutions fit alongside

Digital Approval Workflows

The same idea without a document: leave, purchases and investments with a clear chain.

Automatic Document Filing

The step before: intake, naming and filing location without manual work or sprawl.

SharePoint Migration

For when the old filing structure has to be sorted before an approval path makes sense.

Contract Management

What comes after approval: deadlines, notice periods and review dates kept in view.

Do you know which version currently counts?

In the free intro call we walk through one real case – from draft to archive – and look at one of your libraries. Afterwards you know whether you have an approval problem or a tidying-up problem first.

Book a free intro call
Practical guide

Where SharePoint document workflows creates value in everyday work

Documents receive metadata, review status, ownership and a controlled path from draft to archive when they are stored.

Three concrete operating scenarios to compare with your own process.
01

Apply metadata automatically

Document type, customer, project and status are derived from location or input.

02

Control review

Drafts go to the right role and are published only after approval.

03

Protect archiving

Completed documents receive retention status and are stored in a controlled state.

A strong fit when …

Microsoft 365 is already the main workplace and information should move reliably between Teams, SharePoint, Outlook and Planner.

  • You handle recurring document workflows using repeatable rules.
  • The intake, target system and accountable business role can be named clearly.
  • Exceptions are allowed to remain visible and move to people deliberately.
Transparent potential estimate

Estimate time savings with your own volume

The calculator uses 8 minutes today and 2 minutes after automation as fixed example assumptions. It does not replace process analysis.

Illustrative estimate based on the visible assumptions — not a guarantee.

30Hours per month
360Hours per year
Additional measures after launch Open requests Approval time Status enquiries
Frequently asked questions

What decision-makers should know before starting

How does SharePoint document workflows work in practice?
A document is created, uploaded or changed in a SharePoint library. The workflow then validates the required data, runs approved steps and routes exceptions to the responsible person with context.
Which systems can be connected?
Typical integrations include SharePoint, Power Automate, Microsoft Teams, Outlook, Microsoft Purview. The decisive factors are a stable interface and clearly defined ownership of each data field, not a specific tool.
Which tasks deliberately stay with the team?
Content approval, legal review and permission exceptions remain with the roles authorised for them.
How is the automation introduced?
We use existing Microsoft 365 structures, clarify roles and permissions, and introduce the process with one pilot team first. A tightly scoped first process typically takes 2–5 weeks; scope, interfaces and approvals determine the actual plan.
How can the benefit be measured?
Before implementation we record volume and current handling time. After launch we also compare Open requests, Approval time, Status enquiries. The calculator on this page is a transparent estimate, not a promise.
support tickets in Microsoft Teams digital approval workflows internal ticketing in Microsoft 365
Content reviewed on 26 July 2026 About Lyron AI
arrow_back Back to all products