Fictional sample fields
Field 1 · Parent or guardian nameValue not shown
Field 2 · Class seeking admissionValue not shown
Field 3 · Supporting documentValue not shown
Feature identity
Custom Forms
An illustration, not a screenshot. The interactive example below shows what this capability actually does.
Example view
Automation & ComplianceCustom Forms in a school workflow
Build your own fields
Parent or guardian nameValue not shown
Class seeking admissionValue not shown
Supporting documentValue not shown
Product scope
What it does
Salesforce-grade extensibility rare in school ERPs: build dynamic forms (8 field types, conditional show/hide logic enforced server-side, an anonymous-by-construction option), add governed custom fields to the student record with PII flags and role visibility, and even create whole custom objects — Events, Assets, Clubs — with their own records.
The school problem
School teams need a dependable way to handle Custom Forms: Build your own fields. The required records, assigned roles and review boundary must remain explicit.
Day-to-day work
How your school uses it day to day
Build your own fields.
- Form builder with drafts, publish windows, single-response dedupe and CSV export
- Conditional show-if logic — hidden fields drop their values server-side
- Custom fields with a PII flag for supported AI-context exclusion and per-role visibility
- Tenant-created custom objects with a drag-drop page-layout builder
Operational result
What your school gets
Published forms, governed custom student fields and tenant-defined objects that extend supported school records without code changes.
Access and ownership
Who typically uses it
- Tenant administrator
- Process owner
- Form designer
- Authorised respondent
- Data reviewer
What each person can actually see depends on the role you give them and which classes or records you assign.
Availability and setup
What to confirm before rollout
Automation & Compliance catalogue capability
- Defined field purpose, audience, visibility and retention rules
- Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.
Connected operating context
Available workflows
These are the documented neighbouring capabilities that school teams may review with this module. A related page does not imply that every hand-off is automatic or enabled in every plan.
- Document ManagementStore and retrieve files
- Student AdmissionDigital enrollment workflow
- Student ReportsProfiles and progress
Buyer questions
Frequently asked questions
The questions school owners ask before they subscribe: what it does, who can see it, and what to set up first.
Does Custom Forms work on its own?
Document Management, Student Admission, Student Reports are the documented neighbouring capabilities. They help a school evaluate the surrounding hand-offs, but a related page does not mean every integration is automatic or included in every plan.
What should our school prepare before enabling Custom Forms?
Defined field purpose, audience, visibility and retention rules. Confirm plan scope, role permissions, data dependencies and any provider or migration prerequisites during the demo and proposal.
Is AI used in Custom Forms?
No AI capability is asserted for Custom Forms. Its documented work remains controlled by school records, roles and permissions.
How do we confirm the plan and implementation scope?
Plan inclusion and rollout scope depend on the live plan matrix, readiness state and your school's written proposal. The demo team will confirm the applicable boundary before rollout.
Related evaluation guides
See it in your school context
Run custom forms the connected way.
See how this workflow fits your school's current records, roles, plan and rollout requirements.