Weblate project-level permission boundaries with automatic translation suggestions

Permission inheritance for machine-translated strings

Weblate applies project-level permission boundaries to control whether contributors can commit translations directly or require coordinator review. When automatic translation suggestions are enabled via the integrated machine translation APIs, the system populates translation fields with suggestions that contributors can accept with a single action.

The documentation indicates that permission checks occur at commit time, but it does not explicitly clarify whether accepting a machine-translated suggestion constitutes a "commit" action for permission evaluation purposes. This creates ambiguity when a project is configured to require review for human-contributed translations but the team wants to allow direct acceptance of high-confidence machine suggestions without coordinator intervention.

Assuming Weblate 5.x with the standard review workflow enabled, the desired behavior is to differentiate permission enforcement based on translation origin — human input versus accepted machine suggestion — without disabling the review requirement entirely.

• Does accepting a machine translation suggestion trigger the same permission check as a manual translation edit?
• Can the review workflow be configured to auto-approve suggestions from specific machine translation backends while retaining review for manual entries?
• Is there a supported configuration to log the translation origin (human vs. machine) for audit purposes when permissions are evaluated?