10 · Platform & settings

Rep order consent

Choose whether a field-rep order needs the rep's confirmation, the customer's signed acknowledgement, or the owner's approval.

5 min read · updated 28/05/2026

Overview

Rep order consent decides when an order submitted by a field rep can become a real order. It is one tenant setting with three modes. Collection claims do not use this setting: every claim stays pending until an owner-side payment writer confirms it.

Where to find it

Open the Settings surface and look for the registered Rep Order Consent panel. Its settings-registry key is field-rep.consent; the renderer is FieldRepConsentPanel. The default for a new tenant is owner_approval.

Key concepts

  • rep_confirm — the rep's confirmation is enough to promote the rep draft. The customer still receives the order confirmation on the customer's own channel.
  • customer_ack — Neev sends the customer a signed acknowledgement link on the customer's own channel. The draft stays held until the customer taps the link and its POST acknowledgement is accepted.
  • owner_approval — the draft waits in the owner decision queue at /approvals.
  • Below-list floor — if any line is priced below its list price, the order is forced to owner_approval in every mode. A rep cannot approve their own below-list price.

Common workflows

1
Choose a mode
Set the consent value to rep_confirm, customer_ack, or owner_approval in the Rep Order Consent panel. Save the single order-consent setting; there is no separate collection-consent selector.
2
Review a customer acknowledgement
In customer_ack, the customer receives a signed link to /rep-order/ack. The link is valid for 24 hours. The customer does not need a Neev login; the signed link and its POST acknowledgement are the consent action.
3
Handle the owner rail
In owner_approval, or when the below-list floor applies, open /approvals and approve or reject the rep_order request. A rejected request does not become an order.
4
Let an expired link escalate
If a customer does not acknowledge within 24 hours, the hourly ack sweep marks the hold escalated and files it in the owner approval queue. It does not create an order automatically.

Role notes

  • Owner — changes the setting and decides rep_order approvals. The owner procedure protects the setting write; field-rep.update is the permission key on the settings mutation.
  • Manager — may be an approver through intake.approvals.approve-rep-order and intake.approvals.reject-rep-order, but cannot change this Owner-only setting.
  • Field rep — places drafts through intake.rep-draft.create and sees the resulting status, but cannot change consent or approve an order.

Tips & time-savers

Tip
Keep the default owner_approval while a new rep or beat is being checked. Switch to customer_ack only after each assigned customer has a usable channel handle.

Gotchas

Warning
customer_ack degrades to owner approval when the customer has no channel handle, REP_ORDER_ACK_LINK_SECRET is unavailable, or the draft cannot be represented as a customer acknowledgement. A below-list line also always takes the owner rail; changing the setting cannot bypass that floor.

The customer link is single-use and bound to the tenant, draft, and customer. A bad, expired, already-used, escalated, or mismatched link is denied without promoting the draft.

Related