docs: scoped token's restricted access does not support standby

sources/platform/actors/running/actor_standby.md

@@ -50,6 +50,11 @@ This approach can be useful if you cannot modify the request headers.
     https://rag-web-browser.apify.actor/search?query=apify&token=my_apify_token
     ```
 
+:::tip
+You can use [scoped tokens](/platform/integrations/api#limited-permissions) to send standby requests. This is useful if you want to allow a 3rd party service to use your Actor while not exposing your whole account.
+
+However, using a scoped token to [restrict what a Standby Actor can access](/platform/integrations/api#restricted-access-restrict-what-actors-can-access-using-the-scope-of-this-actor) is currently not supported.
+:::
 
 ## Can I still run the Actor in normal mode
 

sources/platform/integrations/programming/api.md

@@ -140,6 +140,10 @@ When you run an Actor with a scoped token in this mode, Apify will inject a toke
 
 This way you can be sure that Actors won't accidentally—or intentionally—access any data they shouldn't. However, Actors might not function properly if the scope is not sufficient.
 
+:::caution
+This mode is currently not supported for Actors running in the [Standby mode](/platform/actors/running/standby). You can still send standby requests using a scoped token configured with the restricted access, but we can't guarantee it will always work as expected.
+:::
+
 :::tip
 This restriction is _transitive_, which means that if the Actor runs another Actor, its access will be restricted as well.
 :::