Moderator Answer Queue in AceDraft for Teams

When the request behind this page fails, the page prints "Nothing assigned to you yet." Same words, same grey text, as a queue that really is empty. A moderator should know that before they trust a quiet morning. I haven't watched this page run. I read its code on 19 September 2026, and everything below is what the code says.

Key takeaways

The route is moderator-only. The side menu calls it Assigned; the page heading reads Assigned to me.
The server does the filtering, so the list only ever holds requests carrying your id.
Each row opens the review page for that request, which is where the answering actually happens.
Limitation: a failed load and an empty queue print the same sentence.
Limitation: one request for 100 rows, fired as the page opens. No paging, no refresh, no filter, no search.

Prerequisites. A signed-in moderator account and at least one review request an admin has pointed at you. Nothing on this page hands you work.

Who can open the assigned queue?

Moderators, and only moderators. The route names that single role, and the guard bounces anyone else to a page their role can see: an admin lands on the dashboard, a student on their own resumes. The server takes the same view from a different angle. When a moderator calls the message list, the query adds a condition tying every row to their own user id, so there is no version of that call that returns somebody else's queue.

One load, one hundred rows

The page asks for page 1 with a limit of 100 the moment it opens, then stops. The backend would clamp anything larger to 100 regardless. Rows come back newest first.

There is no paging control and no refresh button. A request assigned to you thirty seconds ago appears when you leave the page and come back, not before. If the call fails, loading simply ends and the list stays empty, which is where that opening sentence comes from.

Reading a row

Five columns. Student shows the name above the email, with a dash standing in when no name was stored. Resume is an internal id behind a hash. Status is a single word in a pill, green once it reads answered and amber for anything else. Requested is a short date and time. The last column has no header and holds the Review button.

Answered rows stay put. Nothing here sorts, hides or searches, so what you're looking at is every request ever assigned to you, in the order they arrived. Your dashboard splits the same set into a pending count and an answered one, which is the faster way to know whether there's work waiting.

The resume id is honest and tells you nothing about the document. When one student has two rows open, the Requested column is what separates them.

So where does the answering happen?

Not on this page. Review opens the request's own page, and that is where the student's resume, the editing form and the button that closes the request live. The server checks you again on arrival: it loads a request for an admin, or for the moderator whose id is written on it, and returns "Review request not found." to anyone else. You also get a seat in that student's chat thread, granted at the moment an admin assigned you.

What the Mark answered button changes

One column. The status flips to answered and the update time moves. The resume is untouched by that click, and no text travels to the student with it, because the conversation runs through the chat thread rather than through the request record.

The button then reads Answered and refuses to fire again.

Leaving a finished review unmarked has a cost the student pays. A second request on the same resume is refused while the first one is still pending, so a review you answered in chat and never marked keeps that student locked out of asking again.

Use it, or skip it

Use this as your inbox: open it, read the oldest amber row, press Review. Skip it when you're hunting for a request nobody has assigned to you, because this page cannot see one. Those live on the admin's Review requests page, and it takes an admin to move one your way.

The Assigned Queue in AceDraft for Teams: How a Moderator Finds and Answers a Review Request