Configuration 

Where settings are stored 

The settings of the module are stored in the TYPO3 registry (table sys_registry , namespace tx_contextreporter), not in config/system/settings.php. Each section is saved on its own; the page shows when and by whom the settings were last saved.

Values in $GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['context_reporter'] take precedence over the module. They are shown read-only on the settings page. Use this to pin values per environment, for example to switch off deliveries on a staging system that runs on a copy of the production database:

if (!\TYPO3\CMS\Core\Core\Environment::getContext()->isProduction()) {
    $GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['context_reporter']['email']['enabled'] = false;
    $GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['context_reporter']['webhook']['enabled'] = false;
}

The keys are the setting names below, grouped by section, for example ['reporting']['retentionDays']. Each key is pinned on its own; keys that are not set in the system configuration stay editable. The extension has no Extension Configuration form.

General 

Privacy 

The Privacy section also lists what every report contains and what it never contains, see Allowlist first.

Reports and storage 

The section also shows how many reports, screenshots (with their size) and delivery attempts are stored, and a preview of the cleanup. With the default retention, the history grows with every report.

Email 

Emails are sent with the mail transport of TYPO3 ($GLOBALS['TYPO3_CONF_VARS']['MAIL'], Admin Tools > Settings > Configure Installation-Wide Options). Context Reporter has no SMTP settings of its own.

Webhook 

The webhook is configured by trusted administrators: the endpoint can be any host the TYPO3 server can reach. See Webhook: trusted administrators for the consequences and how to pin the webhook settings.

The secret fields are write-only: the settings page shows whether a value is configured, configured via an environment variable, or whether the environment variable is missing, but never the value. Leave a field empty to keep the stored value, or tick Remove the stored value.

Send test webhook posts the event test with the saved settings, also while webhook delivery is switched off, see Test deliveries. Test deliveries are not added to the delivery history.

Secrets from environment variables 

webhook.url, webhook.secret and webhook.authHeaderValue accept a value of the form %env(NAME)%, both in the settings page and in the system configuration. The value is read from the environment variable NAME when a report is delivered, so the secret itself is not stored in the database or in a configuration file. Settings that are entered directly are stored in sys_registry ; prefer environment variables for production secrets.

The resolved value is sent to the webhook endpoint, as signing key or header value. Any environment variable of the web server process can be referenced, so only reference variables that are meant for the webhook, and see Webhook: trusted administrators.

$GLOBALS['TYPO3_CONF_VARS']['EXTENSIONS']['context_reporter']['webhook']['secret']
    = '%env(CONTEXT_REPORTER_WEBHOOK_SECRET)%';

Secrets are never shown in the backend, and they are removed from stored error messages.

User TSconfig 

Disable reporting for a user or group:

options.contextReporter.enable = 0

The toolbar button, the context menu item and the editing form button are removed, and the server rejects reports from this user.

Hide the context menu item for a table (standard TYPO3 option). Files and folders use the tables sys_file and sys_file_storage:

options.contextMenu.table.tt_content.disableItems = contextReporterReport
options.contextMenu.table.sys_file.disableItems = contextReporterReport

The list view of the file list shows the actions of options.file_list.primaryActions as buttons and all other actions in the More options menu. The extension ships this user TSconfig, which is the TYPO3 default plus the report action:

options.file_list.primaryActions = view, metadata, translations, delete, contextReporterReport

If your project defines its own list, add contextReporterReport to it to keep the action visible.

Access 

• Every backend user can create reports, unless disabled with TSconfig.
• A report can only reference pages and records that the reporter can access (web mounts, page permissions and table permissions), and files and folders in the reporter's file storages and file mounts, with read permission. File metadata can only be reported for accessible files. In a workspace, only live records and versions of the current workspace can be reported. See Protection of reports.
• The System > Context Reports module, including the settings, test deliveries, the cleanup and the review state, is available to administrators only.
• Reporters can download their own reports.