Portal onboarding
The first screen answers what to do next
A portal bought without an implementation partner opens on day one showing an empty window of a company that does not exist yet. The helper answers that: invite people first, and open the modules as they start to mean something. It runs two independent tracks, and a person gets exactly one.
Two independent tracksOwner: 4 steps · employee: 3Every step can be skippedOn by default
app.teamevo.co/studio/programme
Search or run a command…⌘K
Control centre
7
Kate EllisAdministrator"Employee onboarding" templateout of the box
+Learning · Task · Check-in
Dry run Validation passed
The owner's track, in order
- 1
Invite the team
A wizard on the home page takes a pasted list, one person per line with a name and an email. It is the single action that brings the portal to life, and everything after it serves that moment.
- 2
Set the portal up
Three cards: appearance, modules and a welcome message. Each one marks itself done on a real signal from the portal rather than on a checkbox.
- 3
Check that someone arrived
The step closes when a colleague has actually joined. It does not make you wait for it — the step can be skipped and returned to.
- 4
Start the portal's life
The first news post, the first thank-you, the first survey. The checkmarks accumulate in view and the step is finished by a button rather than on the first action.
- 5
The helper leaves
At one hundred per cent it shows a short congratulation and a Dismiss button, then archives itself. It does not hang around forever wearing a full set of ticks.
What the helper does
One track per person, decided by the server
The owner and administrators get portal launch; everyone else gets the introduction. The tracks never overlap, so an owner is never asked to fill in a profile and thank a colleague.
The role is resolved server-side rather than by the interface
Progress computed from the portal state
A step closes when a trace actually appears in the portal: an invitation sent, a logo uploaded, a colleague joined, a first thank-you said. Progress is recomputed from the real state each time.
Nothing that did not happen can be marked as done
Every step is skippable
Each step carries a Skip control, so the track never gets stuck waiting on something outside the person's control. The launch can be walked in five minutes or postponed and resumed.
The one non-skippable step used to be 'invite the team', which dead-ended owners; that is fixed
A companion that follows you
Leave the home page and the helper becomes a compact badge with a progress ring over any screen. A click opens a side panel with the same steps, the invitation funnel, an assistant chat and a way to reach live support.
It hides on the home page itself so the onboarding surface never appears twice
Invite the whole team in one action
The wizard takes a pasted list, normalises and de-duplicates the addresses, and applies one role to the batch. A malformed line does not break the send: every line is processed on its own.
Re-sending the same list produces no duplicates
A per-recipient result
After sending, the owner sees a line for each address: created, already invited, already working, deactivated, duplicate in the list, invalid address, send failed — and can retry only the failures.
Seven statuses per recipient
An invitation email that does not read as phishing
The subject carries the inviter's name and the company, the sender is signed as a person at that company through TeamEvo, and replies reach a human. Available in English, Russian and Kazakh.
No codes are mentioned in the email at all
One click from the email into the portal
The link opens a portal page with a single button and the person is in, with no second email and no code. Simply opening the link does not consume it, so corporate mail scanners that pre-visit links do not burn the invitation.
An expired link is re-requested by the person themselves
An invited-to-joined funnel
After sending, a cut appears: how many were invited and how many actually signed in. It is counted from the same live data as the employee list, so the funnel and the list cannot diverge.
A third 'active' stage is deliberately not computed; the panel links into HR analytics instead
A tour that cannot describe a switched-off module
The employee introduction is a four-slide carousel: news, recognition, achievements, profile. A slide physically cannot describe a module the customer has disabled.
Checked by a dedicated test in continuous integration
State kept where it belongs
Launch progress belongs to the company, so any administrator can continue it. Introduction progress is personal to each employee. The helper is collapsed with a toggle and can be brought back from the archive.
Launching the portal is the admin team's shared job rather than the personal checklist of whoever registered first
Frequently asked questions
They are different modules. This page is portal onboarding: 'I am seeing the portal for the first time, what now', measured in minutes, with content fixed by the product and always on. The employee onboarding program answers 'I started a new job, what do I do for the first few weeks', runs for weeks with dated steps and reminders, is configured by HR, and lives in the learning module at /adaptation.
Related TeamEvo capabilities
Employee onboardingThe other onboarding: a multi-week program with steps, assignees and deadlines, configured by HR.IntegrationsSSO and employee import, for when the company is ready to connect a source system.CustomizationThe appearance card from step two: logo, colors and the home page.Admin and securityRoles and permissions for the people you are about to invite.People and org structureWhere invited employees land, with profiles and reporting lines.PricingEvery module in one plan, free up to 20 employees.
Create a TeamEvo workspace
Free up to 20 employees. Paste the list of people, send the invitations, and let the helper close its own steps as the portal fills up.