A talent application is several steps a person goes through in order. In Appmint that is one Content Studio post with pages: each page is a step, and a page can hold a form from a collection, media, questions or a quiz. Pages can open only after the earlier one is done, and staff can review and approve a page.
Ask first
- What details do you need? (name, contact, age range, location, discipline…)
- What work should they upload? Video, audio, photos — how many of each, and any length or size limit.
- The five words: what they describe (themselves? their art?) — one word each, or a short phrase each.
- The quiz: the questions, the choices and the correct answers, and the pass mark if there is one.
- Who applies? Open to anyone with the link, with a code, or only invited applicants (their emails).
- Who reviews? The staff who approve each step, if any.
Steps
1. Collection builder — three record types
Create these collections (one record per applicant in each):
| Collection | Fields |
|---|---|
talent_application | the details asked for (name, email, phone, location, discipline…) |
talent_work | video files, audio files, photo files (file fields, multiple allowed), plus a short note per upload if wanted |
talent_words | word1 … word5 (short text, required) |
Hands on: the three collection names. Check: each collection opens in the Collection builder with its fields.
2. Content Studio — the application post
Create a post (Content Studio → New) titled for the application. It is a multi-page post: add four pages, in this order.
- Your details — Add → Form from a collection →
talent_application. - Your work — Add → Form from a collection →
talent_work. Say what to upload above the form. - Five words — Add → Form from a collection →
talent_words. - Quiz — Add → Question / Multiple choice for each question. Put the correct answers in the page's answer key (never in the page text). Set the pass mark if there is one.
Outline and order: in Settings → Course outline, make each page open only when the one before is done (a condition on the page: previous page, done). If staff must approve the work before the quiz, add the condition page 2, approved.
Reviewers: on page 2 (and any page staff must approve), set the reviewers.
Hands on: the post's id/slug and its link.
Check: open the post on its own screen; go through it once as a test applicant (a @test.local address): each page saves into its collection, page 2 accepts a file, the quiz marks correctly. Remove the test records.
3. Access — who can apply
In the post's Settings → Access: open (anyone with the link), code (with the access code) or participants (invited only), plus sign-in if applicants must prove who they are, and the opening/closing dates.
4. Invite applicants
Settings → Learners → add the applicants by email (enroll), with the invitation email.
Stop: before inviting, show the addresses and the invitation text; wait for yes.
Check: the Learners roster lists each applicant.
Reviewing applications
Staff open the post's review queue: each applicant's pages, their details, their uploads to watch or listen to, their five words and quiz score — and approve or ask for changes per page.
When it's done
Tell the person: the post (and its link), the four pages in order, which collections hold the answers, the quiz pass mark, who can apply, who reviews, and who was invited. Open the post on its own screen.