Keys, submissions & rewards

This is the part that actually settles a partnership: the creator gets a key, plays the game, submits what they made, and you send what you promised. Every step has a status both of you can see.

Why it works this way

Because "did we ever send that?" is the question that kills partnerships. Each reward package a partner is working on carries its own status — in progress → review requested → verified → reward sent → received — and each step is stamped. Neither side has to remember, and neither side has to ask.

Because a key is inventory, not a message. Keys are uploaded in bulk, assigned to a named partner, and tracked as available / assigned / banned. You can see who has which key and whether they've looked at it. That's also why a revealed key can never go back in the pool: once a creator has seen it, it's out in the world, and pretending otherwise would hand the same key to two people.

Because you approve the work, not a number. Verification is yours. There's no view threshold that releases a reward on your behalf — which is why declining requires a reason, and why the reward means something when it arrives.

Load your keys

Keys tab on your game. Keys live in groups: a Long-term Partnership group for the game itself, plus one per Game Event you run — so an event's allocation can't quietly eat your long-term stock. Each group header shows available / assigned / banned counts.

Paste into Keys (one per line) and press Import. Duplicates are skipped and reported ("N added · M duplicate(s) skipped"), so re-pasting a list you've partly uploaded is safe.

Below, the inventory table lists every key with its status, who it's assigned to, whether it's been revealed, and the date. From there you can move a key to another group, or push an unrevealed one back to Available.

Assign a key to a partner

Open a partner from the Partners → Approved list, then the Key tab → Assign Key. Pick from the available keys, and it's theirs.

After that the tab shows the key (masked, with an eye to reveal it your side) and one of two chips: Not yet revealed or Revealed by creator. The second is your first real signal that a partnership is moving.

If the button isn't there: either you're out of available keys — top up in the Keys tab — or the creator's organization is under review, which pauses assignment.

Review a submission

Creators submit content links against a specific reward package, so the work arrives already attached to the terms it was for. Open the partner → Rewards tab and you'll see each package with its submissions underneath.

Per submission you can:

• Mark as viewed — a quiet acknowledgement, so you can tell what you've been through.
• Like it 👍 — the creator is notified the first time, and later toggles are silent. It's the cheapest good thing you can do for someone who just made you a video.

When the creator thinks the package is finished, they request a review and its status becomes Review requested — that's your cue.

Verify, or decline

On a package awaiting review:

Verify work confirms they've done what the package asked. The status moves to Verified and the reward is now owed.

Decline work requires a reason — the field is mandatory, and rightly so. "Two of the three videos are up" is a message someone can act on; a silent decline is one they can only guess at. The package goes back to them, and they can submit again.

Send the reward

Once verified, Send reward appears. It takes an optional message to the creator — worth using, since this is the moment they find out whether "we'll sort you out" meant anything.

What "sent" means depends on the package's delivery setting: immediately after verification, on release, at the end of the event, on a date, or manually when you say so. The creator confirms receipt on their side, which closes the loop and leaves the whole exchange on the record.

Who can do this

Keys and rewards are the Rewards permission — verifying work, declining, sending, and every part of key management. Note that it's a different switch from Partners (approving people) and Games (writing the packages), so you can hand someone the job of settling partnerships without giving them the roster or the terms.

When the game ends

Archiving a game doesn't cut this short: the hub stays writable for a 30-day resolution window so keys, submissions and rewards can be settled. Key management specifically stays open even after that — the keys are yours regardless.

Next

Running a coordinated campaign around a date is the next thing: Running a Game Event.