Key terms
Learn the core Edmissa terms used throughout the documentation.
These terms are used across Edmissa documentation.
| Term | Meaning |
|---|---|
| Lead | An incoming record from an integration or lead capture source before it is converted. |
| Student | A student profile used to store details, ownership, activity, and related work. |
| Application | A record for a student's application to a program, institution, intake, or service. |
| Pipeline | A configured workflow that defines the stages an application moves through. |
| Stage | A step inside a pipeline. Stages can have checklists, permissions, and requirements. |
| Form template | A configured form layout used to collect student or application information. |
| Field | A configured data point shown on student or application forms. |
| Document type | A configured category for files your team collects or reviews. |
| Task | A follow-up or action item assigned to a user. |
| Location | A branch or operating location used for access, assignment, and reporting. |
| Common layer | Shared product behavior that applies across brands, industries, and regions. |
| Brand layer | Edmissa-specific language, positioning, navigation, and examples. |
| Industry configuration | Study abroad settings and defaults for student recruitment agencies and consultancies. |
| Country and region configuration | Local settings that differ by operating market, branch, or region. |