docs(srv): add info on trigger permissions for faas caas MTA-5533

pages/serverless-containers/how-to/add-trigger-to-a-container.mdx

@@ -24,7 +24,6 @@ A trigger can be an HTTP request, a message from a queue or stream, a CRON sched
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
 - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
-- Created a [containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/)
 - Deployed a container from [Scaleway Container Registry](/serverless-containers/how-to/deploy-container/) or an [external registry](/serverless-containers/how-to/deploy-container/)
 - [Created credentials](/messaging/how-to/create-credentials/) for Scaleway Queues
 - [Created a queue](/messaging/how-to/create-manage-queues/)
@@ -39,6 +38,12 @@ You can create triggers on private containers, but to update the privacy of a co
 
 ## Queue triggers
 
+<Message type="note">
+You must have at least `MessagingAndQueuingReadOnly` permissions in the project containing the queue to add a queue trigger to Serverless Containers.
+
+Refer to the [permissions sets documentation](/iam/reference-content/permission-sets/) for more information.
+</Message>
+
 [Queue triggers](/serverless-containers/concepts/#queue-trigger) allow you to automatically invoke a container using events stored in a [Scaleway queue](/messaging/concepts/#queues).
 
 Only queues created with the Scaleway Queues product are compatible with Serverless Containers.
@@ -61,6 +66,12 @@ When a message is pushed to the selected queues, the container will be triggered
 
 ## NATS triggers
 
+<Message type="note">
+You must have at least `MessagingAndQueuingReadOnly` permissions in the project containing the NATS account to add to a Serverless Container.
+
+Refer to the [permissions sets documentation](/iam/reference-content/permission-sets/) for more information.
+</Message>
+
 [NATS triggers](/serverless-containers/concepts/#nats-trigger) allow you to automatically invoke a container using messages sent in a [NATS](/messaging/concepts/#nats) subject.
 
 [Scaleway NATS subjects](/messaging/quickstart/#quickstart-for-nats) are compatible with Serverless Containers.

pages/serverless-functions/how-to/add-trigger-to-a-function.mdx

@@ -39,6 +39,13 @@ You can create triggers on private functions, but to update the privacy of a fun
 
 ## Queue triggers
 
+<Message type="note">
+You must have at least `MessagingAndQueuingReadOnly` permissions in the project containing the queue to add a queue trigger to Serverless Functions.
+
+Refer to the [permissions sets documentation](/iam/reference-content/permission-sets/) for more information.
+</Message>
+
+
 [Queue triggers](/serverless-containers/concepts/#queue-trigger) allow you to automatically invoke a function using events stored in a [queue](/messaging/concepts/#queue).
 
 Only queues created with the Scaleway Queues product are compatible with Serverless Functions.
@@ -59,6 +66,13 @@ The configuration of the queue retention may affect the behavior of the trigger.
 
 ## NATS triggers
 
+<Message type="note">
+You must have at least `MessagingAndQueuingReadOnly` permissions in the project containing the NATS account to add to Serverless Functions.
+
+Refer to the [permissions sets documentation](/iam/reference-content/permission-sets/) for more information.
+</Message>
+
+
 [NATS triggers](/serverless-functions/concepts/#nats-trigger) allow you to automatically invoke a function using messages sent in a [NATS](/messaging/concepts/#nats) subject.
 
 Scaleway [NATS subjects](/messaging/quickstart/#quickstart-for-nats) are compatible with Serverless Functions.