MyZapp

Viewing the logs

Available in en es fr

Updated on 10/25/2026

The Audit module of Portail ZAPP keeps track of what happened on the instance: actions recorded by the modules, login attempts, email deliveries and application logs. Its four screens are in the menu Administration › Instance and operations › Audit and are reserved for Administrators. All of them are read-only: nothing can be changed or deleted there.

When the Data grids module is installed, each list is a grid: search, filter and sort by column, Excel, PDF or CSV export.

Audit log

Audit logs lists the actions that the modules record, most recent first: for example creating, editing or deleting a group, a file or a CMDB item, a change to two-factor authentication settings, the purge of demo data. Each row gives the Date, the Type of item concerned, its ID, the Operation (green badge for a creation, red for a deletion, orange for the others), the User who did it and their IP address. An operation started by an automatic task has no user.

Detail opens an entry: the same information, the date in UTC, and the Changes block, which shows as-is the content recorded by the module (often the values before and after). This content is not translated.

Without the grid, filter the list by Entity type, Operation and period, then Filter; type and operation must be entered exactly as they appear in the list (for example Delete). Only the 50 most recent entries are then shown.

All administration operations are recorded here, whatever the screen or API used: accounts, groups, permissions, settings, menus and API keys, with the author and, most of the time, the state before and after. A setting appears only by its key, never by its value, and a password never appears. An access refused by a permission is also noted, once per screen and per person every five minutes. When an account is anonymised, the details of the lines about it are emptied; the lines remain. For everything else, only the actions that each module chose to record appear here.

Login attempts

Login attempts lists each login step, successful or not: Date, Email entered, Source (Local, AD, M365, WinSSO…), Step, Result (Success or Failure), Failure reason and IP. Use it to understand why someone cannot log in or to spot repeated attempts on an account.

  • The Credentials step is entering the login and password; TwoFactor is the second-factor check; TwoFactorSend is sending a verification code; LockoutReset is resetting the failure counter (for example after a password reset).
  • The reason is an untranslated code, for example InvalidPassword. On a successful row, the column may also contain a code (the method used to send the code, or the cause of the reset).

Without the grid, filter by email, source, step, result and period, then Filter; Clear removes the filters. The list is paged by 50.

Email deliveries

Email deliveries lists the emails sent by Portail ZAPP (notifications, verification codes, password resets…): Date, Recipient, Subject, status in the Operation column (EmailSent in green, EmailFailed in red), User and IP. A failed delivery usually points to an SMTP server or address problem; the detailed error message is in the audit log, on the matching entry of type Email (Detail).

This screen only works with the Data grids module; without it, a message says so.

Application logs

Application logs shows the technical log files of the instance, one day at a time. Choose the Date (only days for which a file exists are offered, most recent first) and the Minimum level: Debug, Information, Warning+ (default) or Error+. The grid shows the Timestamp, Level, Message and Source; select a row to open the Event detail, with the full entry, including any exception.

Beyond 50,000 lines for the chosen day and level, reading stops and the badge Truncated result — too many lines for this day/level appears: raise the minimum level to see the end of the day. Messages are those written by the application, usually in English.

This screen only works with the Data grids module.

See also

  • "Setting permissions": who can open these screens.
  • "Secure sign-in": lockout after failures and two-factor authentication.
Applies from version 1.0 Verified for version 1.0

Was this article helpful?

Still need help? Create a request