First day setup checklist
Complete the essential Edmissa setup steps before a new agency team starts daily work.
Use this checklist on the first setup day for a new Edmissa workspace. The goal is not to configure every detail. The goal is to create a clear first version that your team can safely test with Leads, student profiles, applications, documents, and follow-ups.
Before you start
Gather the basics before you configure the workspace:
| What to prepare | Why it helps |
|---|---|
| Agency name, website, address, and main country | These details support the agency profile and regional settings. |
| Branch or operating group list | These become locations for ownership, access, and reporting. |
| User list | You need names, emails, roles, locations, and manager relationships for the first invitations. |
| Lead source list | Start with the channels the team will actually review during the first week. |
| Main application workflows | Decide which pipelines are needed first, such as admissions, visa processing, or enrollment support. |
| Required student and application details | Keep the first version focused on information users truly need. |
| Document categories | List the first document types users will collect or review. |
For the recommended configuration order, use the Setup overview.
First day checklist
- Confirm the workspace basics in General settings, including the agency profile, country, and contact details.
- Review country and region configuration so market differences are planned before daily work begins.
- Create the first locations for branches, offices, or operating groups.
- Add the first users and assign the right roles.
- Review permissions and scope so users can access only the work they should handle.
- Configure number formatting for Leads, student profiles, applications, documents, and tasks.
- Add the first Lead sources that the team will use for real review.
- Create the first application pipelines with simple stage names that match the team's real process.
- Configure the first pipeline stages with only the rules needed for safe testing.
- Review student fields and application fields so the first forms collect the right information.
- Create or review form templates for student profile creation and application work.
- Add the first document types the team needs, such as passport, academic transcript, offer letter, or visa file.
- Create short checklists for important stage work, such as document review or submission readiness.
- Review notifications so the right users know when work needs attention.
- Test the first workflow by reviewing a sample Lead, creating or connecting a student profile, creating an application, uploading a document, and assigning a follow-up task.
Recommended first-day scope
Keep the first setup pass small enough to test.
| Area | First-day target |
|---|---|
| Users | Add admins, managers, and the daily users needed for testing. |
| Locations | Add the main branch or operating groups needed for access. |
| Lead sources | Add only active sources the team will review during the first week. |
| Pipelines | Create one or two priority pipelines before adding every possible workflow. |
| Fields | Use essential student and application fields first. Add optional fields later. |
| Form templates | Build the forms needed for the first Lead, student profile, and application flow. |
| Document types | Add the file categories needed for the first real application work. |
| Checklists | Start with short checklists users can complete without extra training. |
What good looks like at the end of day one
By the end of the first setup day:
- Users can sign in and see the right workspace areas.
- Each user has a role, scope, and location that matches their job.
- The team can review a Lead and decide the next action.
- The team can create or connect a student profile.
- The team can create an application in the correct pipeline.
- The team can upload a document using the correct document type.
- The team can assign and complete a follow-up task.
- Admins know which settings need more detail during the first week.
Save for the first week
These items usually work better after users test the first setup:
- Add more detailed application stage rules.
- Expand form templates and optional fields.
- Add more document types and checklist items.
- Tune notifications after users see the first alerts.
- Add automation only after the manual process is clear.
- Review reports after real activity exists.
Use the First week operating checklist for the next pass.
Related guides
| Guide | Use it for |
|---|---|
| What is Edmissa? | Understand how Leads, student profiles, applications, documents, and follow-ups fit together. |
| Key terms | Keep setup language consistent across the team. |
| Quick start | Follow the shortest path from setup to daily work. |
| Setup overview | See the full recommended configuration order. |
| Daily work | Review the work users will perform after setup. |