PD Onboard turns the information needed after a WHMCS order into a customer checklist. Add an upload step when an onboarding task needs a document or image. Confirm the installation’s storage protection before asking customers to submit private files.

Add the upload step

1. Open the checklist and choose A file to upload under What kind of step. This requires Pro.
2. Set What are you asking for to a specific request, such as a logo or project document.
3. Use Guidance to explain the accepted file and avoid requesting unnecessary personal material.
4. Review Requirement and add the step.
5. Use harmless controlled data to check the customer upload and staff Download action before requesting real material.

Check size and type

The module caps a file at 12 MB and accepts a defined set of document, image and archive extensions. Your hosting upload limits may be lower. A permitted extension is not a malware scan or proof that the file’s contents are safe. Review untrusted documents and archives using your normal safe handling process.

If the customer sees a size or type error, request a supported smaller file rather than renaming a prohibited extension. If the step is paused, review the current Pro entitlement. Do not repeatedly upload private files while diagnosing storage access.

Review storage and retention

Check the module’s Report for the reported storage location and protection. The intended private store can fall back to a location inside the public website folder, where effective web-server protection matters. Check the actual storage protection with your server administrator before collecting private uploads.

Use Download from the staff run to review an authorised submission. Cancelling onboarding preserves supplied files; deleting the run attempts to remove them. Neither action recalls copies already downloaded by staff. Do not delete a run merely to correct one upload.

See the PD Onboard WHMCS guide for related tasks, or explore PD Onboard.