Playbooks
Stock a key vault
Load Steam keys or your own codes, and pick the right Steam variant.
Hand out game keys
Give each player a Steam key or a code of your own as they join.
Give keys away with a redeem link
A standalone claim link, with screening, outside any playtest.
Migrate your key inventory
A pile of Steam keys or codes, into vaults.
System vaults and custom vaults
A system vault gives each player their key after the build step and before the session briefing. You still control which screen the key appears on.
Limits
Keys per import and key length are product bounds, the same on every plan. How many keys a single vault can hold, and how many vaults you can have, come from your plan.
Key vault limits by plan
Vaults per studio and keys per vault, on each of the five plans.
Announcing a vault
A custom vault can post its own redeem link to your Discord community when it publishes. Turn Announcement on in the vault’s About tab and write the message on the Announcement tab.Key vault announcements
What the message carries, what it costs, and how the button follows a link reset.
The life of a key
Status comes from what has happened to the key, not from anything you set yourself. Unassigning sends an assigned key back to available. Once a key is redeemed, it stays redeemed.Next steps
Keys
Key types, the four Steam variants, and how to load a vault.
Redeem links
Publish a custom vault and let recipients claim a key themselves.
Vault analytics
Watch keys move from available to assigned to redeemed.
Stock a key vault
Playbook: load your keys and check you have enough for the run.