This is the shared form job set up for new staff: answers land as records in their own collection, only the people invited can open it, and each person proves who they are by a link sent to their email.
Video tutorials for this topic
Ask first
- What should the new hire fill in? The usual set is full name, email, phone, start date, role, emergency contact (name and phone), and a copy of their ID. Ask what to add or drop.
- Which are required? At least name, email, start date and the ID copy.
- Who is the new hire? Name and email. Never guess an address.
- Is there a deadline? It becomes the form's closing date.
- Who should be told when it comes in? A staff email for the notify address.
Steps
1. Collection builder — the onboarding record type
Create a collection (e.g. name staff_onboarding, title "Staff onboarding"). The name is lowercase letters, digits and _, at most 20 characters. Fields:
fullName,phone,emergencyContactName,emergencyContactPhone— textemail— emailstartDate— daterole— select, with the business's roles as optionsidDocument— file upload (allow multiple if front and back are separate)- mark the agreed fields required
Save the collection itself (the builder's Save, or a collection record create); changing the builder on screen without saving keeps nothing.
Hands on: the collection's name.
Check: open it (/collection-builder with name = the collection name); every field is there with its type, and the ID field is a file upload.
2. CRM Forms — the form, invited people only
Create a CRM form (crm_form) on that collection:
| Field | Value |
|---|---|
name / title | e.g. staff-onboarding / "Staff onboarding" |
collection | the collection name from step 1 |
accessMode | participants — only invited people can open it |
authenticationType | magic-link — they confirm by a link sent to their email |
endDate | the deadline, if any |
email | the staff address to notify of each submission |
submitMessage | the thank-you text |
Hands on: the form's name and sk.
Check: open it (/crm-form with uid = the form's sk or name). Setup shows the collection; Access shows participants and magic link.
3. Add the new hire as a participant
Add the new hire to the form's participants as { name, email }. Adding a participant sends nothing. Their personal access code is made when they are invited.
Check: the form's participants list shows the new hire. If the person wants it tried first, fill it in once as a @test.local participant, confirm the record appears in the collection with the file attached, and delete the test record and participant.
4. Send it to the new hire
Stop: this emails a real person. Show the address and say what they will get — an invitation (template form-invitation, or the form's own invitation template) with their own link to the form — and wait for yes.
Real action: POST crm/form/<form name>/invite with { emails: [<the new hire's email>] }. Always pass emails — without it, every participant on the form is invited (and anyone already invited gets a reminder). Each person's link is <site>/form?form=<name>&code=<their code>.
Check: the participant now has an access code and an invite count.
When it's done
Tell the person: the collection (where answers land), the form and who can open it, the deadline, who is notified, and whether the new hire was invited. Open the form on its own screen. Their answers and ID copy will appear in the form's Submissions and as a record in the collection.
Giving the new hire a staff login is a separate job (a staff invitation with a role): Invite staff and set their roles. Ask before doing it.
