fix(jobs): missing permissions to start job (#5955)

* fix(jobs): missing permissions to start job

* Apply suggestions from code review

Co-authored-by: Rowena Jones <[email protected]>

---------

Co-authored-by: Rowena Jones <[email protected]>

Author: thomas-tacquet

pages/serverless-jobs/how-to/run-job.mdx

@@ -53,12 +53,14 @@ The **Job runs** section contains basic monitoring information for your jobs:
 
 Depending on the settings used, Serverless Jobs can have dependencies on other products, such as:
 
+- **Serverless Jobs**: base product permissions
 - **Secret Manager**: to securely inject data into jobs
 - **Container Registry**: to store images of jobs
 
-Executing a Serverless Job can fail if some permissions are not definied properly in an [IAM policy](/iam/how-to/create-policy/), for example:
+Executing a Serverless Job can fail if some permissions are not defined properly in an [IAM policy](/iam/how-to/create-policy/), for example:
 
+- `ServerlessJobsFullAccess` is required to start the Job.
 - If the job definition uses an image from **Container Registry**, add the `ContainerRegistryReadOnly` permission.
 - If the job definition consumes data from **Secret Manager**, add the `SecretManagerSecretAccess` permission.
 
-Refer to the [dedicated documentation](/serverless-jobs/how-to/monitor-job/) for comprehensive information on how to monitor jobs using Scaleway Cockpit.
+Refer to the [dedicated documentation](/serverless-jobs/how-to/monitor-job/) for comprehensive information on how to monitor jobs using Scaleway Cockpit.