cPanel is a control panel for managing a hosting account. It brings tasks such as files, domains, databases and email into a browser interface, so you do not need to perform every routine action directly on a server. It is not the website visitors see, and it is not the same application as WordPress.
The exact tools available depend on the hosting environment and account permissions. Start with the tasks you need to perform, then locate the appropriate tool. This guide explains those jobs without assuming that every cPanel account has an identical interface or that every advanced setting should be changed by a beginner.
Separate hosting administration from website editing
Use WordPress or your selected builder to change page text and design. Use cPanel to manage the hosting resources that support the site. For instance, editing a homepage headline belongs in the website editor; creating a mailbox belongs in the email administration area.
At WH4SA, HOST provides general cPanel hosting for R79/month. BUILD adds WordPress and Elementor Free preparation for R99/month. These are not competing technologies: a WordPress site can run within a cPanel-managed hosting account. Review cPanel hosting and the cPanel versus WordPress comparison if you are choosing a starting point.
A simplified map of common hosting tasks for a South African business account. This is an explanatory illustration, not an actual cPanel interface; enabled tools depend on your service.
Understand where website files belong
The file-management tools let you work with files and folders in the hosting account. A domain's document root is the location from which its website is served. Different domains can have different roots, so confirm the correct location before uploading, replacing or deleting anything.
Do not assume every folder belongs to the public website. Application settings, backups and other account information may live elsewhere. Before a significant change, keep a backup and record what you intend to replace. Uploading a new design over an existing application can damage it if you do not understand which files it needs.
Manage domain connections deliberately
The domain tools describe the names associated with the account and how they connect to website locations. Adding a domain to hosting does not register that name for you. Registration and DNS still need to be handled through the appropriate services.
When connecting another domain, establish whether it should show a separate website or act as an alternative address. Those are different goals. Review the document root and existing DNS before changing settings, particularly if the name already handles email. cPanel's domain management documentation describes the relevant interface and its options.
Create and administer email accounts
Email tools can be used to create and manage mailboxes on a domain associated with the account, subject to the service configuration. A mailbox stores messages for a user or business function. A forwarder sends messages onward and is not necessarily a separate mailbox with its own stored inbox.
Plan who needs an address, the mailbox limits and how people will access their messages. Use the settings supplied for the account when configuring a mail app. Test both incoming and outgoing mail. Creating an address in the panel does not prove the domain's external mail records point to the correct place.
Know why a website might need a database
A WordPress site uses a database for content and settings as well as files for code and uploads. Copying only the files is not a complete move or backup of that site. Database administration involves both the database and the credentials an application uses to connect to it.
Treat tools that edit database records with care. A small change can affect many pages or users. Do not remove a database because its name is unfamiliar; first identify which application uses it. If you need to migrate or recover a site, gather the files, database and relevant configuration together.
A recovery copy of a WordPress business website normally needs its files and database. Copying photographs alone does not preserve the complete site.
Check SSL and HTTPS
SSL-related tools help you inspect and manage certificates available in the hosting environment. A correctly configured certificate supports HTTPS for the applicable names. It does not replace good passwords, website updates or careful handling of customer information.
If a browser warns about a certificate, check the exact domain being visited and the certificate's status before making broad changes. DNS, certificate coverage and website configuration need to agree. A page can also reference insecure resources even when its main address uses HTTPS. Test the real public URL rather than assuming a green status inside a panel proves every page is correct.
Make backups you can actually recover
Find out which backup tools are available and what they include. A full-account backup, a database export and a copy of one directory are not interchangeable. Ask how restores work and whether a particular restore needs provider assistance.
Store an appropriate recovery copy outside the same account and protect it because it may contain sensitive information. Check its date and contents. The cPanel backup documentation explains backup types and relevant limitations. Hosting backups are an additional recovery measure, not a reason to stop keeping your own important business data.
Use file-transfer access carefully
FTP-related tools manage file-transfer accounts where supported. The connection method and permissions depend on the environment. Use the secure method supported by your host and client rather than assuming plain FTP is the right choice for credentials or private files.
Give another person only the access needed for the work. Confirm the target directory and avoid sharing the main hosting password when a more limited arrangement is appropriate. SFTP and FTPS are different protocols; do not guess that a server supports one simply because it supports the other. Ask for the correct connection details when uncertain.
Read resource information in context
Storage is only one part of hosting capacity. A website can be affected by processing, memory, concurrent requests or other account limits even when there is free disk space. Multiple sites, backups and email can all contribute to the account's workload or storage use.
Look for patterns rather than reacting to one isolated number. Note which site or activity was running when a limit or error appeared, and provide that context when asking support for help. “Unlimited” website counts do not mean unlimited physical server resources. The unlimited hosting service page explains the WH4SA account model.
Multiple .co.za projects in one cPanel account share account resources and administration. This does not provide reseller hosting, WHM or separate cPanel accounts.
Understand multiple websites in one account
Where supported, one cPanel account can host several websites. They share the account's resources and administrative boundary. A problematic application or careless file change can affect more than the project you were thinking about.
This is not reseller hosting and does not provide WHM or separate cPanel accounts. Developers should consider access arrangements, resource sharing and recovery for each project. The developer hosting page explains the intended pathway without treating each hosted domain as an isolated account.
Make a safe first-use checklist
- Confirm the correct account and domain before editing.
- Identify each website's document root and database.
- Record the mail service and required client settings.
- Check certificate and backup information.
- Keep credentials secure and avoid unnecessary shared access.
- Change one understood setting at a time and verify the result.
Use cPanel as an administration tool, not as a collection of buttons to experiment with on a live business site. For a task outside your experience, describe the intended outcome and ask for the appropriate procedure before making changes that are difficult to undo.