This article brings together what an administrator needs to know to run the help desk over time: rights, notifications, e-mails, traceability, data protection, languages and billing.
Rights #
The help desk has its own section in the role matrix (Help center). Five rights, each with the Access and Execute levels:
| Right | What it opens | By default |
|---|---|---|
| Administer the help center | The settings: services (including opening them to the API), agents, request types, categories, numbering, portal, incoming e-mail, brand and domain, automations (rules and macros); reporting on the whole help desk; at the Execute level, help desk webhook subscriptions. | The administrator. |
| Help center agent | See (Access) and handle (Execute) the tickets of the services whose agent group one belongs to, macros included. | Nobody. |
| Help center requests | Read one’s requests (Access), file them and reply (Execute); read the internal help. | All employees. |
| Knowledge base writer | Read articles being written (Access), write, publish, archive and classify (Execute). | Nobody. |
| Incidents and problems | Read major incidents and problems (Access); declare, inform about, resolve and edit an incident, attach tickets to it from its page, manage problems (Execute). Without this right, an agent attaches the tickets they can move forward to an ongoing incident. | The administrator. |
The administrator only receives the administration and the incidents and problems (see Major incidents and problems): grant the agent right and the writer right to your teams’ roles, and the incidents right to the roles that steer outages. Service manager is not a right: it is set on the service page, among its agents. Without the right, the matching entry does not exist (no menu, no search, no quick action).
Notifications #
Each event has its own checkbox in the personal settings, Notifications tab, for the notification bell and for e-mail. Agent checkboxes are only shown to those who hold the matching right.

| Checkbox | For |
|---|---|
| Replies to my requests; Acknowledgement of my requests; Progress of my requests; My requests waiting for my reply | The requester |
| Tickets assigned to me; Requester activity on my tickets; Tickets reopened by their requester; Deadline reminders; Escalations of missed deadlines; Poor satisfaction ratings | Agents |
| Tickets I follow | Observers (employees and agents) |
| Knowledge base articles to review | Writers |
Each notification leads straight to the ticket or article concerned.
The “Requester activity on my tickets” checkbox also carries the notifications of service catalogue requests (task refused or cancelled, follow-up awaiting a decision) and the declaration of a major incident on your service; “Replies to my requests” carries an incident’s common messages, and “Progress of my requests” its resolution.
E-mails #
Help desk e-mails are templates you can edit in French, English, German and Italian, in Settings › Manage Illizeo › Emails (Help desk category): acknowledgement, address confirmation and portal sign-in link, reply to the requester, waiting for their reply, status change, resolution with satisfaction survey, reopening, deadline reminder, escalation, poor rating, article to review, assignment, grouping of a request (employee and external person), reply to a person in copy, news of a followed ticket, task of a catalogue request needing your attention, major incident declared, news about an incident and its resolution (employee and external person), acknowledgement of a request that follows an incident. Employees are addressed informally, external people formally. E-mails to requesters carry your logo, colour and footer, and can go out from your address (see Your brand on the portal and e-mails).

Disabling a template stops it from being sent, except for two templates that cannot be switched off — without them the portal would be unusable: the address confirmation of a request filed on the portal and the sign-in link to the portal. Their text remains editable.
Traceability #
Creations, changes and deletions in the help desk (services, groups, managers, types, categories, settings, tickets, articles, canned responses…) are recorded in the activity log, under the Help center module. The log keeps neither message content, nor form answers, nor satisfaction comments. Each rule applied and each macro are also recorded in the ticket’s timeline, action by action. An action taken through the public API is signed with the token’s name in the thread and the timeline (“via API · Supervision”) and recorded in the log under the name of the person who created the token (see The help desk API). Major incidents, their common messages and problems are also recorded in the log, without their descriptions, notes or messages.
Data protection (GDPR) #
- Employee export: the export of their personal data includes a Help desk category — their tickets, the public thread and their satisfaction ratings. Agents’ internal notes are never included.
- Employee erasure: their tickets lose their content (subject, description, answers, messages, attachments) and remain for reporting; their name disappears from the tickets they handled, and they no longer follow any ticket. The requests made for them by a journey (service catalogue) also lose their content.
- External person: at their request, from the Personal data (GDPR) block of one of their tickets, Export their data downloads a file to hand to them, and Erase their data erases their address, name and organisation; their tickets remain for reporting, without their content. The export and the erasure also cover the requests they are in copy of and what they wrote there. This block is reserved for those who administer the help desk (Execute level).
- Retention: in Settings › Help center › External portal, Retention period (months) (24 by default, between 6 and 120): every night, an external person with no open ticket for that period is erased the same way.
- API and webhooks: help desk webhooks send your company’s tools the requester’s name and address, the ticket subject and the text of public replies, never an internal note; the delivery log keeps these payloads for 30 days. An erasure removes them neither from that log nor from the tools that received them (see Help desk webhooks).
- Incidents and problems: they hold no requester personal data; an anonymised ticket is detached from its incident and removed from the problems it was linked to.


An anonymised ticket keeps its number, dates, service, type, category, priority, statuses, commitments, agent and satisfaction rating. Its page says so.
Backup and languages #
- Ticket attachments and article images are included in the workspace backup.
- Screens, messages and e-mails exist in French, English, German and Italian; services, types, canned responses and articles are written in your requesters’ languages.
Activation and billing #
- The help desk is installed from the app store. As long as it is not active, it leaves no trace: no menus, no search, no e-mails, no notifications, no settings, and the external portal does not exist.
- It is billed per agent per month: an agent is an active person who holds the agent right, counted once even if several of their roles grant it. The right to file requests, the writer right, the incidents and problems right and the administration do not count as such. During the trial, agents are counted but not billed; consumption is shown in the subscription management.
