All posts

What Are Claim Codes? Gate Any Page with a One-Per-Person Code

One code, one person, one claim. When a code is used, it is spent. When you need to cut someone off, you void their code, not everyone else's.

Three doors, each with its own uniquely shaped key

A shared password has a familiar failure mode. You send one password to ten people, and from that moment you no longer control access. Anyone can forward it. You cannot revoke one person without locking out everyone else. And you have no idea who actually came in.

Claim codes fix that by giving each person their own key. One code, one person, one claim. When a code is used, it is spent. When you need to cut someone off, you void their code, not everyone else's.

What a claim code is

A claim code is a one-time code that looks like cl_…. A creator generates it, sends it privately to one visitor, and that visitor uses it to unlock something on HTMLPUT. The visitor opens the link, signs in, enters the code, and consents. That is the whole flow.

Two things a claim code is not:

  • It is not a page password. A password controls who can view a page, and everyone with the password sees the same gate.
  • It is not a plan upgrade. Claim codes never add hosting quota or change a storage plan. That is a different kind of code entirely (see the comparison below).

Claim codes are tied to consent. The visitor consents at the moment of redeeming, and the creator only collects the visitor information that is actually necessary.

Two ways to use them

1. Gate a page: one code per person. In a hosted page's access settings, turn on One code per person. From then on, each visitor must enter a unique code before opening the page. This fits demos, portfolios, and client previews where every guest should have separate access instead of one shared password. It also lets you track which visitor has redeemed access.

2. Gate a listed work: require-claim. List a work on your public page and turn on require-claim. Visitors who received a code can then claim that work. This fits creators who list works publicly but want gated claims: the work is visible on the public page, and only code holders can claim it.

Both uses run on the same system. The difference is only where the gate sits: in front of the page, or in front of claiming a listed work.

Claim codes vs passwords vs storage codes

Page password. Controls who can view a page. One secret shared by everyone; changing it locks everyone out; adds no hosting quota.

Claim code. Controls who can claim or open, one person at a time. One code per person; void one person's unused code without affecting others; adds no hosting quota.

Storage redeem code. Controls plan quota only. It adds quota or changes a plan; it never controls page access.

If you remember one line, make it this one: passwords control viewing, claim codes control claiming, storage codes control quota. Mixing them up is the most common source of confusion, and the help center has a dedicated page to keep them straight.

Where codes come from: credits

You generate codes with claim-code credits. There are three kinds:

  • Lifetime pool. A long-term pool that does not expire on a monthly cycle.
  • Monthly free credits. These refresh each UTC calendar month and do not roll over. Use them or lose them.
  • Packs. One-time purchases in sizes such as +30, +100, and +300.

Plan quotas follow the pricing tiers: Free includes a lifetime pool of 30 codes, while Plus, Pro, and Ultra include 10, 20, and 50 codes per month respectively. Packs are priced per tier. If you run out mid-launch, buy a pack from Pricing or the in-console buy flow rather than reusing codes, because a used code cannot be redeemed again.

Practical rules that save trouble

  • Send codes privately. A code is meant for one named visitor. A code shared with additional visitors will fail for everyone after the first redemption.
  • Used, invalid, or revoked codes cannot be redeemed again. If a visitor reports a failure, check whether the code was already used or voided before generating a replacement.
  • Void codes you no longer want redeemed. Unused codes can be voided; already-redeemed codes stay in history for that redeemer.
  • Unlisting stops new claims. If you unlist a work, tell redeemers their codes may no longer be valid.
  • Collect only what you need. Gated access is not a reason to harvest visitor data. Keep the consent step clean.

Who this is for

Claim codes fit anyone who shares a page with named individuals rather than the open internet: a freelancer sending a client preview, a teacher handing out seats instead of files, a team giving each guest separate access, a creator listing works publicly while keeping claims gated. If one shared password has ever burned you, this is the tool built for that exact pain.

What claim codes do not do

They do not process payments, run a marketplace, or send email blasts. They control access. How you charge for a code, if you charge at all, is your own workflow outside the gate. (Friday's post in this series goes deeper: how creators sell access to a page with claim codes.)

Start here