Skip to app details
Back to app library
APPNEURAL APP FAMILYOperations & Projects

Approvals

Every sign-off, with the version it was given on

Ask for approval on an exact version and keep a record of who approved what, and when.

01 / OVERVIEW

See where it fits in your day.

Each domain sets up request types with fields (text, number, money in INR or seven other currencies, date, choice, URL, file), ordered steps where any one or everyone approves, approvers who are the owner, the requester's manager, a named team member or an outside email, step conditions such as "only when Amount is ₹50,000 or more", SLA hours and who may submit; seven ready types cover design, content, quotation discounts, expenses, purchases, leave exceptions and general requests. Requests are numbered APR-0001 with field values, a subject (link, version label and text) and attachments in R2 (25 MB, SHA-256 at upload) or links. Each submission freezes a round under one SHA-256, so every decision records exactly which version it was made on. Approvers approve, reject or request changes with a comment; a resubmission is round 2 with a field and line diff; a seat can be delegated, and nobody approves their own request. Outside approvers open /a/<token> in the domain's brand after a 6-digit email code. An hourly cron reminds approvers past the SLA and escalates once, with a daily 10:00 IST digest per approver. Inbox (waiting on me, my requests, all), a decision log with CSV, POST /api/v1/approvals with a signed callback, webhooks, and Claude for an approver brief, a round-to-round comparison and change-request drafts.

A LOOK INSIDEExample layout · sample content
A request through its steps
SubmittedDiscount request
ManagerApproved
OwnerApproved on round 2
02 / CAPABILITIES

Built around the work you do.

What Approvals does for you.

01

Request types

Fields, approver steps, conditions and an SLA for each kind of request.

02

Rounds and decisions

Approve, reject or request changes; a resubmission is round 2 with a diff.

03

Outside approvers

Clients and partners decide on a branded page after an email code.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Approvals. What you can do depends on your access in the app.

01

Pick a request type

Start from a ready type or build your own.

02

Submit the version

Add the fields, the link or file, and submit.

03

Follow the decision

Reminders go out after the SLA, and the log keeps every decision.

YOUR NEXT MOVE

Make Approvals part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Each domain sets up request types with fields (text, number, money in INR or seven other currencies, date, choice, URL, file), ordered steps where any one or everyone approves, approvers who are the owner, the requester's manager, a named team member or an outside email, step conditions such as "only when Amount is ₹50,000 or more", SLA hours and who may submit; seven ready types cover design, content, quotation discounts, expenses, purchases, leave exceptions and general requests. Requests are numbered APR-0001 with field values, a subject (link, version label and text) and attachments in R2 (25 MB, SHA-256 at upload) or links. Each submission freezes a round under one SHA-256, so every decision records exactly which version it was made on. Approvers approve, reject or request changes with a comment; a resubmission is round 2 with a field and line diff; a seat can be delegated, and nobody approves their own request. Outside approvers open /a/<token> in the domain's brand after a 6-digit email code. An hourly cron reminds approvers past the SLA and escalates once, with a daily 10:00 IST digest per approver. Inbox (waiting on me, my requests, all), a decision log with CSV, POST /api/v1/approvals with a signed callback, webhooks, and Claude for an approver brief, a round-to-round comparison and change-request drafts.

Human decisions with a record: requests of a set type, approver steps, approve or request changes on an exact version, outside approvers, reminders, escalation and an API for other apps.

Automated sequences belong to Workflows; creative review with pinned comments belongs to Proofs.

Priority
P2
Portfolio
Operations & Projects
Capability
Operations & Projects
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:12
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

approval schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

approvals.appneurox.com DEPLOYED

approvals.appneurox.com

Worker
approval-catalog
Health
HEALTHY
Last deployment
2026-11-18 14:03:12
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/approval-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app