AWS explains automatic action review in Amazon Quick

What an approval means

AWS describes a separate model reviewing eligible actions against the request and a bounded conversation context. Each automatic approval applies once to the exact action and parameters; it grants no ongoing permission. Model judgment can be wrong. An approval record also does not prove completion: destination records, such as a sent email, establish whether the action finished.

Existing controls come first

The user guide limits availability to desktop and mobile apps, excluding the web version. Automated review requires the connector’s “Let user choose” setting and the user’s “Ask each time” permission. Policy denials remain blocked, and required human approvals still go to a person. Consequential actions and review failures, including timeouts, return to the user. If their administrator allows the feature, users can turn it off across conversations and scheduled runs; eligible actions then wait for their review.

Check the effective permission profile

AWS’s permission documentation explains that restricting a category blocks its current and future capabilities except explicit allowances. The restriction belongs to that profile; other profiles do not inherit it. Resolution uses the first matching level: user, then role, then account. An account restriction therefore does not automatically govern someone with a user-level profile. AWS recommends testing these configurations before production deployment.