docs(issue 612): updated docs to reflect potential 403 error (#613)

bashbang · web-flow · commit 6bc2e671cf9b · 2025-03-25T22:56:45.000+01:00
* updated docs to reflect potential 403 error when not setting optionl share_with_current_team in monitor_notification_channels
diff --git a/website/docs/r/monitor_notification_channel_custom_webhook.md b/website/docs/r/monitor_notification_channel_custom_webhook.md
@@ -58,7 +58,7 @@ resource "sysdig_monitor_notification_channel_custom_webhook" "sample-custom-web
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_email.md b/website/docs/r/monitor_notification_channel_email.md
@@ -44,7 +44,7 @@ resource "sysdig_monitor_notification_channel_email" "sample_email" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_google_chat.md b/website/docs/r/monitor_notification_channel_google_chat.md
@@ -43,7 +43,7 @@ resource "sysdig_monitor_notification_channel_google_chat" "sample-gchat" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_ibm_event_notification.md b/website/docs/r/monitor_notification_channel_ibm_event_notification.md
@@ -15,7 +15,7 @@ Creates a Sysdig Monitor Notification Channel of type IBM Event Notification (on
 ## Example Usage
 
 ```terraform
-# IBM event notification registering in the same account 
+# IBM event notification registering in the same account
 resource "sysdig_monitor_notification_channel_ibm_event_notification" "sample" {
 	name                    = "Example Channel - IBM Event Notification"
 	enabled                 = true
@@ -27,7 +27,7 @@ resource "sysdig_monitor_notification_channel_ibm_event_notification" "sample" {
 ```
 
 ```terraform
-# IBM event notification registering in different account 
+# IBM event notification registering in different account
 resource "sysdig_monitor_notification_channel_ibm_event_notification" "sample" {
 	name                    = "Example Channel - IBM Event Notification"
 	enabled                 = true
@@ -42,7 +42,7 @@ resource "sysdig_monitor_notification_channel_ibm_event_notification" "sample" {
 
 * `name` - (Required) The name of the Notification Channel. Must be unique.
 
-* `instance_id` - (Required) id of the Event Notifications Instance. Id value can be either an instance id or CRN. If the event notification instance is within the same account, use the actual instance id. If it is in a different account, then use the Event Notifications Instance's [CRN](https://cloud.ibm.com/docs/account?topic=account-crn).   
+* `instance_id` - (Required) id of the Event Notifications Instance. Id value can be either an instance id or CRN. If the event notification instance is within the same account, use the actual instance id. If it is in a different account, then use the Event Notifications Instance's [CRN](https://cloud.ibm.com/docs/account?topic=account-crn).
 
 * `enabled` - (Optional) If false, the channel will not emit notifications. Default is true.
 
@@ -56,7 +56,7 @@ resource "sysdig_monitor_notification_channel_ibm_event_notification" "sample" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_ibm_function.md b/website/docs/r/monitor_notification_channel_ibm_function.md
@@ -66,7 +66,7 @@ resource "sysdig_monitor_notification_channel_ibm_function" "sample-ibm-function
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_msteams.md b/website/docs/r/monitor_notification_channel_msteams.md
@@ -43,7 +43,7 @@ resource "sysdig_monitor_notification_channel_msteams" "sample-msteams" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_opsgenie.md b/website/docs/r/monitor_notification_channel_opsgenie.md
@@ -44,7 +44,7 @@ resource "sysdig_monitor_notification_channel_opsgenie" "sample-opsgenie" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_pagerduty.md b/website/docs/r/monitor_notification_channel_pagerduty.md
@@ -39,10 +39,10 @@ resource "sysdig_monitor_notification_channel_pagerduty" "sample-pagerduty" {
 
 * `enabled` - (Optional) If false, the channel will not emit notifications. Default is true.
 
-* `notify_when_ok` - (Optional) Send a new notification when the alert condition is 
+* `notify_when_ok` - (Optional) Send a new notification when the alert condition is
     no longer triggered. Default is false.
 
-* `notify_when_resolved` - (Optional) Send a new notification when the alert is manually 
+* `notify_when_resolved` - (Optional) Send a new notification when the alert is manually
     acknowledged by a user. Default is false.
 
 * `send_test_notification` - (Optional) Send an initial test notification to check
@@ -57,7 +57,7 @@ In addition to all arguments above, the following attributes are exported:
 * `version` - (Computed) The current version of the Notification Channel.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Import
 
diff --git a/website/docs/r/monitor_notification_channel_prometheus_alert_manager.md b/website/docs/r/monitor_notification_channel_prometheus_alert_manager.md
@@ -51,7 +51,7 @@ resource "sysdig_monitor_notification_channel_prometheus_alert_manager" "sample"
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_slack.md b/website/docs/r/monitor_notification_channel_slack.md
@@ -67,7 +67,7 @@ In addition to all arguments above, the following attributes are exported:
 * `version` - (Computed) The current version of the Notification Channel.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Import
 
diff --git a/website/docs/r/monitor_notification_channel_sns.md b/website/docs/r/monitor_notification_channel_sns.md
@@ -43,7 +43,7 @@ resource "sysdig_monitor_notification_channel_sns" "sample-amazon-sns" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_team_email.md b/website/docs/r/monitor_notification_channel_team_email.md
@@ -43,7 +43,7 @@ resource "sysdig_monitor_notification_channel_team_email" "sample-gchat" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_victorops.md b/website/docs/r/monitor_notification_channel_victorops.md
@@ -46,7 +46,7 @@ resource "sysdig_monitor_notification_channel_victorops" "sample-victorops" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/monitor_notification_channel_webhook.md b/website/docs/r/monitor_notification_channel_webhook.md
@@ -62,7 +62,7 @@ In addition to all arguments above, the following attributes are exported:
 * `version` - (Computed) The current version of the Notification Channel.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Import
 
diff --git a/website/docs/r/secure_notification_channel_email.md b/website/docs/r/secure_notification_channel_email.md
@@ -44,7 +44,7 @@ resource "sysdig_secure_notification_channel_email" "sample_email" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/secure_notification_channel_msteams.md b/website/docs/r/secure_notification_channel_msteams.md
@@ -33,10 +33,10 @@ resource "sysdig_secure_notification_channel_msteams" "sample-msteams" {
 
 * `enabled` - (Optional) If false, the channel will not emit notifications. Default is true.
 
-* `notify_when_ok` - (Optional) Send a new notification when the alert condition is 
+* `notify_when_ok` - (Optional) Send a new notification when the alert condition is
     no longer triggered. Default is false.
 
-* `notify_when_resolved` - (Optional) Send a new notification when the alert is manually 
+* `notify_when_resolved` - (Optional) Send a new notification when the alert is manually
     acknowledged by a user. Default is false.
 
 * `send_test_notification` - (Optional) Send an initial test notification to check
@@ -55,7 +55,7 @@ In addition to all arguments above, the following attributes are exported:
 * `version` - (Computed) The current version of the Notification Channel.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Import
 
diff --git a/website/docs/r/secure_notification_channel_opsgenie.md b/website/docs/r/secure_notification_channel_opsgenie.md
@@ -44,7 +44,7 @@ resource "sysdig_secure_notification_channel_opsgenie" "sample-opsgenie" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/secure_notification_channel_pagerduty.md b/website/docs/r/secure_notification_channel_pagerduty.md
@@ -39,10 +39,10 @@ resource "sysdig_secure_notification_channel_pagerduty" "sample-pagerduty" {
 
 * `enabled` - (Optional) If false, the channel will not emit notifications. Default is true.
 
-* `notify_when_ok` - (Optional) Send a new notification when the alert condition is 
+* `notify_when_ok` - (Optional) Send a new notification when the alert condition is
     no longer triggered. Default is false.
 
-* `notify_when_resolved` - (Optional) Send a new notification when the alert is manually 
+* `notify_when_resolved` - (Optional) Send a new notification when the alert is manually
     acknowledged by a user. Default is false.
 
 * `send_test_notification` - (Optional) Send an initial test notification to check
@@ -57,7 +57,7 @@ In addition to all arguments above, the following attributes are exported:
 * `version` - (Computed) The current version of the Notification Channel.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Import
 
diff --git a/website/docs/r/secure_notification_channel_prometheus_alert_manager.md b/website/docs/r/secure_notification_channel_prometheus_alert_manager.md
@@ -51,7 +51,7 @@ resource "sysdig_secure_notification_channel_prometheus_alert_manager" "sample"
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/secure_notification_channel_slack.md b/website/docs/r/secure_notification_channel_slack.md
@@ -36,10 +36,10 @@ resource "sysdig_secure_notification_channel_slack" "sample-slack" {
 
 * `enabled` - (Optional) If false, the channel will not emit notifications. Default is true.
 
-* `notify_when_ok` - (Optional) Send a new notification when the alert condition is 
+* `notify_when_ok` - (Optional) Send a new notification when the alert condition is
     no longer triggered. Default is false.
 
-* `notify_when_resolved` - (Optional) Send a new notification when the alert is manually 
+* `notify_when_resolved` - (Optional) Send a new notification when the alert is manually
     acknowledged by a user. Default is false.
 
 * `send_test_notification` - (Optional) Send an initial test notification to check
@@ -58,7 +58,7 @@ In addition to all arguments above, the following attributes are exported:
 * `version` - (Computed) The current version of the Notification Channel.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Import
 
diff --git a/website/docs/r/secure_notification_channel_sns.md b/website/docs/r/secure_notification_channel_sns.md
@@ -43,7 +43,7 @@ resource "sysdig_secure_notification_channel_sns" "sample-amazon-sns" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/secure_notification_channel_team_email.md b/website/docs/r/secure_notification_channel_team_email.md
@@ -43,7 +43,7 @@ resource "sysdig_secure_notification_channel_team_email" "sample-gchat" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/secure_notification_channel_victorops.md b/website/docs/r/secure_notification_channel_victorops.md
@@ -46,7 +46,7 @@ resource "sysdig_secure_notification_channel_victorops" "sample-victorops" {
     if the notification channel is working. Default is false.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Attributes Reference
 
diff --git a/website/docs/r/secure_notification_channel_webhook.md b/website/docs/r/secure_notification_channel_webhook.md
@@ -62,7 +62,7 @@ In addition to all arguments above, the following attributes are exported:
 * `version` - (Computed) The current version of the Notification Channel.
 
 * `share_with_current_team` - (Optional) If set to `true` it will share notification channel only with current team (in which user is logged in).
-  Otherwise, it will share it with all teams, which is the default behaviour.
+  Otherwise, it will share it with all teams, which is the default behaviour. Although this is an optional setting, beware that if you have lower permissions than admin you may see a `error: 403 Forbidden` if this is not set to `true`.
 
 ## Import
 
