Note that older API-key schedules keep the old rules until they run out

Schedules an API or widget chat set before schedules recorded their
origin run as the owner's own until they fire or expire.

docs/content/Guides/Connectors.mdx

@@ -53,6 +53,8 @@ An agent called with its API key (the website widget, the API) runs with its own
 
 The same list covers people who open the agent from its public link without being on a team it's shared with, and anything they schedule from that chat. They can't approve write actions on the owner's accounts or credentials, so those run only when the owner allows them there. On a tool where each member connects their own account, they approve writes on their own account as usual.
 
+Schedules that an API or widget chat set up before this version still run as the owner's own, without this list, until they fire or expire. Schedules set from a public link follow the list from their next run.
+
 A webhook is the owner's own automation (its URL is a secret), so its runs are not limited by this list. Nobody can approve during a webhook run, so it still skips every action that needs approval.
 
 ### What answers show