Skip to contentIntroduction
This document provides instructions for Admin users on how to view and undo changes made to the website. Only Admin users can view the audit log.
The audit log tracks the following:
- Date: The date of the change
- User ID: The identifier for the user account that made the change
- Domain: The domain that was changed
- Module: The module that was used to make the change
- Target: The issue that was targeted to be fixed
- Identifier: The edited code snippet
Explanation: The (i) icon lets Admin users view the reason why the user made the change, if any was given.
Instructions
This section provides instructions for Admin users on how to access the audit log and undo reviewed issues.
- Click Admin Settings (the gear icon) on the main menu bar.
The system opens the Admin dashboard. - Click User Management from the menu on the left, and select Audit Log from the expanded list.
The system opens the Audit log dashboard. The following filters are available:- Domain
- User
- Feature
- Date range
The dashboard contains a list with the following columns:
- Date: The date of the change
- By User: The email address or identifier of the user who made the change
- Domain: The domain that the change was made on
- Feature: The feature that the change affected
- Target: Additional information about the data that was changed
- Identifier: Identification for the data that was changed
- Show more: The button to expand the full link to the page with the issue. This option is displayed only when the link is too long to fit in the field.
- Action: The action that was done to change the data
View changes
This section provides instructions on how to view the changes that were made and provides an overview of the attributes that the system tracks.
Click the kebab menu and select View Changes or Show Details for more information about the changes that were made. The information that is shown includes one or more of the following, depending upon the type of change:
- Attribute name: The HTML attribute
- Date and time: The date and time of the update or change.
- User ID: The ID number of the user who made the change.
- Report sent: The status of reporting, if it was sent or not indicated by true or false
- Before: Values before the change
- After: Values after the change
Undo a check review
This section provides instructions for Admin users on how to remove an Accessibility Source Code check review that was done on an issue.
- Navigate to the Audit log dashboard.
- Click the kebab menu on the same row as a reviewed Accessibility Source Code issue and select Undo check review. The option to undo is not displayed when the check review cannot be reverted.
The check review is removed from the audit log and the browser displays the issues view. The issue is reinstated to the previous status.
Tracked attributes
This section provides a list of the attributes that are tracked by the audit log:
- timezone
- cms extra
- domain users.0.send report
- domain users.0.updated at
- domain users.0.id
- domain users.1.send report
- domain users.1.updated at
- domain users.1.id
- domain users.2.send report
- domain users.2.updated at
- domain users.2.id
- domain users.3.send report
- domain users.3.updated at
- domain users.3.id
- domain users.4.send report
- domain users.4.updated at
- domain users.4.id
- domain users.5.send report
- domain users.5.updated at
- domain users.5.id
- domain users.6.send report
- domain users.6.updated at
- domain users.6.id
- domain users.7.send report
- domain users.7.updated at
- domain users.7.id
- domain users.8.send report
- domain users.8.updated at
- domain users.8.id
- domain users.9.send report
- domain users.9.updated at
- domain users.9.id
- domain users.10.send report true
- domain users.10.updated at
- domain users.10.id
- domain users.11.send report
- domain users.11.updated at
- domain users.11.id
- domain users.12.send report
- domain users.12.updated at
- domain users.12.id
- domain users.13.send report
- domain users.13.updated at
- domain users.13.id
- domain users.14.send report
- domain users.14.updated at
Audit log
Introduction
This document provides instructions for Admin users on how to view and undo changes made to the website. Only Admin users can view the audit log.
The audit log tracks the following:
- Date: The date of the change
- User ID: The identifier for the user account that made the change
- Domain: The domain that was changed
- Module: The module that was used to make the change
- Target: The issue that was targeted to be fixed
- Identifier: The edited code snippet
Explanation: The (i) icon lets Admin users view the reason why the user made the change, if any was given.
Instructions
This section provides instructions for Admin users on how to access the audit log and undo reviewed issues.
- Click Admin Settings (the gear icon) on the main menu bar.
The system opens the Admin dashboard. - Click User Management from the menu on the left, and select Audit Log from the expanded list.
The system opens the Audit log dashboard. The following filters are available:- Domain
- User
- Feature
- Date range
The dashboard contains a list with the following columns:
- Date: The date of the change
- By User: The email address or identifier of the user who made the change
- Domain: The domain that the change was made on
- Feature: The feature that the change affected
- Target: Additional information about the data that was changed
- Identifier: Identification for the data that was changed
- Show more: The button to expand the full link to the page with the issue. This option is displayed only when the link is too long to fit in the field.
- Action: The action that was done to change the data
View changes
This section provides instructions on how to view the changes that were made and provides an overview of the attributes that the system tracks.
Click the kebab menu and select View Changes or Show Details for more information about the changes that were made. The information that is shown includes one or more of the following, depending upon the type of change:
- Attribute name: The HTML attribute
- Date and time: The date and time of the update or change.
- User ID: The ID number of the user who made the change.
- Report sent: The status of reporting, if it was sent or not indicated by true or false
- Before: Values before the change
- After: Values after the change
Undo a check review
This section provides instructions for Admin users on how to remove an Accessibility Source Code check review that was done on an issue.
- Navigate to the Audit log dashboard.
- Click the kebab menu on the same row as a reviewed Accessibility Source Code issue and select Undo check review. The option to undo is not displayed when the check review cannot be reverted.
The check review is removed from the audit log and the browser displays the issues view. The issue is reinstated to the previous status.
Tracked attributes
This section provides a list of the attributes that are tracked by the audit log:
- timezone
- cms extra
- domain users.0.send report
- domain users.0.updated at
- domain users.0.id
- domain users.1.send report
- domain users.1.updated at
- domain users.1.id
- domain users.2.send report
- domain users.2.updated at
- domain users.2.id
- domain users.3.send report
- domain users.3.updated at
- domain users.3.id
- domain users.4.send report
- domain users.4.updated at
- domain users.4.id
- domain users.5.send report
- domain users.5.updated at
- domain users.5.id
- domain users.6.send report
- domain users.6.updated at
- domain users.6.id
- domain users.7.send report
- domain users.7.updated at
- domain users.7.id
- domain users.8.send report
- domain users.8.updated at
- domain users.8.id
- domain users.9.send report
- domain users.9.updated at
- domain users.9.id
- domain users.10.send report true
- domain users.10.updated at
- domain users.10.id
- domain users.11.send report
- domain users.11.updated at
- domain users.11.id
- domain users.12.send report
- domain users.12.updated at
- domain users.12.id
- domain users.13.send report
- domain users.13.updated at
- domain users.13.id
- domain users.14.send report
- domain users.14.updated at
domain users.14.iddomain users.15.send reportdomain users.15.updated atdomain users.15.iddomain users.16.send reportdomain users.16.updated atdomain users.16.iddomain users.17.send reportdomain users.17.updated atdomain users.17.iddomain users.18.send reportdomain users.18.updated atdomain users.18.iddomain users.19.send reportdomain users.19.updated atdomain users.19.iddomain users.20.send reportdomain users.20.updated atdomain users.20.iddomain users.21.send reportdomain users.21.updated atdomain users.21.iddomain users.22.send reportdomain users.22.updated atdomain users.22.iddomain users.23.send reportdomain users.23.updated atdomain users.23.iddomain users.24.send reportdomain users.24.updated atdomain users.24.iddomain users.25.send reportdomain users.25.updated atdomain users.25.iddomain users.26.send reportdomain users.26.updated atdomain users.26.iddomain users.27.send reportdomain users.27.updated atdomain users.27.iddomain users.28.send reportdomain users.28.updated atdomain users.28.iddomain users.29.send reportdomain users.29.updated atdomain users.29.iddomain users.30.send reportdomain users.30.updated atdomain users.30.iddomain users.31.send reportdomain users.31.updated atdomain users.31.iddomain users.32.send reportdomain users.32.updated atdomain users.32.iddomain users.33.send reportdomain users.33.updated atdomain users.33.iddomain users.34.send reportdomain users.34.updated atdomain users.34.iddomain users.35.send reportdomain users.35.updated atdomain users.35.iddomain users.36.send reportdomain users.36.updated atdomain users.36.iddomain users.37.send reportdomain users.37.updated atdomain users.37.iddomain users.38.updated atdomain users.38.iddomain users.39.send reportdomain users.39.updated atdomain users.39.iddomain users.40.send reportdomain users.40.updated atdomain users.40.iddomain users.41.send reportdomain users.41.updated atdomain users.41.iddomain users.42.send reportdomain users.42.updated atdomain users.42.iddomain users.43.send reportdomain users.43.updated atdomain users.43.iddomain users.44.send reportdomain users.44.updated atdomain users.44.iddomain users.45.send reportdomain users.45.updated atdomain users.45.iddomain users.46.send reportdomain users.46.updated atdomain users.46.iddomain users.47.send reportdomain users.47.updated atdomain users.47.iddomain users.48.send reportdomain users.48.updated atdomain users.48.iddomain users.49.send reportdomain users.49.updated atdomain users.49.iddomain users.50.send reportdomain users.50.updated atdomain users.50.iddomain users.51.send reportdomain users.51.updated atdomain users.51.iddomain users.52.send reportdomain users.52.updated atdomain users.52.iddomain users.53.send reportdomain users.53.updated atdomain users.53.iddomain users.54.send reportdomain users.54.updated atdomain users.54.iddomain users.55.send reportdomain users.55.updated atdomain users.55.iddomain users.56.send reportdomain users.56.updated atdomain users.56.iddomain users.57.send reportdomain users.57.updated atdomain users.57.iddomain users.58.send reportdomain users.58.updated atdomain users.58.iddomain users.59.send reportdomain users.59.updated atdomain users.59.iddomain users.60.send reportdomain users.60.updated atdomain users.60.iddomain users.61.send reportdomain users.61.updated atdomain users.61.iddomain users.62.send reportdomain users.62.updated atdomain users.62.iddomain users.63.send reportdomain users.63.updated atdomain users.63.iddomain users.64.send reportdomain users.64.updated atdomain users.64.iddomain users.65.send reportdomain users.65.updated atdomain users.65.iddomain users.66.send reportdomain users.66.updated atdomain users.66.idDid not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.
domain users.14.iddomain users.15.send reportdomain users.15.updated atdomain users.15.iddomain users.16.send reportdomain users.16.updated atdomain users.16.iddomain users.17.send reportdomain users.17.updated atdomain users.17.iddomain users.18.send reportdomain users.18.updated atdomain users.18.iddomain users.19.send reportdomain users.19.updated atdomain users.19.iddomain users.20.send reportdomain users.20.updated atdomain users.20.iddomain users.21.send reportdomain users.21.updated atdomain users.21.iddomain users.22.send reportdomain users.22.updated atdomain users.22.iddomain users.23.send reportdomain users.23.updated atdomain users.23.iddomain users.24.send reportdomain users.24.updated atdomain users.24.iddomain users.25.send reportdomain users.25.updated atdomain users.25.iddomain users.26.send reportdomain users.26.updated atdomain users.26.iddomain users.27.send reportdomain users.27.updated atdomain users.27.iddomain users.28.send reportdomain users.28.updated atdomain users.28.iddomain users.29.send reportdomain users.29.updated atdomain users.29.iddomain users.30.send reportdomain users.30.updated atdomain users.30.iddomain users.31.send reportdomain users.31.updated atdomain users.31.iddomain users.32.send reportdomain users.32.updated atdomain users.32.iddomain users.33.send reportdomain users.33.updated atdomain users.33.iddomain users.34.send reportdomain users.34.updated atdomain users.34.iddomain users.35.send reportdomain users.35.updated atdomain users.35.iddomain users.36.send reportdomain users.36.updated atdomain users.36.iddomain users.37.send reportdomain users.37.updated atdomain users.37.iddomain users.38.updated atdomain users.38.iddomain users.39.send reportdomain users.39.updated atdomain users.39.iddomain users.40.send reportdomain users.40.updated atdomain users.40.iddomain users.41.send reportdomain users.41.updated atdomain users.41.iddomain users.42.send reportdomain users.42.updated atdomain users.42.iddomain users.43.send reportdomain users.43.updated atdomain users.43.iddomain users.44.send reportdomain users.44.updated atdomain users.44.iddomain users.45.send reportdomain users.45.updated atdomain users.45.iddomain users.46.send reportdomain users.46.updated atdomain users.46.iddomain users.47.send reportdomain users.47.updated atdomain users.47.iddomain users.48.send reportdomain users.48.updated atdomain users.48.iddomain users.49.send reportdomain users.49.updated atdomain users.49.iddomain users.50.send reportdomain users.50.updated atdomain users.50.iddomain users.51.send reportdomain users.51.updated atdomain users.51.iddomain users.52.send reportdomain users.52.updated atdomain users.52.iddomain users.53.send reportdomain users.53.updated atdomain users.53.iddomain users.54.send reportdomain users.54.updated atdomain users.54.iddomain users.55.send reportdomain users.55.updated atdomain users.55.iddomain users.56.send reportdomain users.56.updated atdomain users.56.iddomain users.57.send reportdomain users.57.updated atdomain users.57.iddomain users.58.send reportdomain users.58.updated atdomain users.58.iddomain users.59.send reportdomain users.59.updated atdomain users.59.iddomain users.60.send reportdomain users.60.updated atdomain users.60.iddomain users.61.send reportdomain users.61.updated atdomain users.61.iddomain users.62.send reportdomain users.62.updated atdomain users.62.iddomain users.63.send reportdomain users.63.updated atdomain users.63.iddomain users.64.send reportdomain users.64.updated atdomain users.64.iddomain users.65.send reportdomain users.65.updated atdomain users.65.iddomain users.66.send reportdomain users.66.updated atdomain users.66.idDid not find what you were looking for?
If this content did not answer your questions, try searching or contacting our support team for further assistance.