Administration 

Backend access and permissions 

Grant a backend user group access to Media > AutoAlt.ai in the usual TYPO3 backend module permissions. Users also need access to the relevant FAL storage and permission to edit file metadata. The extension does not bypass TYPO3 file mount or metadata permissions.

For more granular control, add the following Page TSconfig to a backend user or group configuration:

tx_alttextgenerator.permissions {
    generateSingle = 1
    runBulkGeneration = 1
    manageSettings = 0
}

The values are booleans:

• generateSingle permits the one-image generation control in Filelist.
• runBulkGeneration permits bulk generation workflows and retries.
• manageSettings permits access to the extension settings screens.

Set permissions to 0 where the user should not perform that task. Users must still have the ordinary TYPO3 permissions required for the affected files and metadata records.

API connection and credentials 

Open Media > AutoAlt.ai > Extension Configuration to connect the site to AutoAlt.ai. A user can connect with an existing API key or create/connect an account through the email verification flow.

Treat the API key as a secret:

• Enter it only in the TYPO3 configuration screen or a secure deployment configuration.
• Never commit it to Git, documentation, screenshots, tickets, or browser console logs.
• Rotate the key immediately if it is exposed.
• Remove or replace the key before transferring a site to another team.

Recommended rollout 

1. Install the extension and apply the database schema.
2. Connect a test or production API key.
3. Configure allowed file extensions, writing style, length, and optional keywords.
4. Test one or two representative images in every required language.
5. Run a small batch and have an editor review the output.
6. Enable upload automation only when results are consistently suitable.
7. Give bulk and settings permissions only to users who need them.

This staged rollout keeps metadata quality under editorial control and helps avoid accidental changes to an entire library.

Logging and monitoring 

Enable API-error logging in the extension configuration when diagnosing connection or generation problems. Entries are written through TYPO3's logging framework and can be reviewed in System > Log. The extension also displays recent entries in its Settings error-log panel, where they can be cleared after review.

Check the following after a deployment or configuration change:

• API connection status and credit balance;
• a single test generation;
• TYPO3's System > Log for errors; and
• the extension history for unexpected failures or skipped files.

Upgrades and backups 

Before an extension update, back up the database and application files using your normal TYPO3 deployment process. After updating Composer dependencies, run the extension setup command, then review any proposed changes in the Database Analyzer:

vendor/bin/typo3 extension:setup

Clear TYPO3 caches, verify the connection, and run a small generation test before starting a production batch. Review the release notes and the Changelog for each update.