PPPHP

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:

Contents

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.

Attachments, compression & expiry

Reading, search & receipts

Keyboard shortcuts

Owner settings (Core Configuration)

The owner tunes behaviour in Core Configuration → Mailroom:

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.

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.