FieldProIn development
Home / Modules / Internal Office Mail
Workplace / Source present · live validation pending

Internal Office Mail

Give employees an internal company inbox for direct and department messages, with controlled attachments and personal read status.

Authorized EmployeesOffice AdminDepartment MembersCompany Super Admin

What it is designed to manage

  • Employee inbox and sent messages
  • Department message routing
  • Personal notifications and read status
  • Private attachment upload and download
  • Attachment lifecycle controls
  • Separate from public domain email
FieldPro Internal Office Mail design concept
Design concept with sample records; not a live ERP screenshot.
Tasks 39–44 provide source for internal messaging and attachment governance. Live database, private-storage and authorization testing remain pending. External email and chat are separate products.
Feature-by-feature availability

What is in source, planned or awaiting integration.

  • Employee inbox and sent messagesSource present · live validation pending

    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.

  • Department message routingSource present · live validation pending

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

  • Personal notifications and read statusSource present · live validation pending

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

  • Private attachment upload and downloadSource present · live validation pending

    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.

  • Attachment lifecycle controlsSource present · live validation pending

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

  • Separate from public domain emailSource present · live validation pending

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

Permissions & security requirements.

  • Sender/recipient checks and company scope protect message reads and downloads.
  • Writes require session authentication and CSRF validation. Department send requires membership.
  • Storage must be outside the public web root. MIME checks do not replace malware scanning.

Related role applications.

Module access follows assigned rights. Application package releases and live connections are separate.

A practical view of the process

How the work moves.

01

Choose a colleague or permitted department

02

Write the internal message

03

Attach an allowed file using private storage

04

Recipient opens the inbox and reviews the notice

05

Archive personal messages or route follow-up

Information coming in

  • Authenticated company user
  • Recipient or department membership
  • Subject and message
  • Optional permitted attachment

Records & handoffs coming out

  • Internal message and recipient records
  • Read/archive state
  • Attachment checksum and private metadata
  • In-app notice and audit record
Connected departments

Where this module connects.

Internal MessengerCompany Email & MailboxesAttachment Governance & StorageCommunication & Notification CenterSecurity & access

Source present · live validation pending. Release availability requires the relevant implementation, integration and validation work. The visual above is illustrative.

Start with your business

Map your teams.
Connect your workflow.

Explore the departments and handoffs that match your operation, then prepare a product enquiry around your company structure.

Prepare an enquiryView product scope