Guides / How to build

How to Build an Employee Onboarding Portal: Checklists, Documents and First-Week Plans

How to build an employee onboarding portal: checklist templates, tasks for HR, IT and managers, secure document uploads, and progress tracking.

Mythex Team · 2026-09-29 · 5 min read

An employee onboarding portal turns "welcome aboard, see you Monday" into a plan. The new hire gets one page with everything they need before and during their first weeks — start time, who to ask for, documents to return, what they'll do each day — while HR, IT and the manager each get their own tasks with due dates, so the laptop, accounts and desk are ready on day one. To build one you need checklist templates by role, a copy of that checklist per new hire, tasks assigned to different people, secure document collection, and a view showing what is overdue. An AI app builder can produce a working version quickly; the thought goes into the checklist itself and into protecting personal documents.

What the portal needs

Data

The core idea is templates copied per hire. Each new starter gets their own set of tasks created from a template, with due dates calculated from their start date ("IT: order laptop — 10 days before start"). You can then adjust one person's checklist without changing the template.

Pages

• New hire: welcome page (start time, address, who to ask for, first-week plan), my checklist, document uploads, key policies and contacts.
• Manager and buddy: their tasks for each new starter and progress at a glance.
• HR: all new hires by start date, overdue tasks across everyone, templates, documents to review.
• IT: equipment and account tasks, sorted by start date.

Permissions

New hires see only their own portal. Managers see their own starters. IT sees its tasks but not personal documents. HR sees everything. Personal documents — ID, contracts, tax forms — are the most sensitive data in the app: private storage, HR-only access, and a plan for deleting them after the required retention period. Data protection and record-keeping rules for employee documents vary by country, so check them with an adviser. Role-based access control covers enforcement.

Decisions and trade-offs

How new hires sign in

New hires don't have a work email before day one. Options: a magic link sent to their personal email, a one-time setup link that creates a password, or giving portal access only once work accounts exist (which loses the pre-start window). Magic links are the usual choice.

Collect documents or link to other systems

The simplest portal only tracks that a document was done in another system ("Sign contract in e-signature tool — done"). Collecting files yourself is convenient but brings storage, access and retention responsibility. Contracts are usually best signed in an e-signature product, and bank and tax details handled in payroll.

How much content

A portal is not a wiki. Link to your knowledge base or handbook for policies, and keep the portal about this person's next steps.

Automated reminders

A daily email of overdue tasks to each owner keeps things moving. It needs something that runs on a schedule; if your hosting doesn't offer scheduled jobs, an external scheduler can call an endpoint in your app, or HR can press "send reminders" from the dashboard.

A first prompt that works

Build an employee onboarding portal for a 120-person software company. HR creates a new hire with name, personal email, role, team, manager, buddy, start date, location and a template (Engineering, Sales, Operations). Each template has tasks with an owner role (new hire, HR, IT, manager, buddy), a description and a due date relative to the start date; creating a new hire copies the template into their own task list with real dates. New hires sign in with a magic link sent to their personal email and see a welcome page (start time, office address, who to ask for, first-week schedule), their checklist, and uploads for required documents. Managers, buddies and IT see only their own tasks for each starter. HR sees all new hires by start date, overdue tasks, and uploaded documents. Documents are stored privately and visible only to HR. Roles: new hire, employee, HR, IT. Save everything in a database. Friendly, welcoming design for the new-hire pages; plain and dense for HR and IT.

Build steps

1. Write the checklist on paper first. Ask the last three hires what was missing on their first day, and ask IT what always arrives late.
2. Templates and new hires, with the copy-and-schedule logic tested against a few start dates.
3. Task views per role, each showing only what that person has to do.
4. New-hire portal: welcome page, checklist, resources.
5. Sign-in by magic link for new hires and your chosen login for staff.
6. Document uploads into private storage, HR-only. See adding file uploads.
7. Notifications and reminders through your own email provider.
8. HR overview of overdue tasks and upcoming starters.
9. Pilot with the next two hires, then add offboarding using the same pattern.

Common mistakes

• Starting on day one. The best onboarding work happens in the two weeks before.
• One giant checklist for everyone. Use templates per role and let HR remove tasks that don't apply.
• Tasks with no single owner. "Team to set up accounts" means nobody does it.
• Personal documents in public or shared storage. Keep them private, limit access, and delete them on schedule.
• Turning the portal into a handbook. Link out to policies; keep the portal about next steps.
• Forgetting the manager. The manager's first-week plan matters more to the new hire than any form.

When a ready-made product is the better choice

If you already use HR software, check its onboarding features first: it may already have templates, e-signatures and a link into payroll and employee records, which a custom portal would have to integrate with. Companies hiring in many countries also benefit from products that maintain country-specific paperwork.

A custom portal fits when onboarding is a real bottleneck but your HR tool's version is rigid, when tasks span IT, facilities and client-specific steps it doesn't model, or when you want onboarding, leave requests and other internal requests in one place. It is also a common first internal tool for growing teams.

Building it with Mythex

On Mythex you describe the onboarding workflow in chat and the agent builds it in a live preview, adding a Postgres database for hires and tasks and project file storage for uploads when the app needs them. The internal tool use case in the docs lists an onboarding checklist as one of the first tools that usually pays off. Magic-link sign-in and reminder emails go through your own auth and email providers — Mythex has no built-in end-user login or email sending — with keys stored as project secrets. Use /test to walk through creating a hire and completing tasks before you publish.

For a starting prompt, try the org chart directory or hiring pipeline tracker templates, then extend them into onboarding.