Onboarding Gestion des absences Gestion du temps Présences & badgeages Notes de frais Performance & objectifs Documents & signatures App mobile Libre-service employé
L'entreprise Carrières Sécurité Contact
Entreprises moyennes Petites entreprises Grandes entreprises Partenaires SIRH Suisse SIRH France
Blog Centre d'aide Références clients Presse Panorama SIRH Notes de frais mondiales Absences mondiales Roadmap
Plans Connexion Essai 30 jours gratuit
Skip to content
Illizeo

Core HR Services

Personnel Administration

Files, contracts and centralized data.

People Analytics

Real-time HR dashboards.

Storage & Signature

Documents and electronic signature.

Company documents

Policies, rules and guides, targeted.

Mandatory notices

Legal notices, online.

Bulk signature

Signature campaigns and employee documents.

Project Management

Track cross-functional HR projects.

Modules

HR Requests

Service desk, deadlines, tracking

Help desk

Internal and external tickets, committed times.

Survey

Engagement, pulse and onboarding surveys.

Whistleblowing

Confidential reporting, Sapin 2 & EU compliant.

Recruitment

Requisitions, ATS, pipeline, interviews.

Employee referral

Referrals, tracking and bonuses.

Expense Reports

Capture, validation and reimbursement.

Benefits

Meal vouchers, mobility, well-being

Budget & payroll costs

Budget, salary review, pay equity.

CRM

Accounts, pipeline, quotes, commissions.

 

BDESE

French economic and social database.

Flex Office

Desk booking and hybrid attendance.

Scheduling

Team rosters, shifts and open shifts.

Time Management

Absences, attendance, badging.

Absences Attendance ZKTeco Ultima time clocks Choosing your clocking method

Performance & Objectives

Continuous reviews and aligned OKRs.

Training & skills

Skills, plan, sessions, certifications.

Onboarding & OffBoarding

Automated onboarding and offboarding journeys.

Platform

Emails

Templates, personalization, deliverability.

Employee Self-Service

Personal space for each employee.

Workflows & Approvals

No-code configurable workflows.

Alerts & Notifications

Stay informed in real time.

Mobile App

iOS and Android, offline.

Security & Compliance

ISO 27001, GDPR, SSO.

 

Permissions & Roles

Granular access control.

Governance & Security

History, audit trail, SoD, security by design.

Laws & agreements

Built-in collective agreements, more on request.

Connectors

SSO, payroll, calendar, e-signature: 22 tools.

REST API

Scoped tokens, OpenAPI.

Webhooks

Signed HR events, auto retries.

SFTP exports

Scheduled reports dropped on your server.

Salaries

Swiss payroll

Payroll, withholding tax, certificates.

Preliminary Salaries

Payroll preparation and control.

Outsourced Salaries

Payroll delegated to our experts.

Global Payroll Consolidated

Multi-country, multi-currency.

Consulting

Illizeo Premium Consulting

Tailor-made HR support.

New

Regulatory Compliance in 1 click

Stay automatically up to date with local and international legal changes.

Discover →
Integrations

About us

Our mission, our teams.

Customers

100+ customers trust us.

Press

Articles, awards, press releases.

Careers

Join the Illizeo adventure.

Contact

Let us discuss your project.

By company size

Small Businesses

Get started in under 30 days.

Medium-sized Companies

Manage multiple sites simultaneously.

Large Companies

Multi-country compliance and SSO.

Organizations & Public Sector

Advanced regulatory reporting.

Partnerships

Become an integrator or reseller.

By country

HRIS Switzerland

Withholding tax, BVG/LPP, FADP.

HRIS France

Agreements, leave, BDESE.

Blog

HR insights and product updates.

Help Center

Step-by-step guides and FAQ.

Roadmap

What's coming in Illizeo.

Family allowances

Global HR guide - 147 countries.

Pricing
Login Try for free →

Book a meeting with Illizeo

Pick a slot in the calendar below.

Core HR services

25
  • People Analytics
    • Permissions and data confidentiality
    • Scheduling a report
    • Describing your report to the AI
    • Creating a custom report
    • System reports catalogue
    • System reports
    • The Employee Analytics dashboard
    • Getting started with People Analytics
  • Storage & e-signature
    • Replacing, unpublishing or deleting a document
    • Publishing a company document and choosing its audience
    • Reading and searching company documents
    • Getting started with company documents
  • HR project management
    • Project settings and finances
    • Managing a project team
    • Planning a project and measuring time spent
    • Organising a project’s tasks
    • Monitoring a project from the Overview
    • Getting started with project management
  • Mandatory notices
    • Publishing and withdrawing mandatory display documents
    • Getting started with mandatory display
  • HR access
    • Entering an absence for a whole population
    • Tracking a signature campaign
    • Launching a signature campaign
    • Finding the documents of your whole population
    • Getting started with HR access

Payroll

26
  • Preliminary salaries
    • Payroll settings
    • Entering an employee’s compensation
    • Importing payroll data
    • Preparing the month’s payroll
    • Getting started with Payroll
  • Payroll outsourcing
    • SwissSalary connector: permissions in Business Central
  • Compliance & exports
    • Compensation types and payroll items
    • Approving payroll and exporting items
  • Swiss payroll
    • The Swissdec cockpit
    • Salary certificates, annual statements and payroll accounts
    • Calculating and closing monthly payrolls
    • Completing employee data
    • Setting up Swiss payroll
    • Getting started with Swiss payroll
  • Canadian payroll
    • Producing a record of employment
    • Preparing T4 and RL-1 slips
    • Tracking remittances to the CRA and Revenu Québec
    • Calculating, closing and publishing a Canadian pay
    • The employee’s Canadian payroll tab: tax forms and takeover
    • Setting up a Canadian employer and the payroll settings
    • Getting started with Canadian payroll
  • Moroccan payroll
    • Monthly statements and returns
    • Calculating, closing and publishing the month’s payroll
    • Preparing an employee’s Morocco payroll record
    • Setting up Morocco payroll
    • Getting started with Morocco payroll

Platform

57
  • Emails
    • Automated emails: catalogue and activation
    • Editing an email template
    • Sending reminders until the action is done
    • Tracking the sending history
  • Employee self-service
    • Finding your way around Illizeo: menu, search, language and personal settings
    • The dashboard: your home page
    • My profile: viewing and updating my information
    • The calendar and syncing your work calendar
    • Configuring the company dashboard
  • Flows & approvals
    • Workflows: from request to decision
    • Approving, rejecting or delegating a request
    • Monitoring workflow activity: overview and metrics
    • Creating and editing a workflow
    • Global settings, deadlines and automatic actions
    • HR processes: documents, signatures and deadlines
  • Alerts & notifications
    • The notification centre (the bell)
    • Choosing your notifications
    • Setting company notification defaults and locks
    • Publishing an announcement on the dashboard
    • Role reminders and personal reminders
  • Mobile app
    • Configuring the mobile app
  • Security & compliance
    • Password, session length and IP addresses
    • Two-factor authentication and open sessions
    • Single sign-on (SSO)
    • Country compliance and privacy consent statements (DPCS)
    • Data protection registers
    • Data backups
  • Permissions & roles
    • Understanding roles and permissions
    • Creating and managing roles
    • Setting permissions in the matrix
    • Defining a role’s target population
    • Assigning a role to employees
    • Creating employee groups
  • Governance & security
    • Governance and traceability: overview
    • Viewing user logs
    • The GDPR audit log
    • Running an access review
    • Separation of duties (SoD)
    • Finding the change history
  • REST API
    • Creating and managing API tokens
    • Monitoring and troubleshooting an API token
    • Public API: developer guide
    • The help desk API
  • Webhooks
    • Creating and managing a webhook
    • Monitoring deliveries and retries
    • Receiving and verifying a webhook
    • Webhook event catalogue
    • Help desk webhooks
  • SFTP exports
    • Setting up the company SFTP server
    • SFTP deposits and how to track them
  • Subscription & settings
    • Setting up organisation code generation
    • Finding your way around Settings
    • Installing modules and choosing who can use them
    • Subscribing and changing your subscription
    • Invoices, payment, usage and workspace ownership
    • Workspace logos and global settings
    • Giving Illizeo Support access

Consulting

1
  • Deployment support
    • The Illizeo Pulse method: how we deploy your HRIS

Attendance & Badging

11
  • Filling in your timesheet from your Outlook calendar
  • Attendance & badge clocks: module overview
  • Clocking in and out
  • Filling in and submitting your timesheet
  • Approving attendance and following the team
  • Creating and assigning attendance profiles
  • Clocking rules, entry closing and presence reasons
  • Hour counters
  • Allowances and on-call
  • Badge clocks
  • Administering the Attendance module: permissions, notifications, import/export and personal data

Absence Management

8
  • Absence management: overview and vocabulary
  • Requesting, editing and cancelling an absence
  • Leave balances and counters
  • Approving absence requests
  • The absence calendar
  • Configuring absence types and their policies
  • Company rules and public holidays
  • Administering the Absence management module

Expense Reports

7
  • Expenses: overview and life of an expense report
  • Entering, submitting and tracking an expense
  • Declaring mileage and per diem
  • Approving expense reports
  • Reimbursing, analysing and accounting for expenses
  • Configuring the Expenses module
  • Administering the Expenses module: permissions, notifications, personal data and FAQ

Performance & Goals

13
  • Performance: overview and navigation
  • Setting and tracking objectives (OKRs)
  • Objective-based bonus: preparing and sending to payroll
  • Scheduling and tracking 1:1 meetings
  • Designing review forms
  • Setting up a review cycle and campaign
  • Launching, tracking and closing a campaign
  • Completing and approving reviews
  • The end-of-cycle dossier: validating and signing
  • Continuous feedback
  • The talent review (9-box)
  • Tracking professional interviews (France)
  • Administering the Performance module

Surveys & Engagement

6
  • Survey settings
  • Reading results and generating reports
  • Tracking responses and sending reminders
  • Answering a survey
  • Creating and launching a survey
  • Getting started with Surveys

FlexOffice

18
  • Flex Office: module overview
  • Flex Office calendar
  • Flex Office: week template
  • Flex Office: parking
  • Flex Office: meals
  • Flex Office: visitors
  • Flex Office: meeting rooms
  • Flex Office: site events
  • Flex Office: approvals
  • Flex Office: schedule reminders
  • Flex Office: dashboard
  • Flex Office: locations and floor plans
  • Flex Office: attendance profiles
  • Flex Office: general settings
  • Flex Office settings
  • Flex Office: imports
  • Flex Office: notifications
  • Flex Office: integrations

HR requests

5
  • Administering the HR requests module: traceability, personal data, languages and FAQ
  • Configuring the HR requests module
  • Handling HR requests (HR team)
  • Submitting and tracking an HR request
  • HR requests: overview and life of a request

Scheduling

7
  • Getting started with Scheduling
  • Creating and publishing a schedule
  • Open shifts and replacements
  • Availability and preferences
  • Clocking in on a shift and geofencing
  • Scheduling settings
  • Scheduling public API and webhooks

Budget & payroll costs

10
  • Budget & payroll costs: module overview
  • Monitoring payroll costs against the budget
  • Running the salary review
  • Pay scales and contract positioning
  • Analysing pay equity (Gender Equality Act)
  • Simulating payroll costs and planning headcount
  • Fiscal years, funding and coverage rate
  • Budget module indicators, exports and action log
  • Administering the Budget & payroll costs module: settings, approval workflows and permissions
  • Administering the Budget & payroll costs module: notifications, traceability, personal data and glossary

BDESE

9
  • Recurring works council consultations
  • The works council area: staff list, mandates and experts
  • Calculating and publishing the gender equality index
  • BDESE payroll data
  • Entering, validating and publishing data
  • BDESE settings
  • The group view
  • Choosing a BDESE’s structure and designating contributors
  • Declaring and managing BDESE databases

Training

12
  • Training: overview and navigation
  • Your training space: home, path, catalogue and certificates
  • Taking an online course: lessons, quizzes and assignments
  • Requesting training and getting it approved
  • Building and publishing a course in the catalogue
  • Scheduling sessions and taking attendance
  • The trainer workspace: preparing, running and declaring your hours
  • Steering training: annual plan, budget and analytics
  • Tracking certifications and renewals
  • Managing skills: framework, matrix and gaps
  • Agreements, invoices, certificates and regulatory filings
  • Administering the Training module

Employee referrals

5
  • Setting up the referral programme and campaigns
  • Managing referrals and approving the bonus
  • Tracking your referrals, badges and the ranking
  • Referring a candidate or sharing your link
  • Getting started with Referrals

Whistleblowing

6
  • Analytics, export and data privacy
  • Configuring the scheme
  • Handling a whistleblowing case
  • Submitting and tracking a report
  • Setting up channels and naming handlers
  • Getting started with whistleblowing

CRM

26
  • Enabling and administering the CRM module
  • Managing accounts
  • Managing contacts
  • Finding duplicates and merging records
  • Activities and “My activities”
  • Tracking opportunities in the pipeline
  • The catalogue and quotes
  • Importing, exporting and using the API
  • The dashboard and sales targets
  • CRM settings
  • Protecting contact data (GDPR)
  • From a won deal to a project
  • CRM webhooks
  • Connecting the CRM to Power Automate
  • Connecting the CRM to n8n
  • Microsoft 365 in the CRM: emails, meetings and Teams
  • The CRM forwarding address
  • Artificial intelligence in the CRM
  • Getting records and sendings approved
  • Sales commissions
  • The CRM and HR: time, expenses, absences and departures
  • The CRM in the mobile app
  • Links between organisations and multi-organisation projects
  • Follow-up pipelines: support and business set-up files
  • Memberships and dues
  • Events and public registrations

Help desk

20
  • Setting up the help desk
  • Submitting and following a help desk request
  • Handling help desk tickets
  • Help desk service commitments
  • External portal and incoming e-mail
  • The knowledge base
  • Help desk satisfaction and reporting
  • Workflows and ticket approval
  • The help desk and the CRM: linked customers and contracts
  • Client organisations: shared portal, contact persons and directory
  • The help widget on your customer’s website
  • The help desk in Microsoft Teams
  • Your brand on the portal and e-mails
  • Merging duplicates, linking tickets, observers and copies
  • Help desk automations: rules and macros
  • The help desk API
  • Help desk webhooks
  • The service catalogue: one request, several teams
  • Major incidents and problems
  • Administering the help desk
View Categories
  • Accueil
  • Centre d'aide
  • Help desk
  • The service catalogue: one request, several teams

The service catalogue: one request, several teams

Wilfrid Paul Robert Dusseaux
Updated on 20.11.2026

9 mins de lecture

0:00 / 10:28
  • View as Markdown Open this page as plain Markdown (opens in a new tab)
  • Open in ChatGPT Ask questions about this page (opens in a new tab)
  • Open in Claude Ask questions about this page (opens in a new tab)
  • Open in Google AI Studio Ask questions about this page (Google account required) (opens in a new tab)

A new employee’s arrival needs a workstation from IT, a badge from facilities and access to the applications. With the service catalogue, a single request creates these tasks in the right teams’ queues, in parallel or in sequence, and the requester follows the whole as one. This article is for the help desk administrator, who sets up the catalogue, and for the agents who coordinate a request or handle a task; it also shows what the requester sees.

Before you start #

  • To set up a catalogue item, you need the Administer the help center right (Execute level).
  • To coordinate a request or handle a task, you must be an agent of the service concerned: a member of one of its agent groups who holds the Help center agent right (Execute level).
  • Each service that receives a task must be active and have its agents (see Setting up the help desk).
  • For a journey step to file the request: the Onboarding module installed and the Onboarding — Create / edit step right (Onboarding / Offboarding section of the role matrix).

How it works #

A catalogue item is a request type of one service, to which you add tasks spread across several services. The item’s service coordinates: the request filed arrives in its queue like any request. Each task is created in its own service’s queue: it is a real ticket, with its number, its agent and its deadlines.

  • Tasks are arranged by step. The tasks of the same step start together, in parallel; those of the next step start once the previous step is finished.
  • A resolved or closed task is finished. When all of them are, the request moves to “Resolved” on its own.
  • The requester only follows the request: its progress task by task and the teams’ messages. They see neither the tasks, nor their agents, nor their internal notes.

Creating a catalogue item #

  1. Open Settings › Help center › Services, then the service that will coordinate the request, for example Human resources.
  2. In the Request types section, click New request type, or Edit for an existing type. Fill it in as usual: name, description, default priority, audience and form.
  3. In the Distributed tasks (service catalogue) section, click Add a task for each team to involve.
  4. For each task, set the Step (1 to 10: same number, in parallel; next number, in sequence), the Service that handles it, if needed its Type (optional) among that service’s types, and its Label, for example “Workstation”. The arrows change the order; the bin removes the task.
  5. Click Save.
Distributed tasks (service catalogue) section of a request type window: three tasks, Workstation and Access badge at step 1 (IT, Facilities), Application access at step 2, and the Add a task button
The tasks of a catalogue item

In the service’s list of types, the item carries the Item · 3 task(s) badge. An item has at most 20 tasks, and a label at most 80 characters. The label is entered in your screen language; the other languages already saved are kept, and the requester reads it in their language, otherwise in French. A task’s optional type classifies it within its service: its rules and reporting use it as for any ticket. Removing all the tasks turns the type back into an ordinary request.

Approval before the tasks #

To have the request approved before the teams start, use a “Ticket to approve” workflow limited to this request type (see Workflows and ticket approval). The tasks are only created once the request is approved, and never if it is refused. A task never goes through an approval process itself.

Coordinating the request #

An agent of the coordinating service takes the request and follows it. Its page has one card per step: Tasks — step 1, Tasks — step 2… The current step carries the Current step badge. For each task: its number (a link when you can open it), its label, its state — Upcoming, In progress, Resolved, Refused or Cancelled —, its service, its agent, its deadline and, where relevant, the reason for a refusal or a cancellation.

Page of a catalogue request as the coordinator sees it: The follow-up awaits your decision banner with Restart the follow-up and Cancel the follow-up, Tasks — step 1 card with a resolved task and a refused task with its reason, Tasks — step 2 card with an upcoming task and the Cancel button
The request awaits the coordinator’s decision
  • Cancel, next to an upcoming or in-progress task, cancels it with a reason that the requester will read. An upcoming task will not start; an in-progress task is closed in its service’s queue, and the agent who held it is notified.
  • The request moves neither to “Resolved” nor to “Closed” while a task is in progress or a step is still to come; the screen says so: “This request still has tasks in progress: it is resolved when all of them are finished.”
  • You reply to the requester and write internal notes on the request as on any ticket.

These actions belong to the agent who can move the request forward: the one who holds it, the service manager or, while it is unassigned, any agent of the service. The coordinator is notified, by the notification bell and by e-mail, of each refused or cancelled task and of each follow-up waiting for their decision: the agent who holds the request, otherwise the service’s agents.

Handling a task #

A task arrives in its service’s queue with its label followed by the request’s subject as its subject (“Workstation — Arrival of…”). The agent takes it, handles it and resolves it like any ticket: their service’s rules, macros, commitments, transfer and reporting apply to it. Its page also shows:

  • the Task of AST-… banner, with the request’s status, the task’s step and the coordinating service;
  • the Original request card: the request’s subject, description and form answers, and the employee concerned when it comes from a journey;
  • the Request conversation card: the requester’s exchanges with all the teams, read-only.
Agent’s page of a task: Task of AST-000074 banner, step 1, coordinated by Human resources, with Refuse the task; Original request and Request conversation cards; Task notes in Reply to the requester mode, which writes on the request
A task in its service’s queue

There is a single conversation, held on the request. In Task notes, Reply to the requester writes on the request: the requester receives the message as a reply to their request, marked with your service’s name, and every task reads it (“From task AST-…”). An Internal note stays on the task. When the requester replies, the agent who holds each in-progress task is notified.

Refusing a task #

If your team cannot do the task, click Refuse the task in the banner, write the Reason (read by the requester) (up to 1,000 characters), then confirm. The task is closed, the reason is written in the request’s history, which the requester reads, and the coordinator is notified. A task is refused by the agent who holds it, or by their service manager; when unassigned, by any agent of the service.

When a task is refused or cancelled #

The other tasks of the same step carry on. When all the tasks of the step are finished:

  • if none was refused or cancelled, the next step starts on its own;
  • if one of them was and a step follows, the follow-up waits for the coordinator’s decision: the request’s page carries the The follow-up awaits your decision banner;
  • if no step remains, the request is resolved.

The coordinator then chooses:

  • Restart the follow-up: the next step starts;
  • Cancel the follow-up, with a reason read by the requester: the upcoming tasks are cancelled, and the request is resolved once the remaining tasks are.

What the requester sees #

In My requests, as on the external portal for an external person, the request carries a Progress card: by step, each task with its label, its service, its state and, where relevant, the reason for a refusal or a cancellation. The counter (for example 2/3) shows how many tasks are finished.

Progress card of a request as its requester sees it: 2 of 3 tasks finished, step 1 with Workstation resolved and Access badge refused with its reason, step 2 with Application access upcoming
Progress as the requester sees it
  • The teams’ messages arrive in the request’s Conversation, marked with the name of the service that writes. The requester’s reply is read by every task.
  • The history shows each refused or cancelled task, with its label, its service and the reason, and the cancellation of the follow-up.
  • Nothing that happens on a task notifies them (taking, status change, survey): they receive the teams’ replies and the request’s status changes.

Resolving the request #

When the last task is finished and no step remains, the request moves to “Resolved”; the history says “The system”. The requester is notified and receives the coordinating service’s satisfaction survey, if that service sends it; tasks send no survey. If the requester reopens the request, no task restarts: the coordinator takes over again.

Deadlines #

Each task takes the request’s priority and its own service’s commitments. The request’s resolution deadline covers those of its tasks: it is extended to the latest one, when the tasks are created and each time a task’s deadline changes (after a requalification, for example). A request whose service has no commitment for its priority gets none. See Help desk service commitments.

Filing the request from an onboarding journey #

A journey step can file a catalogue item on its own, for the employee who is arriving:

  1. Open Settings › On-Off/Boarding › Onboarding Steps, then a step of the General type, or create one with New step.
  2. In Catalogue item (Help center), choose the item. None — the step is handled manually removes the link.
  3. Click Save.
New onboarding library step: Catalogue item (Help center) field with the Employee arrival — Human resources item, and the sentence explaining the filing when the journey starts
A journey step linked to an item

When this step is created in an employee’s journey:

  • the request is filed automatically, in the name of the step’s first owner, who is its requester, receives the acknowledgement and follows it in My requests;
  • it is made for the employee concerned: its subject is the item’s label followed by their name, its description recalls the journey and the start date, and the agents’ page shows “For:” followed by their name;
  • in the employee’s journey, the step shows “Request AST-…” and its status; it is completed on its own once the request is resolved.

The onboarding step library also serves crossboarding and reboarding journeys. The link only applies to a step of the General type, to an active item, and only if the help desk is active. If the step has no authorised owner, no request is filed: the step is handled manually.

Good to know #

  • The tasks are taken when the request enters the queue: changing the item afterwards does not change requests already filed. A request that is transferred or requalified keeps its tasks, and nothing restarts.
  • A task never creates tasks: choosing another item as a task’s type only gives it that type. A follow-up request (a reply after closure) is an ordinary request.
  • Neither the request nor its tasks can be merged or attached to a major incident; they can be linked (see Merging duplicates, linking tickets, observers and copies).
  • A rule that replies with a canned response has no effect on a task: the requester follows the request, and the task’s timeline says so.
  • The notifications to the coordinator and to the task agents follow the “Help desk — requester activity on my tickets” checkbox in the personal settings, Notifications tab. Their e-mail is a template you can edit in Settings › Manage Illizeo › Emails, Help desk category.
  • In reporting, each task counts as a ticket of its service, and the request as a ticket of the coordinating service.
  • Data protection: erasing an employee also erases the content of the requests made for them by a journey, and an erased request erases its tasks.
  • The mobile app shows the request and its conversation, without the Progress card.

Similaire #

Updated on 20.11.2026
Help desk webhooksMajor incidents and problems
Table des matières
  • Before you start
  • How it works
  • Creating a catalogue item
    • Approval before the tasks
  • Coordinating the request
  • Handling a task
    • Refusing a task
  • When a task is refused or cancelled
  • What the requester sees
  • Resolving the request
  • Deadlines
  • Filing the request from an onboarding journey
  • Good to know
Onboarding✦Offboarding✦Crossboarding✦Reboarding✦Referrals✦Equipment✦AI✦Signatures✦NPS✦Attendance✦Badging✦Leave✦Performance✦Objectives✦Surveys✦Engagement✦Time✦Roles✦Permissions✦Flows✦Approvals✦Salaries✦Expenses✦FlexOffice✦Projects✦
Onboarding✦Offboarding✦Crossboarding✦Reboarding✦Referrals✦Equipment✦AI✦Signatures✦NPS✦Attendance✦Badging✦Leave✦Performance✦Objectives✦Surveys✦Engagement✦Time✦Roles✦Permissions✦Flows✦Approvals✦Salaries✦Expenses✦FlexOffice✦Projects✦
International HR platform

Run HR
in minutes,
not in days.

Try for free Book a demo
illizeo

Onboarding, payroll, leave, talent — one engine for your teams.

SWISS MADE
Features
  • Solutions
  • Pricing
About
  • Careers
  • Press
  • Customers
  • Partner portal
  • Contact
Resources
  • Blog
  • Global family allowances
  • Comparisons
  • Help Center
  • FAQ
  • Security
Contact
+41 78 669 05 65 contact@illizeo.com
Newsletter
1 email a month. Useful only.
Coming soon to App Store Coming soon to Google Play
All systems operational · Swiss hosting · GDPR & nFADP
© 2026 Illizeo Cloud Solutions
FR/EN
Privacy Policy Legal Notice & Terms Illizeo Terms AI Terms Cookie Settings Sub-Processors MTO Data Processing Addendum (DPA) Support Services Terms
illizeo-logo-primary-white
Gérer le consentement

Afin de vous offrir la meilleure expérience possible, nous utilisons des technologies telles que les cookies pour stocker et/ou accéder aux informations relatives à votre appareil. En acceptant ces technologies, vous nous autorisez à traiter des données telles que votre comportement de navigation ou vos identifiants uniques sur ce site. Le refus ou le retrait de votre consentement peut avoir un impact négatif sur certaines fonctionnalités et fonctions.

Fonctionnel Always active
Le stockage technique ou l'accès est strictement nécessaire à des fins légitimes afin de permettre l'utilisation d'un service spécifique explicitement demandé par l'abonné ou l'utilisateur, ou dans le seul but d'effectuer la transmission d'une communication sur un réseau de communications électroniques.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistiques
Le stockage technique ou l'accès utilisé exclusivement à des fins statistiques. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
Le stockage technique ou l'accès est nécessaire pour créer des profils d'utilisateurs afin d'envoyer des publicités ou de suivre l'utilisateur sur un site web ou sur plusieurs sites web à des fins marketing similaires.
  • Manage options
  • Manage services
  • Manage {vendor_count} vendors
  • Read more about these purposes
Afficher les préférences
  • {title}
  • {title}
  • {title}