What is in the StudentLife OS hiring pipeline?+
Four views over the same applicants: a Pipeline board of drag and drop stage columns, a dense sortable List, an Insights panel with the funnel and response breakdowns, and Automation rules. Around them sit a deep filter engine, an optional AI ranking, self booking interviews, offers with deadlines, and a keep in touch talent pool. One filter applies across every view and every export.
Can I move applicants without emailing them?+
Yes. Silent review is a toggle on every focused opportunity. With it on, dragging applicants between stages sends nothing, so you can triage the entire pool privately. Emails go out only from the actions you choose: Confirm receipt, interview invitations, offers, automation rules you set up, and Mark recruiting complete.
Which kinds of opportunities run through the pipeline?+
Nearly all of them. Internships, jobs, scholarships, programs, and research use apply then get hired or awarded. Events, campus tours, hackathons, conferences, and volunteering use register then attend. A food pantry is a one tap claim per cycle. Discounts are the single exception: a student redeems a code and a link directly, so there is no applicant list to review.
Does the AI ranking see demographics?+
No. The AI never sees race, gender, veteran or disability status, first generation or income, or pronouns, and school prestige is not a ranking input. Ranking is blind to that data by construction. The AI also never moves a candidate and never sends a message. It ranks when you ask it to and you make every decision.
Can I search what applicants actually wrote on my form?+
Yes. Focus a single opportunity and you can filter on the answers applicants gave on its application form, field by field. The form response strip shows a breakdown per question, and one click turns any answer into a filter that narrows the board, the list, and any export.
Is this the same pipeline for organizations, schools, and departments?+
Yes. Every view, control, and stage in this guide works the same way on all three sides, which is why this one guide serves all of them. Inside an account, actions are gated by team role and enforced on the server, so a teammate only sees and can run what their role allows.