School-level feature — managed within your school portal at
yourschool.deandesk.com.Standard sections
Profile forms are made up of standard sections plus any custom fields you add. Basic Information (name, email, phone) is always required and cannot be turned off. The rest are toggleable per audience.For child applications, first name, last name, date of birth, and grade are all required before the child record can be submitted. The validation message is: First name, last name, date of birth, and grade are required.
Customizing child grade options
The Grade picker on a child profile defaults to Pre-K, K, and grades 1–12. You can replace this list with your school’s own grade labels under Profile Form Settings → Child Profiles → Basic Information → Grade Options.1
Open Grade Options
Expand the Grade Options section under the Child Profile tab.
2
Add, rename, or remove grades
Edit the list to match the grades your school uses (e.g. “Nursery”, “KG1”, “KG2”, “Year 1”, etc.). You can mix the defaults with custom labels.
3
Reorder
Drag grades into the order you want them to appear in the dropdown.
4
Save
Save. The new list is used on every new and existing child profile immediately.
1
Open Profile Form Settings
Go to Admin Dashboard → Profile Form Settings.
2
Pick the audience tab
Use the Adult Profiles or Child Profiles tab depending on which audience you want to configure.
3
Toggle sections
Turn each optional section on or off. Changes apply immediately to all surfaces — application flow, the Profile tab in User Management, and the Child Application Manager.
Custom metadata fields
Custom metadata fields let you collect information that isn’t covered by the standard sections — anything from “preferred pronouns” to “bus route” to “scholarship status”.Field scope
Every custom field is scoped to a specific audience so you only collect what’s relevant for each user type:
You can also scope a custom field by role — applicant, parent, student, member, teacher, or admin — so the field only renders for users in those roles. This is useful for role-specific data like “Volunteer hours interest” (parents only) or “Background check date” (teachers only).
Field types
Categories
Group related fields together with categories. Each field can be assigned a category key, label, and order. Fields appear on profile pages grouped under their category heading. For example, you might create a Health & Safety category that contains “Allergies”, “Doctor’s contact”, “Vaccination record” — three different field types presented under one heading.Public vs admin-only fields
Each field has a visibility setting:- Public — the user can view and edit the field on their own profile
- Admin only — the field is editable only from the admin’s view of the user’s profile, never shown to the user
Required fields
Mark a field Required to block submission until it’s filled in. Required fields are enforced both during application onboarding and when admins edit a profile.Adding a metadata field
1
Open the metadata editor
Go to Admin Dashboard → Profile Form Settings, pick the audience tab, and scroll to Custom Fields.
2
Click Add Field
Pick the field type from the list.
3
Configure the field
Set the field name (used as the data key), label (shown to users), description (helper text), category, scope, visibility, and whether it’s required. For dropdown and multi-select fields, also enter the list of options.
4
Save
Save. The field is live immediately on every relevant profile and application surface.
Where metadata appears
Once configured, custom fields appear in the following places:Reordering and removing fields
- Drag fields up or down within their category to reorder them.
- Delete a field to remove it from the schema. Existing data on user profiles is preserved on the server but is no longer surfaced anywhere in the UI.