Password-protect a page

Password-protect the vendor terms page so the procurement team can review before public release. On the page 'Vendor Terms v2' set a password 'Procure2026' and add a short note at the top telling reviewers it's for procurement only. Share the password by email to Priya in procurement and copy Sam in legal, and confirm the page loads correctly behind the password.

Before I send the password to procurement, make it simple for reviewers to access and for us to revoke. Surface where the password lives, add an expiry date or a note about when it will be removed, flag any linked assets that might still be public, and recommend a pattern for password text that is easy to type but not guessable.

I put a password on the review page and emailed the team, but a few reviewers still see the public version without entering a password. I don't know if cached pages, link variations, or CDN settings are at fault. Explain the likely reasons this happened, the immediate steps to ensure everyone sees the password prompt, and how to verify it's actually protected.

We habitually use page passwords for temporary review, then forget to remove them or rotate passwords, creating stale access and confusion. Where do we most often lose track—naming, documentation, or communication—and what one habit and one simple tracking tool would keep password-protected pages temporary and auditable?