Handle premium requests
Read the message a student sent with their upgrade request, grant a seat or decline it, and find out why some rows have no buttons.
Students on Starter can ask your team for a paid seat from inside the app. Their asks land in Premium Requests, with whatever message they wrote, and sit there until someone decides.
Work the queue
The columns are Name, showing the student's name over their email, Message, Requested On, Status and Batch. Requests belong to the batch you are viewing, so check the top-bar pill if one you expect is missing; see Sign in and switch between batches.
Click the eye icon in Message to open Request message. Rows with no message show a dash. What the student wrote is the only context you get, and it often says how many roles they are applying for or which feature they need.
Status is Pending, Approved or Rejected, and only Pending rows carry buttons. An empty queue reads "No upgrade requests found."
Grant or reject
Press Grant to give the student a paid seat. The button reads Granting… while it works, then the row turns Approved and the buttons go. Reject declines and turns the row Rejected.
Granting takes a seat from the batch, the same as granting from the roster, so check Premium seats remaining before a long session; see View students and grant Premium.
Rejecting leaves the student on Starter with their account intact. It is not a block, and they can ask again.
One request at a time
A student cannot send a second request while their first is pending, so duplicates from the same person never stack up in the queue. Once you have granted or rejected theirs, they are free to send a fresh one if their circumstances change.
Tips
- Work in Requested On order so nobody waits longer than they should.
- To upgrade a student who has not asked, grant it from My Students instead.
- The Batch column tells you which cohort the seat would come from.
Was this guide useful? Tell us what is missing on the contact page.