Create a password-protected client page

Guides

Choose appropriate content and protection

A password-protected page can provide a limited-access client update, but it is not a substitute for a dedicated confidential-document system. Anyone who receives the shared password can pass it on. Decide whether this level of protection is suitable before adding client material.

You need administrator access, the intended client page, approved content, and a secure channel for sharing its password. Select the correct website and language. Do not put the password in page copy, button labels, a public URL, an assistant prompt, or a support screenshot.

Prepare only a neutral heading while configuring protection. The MCP page-creation tool defaults to direct-link availability, which is not password protection. If content must never be briefly public, prepare it on a suitably private website or establish and verify access restrictions before adding sensitive material.

Set access before adding details

1. Open the selected page's Page Settings. Under Access, set Availability to Password protected. Enter a strong, non-empty value in Password and save. Do not reuse your administrator password or another account credential.
2. Review In navigation and Show in site navigation. Decide whether the page should have a menu entry, but do not treat menu removal as protection. A direct-link URL can still be shared or indexed when it has no separate access control.
3. Open the page's normal URL in a fresh signed-out browser session. Confirm that it asks for a password before displaying the body. Test an incorrect password, then the correct one. An administrator session can bypass the visitor experience, so checking only your editing tab is insufficient.
4. Once protection is confirmed, add the approved client update in the managed editor. Keep the real header and organize the body into status, next steps, and agreed contact information. Avoid unnecessary personal data and review image captions, filenames, and linked resources too.
5. Check every linked file, image, and external destination independently. Protecting the Beeboo page does not establish that a separately hosted resource requires the same password. Do not publish a sensitive public file URL behind a protected page and assume the file inherited its access rules.
6. Save the content explicitly, then repeat the signed-out access test. Share the verified page URL and password through approved channels. Review any existing translated variants separately instead of assuming their settings are identical.

Check search and ongoing access

Password pages receive noindex treatment, but noindex is not a confidentiality guarantee and cannot recall information already disclosed. Confirm that public listings, summaries, and images do not reveal information you intended to restrict.

If the page opens without a challenge, stop sharing it and verify the actual availability, saved password, website, and browser session. Do not leave a password-protected setting with an empty password. When access should end, change or remove access deliberately and verify again from a fresh session. See pages and navigation, search visibility, and site administration.