Skip to main content

Incident Log

The Incident Log is the Accelero screen where operators manually record day-to-day operational occurrences — incidents, complaints, suggestions and general notes. It works like a logbook of the gatehouse/operation: each record keeps date, author, type, title and description.

Navigation path: Incident Log (side menu)

Do not confuse with the Incident Panel

The Incident Log is a manual record, created by the operator. It is different from the Incident Panel, which is an alarm center fed automatically by system events (controller offline, duress, etc.). They are independent features.

TODO: Add Screenshot

Screenshot of the Incident Log screen with the New occurrence form open (Title, Occurrence type and Description fields) and some records in the list below.


Overview

The screen is made up of an action bar at the top and the list of recorded occurrences:

  • New occurrence — opens the entry form.
  • Search — opens the advanced search filters.
  • More actions — batch actions (e.g. deletion of selected items).

Each row in the list shows the following columns:

ColumnDescription
DateDate and time of the occurrence
OperatorOperator who recorded the occurrence
Occurrence typeClassification of the record (Incident, Complaint, Suggestion, Others)
TitleShort summary of the occurrence
DescriptionDetails of what was recorded
ActionsButton to edit the occurrence

The list is ordered by date (most recent first) and is paginated — you can navigate through the pages or use View all pages to display everything at once.


Record a new occurrence

Click New occurrence and fill in the entry form:

FieldRequiredRules
TitleYesBetween 3 and 100 characters
Occurrence typeYesSelect one of the available types
DescriptionYesFree text with the details of the occurrence

When you confirm with Include, the occurrence is saved already associated with the logged-in operator and with the current date/time, appearing immediately at the top of the list.

Automatic authorship

You do not need to enter who is recording it: the system automatically saves the logged-in operator as the author of the occurrence and stamps the date and time of the record.

TODO: Add Screenshot

Screenshot of the Include form with the Occurrence type selector open, showing the options Incident, Complaint, Suggestion and Others.


Occurrence types

The types classify each record. The system already comes with four default types:

TypeTypical use
IncidentAbnormal situations that require attention or action
ComplaintComplaints from residents, visitors or employees
SuggestionIdeas and improvement suggestions
OthersGeneral records that do not fit the categories above
Type maintenance

The list of occurrence types is fixed by default (Incident, Complaint, Suggestion and Others). Creating/editing types is a restricted technical operation.


Edit an occurrence

Use the edit button in the Actions column of a row to open the occurrence. In the editing, you can adjust the date, the type, the operator, the title and the description, and then Save.

TODO: Add Screenshot

Screenshot of the occurrence editing screen showing all the fields.


Search occurrences

The Search button opens the advanced search filters, which can be combined:

  • Periodstart and end date of the occurrence;
  • Operator — one or more authoring operators;
  • Occurrence type — one or more types;
  • Title — text search in the title;
  • Description — text search in the description.

Batch deletion

To remove several records at once, check the selection boxes of the desired rows and use More actions > Delete.


Permissions

Access to the Incident Log is controlled by two permissions:

PermissionWhat it enables
Incident log - AccessView the list and record new occurrences
Incident log - ManageEdit and delete occurrences
Own occurrences

Regardless of the management permission, every operator can edit and delete the occurrences they recorded themselves. The Manage permission is required to change or delete records made by other operators.

See Profiles to configure these permissions.


Next Steps