Preparing starter files for newly created cPanel accounts

Prepare a minimal static welcome page or other safe starter content. Exclude passwords, private keys, customer data and a preconfigured application database. Confirm the actual reseller home path instead of assuming every server uses the same partition.

1. For a root-owned template, use the supported /root/cpanel3-skel/public_html location. For a reseller, use cpanel3-skel/public_html beneath that reseller’s actual home directory.
2. Upload only the intended starter files and required subdirectories through an authorised file-management method. Use ordinary readable web-file permissions.
3. Keep public FTP starter content separate if the service uses it; do not place private material in a public-transfer directory.
4. Create a disposable test account through the normal authorised workflow and inspect the files copied into its web root.
5. Verify the starter page, then remove the disposable account through your controlled test cleanup process. Record the template version for future account provisioning.

New accounts should receive the expected starter content without secrets or broken absolute paths. Existing customer accounts should retain their own website files.

If files do not appear, confirm whether root or a reseller owns the new account and check that owner’s skeleton path. Do not look for a removed WHM menu or copy a customer’s live application wholesale into the shared template.

The mechanism supplies content during account creation. Updating it is not a deployment system for existing accounts. Make any later customer-site change separately with the proper authorisation and backup.

• Applying reseller contact details and branding without changing server ownership
• Customising a WHM suspension page without exposing customer data
• Terminating a hosting account after a verified handover
• Planning package changes across several reseller accounts

• cPanel: Skeleton Directory