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
  • Major incidents and problems

Major incidents and problems

Wilfrid Paul Robert Dusseaux
Updated on 20.11.2026

8 mins de lecture

0:00 / 9:09
  • 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)

E-mail is down, the VPN no longer responds: dozens of people write about the same thing. A major incident groups their tickets, informs everyone affected with a single message and resolves them together; a banner warns the others before they file a request. A problem then helps find the cause, work around it, and remove it. This article is for the people who manage incidents and for agents; it also shows what requesters see.

Before you start #

  • The Incidents and problems right (Help center section of the role matrix): Access level to read incidents and problems, Execute to declare, inform about, resolve and edit an incident, attach tickets to it from its page and manage problems. By default, only the administrator holds it: grant it to the roles that steer outages. It is not billed.
  • Without this right, an agent (Help center agent right, Execute level) attaches and detaches, from its page, a ticket they can move forward, to an ongoing incident that affects their service.
  • To turn a problem into a knowledge base article, you also need the Knowledge base writer right (Execute level).

Declaring an incident #

  1. Open Help desk › Incidents and click Declare an incident. From a ticket’s page, the Major incident card also offers Declare an incident: that ticket is then attached automatically.
  2. Enter the Title, for example “E-mail unavailable”, and the Banner message, read by users, for example “We are working on it. No need to make a request: just let us know you are affected.”
  3. Tick the Affected services.
  4. If needed, add an Internal description (never shown to users), then click Declare the incident.

The incident gets its number (INC-000001…) and its page opens. The agents of the affected services are notified by the notification bell and by e-mail, and the banner is shown at once to the users of these services. The title and the banner are written in your screen language: a person who reads another language sees the French version, otherwise the language entered.

Incidents page: Declare an incident button, an ongoing incident and a resolved incident with their affected services, numbers of tickets and people affected, and dates
The list of incidents

The list shows the Ongoing incidents, then the Resolved ones, with their Affected services, the number of Tickets and of People affected, and their dates. While the incident is ongoing, Edit, on its page, changes its title, banner, services and description; a service that still has attached tickets cannot be removed.

Attaching tickets #

Attach the tickets that mention the outage to the incident, rather than answering them one by one:

  • from the incident’s page, Attached tickets card: paste one or more numbers in Attach by number, or search your queue (Search your queue: number or subject…), tick the tickets, then Attach the selection. The summary says how many tickets were attached, and why the others were left out;
  • from a ticket’s page, Major incident card: choose the incident under Attach to an ongoing incident, then click Attach. Only the ongoing incidents that affect the ticket’s service are offered.
Page of ongoing incident INC-000002: Edit and Resolve buttons, banner as users see it, three attached tickets with Detach, Reach, Internal description and Related problems cards
An ongoing incident’s page

A ticket can be attached if it is open (neither “Resolved” nor “Closed”), in an affected service, neither awaiting approval nor anonymised, not part of the service catalogue (a request with tasks or one of its tasks), and does not already follow another ongoing incident. One submission attaches at most 200 tickets.

What attaching changes #

  • The ticket keeps its status, and its deadlines are paused: no reminder and no escalation, first response included. A banner says so at the top of its page: “Attached to incident INC-…: its deadlines are paused.”
  • While it follows the incident, it changes neither status nor service and cannot be merged: these actions are refused, with the reason. It can be taken or assigned, and you can leave an internal note on it and reply to the requester, without changing the status in the same move.
  • A reply from the requester does not change its status; the agent who holds it is notified as usual.
  • Attaching is recorded in the ticket’s internal timeline.
Attached ticket as the agent sees it: Attached to incident INC-000002: its deadlines are paused banner, actions limited to assignment, and Major incident card with the attachment date and the Detach button
A ticket attached to an incident

Detach, on the ticket’s page or in the incident’s list, gives the ticket back its own lifecycle: the pause ends and the resolution deadline restarts, shifted by the time spent paused. The agent who can move the ticket forward detaches it, as can the person who manages incidents. A ticket resolved with the incident can no longer be detached.

Informing the people affected #

On the incident’s page, the Inform the people affected card sends a common message: write it, then click Send to N person(s).

  • The message is added, public and signed with your name, to the conversation of each attached ticket. The Messages sent card keeps its history.
  • Each person affected receives it only once, even with several attached tickets: requesters, requesters grouped by a merge, people in copy and observers. An employee receives it in the notification bell and by e-mail, an external person by e-mail.
  • It does not count as the tickets’ first response.

The banner and “I am affected” #

While the incident is ongoing, a banner announces it, with its message, to the users of the affected services:

  • employees, for a service open to employees: at the top of My requests, and in the filing window when the chosen service is affected;
  • external people, for a service open to external people: on the external portal home page and in the help widget.
An employee’s My requests page: banner of the VPN access unavailable incident, its message, the sentence No need to file a request for this outage and the I am affected button, above the list of requests
The banner in My requests

I am affected creates the person’s request, already attached to the incident, with the incident’s title as its subject. They receive an acknowledgement that says so, then the common messages and the resolution notice; the team sees how many people are affected. The banner then shows “You already follow this incident”. On the portal without an open session, and in the widget, the button opens the usual request form, prefilled (service and subject), stating that the request will follow the incident; on the portal, My request is about something else removes this link. Filing a request as usual remains possible for another matter.

Resolving the incident #

  1. On the incident’s page, click Resolve.
  2. Read the warning: the number of tickets still open that will move to “Resolved” and of people who will be notified.
  3. Write the Resolution note (read by each person affected), then click Resolve the incident.

Each attached ticket still open moves to “Resolved”, in your name and with the note. Each person affected receives a single resolution notice: no status notice and no satisfaction survey per ticket. The deadline pause ends, and the banner disappears on its own. A resolved incident cannot be reopened and no longer receives messages or tickets; a request resolved with it can be reopened like any resolved request.

Problems: finding and removing the cause #

A problem describes the cause of one or more incidents, how to work around it, then the permanent solution.

  1. Open Help desk › Problems and click New problem, or, from an incident’s page, Open a problem to find its cause (the incident is linked automatically).
  2. Enter the Title and, if needed, the Description, then click Open the problem. The problem gets its number (PRB-000001…).
  3. On its page, fill in the Root cause, the Workaround (what to do in the meantime) and the Permanent solution, and move the Status along: Open, Workaround in place, Resolved. A problem can only be Resolved with its permanent solution.
  4. Link the incidents (Link an incident) and the tickets (Link a ticket by its number) concerned, then click Save.
Page of problem PRB-000002, Workaround in place status: title, description, root cause, workaround and permanent solution; Related incidents, Related tickets and Knowledge base cards with Create an article
A problem’s page

Related problems are shown on each incident’s page and, in the Major incident card, on each linked ticket. The list of problems shows unresolved ones first.

Turning the solution into an article #

A problem’s solution can help others. In the Knowledge base card of its page, Create an article creates a knowledge base draft: the problem’s title, then the workaround and the solution, each under its own heading. Choose its Service and Category if needed, then click Create the draft. An article filed under a service can be read by that service’s users; without a service, the article is internal. Review it before publishing it (see The knowledge base). This requires the writer right and a saved workaround or solution; a problem has only one article.

Good to know #

  • The search and the numbers on the incident’s page cover the tickets of your queue: someone who manages incidents without being an agent of the affected service finds no ticket there. Agents then attach from their tickets’ pages.
  • The first-response deadline of an attached ticket is not shifted: it has no reminder and no escalation during the incident, and the common message does not meet it. Reply to the requester if that first response matters to you.
  • Notifications follow the checkboxes in the personal settings, Notifications tab: the declaration, “Help desk — requester activity on my tickets”; the common message, “Help desk — replies to my requests”; the resolution, “Help desk — progress of my requests (in progress, resolved, closed)”.
  • The e-mails (incident declared, news about an incident, incident resolved, acknowledgement of a request that follows an incident) are templates you can edit in Settings › Manage Illizeo › Emails, Help desk category. Employees are addressed informally, external people formally, and the e-mails carry your brand.
  • For workflows and rules, the resolution is a status change of each attached ticket; there is no trigger specific to incidents.
  • Incidents, their common messages and problems are recorded in the activity log, without their descriptions, notes or messages. An incident or a problem holds no requester personal data; anonymising a ticket detaches it from its incident and removes its links to problems.
  • The banner only appears in the help desk (My requests, filing window, portal, widget), not elsewhere in Illizeo, nor in Microsoft Teams, nor in the mobile app.

Similaire #

Updated on 20.11.2026
The service catalogue: one request, several teamsAdministering the help desk
Table des matières
  • Before you start
  • Declaring an incident
  • Attaching tickets
    • What attaching changes
  • Informing the people affected
  • The banner and “I am affected”
  • Resolving the incident
  • Problems: finding and removing the cause
    • Turning the solution into an article
  • 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}