Bootcamp portal

A bootcamp portal is where applicants apply from a public page, admissions moves each application to a decision, students hand in weekly projects, and instructors grade each one with written feedback.

Pattern: Requests

Describe it to Pory

“We run a 12-week coding bootcamp. People apply publicly, admissions reviews applications, and once in, students hand in weekly projects that instructors grade with feedback.”

Viewing as

Apply

Applications & weekly submissions

Apply

Powered by Pory

In plain English

What is a bootcamp portal?

A bootcamp portal is where applicants apply from a public page, admissions moves each application to a decision, students hand in weekly projects, and instructors grade each one with written feedback. It follows the Requests pattern: someone submits, someone decides, it moves through statuses. Pory generates it from a plain-English description, with a login for each role (student, instructor and admissions) that shows only what that role should see, and flat pricing with unlimited students.

What it does

01

Would-be students apply from the bootcamp's own page, no account needed

Applications came through a form tool, then got pasted into a tracker by whoever had time on Friday. In Pory an applicant picks a track, says what they do now and why they want in, and the application lands as Applied. Admissions stops copying rows between two tools that never quite agree.

Public pages & formsDone by: Student
02

Admissions moves each applicant from Applied to Interview to a decision

With applicants spread across an inbox and a spreadsheet, nobody was sure who had been interviewed. In Pory admissions sees every application as a card under its stage and drags it along: Applied, Interview, Accepted or Declined. The Monday stand-up stops being a roll call of who emailed whom.

Board by statusDone by: Admissions
03

Students hand in each week's project in one place, repo link attached

Weekly projects arrived as Slack links, zip files and the odd Drive folder nobody had permission to open. In Pory a student files the week's project with the repo link, any files and a line on what they'd do differently, then sees whether it's been graded. Instructors stop hunting three apps for Week 3.

Forms to submit a recordDone by: Student
04

Instructors leave a result and written feedback on every project

Feedback used to live in a DM that scrolled away before the student had read it properly. In Pory the instructor opens the submission and files a result — Exceeds, Meets or Not yet — with written feedback that stays on that project's record. When Week 5 builds on Week 2, the Week 2 feedback is still right there.

Notes & scores on a recordDone by: Instructor

The parts every portal is built from

Pory generates a portal from these pieces and wires the permissions between them. The same parts run a grant round, a help desk, and a tenant portal — only the names on the pages change.

Collect

Forms

Signed-in or public, with typed fields and file uploads. A form files a record; it doesn't start an email thread.

Public pages

An application page, a notice board, an open directory — pages and forms anyone can use without signing in, on your domain.

Self sign-up

People create their own account and land in the role you chose for them.

File attachments

Upload and view files on the record they belong to — not in a folder named FINAL v2.

Decide

Approve / reject with a reason

Decision buttons for whoever may edit the status. Who decided, when, and why stays on the record.

Status tracker

“Where's my request?” answered as a progress bar on the submitter's own page.

Board by status

Cards in columns. Drag a record to move it along.

Checklists

Task lists ticked off per record, in its detail view, with progress — onboarding runs, inspections, opening duties.

Assign to a person

Name who a record is for and it lands on their list, and nobody else's.

Notes & scores

A reviewer's score, a coach's feedback, a clinician's note — kept on the record it belongs to, never lost in a thread.

Reminders by date

Renewals, expiries and overdue work, in an in-app inbox and by email.

Share

Tables

Search, filters, sorting, inline add and edit — the spreadsheet, minus the sharing accident.

People directory

Portraits, names, and roles from a table, shown only to the roles allowed to see them.

Calendar

Records on a month or week view, by date.

Gallery & image grid

Records as cards or photos.

Detail view with related items

Open a unit, a pet or a listing to see its details and everything tied to it — requests, visits, offers. Share it by link; edit, change the status or add a related item from there.

Notices & info pages

Check-in details, benefits, updates — a page for a role to read.

Counts, totals & averages

Live figures over the records a viewer is allowed to see.

Control

Who sees which records

Each person sees their own records, the ones assigned to them, their team's or the ones they manage. Fields can be hidden per role. Generated from your description, not set up field by field.

No-Password Doors

A sign-in link by email, by default. Password sign-in if you'd rather.

Your brand

Your domain, your colours, your logo. Members see you.

Frequently asked questions

Your bootcamp portal, live today.

Describe it in a sentence and send the invite. Unlimited students, flat price.