Skip to content

Getting started: your first approval, start to finish

From a new account to an approved request in the console: install a template, add approvers, file a request, answer it and download the receipt.

Updated · 9 min read

In short

  • Creating an organization, installing a template and adding people to its approver groups is enough to start approving requests - no code and no API key required.
  • A template installs its action and workflows together: pick one, such as content and publication sign-off, and its approver groups and routing are ready to use.
  • Filing a request from the console works exactly like an agent or the API would: pick the action, say why, and DueReason shows similar past decisions while you type.
  • Once a request is decided, a signed receipt can be downloaded or verified by anyone, without a DueReason account, and the same setup carries over once you connect systems or agents.

DueReason approves things: payments, deployments, published content, signed contracts, or anything else your organization wants a person to sign off before it happens. This walks through the console path from nothing to your first approved request - no code, no API key, nothing but an account and a few teammates.

Create your account and your organization

Create an account. The first account in a new organization becomes its owner, with full access to Settings. Everything below - templates, approver groups, members - lives inside that organization, and you can invite teammates into it as soon as it exists.

Install a template

Settings → Templates has a library of ten ready-made templates for common decisions: a payment, a production deploy, an account or access action, a content or publication sign-off, a contract sign-off, a data access export, a discount exception, a hiring offer, a policy exception, and vendor onboarding. Installing one creates its approver groups (or reuses groups with the same name already in your organization), the action it covers and the workflows that route it - you can change all of it afterwards. If the approval you need first is restricting, suspending or revoking someone's access rather than a payment or a publication, the access request approval guide walks through that template specifically. If it is a purchase - a vendor quote, a renewal, a one-off order - rather than another kind of payment, the purchase request approval guide walks through how the amount decides whether Finance alone or Finance plus Management signs off.

Take the content and publication sign-off template as an example that needs no agent or API to use. Installing it creates the Publication action, two approver groups - Content leads and Legal - and two workflows: a routine one that only needs a content lead, and one for anything that makes a legal or financial claim, which routes to a content lead and then Legal. Its groups start empty: nobody can answer until you add people to them.

If you would rather plan out who approves what before installing anything, the approval matrix template is a free, ungated sheet to start from.

Add approvers

Open the groups the template just created from Settings → Approver groups and add members to Content leads (and to Legal, if you installed the claims workflow too). Approver groups are named sets of members that workflow steps can ask; membership is checked when someone answers, so removing a person takes effect immediately.

If the person you need is not in the organization yet, invite them from Settings → Members: an email invitation link stays valid for seven days, and you choose their role when you send it.

Turn on notifications (optional)

Settings → Notifications can post to a Slack or Microsoft Teams channel whenever a step needs answers or a request is decided - paste the channel's webhook address and send a test message to confirm it arrives. Each approver can also turn on email for themselves, and browser or phone push once it is configured on your server. None of these messages carry the payload, the reason, comments or evidence - only the title, the action and a link back to the console, so approvers still sign in to see the rest.

An organization can additionally turn on Approve/Decline links in notifications (off by default). Turning it on lets Slack, Teams, email and push messages carry a link an approver can use without opening the console first - but clicking it still opens a confirmation page that requires signing in as an eligible approver: a link alone never approves anything.

File your first request

From Approvals → New request, pick the action - Publication, if you installed the sign-off template - and fill in a title, the action's own fields (Channel, Title, Draft, and whether it Makes a legal or financial claim), and a reason: this is shown to every approver and kept on the record. You can attach links an approver may want to check, such as the draft itself or a ticket, and up to 5 files - PDF, PNG, JPEG, WebP, HEIC, plain text, Word (DOCX) or Excel (XLSX), 10 MB each - such as a contract draft or a screenshot. Choose how long the request waits for an answer - 24 hours, 3 days or 7 days, or a custom number of hours - before it expires unanswered. While you type, a Similar past decisions panel shows how earlier requests for the same action were decided.

If no action is ready yet, the form says so and points back to Settings → Actions - that is the sign that a template still needs installing or a workflow still needs activating.

Answer it

Whoever is in the matching approver group sees the request waiting for them and opens it to answer. Each approval needs whatever the workflow step asked for - for this template, a written reason - and rejecting always needs one, so the requester learns why. Approving a step that still needs more people leaves it open for the rest; the last approval on the last step approves the whole request and issues a signed grant for whatever is meant to carry it out. You cannot approve your own request - someone else in the group has to.

Get the receipt

Once a request is approved, rejected, expired or cancelled, its Receipt section offers Download PDF, Download receipt.json and Open printable receipt: a self-contained, signed record of the payload, every step's answers and evidence, and the request's ledger events. The PDF has the original receipt.json embedded inside it, so it is self-verifying and ready to attach to an invoice or an audit folder on its own. It can be checked at /verify, with @duereason/sdk, or by hand - whoever is checking it does not need a DueReason account.

When you're ready for systems and agents

Everything above also works unattended: an agent or your own system sends the same kind of request through the API with an API key, reads back the decision, and acts on the grant it receives, all against the same actions, approver groups and workflows you just set up by hand. The API reference covers authentication, request and grant shapes, and webhooks; if you would rather wire approvals into a tool you already use, the no-code webhook recipe connects them to Zapier, Make or n8n without writing a backend.

Questions

Do I need a developer to get started?
No. Creating an account, installing a template, adding approvers, and filing or answering requests all happen in the console. A developer is only needed once you want an agent, a script or another system to request approval through the API.
Can a requester attach a file to a request?
Yes - alongside links, the request form has a Files section for up to 5 files (PDF, PNG, JPEG, WebP, HEIC, plain text, Word or Excel), 10 MB each. An approver can also attach their own evidence when they answer, if the workflow step asks for it.
Can someone approve their own request?
No. DueReason refuses an attempt to answer your own request; someone else in the approver group has to decide it.
What happens if nobody answers in time?
The request expires at the time you chose when filing it - 24 hours, 3 days, 7 days or a custom number of hours - and stops waiting for answers. It still gets a receipt, recording that it expired undecided.

Start your first approval

Create an account, install a template, and you can file your first request within minutes.

Create your account

Sources

This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.

Start with DueReason

Create a free account, try it live, or talk to us about your workflow.

Get product updates