In development
Core business, role and department workflows form the current product direction.
Development & availability
Know the scope. Understand the rollout.
FieldPro is being developed in stages. Product descriptions and design previews are separate from a verified live release.
Planned expansion
The approved expansion scope covers self-service, directory, workflow automation, projects, executive reporting, workplace services and broader recovery controls.
Integration-dependent
Bank execution, external email, video meetings, intercom, remote desktop and AI require the appropriate provider, credentials or infrastructure.
What must be established before release?
- Company isolation, permission matrix and controlled file access
- Cross-module workflows and business-record reconciliation
- Live database integration and migration/rollback verification
- Android APK build and real-device checks for mobile features
- Security review, backup integrity and recovery testing
Build 111 includes all 45 modules, the community forum and database migrations through 092. Run the database upgrade after installing a new version.
Integrations need their own setup.
| Area | What the business should plan for |
|---|---|
| Bank payments | Authorized payment setup and verified confirmation; publishing a payslip is not proof of a credited payment. |
| External email | Configured SMTP/IMAP or provider integration and internet connectivity. |
| Meetings & intercom | Suitable media/SIP/WebRTC infrastructure, permissions, capacity and recording consent. |
| Remote desktop | A dedicated agent or trusted integration; a PHP dashboard alone does not provide device control. |
| Internet policies | |
| AI assistance | Provider configuration, company permissions, source records and human confirmation for writes. |
