Skip to main content
This page walks a new installation through the first hour of real work. It assumes the environment has already been provisioned — if it has not, start at Deployment.
1

Sign in as an administrator

Swiss HR Easy supports two sign-in paths:
  • Microsoft Entra ID (SSO) — the normal path for staff. The installation is registered as a single-tenant app in the customer’s Entra ID.
  • Magic link — a signed, expiring e-mail link. This is how applicants and new hires reach the portal before they have an account.
The first administrator is created during provisioning. See Settings and users for adding more.
2

Set up the organization

Under Settings → Organization, record the structure the rest of the platform hangs off:
  • Locations (Standorte) — sites and their canton. The canton drives public holidays and the default sick-pay scale.
  • Teams and the org graph — who reports to whom. Manager scoping for absences, salary visibility and applications is derived from this.
  • Legal entities (Rechtsträger) — only when the installation employs people through more than one legal employer. See Legal entities.
3

Connect Microsoft 365

Under Settings → Integrations, connect the shared HR mailbox and, optionally, a Teams channel:
  • Outlook mailbox — inbound applications are scanned and attached to the right application automatically; outbound messages are sent from this mailbox.
  • Teams channel — pipeline and hiring notifications are posted here.
A read-only diagnostic at Settings → Integrations → Mailbox reports credential drift or Graph outages without needing server-log access.
4

Configure the recruitment pipeline

Under Settings → Pipeline, define the stages an application moves through and what each stage does — which e-mail template fires, which tasks are created, and which documents are requested. Stage instructions and templates are authored per locale (de / fr / en).Pipeline configuration →
5

Publish your first position

Create a position under Positions → New. Fill in the job ad in every locale you publish in — the built-in translate action drafts the other locales for you, and you edit before publishing.Publishing does three things:
  1. Puts the ad on the public careers page.
  2. Opens the application pipeline for that position.
  3. If the occupation is subject to the Swiss job-reporting duty, prompts you to report it to the SECO Job-Room. See Stellenmeldepflicht.
6

Work the applications

Applications arrive from the careers page or from the shared mailbox. Move them across the Kanban board; each move can send a templated message, create tasks, or request documents. Managers assigned to a position see only their own positions’ applicants unless they hold applications:view-all.Application pipeline →
7

Hire

When you decide, the platform carries the person forward without re-keying:
  1. The application is marked hired and a pre-boarding journey starts.
  2. The new hire receives a magic link to the portal to complete their Personalstammblatt and upload the documents your position requires.
  3. A contract is generated from a template with the captured terms and sent for signature.
  4. On signature, an employee record is created and the onboarding checklist begins.
Pre-boarding and onboarding →
8

Turn on payroll (when you are ready)

Payroll needs master data before its first run: Lohnarten, Kontenplan, Versicherungen, and the tenant Stammdaten. This is a deliberate, one-time setup — plan for it separately.Payroll master data →

Roles and permissions

Who can see and do what, and why the tiers are drawn where they are.

Feature flags

Every module can be switched off per installation.