Messages, notifications & support

Everything that happens to you here — an application, a key, a reward, a reply — arrives in the same place: the bar docked at the bottom of every page. This is how to read it, tune it, and get a human when you need one.

Why it works this way

Because one inbox beats five. Notifications, conversations and support tickets are rendered in the docked bar and nowhere else. No page grows its own private message list, which is why read state means the same thing everywhere — something marked read is read, full stop.

Because it follows your context, not your account. The bar shows what the organization you're currently acting as can see. Switch context and it changes with you: a studio's applications aren't mixed into your creator notifications.

And because the conversation belongs to the work. Every chat is attached to something — a partnership, an event, a support ticket. Nothing lives in a private thread that a colleague can't find next year.

The docked bar

Three trays, each opening from the bottom edge:

Notifications — everything that happened, newest first. Mark all as read and Clear all are in the header, and the gear takes you straight to the settings below. An empty tray says "You're all caught up!", which is the point of the whole thing.

Messaging — every conversation you're part of: your partnership chats, event community rooms, and direct messages with the organizations you're working with. Any conversation can be popped open in a new tab if you'd rather keep it beside your work.

Support — your open tickets, with a shortcut to the full support page.

Tune what reaches you

Account → Notifications controls three separate things:

In-app notifications — the tray itself.

Opportunity alerts — the interesting one. New games and new events are announced to creators whose taste matches, and you set the bar: a minimum match score for game alerts and another for event alerts. Set it high and you hear about a handful of things you'd genuinely play; set it to zero and you hear about everything.

Email summaries — a digest rather than a message per event, sent once a day, every 3 days or once a week. Off is also an option; nothing here is required for the platform to work.

If you feel over-notified, raise your alert threshold before you turn anything off. It's almost always volume from a threshold set too low, not the wrong channel.

Getting help

Signed in: /support. Start a ticket with a Title and a Topic — General · Game Related · Organisation Related · Feedback · Other. It's a conversation, not a form: replies land in your Support tray and the ticket stays open until it's resolved. Answering a resolved ticket reopens it.

Tickets are grouped by who they belong to: your Personal tickets, then one section per organization you're in. Organization tickets are visible to your whole team — deliberately, so a teammate can pick up a thread you started. Our team typically replies within 24 hours.

Signed out, or locked out: /contact. If you can't reach /support — suspended account, lost password, never registered — that's the page that still works. It's the only support surface that doesn't need an account, so it's the right door when something has gone wrong with the account itself.

Locks and suspensions always come with a reason and a link to the ticket that explains them. If a game or organization of yours is locked, the banner points at the conversation rather than leaving you guessing.

A last word

The whole platform is built on the assumption that a partnership is a relationship you keep, not a transaction you complete. The tools above are there to make the small courtesies cheap: answering an application, saying what you liked about a video, telling someone why you declined. Those are what people remember at launch.

If something here doesn't work the way this guide describes, tell us — that's what Feedback tickets are for, and the guides get corrected the same day.