Report a bug and follow its resolution

Use Signaler un bug at the top of any authenticated page. Describe what happened and what you expected, review or remove the screenshot, then choose Envoyer.

The screenshot is prepared before the dialog opens. It covers the visible application page, not your desktop or other tabs. Password and secret fields are masked, but other visible personal data may remain: review it before sending. Embedded and external content may be missing. If capture fails, you can submit the description and page context without an image. No image is uploaded before you submit.

Reports include the page, authorised bot or conversation, application version, browser and viewport. At most ten new reports per hour are allowed. API screenshots accept PNG or JPEG up to 4 MiB, within the documented dimension limits. An error keeps your draft; retrying the same submission does not create a duplicate.

Open Mes signalements in your avatar menu to read replies, add details and follow status changes. The global button shows an unread count; updates also notify you by email. Statuses are New, In progress, Needs information, Resolved and Closed. Only platform administrators can change status. If another update occurs while you are writing, keep your draft and reload before publishing again.

Only the author and platform administrators can access a report, its screenshot and discussion. Organisation managers and resellers do not inherit access to other users’ reports. Platform administrators have Suivi des bugs in their administration menu and receive new report notifications. Emails contain an authenticated link, without the description or screenshot.

Release notes appear automatically once per account and version after every update. An already open page checks for new versions every minute while visible, and when you return to its tab. An open dialog, screenshot capture or unsaved changes defers the presentation until your work is safe; it then resumes automatically. A background tab never marks release notes as viewed.

Choose Version … · Nouveautés in your avatar menu to reopen the history. Viewing a release on another device signed in to the same account also counts as a presentation; the history remains available in this menu. The public API exposes the same workflows and permissions through /api/v1/bug-reports and /api/v1/releases.