Meta’s current Muse Connector Platform guidelines say sensitive write actions, including purchases and sending email, require approval on every use. Their choices are Allow once or Deny, not Always allow. For non-sensitive tools, users can save permission for future uses within the tool’s approved scope and revoke it later. This is a documented boundary for platform connectors, not a newly announced change or a claim about every browser or custom-connector workflow.
Approval also follows the details shown. The platform guide requires fresh approval if a write’s price, recipient or scope changes. Meta’s user-facing oversight guide separately explains where to review connector permissions, inspect task details before approving and check the Activity log for actions and permissions already granted. These are documented controls; we have not tested their enforcement.
Editorial take: Plan unattended work around the point that needs a person, rather than assuming a saved permission makes the whole workflow autonomous. An agent may gather options while a consequential step still waits for review. Before relying on a recurring assignment, identify that decision point and how you will notice it. A pause for the required approval is different from a failed task.