Turn On One Code per Person as a Page Access Gate
Use a one-code-per-person claim-code gate so each visitor must enter a unique code before opening your hosted page.
Use a one-code-per-person claim-code gate so each visitor must enter a unique code before opening your hosted page.
Who it's for
- Owners sharing demos, portfolios, or client previews with individual visitors.
- Teams that want separate access for each guest instead of one shared password.
- Anyone who needs to track which visitor has redeemed access.
Steps
- Sign in to HTMLPUT, open the page’s history, and find its access settings. See Edit page title and access settings in History for the location.
- Turn on One code per person and save the change. This adds a claim-code gate to the hosted page.
- Generate and manage claim codes for the visitors you expect. If generation is unavailable, check the page’s listing status, access gate, and available claim-code quota using Cannot Generate Claim Codes: Quota, Listing, or Gate.
- Send one unused code privately to each visitor. When they open the page, they can follow the Redeem a claim code on a public work flow to enter it.
- Track redeemed codes and issue a new code to anyone whose code has already been used. A successful code should not be shared with additional visitors.
- If the page also collects registrations or responses, connect that form to your HTML with Wire page data into your own HTML. Page data stores submitted information; it does not replace the access gate. Learn more in What page data is.
Gotchas
- Claim codes differ from shared page passwords and storage redeem codes. See How claim codes, storage redeem codes, and page passwords differ.
- Reused, invalid, or revoked codes cannot be redeemed again. Follow Claim code redeem failed: invalid, used, or revoked to resolve common failures.
- Send codes privately and collect only necessary visitor information. Review Claim codes: privacy, consent, and terms before publishing a gated form.