Send access to students

Pending deliveries is the list of students who should get access codes: waiting, scheduled, sent, or stuck.

​

Where to find it

Go to Program Dashboard → Courses → Pending deliveries.

• Program owners can release, resend, bulk release, and hand-enter.
• Instructors can view the list.

The Courses menu can show a badge when people are waiting on manual release or Waiting for codes. You can also open one student: Students → select the student → Access.

​

Filter tabs

Refunded or withdrawn rows show as Refunded, Withdrawn, Transferred, or Taken back. They stay under All. They are not in the Failed tab.

​

What each row shows

• Student
• Course
• Seat — for a multi-seat purchase, Seat 1, Seat 2, and so on
• Status
• Timing — a short line such as Reserved, waiting manual release
• Actions — Release, Resend, View

​

Release (send the codes now)

Use Release when timing is When staff sends it, or when you want to send a scheduled code early.

1. Find the row (or open View).
2. Click Release.
3. The student gets the access email. The values appear in Your Credentials.

To send several at once, check the boxes and click Release (N). Release only works if:

• Unique codes are in stock (or already held for that student)
• Shared values are filled in (Course ID, website, and so on)

If a shared value is missing, send is blocked until you fill it in on the course or cohort.

​

Resend the email

Use Resend when the student already has access in the dashboard but cannot find the email.

• Works for Released rows
• Also works if the email failed but the codes are still on the dashboard
• Does not work after a refund took the access back

​

Hand-enter a code

Use this when one student is missing a code and you do not want to wait on a full import. Example: the vendor emailed you a replacement URL for Jordan only.

1. Open View on that delivery.
2. Choose Hand-enter code.
3. Type the unique field values.
4. Save. If the delivery was waiting, it can release right after.

Hand-entered sets are marked Entered by hand in inventory history.

​

Out of stock (Needs fulfillment)

If a student enrolled or bought when you had no unused codes:

1. The row shows Waiting for codes / Needs more codes.
2. Your team gets an email: [Action needed] Credential stockout: .
3. The student is told the organization will send codes when ready. They are not told you ran out.
4. Import more codes under Access codes. Waiting rows are filled automatically from the new stock.
5. After that, send follows the course timing (immediate, scheduled, or wait for Release).

​

Open a delivery (the detail sheet)

View opens the full record:

• Each field and its value (owners see values; timing still hides unsent values from students)
• Whether the unique code is in stock, held, sent, or needs a check
• Email history
• Actions: Release, Resend, Hand-enter, and after a take-back, what happened to the code

​

Student profile → Access

On a student record, the Access tab lists that person’s courses:

• Status chips
• Release access
• Resend access email

Same tools as Pending deliveries, focused on one person.

​

Who can do what