Request types
Fields, approver steps, conditions and an SLA for each kind of request.
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.
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.
What Approvals does for you.
Fields, approver steps, conditions and an SLA for each kind of request.
Approve, reject or request changes; a resubmission is round 2 with a diff.
Clients and partners decide on a branded page after an email code.
A suggested path for Approvals. What you can do depends on your access in the app.
Start from a ready type or build your own.
Add the fields, the link or file, and submit.
Reminders go out after the SLA, and the log keeps every decision.
Live host, inventory, governance, health checks, verification, dependencies and history.
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.
Automated sequences belong to Workflows; creative review with pinned comments belongs to Proofs.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
approvals.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.