My Resumes in AceDraft for Teams: The Student's Resume List
Gowri Shanker·Sep 23, 2026
On this page a resume is a number. There is no title column, no search box, and the list stops at the 50 newest rows. I wrote the screen, and I read its code again on 19 September 2026; everything below comes from the code, not from watching anyone use it.
Key takeaways
- This is where a student lands after signing in. The admin and moderator pages are closed to you; the editor, export, chat and Settings pages are not.
- One button per row asks your organisation for a review. The next one waits until the last is answered.
- Limitation: rows are identified by id and theme, capped at 50, with no pagination.
- Limitation: a failed load and an empty account look identical.
- When the batch expires, creating, editing, downloading and requesting all switch off. History and chat do not.
Why a student lands here
Sign-in routes an enterprise_user to /enterprise/my-resumes and everyone else to the dashboard. The route itself allows that one role, and the shared guard bounces a student who reaches for an admin page straight back to this list.
Two paths are registered: the bare one and /my-resumes/:resumeId. The component never reads the parameter, so both render the same list. The second exists for deep links that expect an id.
What the page puts in front of you
Four tiles, then a table. The tiles read Total Resumes, Avg. ATS Score, Paid Exports and Drafts, and they come from the same stats call the personal dashboard uses. If that call fails, each tile shows a dash and the rest of the page carries on.
The table columns are Resume, Theme, Created, Status, Review and Action. Resume is the internal id with a hash in front. Review shows the status of your most recent request on that resume, and N/A when you have never asked.
While it loads you get "Loading…". With no rows, "You haven't created any resumes yet." A failed request stops the loading state and leaves that same sentence, which means a broken call reads as an empty account. That one bothers me and it is still there.
Requesting a review
Press Request review and the server files a pending request against that resume for your organisation. The button then reads Requesting…, and Requested once the row comes back pending.
The server checks in order before it writes anything. An expired batch is refused with a message telling you to renew or migrate in Settings. A session with no organisation on it is refused. A resume id that is not yours comes back as not found. A request already pending for the same resume is refused with "A review request for this resume is already pending."
So the rule is one open request per resume, and no ceiling after that: once a moderator answers, you can ask again. What happens on their side is a separate screen with its own queue.
View history opens a panel under the row and loads that resume's past requests once, then keeps them. It shows "Loading history…" while fetching and "No review requests yet for this resume." when there are none. Each entry carries its status, when it was requested, when it was answered, and the moderator's name once one is assigned. Under the list sits a line pointing you at your chat thread, because the written feedback lives there and never on this page.
Edit and Download
Edit sends you to the enterprise editor for that resume id, showing Opening… on the way.
Download fetches the saved resume first, stores what the export page needs, then loads that page as a fresh document. Two things stop it: a fetch that fails gives "Could not load this resume — please try again.", and a resume with no rendered content gives "No exportable content found for this resume." The page's own subtitle says plainly that exporting uses your batch credits.
Opening this list also wipes leftover per-resume storage from an abandoned draft or export, so an old score or preview cannot attach itself to the next resume you open.
When the batch expires
Active means you hold at least one seat on a batch account whose expiry is either empty or still in the future. The page asks the server for that answer on load.
If the answer is no, + Create a resume turns into a dead button, Edit, Download and Request review all go disabled, and an amber notice appears pointing at Settings to migrate to a personal account and keep your resumes. Typing the editor URL yourself is caught by a second guard that returns you here.
If the check errors, it fails open and the buttons stay live. The server is the real boundary; this is only the polite version of it.
Use this if you are a student in a batch who wants a moderator to look at a specific resume, or you want your export and edit buttons in one place.
Skip this if you are looking for the moderator's written notes. Those are in chat, and this page only ever tells you a request exists.
Related pages
Comments
No comments yet. Be the first to comment.