Modern Workplace

    SharePoint approval workflows with deadlines and evidence.

    Documents, invoices and applications go to review, approval or signature in SharePoint. Power Automate reminds before deadlines and records every decision.

    For finance, legal, research and quality teams whose invoices, documents and requests pass through several approvals.

    • SharePoint Online
    • Power Automate
    • Approvals app in Teams
    • SharePoint eSignature
    • Dataverse
    • Entra ID
    A document moves across the desk from inbox via review and approval stamp to signature, a calendar with a deadline beside it
    01

    An invoice on Monday morning

    Monday, eight o'clock. A supplier's invoice sits in the intake library, with the key details already in the columns. The cost centre manager receives the request in Teams and approves it. If she is on holiday, the request goes to her deputy after the agreed period. Accounts sees the status, and the history shows who decided when.

    02

    Workflows for your approvals

    Each workflow follows a rule your process owners set: who reviews, who approves, who deputises and when it escalates. We build with real cases, first one workflow in one area, and choose the right tool for each: approvals in the library, Power Automate or SharePoint Approvals. After that, your team adjusts roles and deadlines on its own.

    • Review and approveA document goes to one or more people, one after the other or at the same time; whoever rejects it adds a comment, and the author revises the same file.Result: the approved version is marked as such in the library, with date and person.
    • SignatureAfter approval, the document goes from the library for electronic signature to people inside and outside the organisation, with a deadline and reminders; the signed version lands back in the same place.Result: approval and signature are attached to the same document.
    • Deadlines and deputiesA reminder before the deadline, forwarding to the deputy during absences and escalation to management if nothing happens.Result: every open request has a responsible person at all times.
    • Invoices and applicationsReceipts and forms arrive with their details in a library, the workflow routes them by amount, cost centre or application type to the right place and defines what happens after a rejection.Result: every incoming item has a status and a responsible person.
    • History and reportingEvery decision with person, time and comment on the document and in the Microsoft Purview audit log, plus a view of open approvals per area.Result: audit and management find the evidence in the system.
    03

    Rules before anything runs automatically

    One owner per workflow and a set of real cases, including some with rejection or absence. Roles and deputies as groups in Entra ID, and a rule for what happens when an already approved document changes. For signatures, your specialists decide the level required; on the technical side we check licences, service accounts for the workflows and pay-as-you-go billing for eSignature.

    04

    The workflow in testing and after

    Workflows in your Microsoft 365, tested with your cases: approval, rejection, absence, an expired deadline and a failure in the workflow itself. A view of open and completed approvals and a short handbook for requesters, approvers and the person on your team who adjusts roles. Failed runs go to a named contact, and on request our support team monitors the workflows.

    Sound familiar? Tell us where you stand today.

    Contact

    What's new.

    As of: 9 October 2026

    • As of 11 September 2025

      SharePoint eSignature is available in Switzerland too.

      Microsoft offers eSignature worldwide through the Microsoft 365 public cloud, with the exception of Indonesia. The signatures are simple electronic signatures under eIDAS; external signers access the document as guests through Entra ID. Every step appears in the Microsoft Purview audit log, and signature requests can be tracked in the Approvals app in Teams.

      Source: Microsoft Learn: Overview of eSignature
    • As of 14 April 2026

      The Approvals app stores in Dataverse and logs in Purview.

      Requests from the Approvals app in Teams are stored in the default Dataverse environment; according to Microsoft, this environment does not currently support backups. Approving, rejecting, reassigning and signature steps appear in the Microsoft Purview audit log. Signature requests through Adobe Sign or DocuSign are stored in that provider's cloud and need its licence.

      Source: Microsoft Learn: Manage the Approvals app in Microsoft Teams

    Multi-step approvals as a product.

    For approvals with several stages, owners, deadlines and a history, there is a ready-made product that runs in your library.

    What process owners ask before the first workflow.

    Are the built-in approvals in lists and libraries enough?

    For many cases, yes. Approvals can be switched on in any list or library: a person requests one for a file, and approvers respond in the library or in Teams. For several stages, deputies, escalations or fields set after approval, we build a workflow with Power Automate or use SharePoint Approvals.

    What signature level does eSignature provide?

    A simple electronic signature. That is enough for confirmations, internal agreements and many forms. Where the law requires a qualified electronic signature, the workflow passes the document to a provider that issues this level under Swiss law. Your specialists decide which level a document needs.

    What happens if someone changes the file during approval?

    The approval is cancelled. With approvals in the library this happens automatically as soon as a change is saved; in a custom workflow we decide whether the changed version starts again or returns to the same step. That way every approval refers to exactly the version that was reviewed.

    Where do approvers see their open requests?

    In the Approvals app in Teams, collected from libraries, workflows and signature requests, on the phone too. Requesters see the status of their requests there and can follow up or reassign a request. Worth knowing before the start: a request does not give the approver access to the file, so the permission must already exist.

    How long is the history kept?

    As long as your rule requires. Activities appear in the Microsoft Purview audit log, requests from the Approvals app are stored in Dataverse, and the documents are covered by a retention policy. Where the evidence must last longer than the audit log, the workflow also writes decision, person and time as columns on the document.

    What happens to the workflows when the person who built them leaves?

    The workflows keep running. We set them up with a service account or as a solution with several owners, so no workflow depends on a personal account. Your team receives a list of all workflows with purpose, trigger and responsible person.

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.