Protect a Webuzo or Legacy Bread Basket Directory

Webuzo Directory Privacy can add a web password gate to a selected directory. Older InterServer Bread Basket documentation used the same feature name. Confirm your installed Webuzo version, web server and actual directory before applying historical instructions.

Create the intended protected directory entry

1. Sign in to the trusted panel over HTTPS and locate Security > Directory Privacy where available.
2. Enter the exact directory path using the base required by that interface. In the historical v2 form, the path is relative to the user’s directory, such as public_html/test_path.
3. Enter a descriptive protection label, a separate authorized username, and a long unique password with confirmation. An old five-character form minimum is not a recommended password length.
4. Save and inspect the resulting entry. Keep the credential out of screenshots and public tickets.

Check coverage instead of assuming it

Test an unauthenticated request to a known file and an authorized request through the intended HTTPS hostname. Check child directories and any alternate public routes that matter to the application. Panel version and server integration affect support; the old Apache-only guidance must not be applied indiscriminately to current Webuzo.

A web authentication gate does not restrict the same files through authorized local or file-transfer access. Sensitive backups and secrets should not be placed in the public website merely because the panel offers directory protection.

Delete a user or remove protection

Review the exact user entry before using its delete control and confirmation. Removing a user is not necessarily the same action as removing the directory’s protection. If the interface lacks a clear directory-disable control, consult the current panel documentation or host; do not delete unrelated configuration files as a shortcut. Recheck unauthenticated and authorized responses afterward.

References: historical Webuzo Directory Privacy procedure; current security-feature documentation; version-specific server integration changes.

Reviewed October 15, 2026. Documentation review; no panel user, password or web-server configuration was changed.