1. Open Website portal in Hosting Suite administration.
2. Choose Client area only, Both or Website portal only according to the experience you intend to offer.
3. Select One login per client when a customer should manage their eligible websites through one portal identity. Select One login per website when access should be issued separately for each website.
4. Set the portal name, logo, favicon and footer. Check that branding links lead to your real support and business pages.
5. Choose the session length and save with Save portal settings.
6. Test with an ordinary customer account and verify which websites and actions are visible.

A client-level portal login can participate in the authorised WHMCS single sign-on flow. A website-specific login does not automatically grant access to the customer's billing account. This distinction matters when a customer gives a developer access to one website.

Use the actual issued portal credentials. Do not tell customers that their WHMCS password must also be their portal password. Portal login, password reset and session handling are implemented separately, even when authorised transitions make the experience convenient.

If using the optional short address, enter the intended path and select Apply address. The module manages a marked rewrite block, keeps a backup and probes the result. Confirm that both the short address and the full portal address load correctly.

Rewrite support depends on the web server. If the short address cannot be applied, use the full working portal URL while correcting the web-server configuration. Do not repeatedly replace an existing rewrite file without checking other applications and routing rules.

Test sign-in, sign-out, password recovery, any enabled captcha or two-factor flow and the expected website selection. Confirm Plan & billing behaves appropriately for the selected login model. Portal sign-out should not be described as signing out every independent application session.

Review the access email before sending it. Issuing or resetting portal access can invalidate existing portal credentials and sessions, especially for a client-level identity shared across that client's websites. Coordinate this with support and the customer so a routine access email does not become an unexpected interruption.

• Issue and recover website portal logins
• Brand and test the Hosting Suite client experience
• Customize Hosting Suite emails and control automatic template updates
• Configure Hosting Suite access rules and verify effective permissions