Booking
Capture the customer order and submit it for the configured review.
Typical owner: Order Booker / SalesRecord assigned customer interactions and submit eligible order requests for the configured approval path.
These are FieldPro security requirements and intended permission boundaries. Actual enforcement depends on implementation, company policy and release validation.
Capture the customer order and submit it for the configured review.
Typical owner: Order Booker / SalesApprove, reject or return the order for rework according to company policy.
Typical owner: Assigned ApproverOwner labels show the agreed operating flow; actual assignment, branch limits and approvals remain company-configured.
Each module shows what it manages, its process, information in and the records it hands off.
Show how a customer order moves from the sales team into approval and fulfilment.
Maintain assigned customers and their authorized business context.
Keep quotation revisions and their approval history.
Route the chosen quotation revision to the assigned approver.
Turn an approved customer request into a controlled order.
Connect the order to warehouse dispatch and transport handoffs.
Manage invoice lifecycle through assigned issue/cancellation rights and audit.
Route eligible returns through the required warehouse and finance review.
Review assigned team, customer and order activity.
Provide permitted sales reports/documents in their appropriate export formats.
Carry source-linked stock and financial handoffs across departments.
Retained from the earlier FieldPro scope; release availability is reviewed separately.
Retained from the earlier FieldPro scope; release availability is reviewed separately.
Retained from the earlier FieldPro scope; release availability is reviewed separately.
Retained from the earlier FieldPro scope; release availability is reviewed separately.
Make approval ownership explicit, including sequential reviews, escalation and reject/rework paths.
Previously documented product scope; release availability is assessed separately.
Previously documented product scope; release availability is assessed separately.
Previously documented product scope; release availability is assessed separately.
Previously documented product scope; release availability is assessed separately.
The source manager dashboard supports review, follow-up, independent decisions, eligible closure and rejected-item rework for recovery-security alert reviews.
Filter by status, decision and manager, search text and browse 50 records per page in the source approval-review queue.
Assigned managers can add a follow-up to at most 25 eligible reviews together. This does not bulk-approve, reject or close them.
Inspect advisory same-department workloads, choose an eligible active manager and reassign only open unreviewed items with a reason and history.
Monitor overdue review work and issue scheduled, company-scoped internal reminders using configured policy.
View decision/rework history, verify the recorded audit chain and export bounded formula-neutralized reports within company permissions.
Give authorized field teams company-scoped communication channels, transmit permissions and a controlled turn to speak.
Channel listing, members, creation, grant and revoke are recorded in the source batch; active company context is required.
Company/channel speaking-turn controls use a 15-second lease and a holder-only release.
Initial Flutter sign-in, secure token storage and read-only channel selection exist. Role mapping and platform project generation remain pending.
Microphone capture, an independently authorized media service and live audio delivery remain to be implemented.
PTT is intended across these field apps; a separate finished implementation for each is not established.
Bluetooth or Wi-Fi Direct has local range; no 1–2 km or long-distance offline voice capability is claimed.
Explore the departments and handoffs that match your operation, then prepare a product enquiry around your company structure.