The GM side of the requests players send from the taskbar (see Getting Help). They land in Admin Tools → Player Requests, which is also the Requests tab of Manage Content.
Most requests are deadline extensions now, because that's what the player's form asks for. Each one names the module, opens with the date the player is asking for (Extension requested until: followed by the date) and gives their reason.
Reading the Queue
Each request is a card: the player's picture, name and email, the subject, when it was sent, its status and the full message. Use the search box to find a player or a module, and the status buttons to narrow the list: All, Pending, Read, Resolved and Dismissed, each with its count. The list shows the 200 most recent requests; the counts are always the true totals.
Acting on a Request
- Mark Read — you've seen it and you're on it.
- Resolve — dealt with.
- Dismiss — you won't be acting on it.
- Reopen — puts a resolved or dismissed request back to Pending.
Before you press one, you can type an Admin note in the box on the card. It's saved with the status change, and the player sees it on their My Requests page as the admin response. Tell them yes, no, or what happens next.
A request is only a message. Resolving it doesn't change any dates by itself; granting the extension is up to you.
A Rhythm That Works
Nothing is emailed when a request arrives or changes, so check the queue regularly. Treat it like any support queue: skim what's new, act on it, then mark it Resolved or Dismissed with a note, so Pending stays a true "still needs attention" list rather than a graveyard of old tickets.
NPCs can read every request but can't change a status or write a note.