summaryrefslogtreecommitdiffstats
path: root/docs/cloud/manage/plans.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/cloud/manage/plans.md')
-rw-r--r--docs/cloud/manage/plans.md21
1 files changed, 12 insertions, 9 deletions
diff --git a/docs/cloud/manage/plans.md b/docs/cloud/manage/plans.md
index 9180ab5a0..23077f898 100644
--- a/docs/cloud/manage/plans.md
+++ b/docs/cloud/manage/plans.md
@@ -19,7 +19,7 @@ The plan is an attribute that is directly attached to your space(s) and that dic
Netdata Cloud plans, with the exception of Community, work as subscriptions and overall consist of two pricing components:
-* A flat fee component, that is a price per space, and
+* A flat fee component, that is applied on yearly subscriptions for the [comitted-nodes](#committed-nodes) charte (space subscription fee has been waived off)
* An on-demand metered component, that is related to your usage of Netdata which directly links to the [number of nodes you have running](#running-nodes-and-billing)
Netdata provides two billing frequency options:
@@ -55,16 +55,13 @@ If, for a given month, your usage is over these committed nodes we will charge t
It is ok to change your mind. We allow to change your plan, billing frequency or adjust the committed nodes, on yearly plans, at any time.
-To achieve this you will need to:
+To achieve this you can check the [Update plan](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/view-plan-billing.md#update-plan) section.
-* Move to the Community plan, where we will cancel the current subscription and:
- * Issue a credit to you for the unused period, in case you are on a **yearly plan**
- * Charge you only for the current used period and issue a credit for the unused period related to the flat fee, in case you are on a **monthly plan**
-* Select the new subscription with the change that you want
-
-> ⚠️ On a move to Community (cancellation of an active subscription), please note that you will have all your notification methods configurations active **for a period of 24 hours**.
+> ⚠️ On a downgrade (going to a new plan with less benefits) or cancellation of an active subscription, please note that you will have all your notification methods configurations active **for a period of 24 hours**.
> After that, any notification methods unavailable in your new plan at that time will be automatically disabled. You can always re-enable them once you move to a paid plan that includes them.
+> ⚠️ Downgrade or cancellation may affect users in your Space. Please check what roles are available on the [each plans](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/plans.md#areas-impacted-by-plans). Users with unavailable roles on the new plan will immediately have restricted access to the Space.
+
> ⚠️ Any credit given to you will be available to use on future paid subscriptions with us. It will be available until the the **end of the following year**.
### Areas impacted by plans
@@ -104,7 +101,13 @@ The plan on your space will determine what type of notifications methods will be
* **Pro** - Email, Discord and webhook
* **Business** - Unlimited, this includes Slack, PagerDuty, Opsgenie etc.
-For mode details check the documentation under [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md).
+For more details check the documentation under [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#alert-notifications).
+
+##### Alert notification silencing rules
+
+The plan on your space will determine if you are able to add alert notification silencing rules since this feature will only be available for paid plans: **Pro** or **Business**.
+
+For more details check the documentation under [Alert Notifications](https://github.com/netdata/netdata/blob/master/docs/cloud/alerts-notifications/notifications.md#silencing-alert-notifications).
### Related Topics