This article describes the key features of Swif's team-level onboarding checklists and how employee onboarding status works once the checklist is moved into Settings → Teams.

Swif lets you define custom onboarding checklists per team and (optionally) per user group within a team. These checklists drive the employee’s Onboarding / Active status and surface as a status tag on the employee card/list.

This update moves onboarding configuration away from a single, organization-wide checklist and makes onboarding:

Instead of a global onboarding checklist at the organization level, onboarding is now configured under Teams:

From here, admins manage onboarding and offboarding templates for each team.

In Settings → Teams → Onboarding Templates, you can:

The templates table includes a User Group column and a tooltip explaining how templates behave for teams vs user groups.

Note: Offboarding templates are still supported, but the core of this feature focuses on onboarding. Offboarding enhancements may be covered by separate updates.

Swif supports two scopes for onboarding templates:

Use this when you want one universal checklist for all new hires in that team.

Use this when different roles within the same team require different onboarding steps.

Previously, there was a single, organization-wide onboarding checklist under Settings → General → Onboarding Checklist.

With this update:

This gives each team full control over its own onboarding process.

Swif includes a system default onboarding flow, but it should no longer block your custom team checklists.

With this change:

In practice, this means:

Employee status is now directly driven by whether the team has a customized onboarding checklist:

A status tag is shown on the employee card/list (as per the “Onboard Employee 1.0.0” Zeplin design). This tag:

To avoid confusion once an employee is fully onboarded:

Admins rely instead on the status tag and checklist completion rather than manually re-triggering onboarding.

The employee’s status changes based on completion of the team’s checklist:

When a team has at least one onboarding checklist template applied:

This ensures the employee only becomes Active once all required onboarding tasks for that team are completed.

If there is no custom checklist defined for a team:

In other words, system default onboarding has no impact on status when there is no team-level checklist. The employee remains Active by default.

To help teams stay on top of onboarding:

Key points:

After this feature is released, two important behaviors ensure a smooth transition:

These rules guarantee that only team-level checklists control whether an employee is considered “Onboarding” or “Active”.

The feature includes handling for common edge cases:

From the admin’s perspective, the experience is:

With team-level onboarding checklists:

This provides a more flexible, accurate, and transparent onboarding experience for both admins and employees.