Skip to content

Mezan Workflows

The procedures you currently run over WhatsApp

A request is raised, reviewed, approved, then carried out. Mezan Workflows writes that path into the system instead of leaving it as folklore in people’s heads.

  • Available since July 2026
  • Statuses and fields you define
  • Tasks and an inbox

What is inside

  • Workflows

    A path per internal procedure, with its statuses in order.

  • Fields and statuses

    What the requester fills in, and the stages a request passes through.

  • Access and members

    Who sees a path, and who can move it forward.

  • Tasks

    Tasks linked to each other and to their documents.

  • Inbox and notifications

    What is waiting on you, in one place.

How you build a path

No code and no consultant. Define it once, and your team works it every day.

  1. 1

    Name the procedure

    A purchase request, a discount approval, a maintenance ticket, a new customer account — anything that recurs.

  2. 2

    Set the statuses

    The stages a request moves through and their order: new, under review, approved, rejected, done.

  3. 3

    Set fields and access

    What has to be filled in at each stage, and who is allowed to move a request to the next one.

  4. 4

    Run it

    Requests land in the right inboxes with their notifications, and every step stays on the record.

What you get

The point is not more bureaucracy. It is that "who has the request right now?" stops being a question.

  • Paths you define

    A path per internal procedure, with the statuses and order your business uses rather than a fixed template.

  • Fields per path

    Decide what a request must state, so requests stop arriving incomplete and bouncing back.

  • Access and members

    Who sees a path and who approves in it is set per path, not at the level of the whole system.

  • Linked tasks

    Tasks are assigned and linked to each other and to documents, so context travels with the task.

  • Inbox and notifications

    Everyone opens one inbox to see what is waiting on them, and is notified when something of theirs moves.

  • Inside Mezan, not beside it

    Paths sit next to your documents, your team and your permissions — no second subscription, no copying between systems.

Examples

What people build with it

These are examples of what can be built, not templates. Paths are defined around your own procedures, because what needs an approval in a contracting firm is not what needs one in a law office.

  • Approving purchase requests before the purchase order is raised
  • Approving discounts above a threshold
  • HR procedures: hiring, offboarding, special requests
  • Maintenance and internal support requests, tracked to closure

What a path is made of

  • Statuses

    The stages a request passes through, in order.

  • Fields

    What must be filled in before it moves on.

  • Members

    Who takes part in the path and in what role.

  • Notifications

    Who is told on each transition.

Common questions

Is Mezan Workflows available now?

Yes. Mezan Workflows is available now.

Do I need a developer to build a path?

No. A path is defined inside the system: you name it, set its statuses, fields and members, and start using it.

Can a path be linked to Mezan documents?

Yes. Tasks link to each other and to their documents, so a request and its context stay together rather than in a separate conversation.

Who can see requests?

Access and members are set per path, so each person sees only the paths they take part in.

Book a demo

Leave your details and we’ll call you back within one business day to arrange your session.

We use your details only to contact you about your Mezan session.