Mailroom — in-app messaging
Mailroom is an email-like messaging engine built into PPPHP.
People write to each other — a subject, a body, optional files — and the message lands on the recipient's
notification bell. Conversations thread like email. It reuses the bell, your user groups and the
platform storage drivers, so it stays light. Open it at
/mailroom.
Mailroom works in three places, all sharing one engine:
- The console — messaging between the people who run this platform.
- Owner ↔ Client — a support channel from the licence server to a client installation.
- Inside your generated apps — a full inbox your app's own users get, configured in Misc → Mailroom.
Contents
- Turning it on & the plan capability
- Writing a message
- Attachments, compression & expiry
- Reading, search & receipts
- Keyboard shortcuts
- Owner settings (Core Configuration)
- Owner ↔ Client messaging
- Mailroom in your generated apps
- Privacy & the Support channel
Turning it on & the plan capability
Mailroom's availability is a plan capability — Mailroom — exactly like Server AI,
Email, SMS and Cloud Storage. Grant it to a plan in Licensing → Plans;
it ships on Pro and Premium. The grant travels inside the signed licence, so a
Standard-plan client sees Mailroom locked (both the console inbox and the Misc → Mailroom
tab show an upgrade nudge). On the licence server itself, Mailroom is always available.
Writing a message
Press Compose (or the c shortcut). The To field is a live contact search — type a name, username or email and pick from the dropdown; recent contacts appear before you type.
- Audiences. Administrators can address individual people, a group, a role, or everyone. Other users message individual people or the built-in Support target.
- Rich text. A toolbar for bold, italics, underline, strike, lists, quotes, headings and links. Bodies are sanitised on save. The Owner can switch Mailroom to plain-text.
- Drafts. An unfinished message is kept in your browser and restored next time you open the composer.
Attachments, compression & expiry
- Attach or drag-drop files onto the composer; they show as chips, images preview inline with a lightbox.
- Private & safe. Files are streamed only to people in the conversation (never a public URL), with a deny-list (php, exe…) and a magic-byte check on upload.
- Compressed automatically. Images are downscaled (max 1920px) and re-encoded to WebP on upload — kept only when the result is smaller. Photos and screenshots typically shrink several-fold. Toggle it in settings.
- Attachment expiry. Old attachment files can auto-delete after 30 / 60 / 90 / 180 / a custom number of days — the message text stays, the heavy bytes go. This is separate from thread retention (which removes whole conversations).
- Where they live. This server's private Email/ folder by default, or any Cloud Storage / FTP connection you set up in Storage Connections.
Reading, search & receipts
- Folders — Inbox, Starred, Sent, Archived; unread conversations are bold with a live count.
- Search (/) across subjects, message bodies and people.
- Reply inline; send with the button or Ctrl/⌘+Enter.
- Read receipts — your sent messages show Seen once everyone else has read them. In a built app's group conversation they count up on the way there: Seen by 2 of 5.
- Star, Archive, Mark unread and Remove (delete for you) from the thread header.
Keyboard shortcuts
- c — compose a new message
- / — jump to search
- Ctrl/⌘+Enter — send the current reply
- Esc — close the composer or an open image
Owner settings (Core Configuration)
The owner tunes behaviour in Core Configuration → Mailroom:
- Thread retention — auto-remove whole conversations after N days (0 = keep forever).
- Attachment expiry — drop old files while keeping the text (30/60/90/180/custom).
- Attachment caps — maximum file size and files per message.
- Compress images — the storage saver above (recommended).
- Attachment storage — the private Email/ folder or any connection.
- Rich text, who can start conversations, and an optional email copy via the mail queue.
These are behaviour settings only — whether a client has Mailroom is the plan capability above.
Owner ↔ Client messaging
From the licence server you can message a client installation directly — a two-way support channel. In the composer's To field, search for the install by its label or host (client installs show a network icon) and write as usual.
- Delivery is eventual. A message rides the client's next licence check-in (minutes to hours); the thread is marked Cross-install. Client replies post immediately and land in the same conversation.
- Secure — every cross-install message is signed with the vendor key and verified by the client, exactly like a licence lease. A client's admins see it on their bell even if their plan has no Mailroom.
Mailroom in your generated apps
Give the apps you build their own inbox. Open a project's Misc → Mailroom tab (if your plan includes Mailroom). Messages are delivered to the app's notification bell, so when Notifications are off the tab offers Enable Notifications — it names and creates the notifications table and you stay on the tab. Then turn on Enable Messages and set the menu label, attachment caps, storage, compression, attachment expiry, rich text, who-can-start and an optional email copy. Rebuild the app and a Messages page appears in its menu.
In the built app, people are listed by their full names. An administrator can also write to one of the app's groups — type its name (e.g. Team) and the whole group becomes one recipient chip (Group · 5 people); the conversation is listed under the group's name. Each new message lands on the recipients' bell (“Sam Rivera — This week's task reports …”), and one click opens the conversation, even when the app is installed in a sub-folder. Attached PDFs and images open right in the browser.
Inside the built app, an admin/superadmin can adjust attachment expiry, compression and a few other options live from a gear on the Messages page — no rebuild needed. Because a generated app has no background scheduler, attachment expiry runs when someone opens the inbox (at most once a day).
Privacy & the Support channel
Non-administrators never see the hidden owner account by name. When they use the Support (Owner & Admins) target, the conversation reaches the right people, but the owner and superadmins appear only as “Support team”. Attachments are streamed to conversation participants only — there is no public URL.