Supervisor App

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.

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.

Incident creation queues recipient-specific inbox entries for eligible active company admins and supervisors.

Separate view/respond/muster grants and revocation; acknowledgement and resolution require response permission.

Authorized headcount recording and summary routes exist in source.

CLI worker queues eligible open non-drill incidents, with duplicate prevention and transaction locking. Cron activation remains pending.

Company inbox and incident details refresh every 30 seconds while visible; stale warnings and last-check time are displayed.

These delivery channels are not implemented; database polling is a best-effort status view.

Review configured limits and customer exposure with assigned approval authority.

Follow unpaid invoices and outstanding balances in the assigned scope.

Assign collection follow-ups and review target progress.

Submit payment details for Accounts verification and authorized posting.

Group outstanding invoices by due-date/aging context.

Send permitted reminders using configured communication providers.

Track customer disputes and route adjustments to the authorized approver.

Review assigned collector activity and recorded collection outcomes.

Bring credit reviews, follow-ups, disputes and payment submissions together.

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.

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.

Retained from the earlier FieldPro scope; release availability is reviewed separately.

Create a customer receipt, submit it, and require a different authorized reviewer to approve or reject. Rejection requires a reason.

Allocate only approved receipts to the same customer and currency, with remaining receipt/invoice balance checks and a CNC subledger entry.

Record invoice due dates and currency, then inspect a customer ledger and currency-grouped balances. This is not a completed general-ledger integration.

Submit adjustment requests and post the source adjustment only after independent authorized review.

Record company bank metadata, review deposits independently, import statement lines and manually match eligible approved deposits. This does not initiate a bank transfer.

Inspect stale pending deposits, unmatched statement lines and approved deposits awaiting a match.

The receipt collector can submit a bounded handover against their approved receipt. A different authorized reviewer verifies or rejects it.

Compare approved receipts with verified handovers by collector, date and currency; require an explanation for shortage/excess and independent review.

Plan collector routes, record visits and allow the assigned collector to complete or mark no-contact. Optional submitted coordinates are not independently verified device GPS.

Set period/currency targets and compare approved receipt amounts. These figures do not prove bank-settled recovery; visit performance is a separate count.

Configure basis-point plans, calculate eligible claim proposals and route claims to independent review. Approval is not payroll payment.

Record promises, fulfillment/break/cancel states, disputes, escalation and resolution. Forecast summary is descriptive, not predictive AI.

Schedule follow-ups, complete/cancel tasks, generate reminder records and review a supervisor queue.

Record templates, campaign approval, planned communication history and manually reported outcomes. A manual status is not provider-verified delivery.

Store purpose/channel preferences with change history and cancel queued notices when consent is withdrawn.

Use consent checks, idempotency keys, attempts, dead-letter records and independently reviewed recovery requests in the notification foundation.

Provider configuration, secret rotation and signed-event/replay handling exist in source. Dry-run workers and standalone outbound adapters are not a verified live send pipeline.

Company-scoped employee-to-employee messages, message detail, sent history and personal archive are present in source. Recipients are company users, not public email addresses.

An active department member can send to up to 100 other active members. Department delivery is recorded as one database transaction.

Internal notices identify new messages and uploaded attachments. Users can mark only their own notices read; this does not establish mobile push delivery.

Sender upload supports PDF, PNG, JPEG and plain text up to 5 MiB. Private storage, randomized keys, SHA-256 checks and authorized downloads are in source.

Retention previews, legal holds, configured company quotas and independent cleanup review connect to the dedicated governance workspace.

Office Mail stays inside the company database. It does not use SMTP/IMAP or create a company-domain mailbox.

Company-scoped recent events and failure counters cover recovery grant creation, redemption and integrity failures without exposing tokens or file paths.

Open a review for a company user and require another reviewer to close it. The source also provides temporary manual recovery-download restrictions.

Escalate an open review to an incident. The opener cannot acknowledge or resolve their own incident; the independent acknowledging admin records the resolution.

Company policy controls acknowledgment and resolution targets. Assignment validates active company and department membership.

A scheduled worker routes overdue assigned incidents through configured active department members at levels 1–5. It records internal notices and dispatch history.

A designated recipient records one response note per dispatch. An escalation response is distinct from resolving the incident.

Per-level response targets, overdue response alerts and bounded 30-day department performance reports are present in source.

Formal active department managers receive follow-ups. A different authorized manager decides approval or rejection before permitted closure.

Reopen an eligible rejected review with a reason, preserve prior decisions and resubmit for independent review.

The manager dashboard exposes permitted review, follow-up, decision, close, rework, notice-read and export controls.

New decision/rework actions write chained audit entries; tenant-scoped CSV neutralizes spreadsheet formulas. The chain is not externally anchored and cannot defeat a privileged database rewrite.

An authenticated operations workspace combines personal approval notices, company escalation analytics and sanitized worker telemetry.

Filter personal in-app notices by read/unread state and type. Mark-all-read affects only the current user.

A company can configure an approval threshold of 1–720 hours. The worker uses company policy unless an operator explicitly overrides it.

Open reviews remind their assigned manager; reviewed items awaiting decision notify other eligible independent managers. No automatic approval or reassignment occurs.

Successful executed runs and qualifying failures are recorded. Early startup errors, process kills and failed log writes may not be recorded.

Configure a stale threshold of 15–1440 minutes and failure warnings. Run/failure trends are global operational metadata, not other companies’ business records.

A separate health-monitor job opens deduplicated warning events, records recovery and creates internal notices for authorized active company administrators.

Record who responded to a warning and their note. Acknowledgment does not clear a warning, repair a worker or replay a job.

Configure a 5–1440 minute response target and view a bounded 30-day report based on first acknowledgment during each event lifetime. Historical records use the current policy.

Assign an active company user, require a resolution note and enforce supported state transitions. Manual response state stays separate from observed worker recovery.

Assignment changes and eligible resolve/reopen actions create in-app notices for the assigned active user. Repeated unchanged assignment does not generate another assignment notice.

A permitted reviewer can approve a resolved incident or reject it with a reason. Self-review is denied; rejection returns the manual workflow to investigation.

Health resolution review requires a separately granted health.incidents.review permission. Existing supervisors are not granted this automatically; dashboard access still uses company.update.

Assign an incident to a department in the same company and report investigating, resolved and historical approval/rejection counts. Assignment is manual; approved/rejected counts can overlap after resubmission.

Reviewer decisions have a 30-day summary. The separate department mapping report is bounded and is not represented as a mutually exclusive completion percentage.

A stopped health-monitor job cannot report its own outage. Cron setup and independent uptime monitoring are deployment work.