Key terms
Learn the public Edmissa terms used across student recruitment workflows.
Use these terms across Edmissa docs and agency training so users describe the same work in the same way.
| Term | Meaning |
|---|---|
| Edmissa | The student recruitment platform your agency uses to manage Leads, students, applications, documents, and follow-ups in one workspace. |
| Workspace | The Edmissa area where your agency's users, settings, student profiles, applications, tasks, documents, and reports live. |
| Lead | Incoming student interest from a lead capture channel, integration, form, or webhook before the team decides what to do next. |
| Lead source | The channel or setup that created a Lead, such as a public form, connected ad form, or webhook. |
| Student | The person your agency is counseling or supporting. |
| Student profile | The complete workspace profile for a student, including contact details, study context, ownership, location, activity, documents, tasks, and related applications. |
| Application | Work connected to a student's program, institution, intake, visa process, enrollment step, or other service your agency manages. |
| Pipeline | A configured application workflow. A pipeline defines the stages an application moves through. |
| Application stage | A step inside a pipeline. Application stages can include forms, checklists, requirements, approvals, access rules, and notifications. |
| Form template | A configured form layout that controls which fields users complete when creating or updating student profiles or applications. |
| Field | A configured data point shown on a form, list, profile, application, filter, or report. |
| Student field | A field that stores information about the student as a person, such as contact details, nationality, study preferences, or source context. |
| Application field | A field that stores information about one application, such as program choice, institution, intake, deadline, offer status, or visa outcome. |
| Document type | A configured file category your team collects or reviews, such as passport, academic transcript, offer letter, or visa file. |
| Checklist | A reusable set of steps users complete as part of stage work, task work, or approval review. |
| Task | A follow-up or action item assigned to a user, usually with a due date or clear owner. |
| Follow-up | The next action needed to keep a student or application moving, often tracked as a task. |
| User | A person with access to the Edmissa workspace. |
| Role | A named set of permissions that describes what a user can do. |
| Permission | A rule that allows or limits an action, such as viewing, creating, updating, approving, or deleting work. |
| Scope | The range of work a user's access applies to, such as assigned work, location-based work, or wider workspace access. |
| Location | A branch or operating group used for ownership, access, assignment, and reporting. |
| Integration | A connection between Edmissa and another approved tool or channel. |
| Automation | A configured action that helps reduce repeated manual work. |
| Notification | A message that alerts users about work that needs attention. |
| Dashboard | A reporting view used to review progress, activity, workload, or performance. |
| Shared settings | Settings or behavior that work the same way across the platform. |
| Edmissa defaults | Recommended setup choices for education agencies and consultancies using Edmissa for study abroad work. |
| Country and region configuration | Settings that differ by operating market, branch, destination, or local process. |
How to choose the right term
Use Lead before a user has reviewed incoming student interest and decided what should happen next.
Use student profile when talking about the complete workspace profile for a student. Use student when talking about the person.
Use application for work tied to a specific program, institution, intake, visa process, enrollment step, or service. A student can have more than one application.
Use workspace after Edmissa has already been introduced. For example, "invite users to the workspace" is clearer than repeating the full product name in every sentence.