This guide explains how file attachments work with messaging workflows in Productized Services.
Primary inbox page:
/wp-admin/admin.php?page=psfw-messages
What This Guide Covers #
- what is available in Free vs Pro
- how message attachments work in Pro
- limits and allowed file types
- practical workflow and troubleshooting
Free vs Pro at a Glance #
Free Plugin #
At /wp-admin/admin.php?page=psfw-messages, Free messaging supports:
- conversation list and thread view
- unread/read workflow
- message composer with rich text formatting
- sending text messages
Free messaging inbox does not provide a native file-attachment upload control in the message composer.
Pro Plugin #
With Productized Services Pro active, message attachments are added to the messaging system.
Pro attachment capabilities include:
- upload files to a message flow
- attach multiple files to one message
- image/file rendering support in message data
- attachment-aware message display handling
- ability to send attachment-only message entries when files are present
Why Message Attachments Matter #
When used well, message attachments help teams:
- keep proof files and conversation context together
- reduce back-and-forth across email/chat tools
- speed client approvals by keeping assets in-thread
- maintain cleaner project communication history
How Pro Message Attachments Work #
Pro attachment handling follows a two-step flow:
- file upload starts as a pending attachment
- attachment is linked to the created message on successful send
Operational benefit:
- safer message composition because files can be staged before final send
Attachment Limits and File Rules (Pro) #
Pro message attachments enforce:
- maximum file size: 10 MB per file
- maximum files: 5 files per message
Allowed types include common formats such as:
- images: JPG, PNG, GIF, WEBP, SVG
- documents: PDF, DOC, DOCX, XLS, XLSX, TXT, CSV
- archives: ZIP, RAR
If a file type is not allowed or size is too large, upload is rejected.
Recommended Workflow for Teams #
- Open the target conversation in
/wp-admin/admin.php?page=psfw-messages&project_id=123. - Draft a concise client-facing update.
- Add required files (Pro environments).
- Verify the message clearly explains each file’s purpose.
- Send the message.
- Confirm success feedback.
Benefit:
- better clarity for clients and fewer clarification loops
Writing Better Attachment Messages #
When you include files, pair each upload with context.
Good practice:
- state what the file is
- state what action is needed (review, approve, provide edits)
- state any deadline or dependency
This keeps collaboration actionable instead of just “file dropped.”
Permissions and Access #
Messaging remains project-access aware.
Users can only work with conversations they can access, and attachment actions should follow the same project access scope.
Benefit:
- safer file handling inside the same permission model as project messaging
Common Mistakes and Better Practice #
Mistake: Uploading Files Without Context #
Better practice:
- add one clear sentence explaining why each attachment matters.
Mistake: Sending Too Many Files in One Message #
Better practice:
- group files logically and split into staged updates when needed.
Mistake: Treating Attachments as a Separate Channel #
Better practice:
- keep decisions and file intent in the same thread message.
Troubleshooting #
File Upload Fails #
Check:
- file type is allowed
- file size is within 10 MB
- file count does not exceed 5 for the message
Attachment Not Linked After Send #
Check:
- message submission completed successfully
- you are still in the same project thread context
You Don’t See Attachment Controls in Inbox #
Likely cause:
- environment is running Free-only messaging inbox or Pro attachment feature is not active in that context
Summary #
For /wp-admin/admin.php?page=psfw-messages, Free gives a strong text-first messaging workflow, while Pro adds structured message attachment handling for richer client collaboration.
Use attachments with clear message context to get the most operational value.
