diff --git a/cloud/assets/login-page-oauth-buttons.png b/cloud/assets/login-page-oauth-buttons.png
index dabd04bf1a..c1f61ae6bb 100644
Binary files a/cloud/assets/login-page-oauth-buttons.png and b/cloud/assets/login-page-oauth-buttons.png differ
diff --git a/cloud/assets/product-features-automatic-storage-extension-configuration-edit.png b/cloud/assets/product-features-automatic-storage-extension-configuration-edit.png
new file mode 100644
index 0000000000..cb1f3573d2
Binary files /dev/null and b/cloud/assets/product-features-automatic-storage-extension-configuration-edit.png differ
diff --git a/cloud/assets/product-features-automatic-storage-extension-configuration.png b/cloud/assets/product-features-automatic-storage-extension-configuration.png
index b83c335f0b..bd2440fa59 100644
Binary files a/cloud/assets/product-features-automatic-storage-extension-configuration.png and b/cloud/assets/product-features-automatic-storage-extension-configuration.png differ
diff --git a/cloud/assets/product-features-autoscaling-configuration-edit.png b/cloud/assets/product-features-autoscaling-configuration-edit.png
index 2ae544ac93..3db6c7928e 100644
Binary files a/cloud/assets/product-features-autoscaling-configuration-edit.png and b/cloud/assets/product-features-autoscaling-configuration-edit.png differ
diff --git a/cloud/assets/product-features-autoscaling-configuration.png b/cloud/assets/product-features-autoscaling-configuration.png
index 340ff62bf7..69894299e6 100644
Binary files a/cloud/assets/product-features-autoscaling-configuration.png and b/cloud/assets/product-features-autoscaling-configuration.png differ
diff --git a/cloud/cloud-account.mdx b/cloud/cloud-account.mdx
index d076814889..d4ac9af935 100644
--- a/cloud/cloud-account.mdx
+++ b/cloud/cloud-account.mdx
@@ -68,6 +68,10 @@ Per-product access is assigned as a single **preset** — you choose one preset
The **Monitoring/OpenTelemetry** and **Power BI** features are a special case. **Enabling or disabling** them requires the **Manager** (or **Admin**) preset **together with** the **Security admin** add-on. To only **configure** such a feature once it is enabled, the **Security admin** add-on is sufficient.
+
+Removing a user from the account — or revoking their permissions for a single product — also removes their email address from every [product alert](./cloud-maintenance-troubleshooting.mdx#alerts) rule they were subscribed to. If they were a rule's **last** remaining subscriber, that rule is **deleted**. Prefer a shared alias as a rule's subscriber when the alert matters to your operations.
+
+
### Who can manage product permissions
Product permissions are managed by the **Account Owner** and by users with the **Account with User Management** role, subject to a **subset rule**:
@@ -100,3 +104,7 @@ This can be useful if you need to separate environments, teams, or billing conte
However, creating multiple Cloud Accounts under one email is not available through the self-service UI.
To set this up, please contact *RavenDB Cloud Support* and request a multi-account configuration.
+
+Once you have more than one account, use the **account switcher** at the top of the
+[Portal sidebar](./portal/cloud-portal.mdx#cloud-portal-overview) to move between them. Each account is identified there
+by its **domain name**.
diff --git a/cloud/cloud-api.mdx b/cloud/cloud-api.mdx
index 3714c95421..8dcb26a7fa 100644
--- a/cloud/cloud-api.mdx
+++ b/cloud/cloud-api.mdx
@@ -27,7 +27,7 @@ The API is defined using the OpenAPI 3.0 standard.
## Swagger & available clients
-
+
You can use [Swagger UI](https://api.cloud.ravendb.net/swagger/index.html) to perform the API calls directly from the website
or use [Swagger JSON](https://api.cloud.ravendb.net/api/v1/swagger.json) to prepare your own API client.
diff --git a/cloud/cloud-aws-marketplace.mdx b/cloud/cloud-aws-marketplace.mdx
index bc8a5c3c1b..6dd8b238e3 100644
--- a/cloud/cloud-aws-marketplace.mdx
+++ b/cloud/cloud-aws-marketplace.mdx
@@ -59,23 +59,23 @@ For the most up-to-date information, see [AWS Marketplace Sellers Tax Help](http
To subscribe your *AWS* account to the *RavenDB Cloud*, search for the **RavenDB Cloud** offer in *AWS Marketplace* and click on it.
-
+
In the main page of the offer, click **View purchase options**.
-
+
Then, please click **Subscribe** down below.
-
+
At the top you will see:
-
+
Please click **Set up your account**.
You'll be redirected to RavenDB Cloud, once you have subscribed, the next step is to configure the account in the *RavenDB Cloud*.
Provide the necessary information required to end the registration process:
-
+
1. **Email Address**
Provide an email address that you will use in RavenDB Cloud.
@@ -92,7 +92,7 @@ Provide the necessary information required to end the registration process:
After providing the information, please click **Sign up**.
Your account is now ready to use. To sign in to the account, click **Continue to sign in**.
-
+
Successful registration process is also confirmed by an email from *AWS Marketplace*.
@@ -103,16 +103,16 @@ Successful registration process is also confirmed by an email from *AWS Marketpl
To cancel your subscription, go to *AWS Marketplace* service in AWS account which you used to subscribe to RavenDB Cloud.
-
+
Click **Manage** on the **RavenDB Cloud** product.
-
+
Navigate to **Cancel subscription**.
-
+
Confirm and finalize the process.
-
+
Subscription cancellation is **irreversible**. Your account and data and will be permanently lost.
diff --git a/cloud/cloud-backup-and-restore.mdx b/cloud/cloud-backup-and-restore.mdx
index a61d260031..3500eca677 100644
--- a/cloud/cloud-backup-and-restore.mdx
+++ b/cloud/cloud-backup-and-restore.mdx
@@ -49,13 +49,16 @@ You can [contact support](../cloud/portal/cloud-portal-support-tab.mdx) to prolo
#### The Backup Task
-To view or activate the mandatory backup task, open your product's management studio and -
+The mandatory backup is a [Server-Wide Backup](../7.2/backup/create/periodic-tasks/server-wide-backup) task, so it
+covers every database on the product rather than being defined per database.
-* Choose the database whose backup task you want to view
-* Click **Manage Ongoing Tasks**
-* Click the "Server Wide Backup" task.
+To view it, open your product's RavenDB Studio and -
-
+* Choose any database on the product
+* Open the **Ongoing Tasks** view
+* Click the **Server Wide Backup** task.
+
+
#### Tier Requirements and Failure Disclaimer
@@ -180,13 +183,13 @@ Your mandatory backup files are encrypted.
You can create your own [ongoing backup tasks](https://ravendb.net/docs/article-page/4.2/Csharp/studio/database/tasks/ongoing-tasks/backup-task)
on your RavenDB cloud instance, as you would off-cloud.
Use your cloud instance's management Studio to create a new task.
-
+
Add a Backup task
-
+
You can store custom-backup files on an unrelated cloud service like an S3 bucket, a Glacier vault, or an Azure platform.
Activate and configure your unrelated cloud storage service, e.g. the bucket in which your backup files would be kept.
-
+
@@ -199,27 +202,27 @@ Backup files that have already been created, are listed in the backups tab.
Its backups will be shown, listed by the databases they've been created for.
* Click "Generate Restore Link" for the database you want to restore.
The backup link window will open.
- 
+ 
#### Restore the Database
Clicking the **Generate Restore Link** button will show you a simple procedure. Follow it to restore your database.
-
+
* **A.** Create a **New Database From Backup**
- 
+ 
* **B.** Choose **Cloud** as your Source
- 
+ 
* **C.** Copy the Backup Link you've been given in the Backups Tab, to the **Backup Link** box here.
- 
+ 
* **D.** Choose a **Restore Point**
- 
+ 
* **E.** Encryption Key for an **Encrypted** Database
If your original database **is** encrypted, its backup has been encrypted with the same key. Find it and paste it here.
- 
+ 
* **F.** Encryption Key for an **Unencrypted** Database
If your original database is **not** encrypted, we used your account-wide encryption key to encrypt your backup file.
Copy it from the right Backups Tab box.
- 
+ 
diff --git a/cloud/cloud-features.mdx b/cloud/cloud-features.mdx
index a7559d3b7f..73e3f2b9b0 100644
--- a/cloud/cloud-features.mdx
+++ b/cloud/cloud-features.mdx
@@ -36,7 +36,7 @@ described [here](https://ravendb.net/docs/article-page/latest/csharp/integration
*Power BI* is a security-related feature: **enabling or disabling** it requires the [**Manager** (or **Admin**) preset together with the **Security admin** add-on](./cloud-account.mdx#permission-presets), while the **Security admin** add-on alone is enough to *configure* it once enabled.
-## Configuration
+### Configuration
*Power Bi* IPs must be configured after enabling *PowerBi* feature.
@@ -49,7 +49,7 @@ Your product will be restarted automatically node by node to apply settings need
To access *Power Bi* Configuration View click **Configure** Button in *Power Bi* feature row. Here you can edit your IP
addresses that will have access to *RavenDB Power Bi* port.
-
+
*Power Bi* IPs entries are [CIDR ranges](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)
@@ -120,7 +120,15 @@ data collection and analysis by an OpenTelemetry retriever.
*Monitoring* (SNMP / *OpenTelemetry*) is a security-related feature: **enabling or disabling** it requires the [**Manager** (or **Admin**) preset together with the **Security admin** add-on](./cloud-account.mdx#permission-presets), while the **Security admin** add-on alone is enough to *configure* it once enabled.
-## Configuration
+
+Enabling *Monitoring* also unlocks the product's **Alerts** tab, where you can have
+[Cluster Health](./cloud-maintenance-troubleshooting.mdx#cluster-health) events emailed to you as a daily summary or as
+per-event custom alerts. See [Alerts](./cloud-maintenance-troubleshooting.mdx#alerts).
+
+Disabling *Monitoring* **discards** the product's alert rules.
+
+
+### Configuration
Click the **Configure** button in the *Monitoring* feature row to configure this feature.
You will be taken to the *Monitoring Configuration View*, which is divided into two tabs:
@@ -137,8 +145,8 @@ You will be taken to the *Monitoring Configuration View*, which is divided into
- Specify where these Meters should be sent.
-
-
+
+
OpenTelemetry feature is available only for *RavenDB* **6.2 and newer**.
@@ -156,7 +164,7 @@ Your product will be restarted automatically (node by node) to apply settings ne
This section allows you to specify IPs that will have access to your product using the *SNMP* protocol.
-
+
### SNMPv3 Monitoring credentials
@@ -183,37 +191,86 @@ This section allows you to select meters and specify where these should be sent
You can read step by step OpenTelemetry & Grafana configuration [here](https://ravendb.net/articles/grafana-cloud-configuration-with-opentelemetry).
-
+
## Autoscaling
-*RavenDB Cloud* allows you to autoscale your *RavenDB Cloud* instances based on the CPU usage.
+*RavenDB Cloud* can resize your instance automatically, within a range you choose, so it follows your actual workload
+instead of being fixed to the size you provisioned.
+
+Scaling is driven by three sustained signals, each watched independently:
+
+* **Load average** — how busy the node's CPUs are.
+* **Available memory** — how much memory is left for processing.
+* **IO wait** — how much time the node spends waiting on disk.
+
+Each signal has a low and a high limit, and each limit has its own duration. A limit must be breached for the whole of
+its duration before it counts, and a **grace period** then applies before the resize itself, so a brief spike never
+moves your instance.
-## Configuration
+### Autoscaling range
-Click **Configure** Button in *Autoscaling* feature row in order to configure this feature.
-You will see Autoscaling Configuration View. It's separated into downscaling parameters and upscaling parameters.
+**Lowest type** and **Highest type** bound the resizing. Autoscaling never moves your instance below the lowest or above
+the highest type, and both bounds are inclusive.
-| Parameter | Description |
-|-----------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------|
-| Highest Type | The maximum virtual machine size (inclusive) available for upscaling. |
-| Upscaling Grace Period | The time delay before upscaling begins after a high resource threshold is exceeded, allowing the system to avoid immediate scaling. |
-| High Cpu Threshold | The average CPU usage percentage from last *High CPU Threshold Duration* that triggers the upscaling process. |
-| High Cpu Threshold Duration | The duration for which the average CPU usage must exceed the threshold before triggering upscaling. |
-| Upscaling Step | Determines by how many instances upscaling should take place in one go. For example with step set to 2 it will scale up from *Dev10* to *Dev30*. |
-| Lowest Type | The minimum virtual machine size (inclusive) available for downscaling. |
-| Downscaling Grace Period | The time delay before downscaling begins after a low resource threshold is exceeded, allowing the system to avoid immediate scaling. |
-| Low Cpu Threshold | The average CPU usage percentage from last *Low CPU Threshold Duration* that triggers the downscaling process. |
-| Low Cpu Threshold Duration | The duration for which the average CPU usage must exceed the threshold before triggering downscaling. |
-| Downscaling Step | Determines by how many instances downscaling should take place in one go. For example with step set to 2 it will scale down from *Dev30* to *Dev10*. |
+### Configuration
-
+Click the **Configure** button in the *Autoscaling* feature row to open the Autoscaling Configuration view, which is
+split into upscaling and downscaling parameters.
-You can edit Autoscaling parameters by clicking on **Edit** button.
+
-
+#### Upscaling parameters
+
+| Parameter | Range | Description |
+|--------------------------------------|-------------|------------------------------------------------------------------------------------------------------|
+| Upscaling grace period | 3–60 min | The delay before upscaling begins after a high resource threshold is exceeded, so short spikes do not trigger a resize. |
+| High load average threshold | 50–90% | The average load percentage, over the *high load average threshold duration*, that triggers upscaling. |
+| High load average threshold duration | 180–600 sec | How long the average load must stay above the threshold before upscaling is triggered. |
+| Low available memory threshold | 1–15% | The available memory percentage below which upscaling is triggered. |
+| Low available memory duration | 180–600 sec | How long available memory must stay below the threshold before upscaling is triggered. |
+| IO wait max value | 25–95% | The IO wait percentage above which upscaling is triggered. |
+| IO wait max duration | 180–600 sec | How long IO wait must stay above the maximum before upscaling is triggered. |
+| Upscaling step | 1–3 | How many instance sizes to move in one go. With a step of 2, a *Dev10* scales up to *Dev30*. |
+
+#### Downscaling parameters
+
+| Parameter | Range | Description |
+|-------------------------------------|-------------|-------------------------------------------------------------------------------------------------------|
+| Downscaling grace period | 3–60 min | The delay before downscaling begins after a low resource threshold is reached. |
+| Low load average threshold | 1–35% | The average load percentage, over the *low load average threshold duration*, that triggers downscaling. |
+| Low load average threshold duration | 180–600 sec | How long the average load must stay below the threshold before downscaling is triggered. |
+| High available memory threshold | 20–90% | The available memory percentage above which downscaling is allowed. |
+| High available memory duration | 180–600 sec | How long available memory must stay above the threshold before downscaling is triggered. |
+| IO wait min value | 0–15% | The IO wait percentage below which the node is considered idle enough to allow downscaling. |
+| IO wait min duration | 180–600 sec | How long IO wait must stay below the minimum before downscaling is triggered. |
+| Downscaling step | 1–3 | How many instance sizes to move in one go. With a step of 2, a *Dev30* scales down to *Dev10*. |
+
+
+Load average and IO wait follow utilisation, so their **low** limits belong to downscaling and their **high** limits to
+upscaling. **Available memory runs the other way** — it is what's left, not what's used — so it is the **low** available
+memory limit that triggers upscaling and the **high** one that permits downscaling.
+
+
+You can edit the Autoscaling parameters by clicking the **Edit** button.
+
+
+
+### Serverless Autoscaling
+
+[Serverless products](../cloud/cloud-instances.mdx#a-serverless-cloud-product) autoscale on the same three signals,
+using the same defaults, but the feature is presented separately as **Serverless Autoscaling** and behaves differently
+in two ways:
+
+* It is **always enabled**. You cannot turn it off yourself — a Serverless product that did not resize itself would not
+ be serverless. Contact support if you need it disabled.
+* Its configuration exposes **only the instance range** — the lowest and highest type, set with a slider. The thresholds
+ and grace periods above are managed for you and are not editable.
+
+To leave Serverless autoscaling behind entirely, switch the product to a regular deployment — see
+[Switching to Regular Deployment](../cloud/cloud-instances.mdx#switching-to-regular-deployment).
@@ -253,10 +310,90 @@ This feature is available only for *RavenDB* **7.0 and newer**.
## Automatic Storage Extension
-*RavenDB Cloud* allows you to automatically extend your *RavenDB Cloud* instances disk storage upon reaching set threshold of used memory percentage.
+*RavenDB Cloud* can extend your instance's disk automatically once disk usage passes a threshold you set,
+so a growing dataset does not run the product out of space while you are not watching.
+
+The feature is **enabled by default** with a threshold of **90%**, and the feature itself is **free of charge** —
+you are billed only for the larger disk it provisions, at the normal
+[storage rate](./cloud-pricing-payment-billing.mdx).
+
+
+Automatic Storage Extension is offered on
+[Development](./cloud-instances.mdx#a-development-cloud-server) and
+[Production](./cloud-instances.mdx#a-production-cloud-cluster) tier products, except for **Dev10** and
+**PN**-type instances. It is not offered on the [Free tier](./cloud-instances.mdx#a-free-cloud-node).
+
+Products that are not eligible have no *Automatic Storage Extension* row in the *Additional Features* table.
+
-Click **Configure** Button in *Automatic Storage Extension* feature row in order to configure the threshold.
+### How it works
-
+Each node reports its disk usage to *RavenDB Cloud*. Once usage exceeds the configured threshold, the disk is
+extended to the **next larger size available for the current instance type** — not to the size that would merely
+clear the threshold — and the product briefly enters *Deploying changes* while the volume is resized.
+You are notified by email when this happens. The message states the previous size, the new size, and the
+**maximum size your instance type allows**, which is the point at which extension stops and an instance type
+upgrade becomes necessary.
+
+On *Azure* **Premium** disks, disk performance follows disk size. When the new size belongs to a higher
+[performance tier](./cloud-scaling.mdx#azure-premium---azure-performance-tier-customization), the extension
+raises **IOPS** and **throughput** to that tier as well. *Standard* disks keep their fixed performance.
+
+
+### Configuration {#storage-extension-configuration}
+
+Click the **Configure** button in the *Automatic Storage Extension* feature row to open the
+**Storage Extension configuration** dialog, then click **Edit** to change the single setting it holds:
+
+**Disk Space Used Threshold** — the percentage of disk usage above which the storage is extended. It accepts a value
+between **70** and **95**, and **defaults to 90**.
+
+
+* The product must be **Active**.
+* The threshold **cannot be changed on yearly contracts** — only on *On-Demand* products.
+* The feature itself must be enabled, which requires the
+ [**Manager** (or **Admin**) preset](./cloud-account.mdx#permission-presets).
+
+Where a condition is not met the **Edit** button is disabled and the reason is shown in its tooltip.
+
+
+
+
+You can edit the threshold by clicking the **Edit** button.
+
+
+
+### Enabling and disabling
+
+The *Automatic Storage Extension* row carries a **Disable** button while the feature is active, and an **Enable**
+button once it is off. Both require the product to be **Active** and the
+[**Manager** (or **Admin**) preset](./cloud-account.mdx#permission-presets); otherwise the button is disabled and
+its tooltip gives the reason.
+
+While the feature is off, the disk is never extended automatically — no matter how full it gets — and the
+**Configure** button disappears with it.
+
+### When storage is not extended
+
+Some products cannot be extended even with the feature on. In those cases nothing is resized and you receive an
+email instead, so the condition does not pass unnoticed:
+
+| Condition | What happens |
+|---|---|
+| **The instance type's maximum disk size is reached** | No larger size is available. The email names your instance type and its limit; extension resumes only after you [upgrade the instance type](./cloud-scaling.mdx#scaling---change-instance-type). |
+| **The cloud provider's root-disk limit is reached** | Products whose data lives on the OS disk cannot grow past **1,000 GB** on *AWS* and *GCP*, or **1,024 GB** on *Azure*. Migrate the storage to a [Data Disk](./cloud-scaling.mdx#data-disks) to grow beyond that. |
+| **The product is on a yearly contract** | Storage cannot be changed under a yearly contract. Contact [support](./cloud-support.mdx) for a tailored solution. |
+| **The product is on the Free tier** | Free tier storage is fixed. Reduce the stored data or move to a paid tier. |
+
+
+At most **one** such email is sent per product per **24 hours**, so a product sitting above its threshold does not
+produce a stream of identical messages.
+
+
+
+Storage changes — automatic and manual alike — are rate limited per product: at least **6 hours** must pass between
+two changes on *AWS*, and **12 hours** on *Azure* **Premium** disks. An automatic extension that falls inside that
+window is skipped and retried later, so a disk filling up quickly may cross its threshold well before it grows.
+
diff --git a/cloud/cloud-instances.mdx b/cloud/cloud-instances.mdx
index ec25691df2..ed2ffab2e0 100644
--- a/cloud/cloud-instances.mdx
+++ b/cloud/cloud-instances.mdx
@@ -20,8 +20,8 @@ import LanguageContent from "@site/src/components/LanguageContent";
a Free node, a Development node, a Production cluster, or a Serverless product.
- Free and Development nodes, as well as Production "basic" grade clusters, are operated by
[burstable instances](../cloud/cloud-overview.mdx#burstable-vs-reserved-clusters).
-- The Production cluster grades [Standard](../cloud/cloud-instances.mdx#standard-grade-production-cluster)
-and [Performance](../cloud/cloud-instances.mdx#performance-grade-production-cluster) are
+- The Production cluster grades [Standard](../cloud/cloud-instances.mdx#2-standard-grade-production-cluster)
+and [Performance](../cloud/cloud-instances.mdx#3-performance-grade-production-cluster) are
[Reserved clusters](../cloud/cloud-overview.mdx#burstable-vs-reserved-clusters).
In this page:
@@ -46,7 +46,7 @@ You can run only one free node per [account](../cloud/cloud-overview.mdx#your-ac
To raise a free cloud node, use the [Products tab](../cloud/portal/cloud-portal-products-tab.mdx)
to create a **free**-tier instance.
-
+
* A free instance is identical to a development [Dev10](../cloud/cloud-instances.mdx#a-development-cloud-server) instance.
It comes with a monthly credit of **$14**, used to cover the cost of the instance and incidentals like backup storage
@@ -69,25 +69,25 @@ but is **not** suitable for production for the following reasons:
* A single-node configuration (no [replication](../7.2/server/clustering/replication/replication-overview)).
* [Burstable](../cloud/cloud-overview.mdx#burstable-instances) CPU usage, suitable for small to medium production loads.
Burstable instances can become throttled if usage exceeds allocated resources.
-* Lack of [backup](../cloud/cloud-backup-and-restore.mdx#cloud-backup) procedure.
+* Lack of [backup](../cloud/cloud-backup-and-restore.mdx#the-mandatory-backup-routine) procedure.
* No [Service Level Agreement](../cloud/cloud-support#available-support-options).
To raise a cloud Development server, create a product using the Products tab and select the **Development** tier.
-
+
#### Select your server's configuration
Select a configuration from Dev10 to Dev70.
The configurations are increasingly more and more powerful.
-
+
-
+
#### Select your storage
Select your storage type and size.
-
+
In addition to the CPU / memory resources allocated to your instances, you can select the type of storage that will
be assigned to your RavenDB instances. It is fairly obvious why the size of the storage matters, but it is important
@@ -114,7 +114,7 @@ with configurations that suit your needs.
This option is not available for **PS** instance types.
-
+
Please be aware that cloud cluster nodes are provided with dynamic IP addresses and are
@@ -143,7 +143,7 @@ While suitable for low to medium workloads, they trade-off peak efficiency for l
If burstable instances use more than their allocated budget, they can become [throttled](../cloud/cloud-overview.mdx#budget-credits-and-throttling).
-
+
#### 2. Standard-grade Production Cluster
The resources of standard production clusters are [reserved](../cloud/cloud-overview.mdx#reserved-clusters).
The cluster can utilize them at all times, and is equipped to handle constant production load.
@@ -153,11 +153,11 @@ Use the slide-bars to select your Standard Production cluster's configuration an
P60 and P70 products can be created only via support request.
-
+
-
+
-
+
In addition to the CPU / memory resources allocated to your instances, you can select the type of storage that will
be assigned to your RavenDB instances. It is fairly obvious why the size of the storage matters, but it is important
@@ -189,7 +189,7 @@ Local NVMe drives on PN clusters are encrypted by default using hardware-based e
-
+
@@ -211,13 +211,17 @@ Serverless is available on **On-Demand** billing only. It is not available for y
For instructions on how to create a Serverless product, see
[Provisioning a New Product](../cloud/portal/cloud-portal-products-tab.mdx#provisioning-a-new-product).
-
+
### Autoscaling
-The cluster scales up and down automatically within a fixed band, driven by sustained signals:
-CPU load average, available memory, and disk queue depth. Scaling moves one step at a time.
-Grace periods are applied before each step to prevent flapping caused by short load spikes.
+The cluster scales up and down automatically within a band you choose, driven by three sustained signals:
+**load average**, **available memory** and **IO wait**. Scaling moves one step at a time, and a grace period is applied
+before each step to prevent flapping caused by short load spikes.
+
+Serverless Autoscaling is always enabled, and only its instance range — the lowest and highest type — is configurable;
+the thresholds and grace periods are managed for you. See
+[Serverless Autoscaling](../cloud/cloud-features.mdx#serverless-autoscaling) for details.
### Billing
diff --git a/cloud/cloud-maintenance-troubleshooting.mdx b/cloud/cloud-maintenance-troubleshooting.mdx
index 842db8af5a..1b7b9bc5e3 100644
--- a/cloud/cloud-maintenance-troubleshooting.mdx
+++ b/cloud/cloud-maintenance-troubleshooting.mdx
@@ -49,6 +49,11 @@ This dashboard has four separated sections:
- [Suggestions](cloud-maintenance-troubleshooting#suggestions)
- [Product changes in time](cloud-maintenance-troubleshooting#product-changes-in-time)
+
+Instead of checking this dashboard, you can have the events it records emailed to you - as a daily digest or as soon as
+they happen. See [Alerts](#alerts).
+
+
## Nodes Availability
The **Nodes Availability** section shows the availability status of each node within your cluster.
@@ -67,7 +72,7 @@ Each node's status is color-coded based on its availability percentage:
| 95% – 99.9% | Degraded | 🟡 Yellow |
| < 95% | Critical | 🔴 Red |
-
+
These thresholds help you identify which nodes might require attention:
@@ -80,7 +85,7 @@ These thresholds help you identify which nodes might require attention:
The *RavenDB Cloud* monitoring system tracks incidents and cluster performance.
This section lets you analyse your cluster incidents for a selected *time period*, *cluster node*, *severity*, *category* and *event status*.
-
+
#### Categories and their descriptions
@@ -95,11 +100,16 @@ Incidents are split into *six* categories. **Description** column contains addit
| IO | Product is experiencing high input/output operations. |
| Availability | Product is currently not responding to input or commands or has been restarted. |
+
+Node restarts are **always** recorded here, including the reason the node's service stopped, so *Incidents History*
+remains the complete record of your cluster's availability events.
+
+
## Suggestions
This section displays suggestions for a selected *cluster node* based on incident trends.
-
+
Suggestions are generated based on a 60-day period divided in half.
@@ -128,18 +138,92 @@ Suggestions are generated using three types of analyses for specific suggestion
Below examples of the suggestions with the analyses:
-
+
-
+
-
+
## Product changes in time
This view shows changes in product type over time. Changes can be presented as a graph or a table.
-
+
+
+
+
+## Alerts
+
+*Alerts* have the events described above **emailed to you**, so you do not have to watch the dashboard to learn that an
+instance is under pressure. They are configured per product, on the
+[Alerts tab](./portal/cloud-portal-products-tab.mdx#view-the-alerts) of the product view.
+
+There are two kinds of rule, and a product can use both at once.
+
+### Daily summary
+
+A **single digest email per day**, listing everything that happened to the product in the last 24 hours.
+A product can have **at most one** daily summary.
+
+* It covers **every** trigger event, so there is nothing to choose - the panel lists them all for reference.
+* The email groups the events by name and includes the counts for the period.
+* It also carries the current [Suggestions](#suggestions) for the product, when there are any.
+* If nothing happened in the period, **no email is sent** - a daily summary never arrives empty.
+
+### Custom alerts
+
+A custom alert is sent **as soon as** a matching event is recorded, rather than waiting for the daily digest.
+Use custom alerts to route specific conditions to specific people - disk-space warnings to your operations mailbox,
+*Node not responding* to an on-call address.
+
+* A custom alert must name **at least one** trigger event; a rule with no events is rejected.
+* Several rules may watch the same event with different recipients. Each fires independently, to its own list.
+* When an open incident **recovers**, a second email follows to report the recovery.
+
+### Trigger events
+
+A custom alert can be triggered by any of the conditions listed in the [Labels](#labels) table above - *Node not
+responding*, *High CPU usage*, *High IO usage*, *Low memory*, *CPU Credits are low*, the two disk-space levels, and the
+four uptime degradation bands. That table also gives the **thresholds** for the disk-space and uptime conditions.
+
+Use [Incidents History](#incidents-history) to see which of them your product actually raises before deciding what to
+subscribe to.
+
+### Rules and subscribers
+
+Every rule has a name, a state (**Enabled** or **Disabled** - a disabled rule is kept but sends nothing), its trigger
+events, and its own list of recipient email addresses.
+
+Recipients do **not** have to be users of your cloud account, so a shared alias or a dedicated notifications mailbox
+works - usually what you want for an on-call rota.
+
+The following limits apply per product:
+
+| Limit | Value |
+|---|---|
+| Alert rules per product | **25** |
+| Recipients per rule | **20** |
+| Daily summary rules per product | **1** |
+
+An address may appear only once within a rule, and every address must be a valid email address. A rule with no
+recipients is rejected, because it could never deliver anything. Requests that break any of these rules are rejected
+with an explanation, and nothing is saved.
+
+### When alert rules are removed automatically
+
+Alert rules are tied to the product and to the people subscribed to them, so a few unrelated actions clear them.
+This is by design, but worth knowing before you rely on an alert:
+
+* **Disabling the [Monitoring](./cloud-features.mdx#monitoring) feature** discards all of the product's alert rules.
+ Re-enabling Monitoring does not bring them back - you have to define them again.
+* **Terminating a product** deletes its alert rules, so no alerts are sent about an instance that no longer exists.
+* **Removing a user from the cloud account** strips their address from every alert rule on the account. If that user was
+ a rule's **last** remaining recipient, **the whole rule is deleted**.
+* **Revoking a user's permissions for a single product** does the same, limited to that product's rules.
-
+
+If your alerts matter to your operations, prefer a **shared alias** over an individual's mailbox as a rule's only
+recipient. An alias is not affected when people join or leave the account.
+
diff --git a/cloud/cloud-microsoft-azure-marketplace.mdx b/cloud/cloud-microsoft-azure-marketplace.mdx
index 7394e16369..46cf98e6bd 100644
--- a/cloud/cloud-microsoft-azure-marketplace.mdx
+++ b/cloud/cloud-microsoft-azure-marketplace.mdx
@@ -60,15 +60,15 @@ For the most up-to-date information, see [Microsoft's tax responsibilities docum
To connect your *Microsoft Azure* account to the *RavenDB Cloud*, search for the **RavenDB Cloud** offer in *Microsoft Azure Marketplace* and click on it.
-
+
In the main page of the offer, click **Subscribe**.
-
+
Provide the necessary information required to subscribe to the offer:
-
+
1. **Subscription**
Select the *Microsoft Azure subscription* from which your payment information will be used for this offer.
@@ -89,7 +89,7 @@ The **recurring billing** option must be enabled. Otherwise, creating a *Cloud A
After providing the information, please click **Review + subscribe**.
The last page shows selected options and basic information about your *Microsoft Azure* account.
-
+
Providing *Primary phone number* **is not required**.
@@ -98,11 +98,11 @@ Providing *Primary phone number* **is not required**.
After reviewing the information, please click **Subscribe**.
Once you have subscribed, the next step is to configure the account in the *RavenDB Cloud*.
-
+
Provide the necessary information required to end the registration process:
-
+
1. **Email Address**
Provide an email address that you will use in RavenDB Cloud.
@@ -119,7 +119,7 @@ Provide the necessary information required to end the registration process:
After providing the information, please click **Sign up**.
Your account is now ready to use. To sign in to the account, click **Continue to sign in**.
-
+
Successful registration process is also confirmed by an email from *Microsoft Azure Marketplace*.
@@ -131,10 +131,10 @@ Successful registration process is also confirmed by an email from *Microsoft Az
To cancel your subscription, go to your SaaS resource that is associated with the resource group you selected earlier.
Then click the **Cancel Subscription** button.
-
+
Fill the standard cancellation form and click **Cancel subscription**.
-
+
Subscription cancellation is **irreversible**. Your account and data and will be permanently lost.
diff --git a/cloud/cloud-migration.mdx b/cloud/cloud-migration.mdx
index c02cffeece..21a37498da 100644
--- a/cloud/cloud-migration.mdx
+++ b/cloud/cloud-migration.mdx
@@ -31,29 +31,29 @@ In order to do so, the **source server** needs to have the **destination server'
Open the [Management Studio](../7.2/studio/overview) of each server.
Each server's Studio is available in the [Portal](../cloud/portal/cloud-portal.mdx#cloud-portal)'s
-[Product tab](../cloud/portal/cloud-portal-products-tab.mdx#cloud-account-portal-products).
+[Product tab](../cloud/portal/cloud-portal-products-tab.mdx#managing-an-existing-product).
Learn how to [install the certificate and access RavenDB Cloud Studio](../cloud/cloud-overview.mdx#ravendb-studio---graphic-user-interface) if this is your first time using Cloud Studio.
If you have already installed the certificate and accessed Studio,
click the URLs in the Products tab to open a Studio GUI for each node.
-
+
In each studio, select server dashboard and click **Manage certificates**.
-
+
Export the **destination server**'s **Cluster certificate**.
-
+
Import the certificate as a **Client Certificate** by the **source server**.
-
+
Configure the Client Certificate's **Database Permissions** to include the database whose data you want to migrate.
-
+
In the Destination Server, create or select an empty database and open its **Tasks --> Import Data** option.
-
+
1. Select the **Tasks** tab.
2. Select **Import Data**.
@@ -75,7 +75,7 @@ Another option is to [export a database](../7.2/studio/database/tasks/export-dat
This option doesn't require passing certificates:
#### First export the data from source server
-
+
1. In the source server, select a database to export and go to **Tasks tab**.
2. Select **Export Database**.
@@ -85,7 +85,7 @@ This option doesn't require passing certificates:
5. After choosing which data to export, click **Export Database**.
#### Next import the data to destination server from file
-
+
1. In the destination server, go to **Tasks** tab.
2. Select **Import Data**.
diff --git a/cloud/cloud-overview.mdx b/cloud/cloud-overview.mdx
index 67963e87e6..9741a9fb2e 100644
--- a/cloud/cloud-overview.mdx
+++ b/cloud/cloud-overview.mdx
@@ -35,7 +35,7 @@ like adding or removing nodes, and run recurring tasks like backing up your data
- [Register](../cloud/cloud-overview.mdx#register-your-account)
- [Login](../cloud/cloud-overview.mdx#login-to-your-account)
- [Login with a magic link](../cloud/cloud-overview.mdx#login-with-a-magic-link)
- - [Login with GitHub or Google](../cloud/cloud-overview.mdx#login-with-github-or-google)
+ - [Login with Google, GitHub or Microsoft](../cloud/cloud-overview.mdx#login-with-google-github-or-microsoft)
* [RavenDB on the Cloud](../cloud/cloud-overview.mdx#ravendb-on-the-cloud)
* [Instances, Provisioning and RavenDB Products](../cloud/cloud-overview.mdx#instances-provisioning-and-ravendb-products)
* [RavenDB Tiers: Free, Development and Production](../cloud/cloud-overview.mdx#ravendb-tiers)
@@ -71,11 +71,11 @@ To create a new account, enter [https://cloud.ravendb.net/user/register](https:/
and allow the wizard to walk you through the 5 simple stages of the registration procedure:
-You can also start registration by clicking **Login via GitHub** or **Login via Google** on the
+You can also start registration with the **Sign in with Google**, **Sign in with GitHub** or **Sign in with Microsoft** buttons on the
[login page](../cloud/cloud-overview.mdx#login-to-your-account). If no Cloud account exists yet for
the email reported by the provider, a registration link is sent to that address and the registration
form opens with the email already filled in.
-See [Login with GitHub or Google](../cloud/cloud-overview.mdx#login-with-github-or-google).
+See [Login with Google, GitHub or Microsoft](../cloud/cloud-overview.mdx#login-with-google-github-or-microsoft).
1. **Email**
@@ -84,20 +84,20 @@ See [Login with GitHub or Google](../cloud/cloud-overview.mdx#login-with-github-
4. **Payment information**
5. **Summary**
#### 1. Email
-
+
- Provide your email address.
- Read the **terms & conditions** and the **privacy policy**.
- Click the **Continue** button.
#### 2. Account information
-
+
- Enter an unoccupied domain name of your choice, that would be used for your cloud products.
The domain name is typically your organization or project name and will be used in all your products' URLs. The procedure will check this name's availability.
- Select your account type. For typical purposes, select the **Regular** button. If you need a *HIPAA-compliant* account, select the **HIPAA** button.
- Click the **Continue** button.
#### 3. Billing information
-
+
- Enter your billing information.
- Click the **Continue** button.
@@ -106,17 +106,17 @@ See [Login with GitHub or Google](../cloud/cloud-overview.mdx#login-with-github-
Click the **Skip Billing Information** button if you prefer to evaluate the cloud service for now using the free product.
#### 4. Payment information
-
+
- Enter your payment information.
- Click the **Continue** button.
#### 5. Summary
-
+
- Verify your choices, confirm you're not a robot, and click the **Create account** button to register your cloud account.
- You’ll receive an email with sign in link which allows you to sign in to the RavenDB Cloud portal.
-
+
#### Signing up will send you a message with a link to your email.
- The sign-up process will send a registration link to your email.
@@ -130,9 +130,9 @@ Click the **Skip Billing Information** button if you prefer to evaluate the clou
To access your account, click [https://cloud.ravendb.net/user/login](https://cloud.ravendb.net/user/login).
You can sign in either with a **magic link** sent to your email, or by using your
-**GitHub** or **Google** account.
+**Google**, **GitHub** or **Microsoft** account.
#### Login with a magic link
-
+
- Enter the same email address you provided during registration, confirm you're not a robot, and
click the **Send Magic Link** button
@@ -152,34 +152,76 @@ You can sign in either with a **magic link** sent to your email, or by using you
We advise you to enable 2FA. Setup is described [here](../cloud/cloud-security.mdx#enable-mfa).
-#### Login with GitHub or Google
+#### Login with Google, GitHub or Microsoft
-In addition to the magic link, you can sign in using your **GitHub** or **Google** account.
-The login page shows **Login via GitHub** and **Login via Google** buttons below the magic-link form.
+In addition to the magic link, you can sign in using your **Google**, **GitHub** or **Microsoft**
+account. The login page shows **Sign in with Google**, **Sign in with GitHub** and
+**Sign in with Microsoft** buttons below the magic-link form.
-
+
-- Click **Login via GitHub** or **Login via Google**.
-- Authorize RavenDB Cloud at the chosen provider.
+- Click the button for the provider you want to use.
+- Authorize RavenDB Cloud at that provider.
- You are returned to RavenDB Cloud and signed in to the account whose email address matches the one
reported by the provider.
-Your RavenDB Cloud account is identified by **email address**. GitHub and Google sign in only
-succeed when the email reported by the provider matches the email of an existing Cloud account.
+Your RavenDB Cloud account is identified by **email address**. Single sign-on only succeeds when the
+email reported by the provider matches the email of an existing Cloud account.
+
+RavenDB Cloud only accepts an email address that the provider itself vouches for:
+
+- **Google** — the address must be verified on your Google account.
+- **GitHub** — the address must be both **verified** and set as your **primary** email.
+- **Microsoft** — a **personal** Microsoft account is accepted, because Microsoft verifies those
+ addresses when the account is created. For a **work or school** (Microsoft Entra ID) account, the
+ sign-in token must additionally carry proof that the tenant owns the address's domain - see the note
+ below.
+
+If the address cannot be verified, sign-in is refused. Verify it at the provider (or, on GitHub, set a
+verified address as primary) and try again.
+
+
+
+A tenant administrator in Microsoft Entra ID can set a user's email address to a domain the tenant does
+not own, so RavenDB Cloud does not take the address on trust. It requires the token to include the
+**optional claim that attests domain-owner verification** (`xms_edov`), which a tenant administrator
+enables for the application in Entra ID.
+
+If your organization's tenant does not emit that claim, Microsoft sign-in fails with *"Your Microsoft
+account's email address could not be verified"*, even though the address is correct. Ask your Entra ID
+administrator to enable the claim, or use a [magic link](../cloud/cloud-overview.mdx#login-to-your-account)
+instead.
+
+
+**When sign-in cannot complete**
+
+If sign-in cannot be completed you stay on the login page with an explanation. The most common cases:
+
+| Message | What it means |
+|---|---|
+| The email address on the selected account has not been verified with your provider | The provider returned an address it does not report as verified. Verify it at the provider and retry. |
+| The selected account does not expose an email address | The provider shared no email address - for example, because the permission was declined. Grant access to your email address and retry. |
+| Your Microsoft account's email address could not be verified | A work or school account whose tenant does not attest domain ownership - see the note above. |
+| Your Microsoft sign-in could not be processed | The token was internally inconsistent. This needs [Support](../cloud/cloud-support.mdx) to look at it. |
+| *Provider* authentication failed | Authorization failed or was cancelled at the provider. Retry, or use a magic link. |
+| This sign-in method is currently unavailable | That provider is temporarily not configured. Use another provider or a magic link. |
+
+You can always fall back to the [magic link](../cloud/cloud-overview.mdx#login-to-your-account) sign-in.
+
Users are responsible for enabling and maintaining Two-Factor Authentication (2FA) on their designated Single Sign-On (SSO) provider.
**No Cloud account for the email**
-If no RavenDB Cloud account exists for the email returned by GitHub or Google, you are taken to a
+If no RavenDB Cloud account exists for the email returned by the provider, you are taken to a
**Check your inbox** page and an email with a sign-in link is sent to that address. Following the
link opens the registration form with the email pre-filled, so you can finish creating the account.
-
+
## RavenDB on the Cloud
@@ -226,8 +268,8 @@ HW selection or a multi-region cluster.
| **Tier** | **Sub-tiers** | **CPU** | **Options** | **SLA** |
| -- | -- | -- | -- | -- |
| Free | - | Very low | None | No |
-| Development | Dev10-Dev70 | Very low - High | All | [Yes](../cloud/portal/cloud-portal-support-tab.mdx#support-entitlement) |
-| Production | **By CPU Priority** (Basic/Standard/Performance)
**By Cluster Size**| Up to extra performance, high network and reserved NVMe | All | [Yes](../cloud/portal/cloud-portal-support-tab.mdx#support-entitlement) |
+| Development | Dev10-Dev70 | Very low - High | All | [Yes](../cloud/cloud-support.mdx#available-support-options) |
+| Production | **By CPU Priority** (Basic/Standard/Performance)
**By Cluster Size**| Up to extra performance, high network and reserved NVMe | All | [Yes](../cloud/cloud-support.mdx#available-support-options) |
## Burstable vs. Reserved clusters
@@ -265,7 +307,7 @@ Credits are **consumed** when the instance uses computing and I/O resources, and
* **Burstable CLUSTERS and throttling**
- [Basic-grade production clusters](../cloud/cloud-instances.mdx#basic-grade-production-cluster) are burstable: each node of such a cluster
+ [Basic-grade production clusters](../cloud/cloud-instances.mdx#1-basic-grade-production-cluster) are burstable: each node of such a cluster
is accommodated by a burstable instance.
When the budget of a burstable cluster is drained or nearly so, the cluster automatically shifts the workload to cluster nodes that still have
credits to work with.
diff --git a/cloud/cloud-pricing-payment-billing.mdx b/cloud/cloud-pricing-payment-billing.mdx
index 8e355e3cdb..7c391d9ef0 100644
--- a/cloud/cloud-pricing-payment-billing.mdx
+++ b/cloud/cloud-pricing-payment-billing.mdx
@@ -147,6 +147,10 @@ Approach our Support personnel to use wire transfer or purchase order.
Your Portal's [Billing & Costs tab](../cloud/portal/cloud-portal-billing-tab.mdx) summarizes your
outstanding charges and past invoices. Additional data you can see there includes Daily cost, Total
cost, and the expected charge at the end of this month.
+
+To see how a given period's costs split across your products, and which cost categories drive them, open its
+[Cost details](../cloud/portal/cloud-portal-billing-tab.mdx#cost-details) view. Costs for the period still in progress
+are a **prediction** and may change before the period closes.
#### Billing Period
Each billing period runs from the **26th of one calendar month** to the **25th of the following month**.
diff --git a/cloud/cloud-scaling.mdx b/cloud/cloud-scaling.mdx
index c8f723d61f..ef503bc2cb 100644
--- a/cloud/cloud-scaling.mdx
+++ b/cloud/cloud-scaling.mdx
@@ -95,6 +95,18 @@ There are two types of storage: **Standard** and **Premium**. They differ signif
depending on the cloud provider in question. Pick either to change your current storage capacity.
+
+
+Storage can also grow **on its own**: with
+[Automatic Storage Extension](./cloud-features.mdx#automatic-storage-extension) enabled, the disk is extended to the
+next available size once disk usage passes a threshold you set.
+
+
+
+Storage changes are rate limited per product: at least **6 hours** must pass between two changes on *AWS*, and
+**12 hours** on *Azure* **Premium** disks. Until the window elapses the storage form reports how long is left.
+
+
### AWS Disks
#### AWS Standard & Premium - Default Performance
@@ -143,7 +155,7 @@ default one.
**IOPS** and **Throughput** that can be configured independently of the disk size, giving you finer
control over storage performance and cost.
-
+
**Availability and constraints:**
@@ -180,7 +192,7 @@ There are two ways to start using **Premium SSD v2**:
[Managing an Existing Product](../cloud/portal/cloud-portal-products-tab.mdx#change-instance-type-and-storage)
in the portal documentation.
-
+
The upgrade is performed **node by node**. Each node being migrated is briefly unavailable, and the
full operation may take **multiple hours** to complete. The migration uses your current **IOPS** and
@@ -199,7 +211,7 @@ The use of a data disk is mandatory for deployments requiring more than 1TB of s
**Data Disk** can be selected during instance creation or migrated to on already existing instances.
-
+
On **Azure**, when the product's region supports **Premium SSD v2**, migrating to a Data Disk
diff --git a/cloud/cloud-security.mdx b/cloud/cloud-security.mdx
index a161711378..25e62d95b1 100644
--- a/cloud/cloud-security.mdx
+++ b/cloud/cloud-security.mdx
@@ -43,19 +43,19 @@ The certificate will be automatically regenerated **30 days** before its expirat
Go to the [Products tab](../cloud/portal/cloud-portal-products-tab.mdx) in the cloud [portal](../cloud/portal/cloud-portal.mdx)
and click the **Download Certificate** button.
-
+
#### Install the certificate
Extract the certificate package, open the extracted files' folder, and double-click the **.pfx** file that requires no password.
When the certificate import wizard is launched, click "Next" all the way through the wizard.
-
+
#### Access your product
If you're using Chrome on Windows, you will now be able to access your *RavenDB Cloud* instance. You may need to restart your browser.
In other cases (e.g. if you're using Firefox) you will have to import the certificate to your browser manually.
-
+
Once the certificate is imported, please make sure your IP address is on the [allowed IPs list](#managing-allowed-ips) and then click your cloud instance's URL.
Your browser will prompt you to select a certificate. When you select the client certificate, your product's
@@ -97,7 +97,7 @@ Cross-instance communication **inside the cluster** is **not** subject to these
Your initial [operator-level](../7.2/server/security/authorization/security-clearance-and-permissions#operator)
certificate allows you to perform operations like creating and deleting databases, managing access to the cluster, and inspecting the cluster's state.
-Operations like adding and removing cluster nodes are left for your [products administrators](../cloud/cloud-overview.mdx#ravendb-on-the-cloud-overview).
+Operations like adding and removing cluster nodes are left for your [products administrators](../cloud/cloud-overview.mdx#ravendb-on-the-cloud).
We recommend that you generate and use **different certificates** for your client applications, for maximum security.
@@ -114,9 +114,9 @@ We therefore recommend that you generate your certificates off-cloud and import
or [user](../7.2/server/security/authorization/security-clearance-and-permissions#user) certificates**:
* Go to the server management studio, and click the `Manage Certificates` button.
- 
+ 
* Click **Generate client certificate**
- 
+ 
@@ -144,18 +144,18 @@ To enable Multi-Factor Authentication either visit
the [enable-authenticator](https://cloud.ravendb.net/portal/profile/enable-authenticator) page
or open your RavenDB Cloud [Profile](https://cloud.ravendb.net/portal/profile).
-
+
1. Click the **Add authenticator app** button.
-
+
2. Scan the provided QR code or enter the provided text code into an authentication app of your choice.
3. Type in the 2FA code generated by your authentication app.
4. Type in a recovery phone number.
5. Click **Verify**.
-
+
After verifying, you will be provided with recovery codes. Save them in a secure place.
MFA is now enabled on your account.
@@ -166,11 +166,11 @@ To disable Multi-Factor Authentication either visit
the [disable-authenticator](https://cloud.ravendb.net/portal/profile/disable-2fa) page
or open your RavenDB Cloud [Profile](https://cloud.ravendb.net/portal/profile).
-
+
1. Click the **Disable 2FA** button.
-
+
2. Type in the 2FA code generated by your authentication app.
3. Click **Disable 2FA**.
diff --git a/cloud/cloud-settings.mdx b/cloud/cloud-settings.mdx
index 2d7400f2fa..bd266dc114 100644
--- a/cloud/cloud-settings.mdx
+++ b/cloud/cloud-settings.mdx
@@ -59,7 +59,7 @@ The factors to consider when adjusting the max indexing batch size:
* [Size of documents](https://ravendb.net/articles/dealing-with-large-documents-100-mb#:~:text=RavenDB%20can%20handle%20large%20documents,isn't%20a%20practical%20one.)
* [The Complexity of calculations](../7.2/studio/database/indexes/indexing-performance#common-indexing-issues) that static indexes do.
-* [IOPS](../cloud/cloud-scaling.mdx#change-storage) - Input/Output Operations Per Second
+* [IOPS](../cloud/cloud-scaling.mdx#scaling---change-storage) - Input/Output Operations Per Second
#### Cloud Indexing Batch Size
RavenDB Cloud sets batch sizes with the following default formula:
diff --git a/cloud/cloud-support.mdx b/cloud/cloud-support.mdx
index d43f88fb7b..90301a470e 100644
--- a/cloud/cloud-support.mdx
+++ b/cloud/cloud-support.mdx
@@ -49,6 +49,13 @@ The **Cloud Support option** requires at least **one production tier** instance.
For a full support options comparison please check the [Pricing](https://cloud.ravendb.net/pricing#support-options) page.
+
+With an active **Cloud Support** option, you can open a request straight from a product using
+**Request support for this instance**, which pre-selects that product on the support form.
+See [Request support from a product](./portal/cloud-portal-support-tab.mdx#request-support-from-a-product).
+
+
+
## Severity and response time types
@@ -71,9 +78,25 @@ Please make sure you understand what each of the options stands for, so your req
| Next business day | Reply within a next business day. |
| Within 2 hours | Your query will be responded to within two hours. |
-
-**Within 2 hours** response time is only available for **Production tier** related issues.
-**Within 2 hours** and **Next business day** response times are only available for Customers with the **Cloud Support** support option.
+
+**Standard** is always available. The two faster response times are offered only when **all** of the conditions below
+are met — otherwise they appear greyed out on the form:
+
+| Response time | Requires |
+|---|---|
+| **Next business day** | The **Cloud Support** option, **and** a severity of *Normal* or *Critical*. |
+| **Within 2 hours** | The **Cloud Support** option, **and** a severity of *Critical*, **and** — for a product-related question — a product that is **not** on the *Free* or *Development* tier. |
+
+Severity is the condition most often overlooked: a *Minor* issue can only be submitted with the **Standard** response
+time, however your account is licensed.
+
+The tier condition applies only to **product-related** questions. A **general** question is never restricted by tier,
+so a Cloud Support customer can select **Within 2 hours** for a critical general question even with no production
+product.
+
+You do not have to work this out yourself: the form states the outcome under the options — *"Based on your current
+Cloud Support contract and selected Severity, the maximum Response Type is …"*. Raising the severity re-evaluates it
+immediately.
diff --git a/cloud/portal/assets/portal-backups-tab-generate-backup-link-button.png b/cloud/portal/assets/portal-backups-tab-generate-backup-link-button.png
index e044023c9d..44cc3ed16d 100644
Binary files a/cloud/portal/assets/portal-backups-tab-generate-backup-link-button.png and b/cloud/portal/assets/portal-backups-tab-generate-backup-link-button.png differ
diff --git a/cloud/portal/assets/portal-billing-costs-tab-current-period-costs.png b/cloud/portal/assets/portal-billing-costs-tab-current-period-costs.png
new file mode 100644
index 0000000000..f3ac3a16e4
Binary files /dev/null and b/cloud/portal/assets/portal-billing-costs-tab-current-period-costs.png differ
diff --git a/cloud/portal/assets/portal-billing-costs-tab-spending.png b/cloud/portal/assets/portal-billing-costs-tab-spending.png
index 66b2353e73..4dca4b687e 100644
Binary files a/cloud/portal/assets/portal-billing-costs-tab-spending.png and b/cloud/portal/assets/portal-billing-costs-tab-spending.png differ
diff --git a/cloud/portal/assets/portal-home-tab-overview.png b/cloud/portal/assets/portal-home-tab-overview.png
index 735d49173b..f68f30f54d 100644
Binary files a/cloud/portal/assets/portal-home-tab-overview.png and b/cloud/portal/assets/portal-home-tab-overview.png differ
diff --git a/cloud/portal/assets/portal-home-tab-roles-and-access.png b/cloud/portal/assets/portal-home-tab-roles-and-access.png
index 7c599aab77..cde99927b3 100644
Binary files a/cloud/portal/assets/portal-home-tab-roles-and-access.png and b/cloud/portal/assets/portal-home-tab-roles-and-access.png differ
diff --git a/cloud/portal/assets/portal-product-alerts.png b/cloud/portal/assets/portal-product-alerts.png
new file mode 100644
index 0000000000..8fa550e90f
Binary files /dev/null and b/cloud/portal/assets/portal-product-alerts.png differ
diff --git a/cloud/portal/assets/portal-product-details-cluster-health.png b/cloud/portal/assets/portal-product-details-cluster-health.png
index b55f060660..aa7fa1b087 100644
Binary files a/cloud/portal/assets/portal-product-details-cluster-health.png and b/cloud/portal/assets/portal-product-details-cluster-health.png differ
diff --git a/cloud/portal/assets/portal-product-details-edit-tier.png b/cloud/portal/assets/portal-product-details-edit-tier.png
index 6d1cf21c7e..dd3efc98ae 100644
Binary files a/cloud/portal/assets/portal-product-details-edit-tier.png and b/cloud/portal/assets/portal-product-details-edit-tier.png differ
diff --git a/cloud/portal/assets/portal-product-details-instance-parameters.png b/cloud/portal/assets/portal-product-details-instance-parameters.png
index f13bfb598d..53dd2608aa 100644
Binary files a/cloud/portal/assets/portal-product-details-instance-parameters.png and b/cloud/portal/assets/portal-product-details-instance-parameters.png differ
diff --git a/cloud/portal/assets/portal-product-details-manage-access.png b/cloud/portal/assets/portal-product-details-manage-access.png
deleted file mode 100644
index d8bacfcdad..0000000000
Binary files a/cloud/portal/assets/portal-product-details-manage-access.png and /dev/null differ
diff --git a/cloud/portal/assets/portal-product-details-metrics.png b/cloud/portal/assets/portal-product-details-metrics.png
index 401bb4552d..5e187ef125 100644
Binary files a/cloud/portal/assets/portal-product-details-metrics.png and b/cloud/portal/assets/portal-product-details-metrics.png differ
diff --git a/cloud/portal/assets/portal-product-details.png b/cloud/portal/assets/portal-product-details.png
index 50db2a6712..fb4a8e3e5c 100644
Binary files a/cloud/portal/assets/portal-product-details.png and b/cloud/portal/assets/portal-product-details.png differ
diff --git a/cloud/portal/assets/portal-product-edit-security.png b/cloud/portal/assets/portal-product-edit-security.png
new file mode 100644
index 0000000000..123c709539
Binary files /dev/null and b/cloud/portal/assets/portal-product-edit-security.png differ
diff --git a/cloud/portal/assets/portal-product-list-add-product-button.png b/cloud/portal/assets/portal-product-list-add-product-button.png
index 2e714d623a..c255f06cad 100644
Binary files a/cloud/portal/assets/portal-product-list-add-product-button.png and b/cloud/portal/assets/portal-product-list-add-product-button.png differ
diff --git a/cloud/portal/assets/portal-product-list-manage-button.png b/cloud/portal/assets/portal-product-list-manage-button.png
index b4dbbb0b9c..75ed4ff99b 100644
Binary files a/cloud/portal/assets/portal-product-list-manage-button.png and b/cloud/portal/assets/portal-product-list-manage-button.png differ
diff --git a/cloud/portal/assets/portal-support-activation-request-form-6-months.png b/cloud/portal/assets/portal-support-activation-request-form-6-months.png
new file mode 100644
index 0000000000..1fe7e7d097
Binary files /dev/null and b/cloud/portal/assets/portal-support-activation-request-form-6-months.png differ
diff --git a/cloud/portal/assets/portal-support-activation-request-form.png b/cloud/portal/assets/portal-support-activation-request-form.png
index acd371836e..b7527eeff0 100644
Binary files a/cloud/portal/assets/portal-support-activation-request-form.png and b/cloud/portal/assets/portal-support-activation-request-form.png differ
diff --git a/cloud/portal/assets/portal-support-general-question-cloud-support.png b/cloud/portal/assets/portal-support-general-question-cloud-support.png
index f6d215c09a..9c1349c974 100644
Binary files a/cloud/portal/assets/portal-support-general-question-cloud-support.png and b/cloud/portal/assets/portal-support-general-question-cloud-support.png differ
diff --git a/cloud/portal/assets/portal-support-instance-related-question-cloud-support.png b/cloud/portal/assets/portal-support-instance-related-question-cloud-support.png
index 765827dbec..82b0049874 100644
Binary files a/cloud/portal/assets/portal-support-instance-related-question-cloud-support.png and b/cloud/portal/assets/portal-support-instance-related-question-cloud-support.png differ
diff --git a/cloud/portal/assets/portal-support-request-cloud-support-on-free-support.png b/cloud/portal/assets/portal-support-request-cloud-support-on-free-support.png
index 246c9a4f7f..7c4bfba67f 100644
Binary files a/cloud/portal/assets/portal-support-request-cloud-support-on-free-support.png and b/cloud/portal/assets/portal-support-request-cloud-support-on-free-support.png differ
diff --git a/cloud/portal/assets/portal-support-subscriptions-tab.png b/cloud/portal/assets/portal-support-subscriptions-tab.png
new file mode 100644
index 0000000000..c6eb9bac75
Binary files /dev/null and b/cloud/portal/assets/portal-support-subscriptions-tab.png differ
diff --git a/cloud/portal/assets/portal-support-tab.png b/cloud/portal/assets/portal-support-tab.png
index 1daa0dbb6f..03231e51e6 100644
Binary files a/cloud/portal/assets/portal-support-tab.png and b/cloud/portal/assets/portal-support-tab.png differ
diff --git a/cloud/portal/assets/portal-tabs.png b/cloud/portal/assets/portal-tabs.png
index 2559959ef2..6de1586bec 100644
Binary files a/cloud/portal/assets/portal-tabs.png and b/cloud/portal/assets/portal-tabs.png differ
diff --git a/cloud/portal/cloud-portal-account-tab.mdx b/cloud/portal/cloud-portal-account-tab.mdx
index c2b0605fc9..1047d39801 100644
--- a/cloud/portal/cloud-portal-account-tab.mdx
+++ b/cloud/portal/cloud-portal-account-tab.mdx
@@ -24,23 +24,23 @@ This tab allows you to manage your account and payment information.
## The Account Tab
-
+
### Billing information management
In this section you can edit the data that will be used for the invoice.
-
+
In this section you can edit the email address to which invoices will be sent.
If a custom recipient email is not provided, the invoice is sent to the *account owner*.
-
+
In this section you can manage payment cards that will be used to pay for RavenDB Cloud services.
You can add, remove or change the default credit card.
-
+
### User management
diff --git a/cloud/portal/cloud-portal-api-tab.mdx b/cloud/portal/cloud-portal-api-tab.mdx
index 45e8c0db4e..a262d8d3a9 100644
--- a/cloud/portal/cloud-portal-api-tab.mdx
+++ b/cloud/portal/cloud-portal-api-tab.mdx
@@ -26,43 +26,43 @@ The RavenDB Cloud API allows you to automate actions on your RavenDB Cloud produ
## The API Tab
-
+
You can read more about the *RavenDB Cloud API* in the [API](../../cloud/cloud-api.mdx) page.
### Create API Key
-
+
**1**. Click the *Add API Key* button.
-
+
**2**. Enter an API Key description.
**3**. Select an API Key expiration date.
**4**. Click the *Create* button.
-
+
**5**. Copy your API Key.
**6**. Click the *Close* button.
### Edit API Key
-
+
**1**. Click the *Edit* button.
-
+
**2**. Enter an API Key description.
**3**. Select an API Key expiration date.
**4**. Click the *Save* button.
### Deactivate API Key
-
+
**1**. Click the *Deactivate* button.
-
+
**2**. Click the *Deactivate* button.
diff --git a/cloud/portal/cloud-portal-backups-tab.mdx b/cloud/portal/cloud-portal-backups-tab.mdx
index cf18d74e11..3331f6f9b7 100644
--- a/cloud/portal/cloud-portal-backups-tab.mdx
+++ b/cloud/portal/cloud-portal-backups-tab.mdx
@@ -22,12 +22,12 @@ from the portal's Backups tab and [restore them](../../cloud/cloud-backup-and-re
management Studio.
* In this page:
- * [Backups List](../../cloud/portal/cloud-portal-backups-tab.mdx#backup-files)
+ * [Backup List](../../cloud/portal/cloud-portal-backups-tab.mdx#backup-list)
## Backup List
The Backups tab lists your products, their databases and their backup files.
-
+
diff --git a/cloud/portal/cloud-portal-billing-tab.mdx b/cloud/portal/cloud-portal-billing-tab.mdx
index db4a56d2c1..337231fb86 100644
--- a/cloud/portal/cloud-portal-billing-tab.mdx
+++ b/cloud/portal/cloud-portal-billing-tab.mdx
@@ -21,9 +21,11 @@ Use your account's Billing & Costs tab to view your present costs, past invoices
* [The Billing & Costs Tab](#the-billing-&-costs-tab)
* [Pay Now](../../cloud/portal/cloud-portal-billing-tab.mdx#pay-now)
* [Current billing period](../../cloud/portal/cloud-portal-billing-tab.mdx#current-billing-period)
+ * [Current billing period costs](../../cloud/portal/cloud-portal-billing-tab.mdx#current-billing-period-costs)
* [Account benefits](../../cloud/portal/cloud-portal-billing-tab.mdx#account-benefits)
* [Billing history](../../cloud/portal/cloud-portal-billing-tab.mdx#billing-history)
* [Spending](../../cloud/portal/cloud-portal-billing-tab.mdx#spending)
+ * [Cost details](../../cloud/portal/cloud-portal-billing-tab.mdx#cost-details)
## The Billing & Costs Tab
@@ -32,9 +34,9 @@ The Billing & Costs tab will show your existing resources and their costs as wel
### Pay Now
-
+
-
+
The *Pay Now* button is designed to facilitate immediate payment of outstanding costs accrued from previous billing
cycles. This feature is especially useful for ensuring timely payments and maintaining up-to-date account status.
@@ -43,26 +45,128 @@ The Billing & Costs tab will show your existing resources and their costs as wel
### Current billing period
-
+
The *Current billing period* widget shows information about accrued costs in the current billing period and basic information about the last invoice.
+It also shows your **Unbilled** total — the costs accrued so far that have not yet been settled by an invoice — and a
+progress bar marking today's position between the start and end of the period. Use the **Cost Details** button to open
+the [Cost details](../../cloud/portal/cloud-portal-billing-tab.mdx#cost-details) view for the unbilled period.
+
+### Current billing period costs
+
+
+
+The *Current billing period costs* widget breaks the current period's costs down as a donut chart, so you can see at a
+glance what is driving the bill.
+
+Use the **Group costs by** selector to switch the breakdown between:
+
+* **Cost type** — machine cost, storage, data transfer, enabled features, and so on.
+* **Product** — one slice per product on the account.
+
+The chart shows the largest **seven** slices individually and groups everything else into a single **Other** slice;
+hover it to see what it contains.
+
+
+The amounts in this widget **exclude account benefits, backup and support costs**. For the complete picture of a period,
+including support costs, open its [Cost details](../../cloud/portal/cloud-portal-billing-tab.mdx#cost-details) view.
+
+
+Depending on the state of the period, the widget may report instead that:
+
+* no instances ran in this period,
+* the costs for this period have not been calculated yet, or
+* no costs were recorded in this period — in which case it also shows when costs were last calculated.
+
### Account benefits
-
+
The *Account benefits* widget shows information about current and expired benefits, their scope, validity dates and amounts.
### Billing history
-
+
The *Billing history* widget shows information about issued invoices, their status, billing period and their amount.
+Use the year selector above the table to move between years. Only years for which you have billing history are offered,
+and the selector always reflects the year the table is currently showing.
+
+Selecting a row opens that period's [Cost details](../../cloud/portal/cloud-portal-billing-tab.mdx#cost-details) view.
+
### Spending
-
+
The *Spending* widget gives you a clearer picture of where your money is going with our spending chart. Select a daily or calculated monthly expense to see trends.
+**Filter by cost category**
+
+Use the **Filter by cost category** dropdown to restrict the chart and the table below it to the categories you care
+about — for example, only storage, or only the cost of a single feature. Select individual categories, use *Select All*,
+or clear the selection to go back to the full picture. The categories currently selected are shown as badges above the
+chart.
+
+The available categories are:
+
+| Group | Categories |
+|---|---|
+| Instances and storage | Machine Cost, Storage, Additional Storage, Azure Performance Tier |
+| Traffic and disk | Data Transfer, Disk Operations |
+| Backups | Backup |
+| [Product features](../cloud-features.mdx) | Monitoring, Power BI, OLAP ETL, Queue ETL, Data Archival, AI Embeddings etc. |
+
+
+Which categories appear for your account depends on what you actually use — a feature you have never enabled produces
+no costs and so is not offered as a filter.
+
+
+**Visualization type and date range**
+
+Switch between **daily** and **monthly** visualization. In the monthly view, the year picker only offers years for which
+costs exist, so you cannot navigate to an empty year by accident.
+
+When the costs for the selected range have not been calculated yet, the widget says so instead of drawing an empty chart.
+
+
+Daily spending **excludes account benefits, backup and support costs**. Monthly spending is taken from the calculated
+account summary, which already includes backup costs, and so **excludes account benefits and support costs** only.
+
+
+## Cost details
+
+The *Cost details* view breaks a single billing period down to the individual products that produced the costs.
+Open it with the **Cost Details** button on the
+[Current billing period](../../cloud/portal/cloud-portal-billing-tab.mdx#current-billing-period) or
+[Current billing period costs](../../cloud/portal/cloud-portal-billing-tab.mdx#current-billing-period-costs) widget, or
+by selecting a row in [Billing history](../../cloud/portal/cloud-portal-billing-tab.mdx#billing-history).
+
+The view is headed with the period it describes and contains:
+
+* **Invoice links** — the invoices that settle this period, when it has been billed.
+* **Total** — the total cost for the period.
+* **A card per product** — each showing the product's cost, and both the pre-discount and final amount where a discount
+ or benefit applies.
+* **Support costs** — shown separately from the per-product costs.
+* **A daily spending chart** for the period's month, below the cost cards.
+
+
+For the **unbilled** period — the one still in progress — the heading carries an information icon noting that the
+presented cost is a **prediction**. It is based on the costs accrued so far and may still change before the period
+closes. Billed periods show final amounts and no such note.
+
+
+
+If your subscription is managed through the
+[Microsoft Azure](../cloud-microsoft-azure-marketplace.mdx) or [AWS](../cloud-aws-marketplace.mdx) Marketplace, the view
+states that your payment information is managed by that provider. Costs are still shown here in full.
+
+
+
+The Billing & Costs views, including *Cost details*, require the account-level **Billing** role.
+See [Account roles](../cloud-account.mdx#account-roles).
+
+
diff --git a/cloud/portal/cloud-portal-home-tab.mdx b/cloud/portal/cloud-portal-home-tab.mdx
index 58e661ad05..cfc79f0386 100644
--- a/cloud/portal/cloud-portal-home-tab.mdx
+++ b/cloud/portal/cloud-portal-home-tab.mdx
@@ -23,7 +23,7 @@ Use this tab to manage your account and assigned roles. You can also use it to v
## The Home Tab
-
+
In the **Your profile** section, you can check your 2FA settings and the date of your last login.
@@ -34,7 +34,7 @@ In the **Roles and access** section, you can review your access on this account
If you are the **Account Owner** (or otherwise have full account access), this section shows a short full-access summary instead of a per-product list.
-
+
In the **Documentation** section, you can explore important topics.
diff --git a/cloud/portal/cloud-portal-products-tab.mdx b/cloud/portal/cloud-portal-products-tab.mdx
index 08c4aab6a1..ea708d2972 100644
--- a/cloud/portal/cloud-portal-products-tab.mdx
+++ b/cloud/portal/cloud-portal-products-tab.mdx
@@ -26,11 +26,15 @@ and [Production](../../cloud/cloud-overview.mdx#the-production-tier).
* [Provisioning a New Product](../../cloud/portal/cloud-portal-products-tab.mdx#provisioning-a-new-product)
* [View the Product Metrics](../../cloud/portal/cloud-portal-products-tab.mdx#view-the-product-metrics)
* [View the Cluster Health](../../cloud/portal/cloud-portal-products-tab.mdx#view-the-cluster-health)
+ * [View the Alerts](../../cloud/portal/cloud-portal-products-tab.mdx#view-the-alerts)
* [Managing an Existing Product](../../cloud/portal/cloud-portal-products-tab.mdx#managing-an-existing-product)
+ - [Instance Access: Open Studio](../../cloud/portal/cloud-portal-products-tab.mdx#instance-access)
- [Change Instance Type and Storage](../../cloud/portal/cloud-portal-products-tab.mdx#change-instance-type-and-storage)
- - [Security: Your Certificate, Audit Logs and Allowed IPs](../../cloud/portal/cloud-portal-products-tab.mdx#security-your-certificate-audit-logs-and-allowed-ips)
+ - [Security: Certificate and Audit Logs](../../cloud/portal/cloud-portal-products-tab.mdx#security-your-certificate-audit-logs-and-allowed-ips)
+ - [Allowed IPs](../../cloud/portal/cloud-portal-products-tab.mdx#allowed-ips)
- [Manage features](#manage-features)
- [Nodes: Additional product nodes](../../cloud/portal/cloud-portal-products-tab.mdx#nodes-additional-product-nodes)
+ - [Subscription & support](../../cloud/portal/cloud-portal-products-tab.mdx#subscription-and-support)
- [Maintenance and Danger Zones: Terminate and Restart your Instance](../../cloud/portal/cloud-portal-products-tab.mdx#maintenance-and-danger-zones)
- [User Access](../../cloud/portal/cloud-portal-products-tab.mdx#user-access)
@@ -38,7 +42,7 @@ and [Production](../../cloud/cloud-overview.mdx#the-production-tier).
## Provisioning a New Product
To provision a new product, open your Portal's Products tab and click **Add Product**.
-
+
Creating a product requires the [**Products Creation**](../../cloud/cloud-account.mdx#account-roles) account role — the **Add Product** button is hidden otherwise. Users without any relevant access do not see the **Products** tab at all.
@@ -52,10 +56,23 @@ C. [Billing](../../cloud/portal/cloud-portal-products-tab.mdx#c-new-product-bill
D. [Customize](../../cloud/portal/cloud-portal-products-tab.mdx#d-new-product-customize)
E. [Summary](../../cloud/portal/cloud-portal-products-tab.mdx#e-new-product-summary)
+
+**Account** and **Billing** are only asked for when the wizard still needs that information:
+
+* **Account** appears only when your account has neither its details nor a payment method on file.
+* **Billing** appears only when no payment method is on file, and never for
+ [Microsoft Azure](../cloud-microsoft-azure-marketplace.mdx) or [AWS](../cloud-aws-marketplace.mdx) Marketplace
+ accounts, whose payment is handled by the provider.
+
+So the first product you provision usually walks through all five stages, while later ones typically go straight from
+**Plan** to **Customize** and **Summary**.
+
+
+
#### A. New Product: Plan
Use the Plan page to choose your product's cloud **Provider**, **Region**, **Tier**, **Instance**, **Storage** and **Payment model**.
-
+
1. **Cloud Provider**
Choose your cloud host. It can currently be one of three providers:
@@ -85,17 +102,17 @@ Use the Plan page to choose your product's cloud **Provider**, **Region**, **Tie
#### B. New Product: Account
Enter your account information and click **Next**.
-
+
#### C. New Product: Billing
Enter your billing details and click **Next**.
-
+
#### D. New Product: Customize
Choose your product's display name, release channel and allowed IP addresses.
-
+
The **Display Name** is simply the name that would appear in your Cloud Products tab.
@@ -107,17 +124,17 @@ The **Display Name** is simply the name that would appear in your Cloud Products
#### E. New Product: Summary
The Summary stage shows you your choices and lets you edit them if you wish.
-
+
When you finish defining your product, the cloud provisioning routine will show you
your new product's status until it's ready to go.
-
+
-
+
## View the Product Metrics
-
+
This allows you to analyse your machine resources for a selected time period and cluster node.
It's useful for analysing usage, instance overload and traffic.
@@ -128,7 +145,7 @@ The **Metrics** and **Cluster Health** buttons — on both the product list and
## View the Cluster Health
-
+
This allows you to analyse your cluster incidents for a selected *time period*, *cluster node*, *severity*, *category* and *event status*.
In addition, **Cluster Health** generates suggestions for a selected *cluster node* based on incident trends that can help resolve cluster stability issues.
@@ -137,6 +154,23 @@ It's useful for analysing usage, instance overload and traffic.
More details can be found [here](../cloud-maintenance-troubleshooting.mdx#cluster-health).
+## View the Alerts
+
+
+
+This allows you to have the events recorded by **Cluster Health** emailed to you, so you do not have to watch the Portal
+to learn that an instance is under pressure. You can configure a single *daily summary* digest and any number of
+*custom alerts* that fire as soon as a chosen event is recorded, each with its own list of recipients.
+
+
+The **Alerts** tab requires the [Monitoring](../cloud-features.mdx#monitoring) feature to be enabled on the product,
+plus at least [**Viewer** access](../../cloud/cloud-account.mdx#permission-presets) to it. Changing the rules
+additionally requires the **Manage features** permission together with the
+[**Security admin** add-on](../../cloud/cloud-account.mdx#permission-presets), and the product must be **Active**.
+
+
+More details can be found [here](../cloud-maintenance-troubleshooting.mdx#alerts).
+
## Managing an Existing Product
@@ -145,24 +179,43 @@ The actions available on a product depend on your [per-product permissions](../.
To modify an existing product, find it in the Products tab and click its Manage button.
-
+
This is a general view of the product details page:
-
+
This is a general view of the serverless product details page:
-
+
+
+### Instance Access: Open Studio {#instance-access}
+
+The bar at the top of the product view — above the **Manage**, **Metrics**, **Cluster Health** and **Alerts** tabs —
+shows the product's name and status, and carries the **Open Studio** button that takes you to RavenDB Studio.
+
+* On a **single-node** product, **Open Studio** is a plain button that opens that node's Studio in a new tab.
+* On a **multi-node** product, **Open Studio** is a dropdown listing every node — **Node A**, **Node B**, and so on —
+ so you can pick the node whose Studio you want to open.
+
+The button appears only while the product is **Active** or **Deploying changes**. Until you have downloaded the client
+certificate, hovering it shows the reminder *"Please remember to download Certificate before accessing studio"* —
+Studio will not let you in without an installed certificate, so
+[download it first](#security-your-certificate-audit-logs-and-allowed-ips).
+
+
+**Open Studio** is also available per product directly in the [Products list](#managing-an-existing-product), next to
+the **Manage** button.
+
### Change Instance Type and Storage
You can view your configuration and change your product's instance type and storage size here.
-
+
* **Change Instance Type**
Use sliders to set your desired configuration. This can be changed later as you need to scale to changing data processing needs.
-
+
Changing instance type for Serverless product is not possible.
@@ -172,36 +225,48 @@ You can view your configuration and change your product's instance type and stor
* **Change Storage**
Use this slider to modify your product's storage.
-
+
Disk can be migrated to **Data Disk** using *Migrate disk* button.
-
+
When eligible, the *Storage* section also shows an **Upgrade to Premium V2** button to upgrade
the disk to **Azure Premium SSD v2**.
-
+
More details can be found [here](../cloud-scaling.mdx#scaling---change-storage). For
**Azure Premium SSD v2** — eligibility, constraints, and behavior of the upgrade — see
[Azure Premium SSD v2](../cloud-scaling.mdx#azure-premium-ssd-v2).
-### Instance Access
+### Security: Certificate and Audit Logs {#security-your-certificate-audit-logs-and-allowed-ips}
-* **Open Studio**
- Click this button to open the RavenDB Studio of node A.
+The **Security** card holds your instance's client certificate and its audit logs.
+See the [Security](../../cloud/cloud-security.mdx) page for the wider picture.
-### Security: Your Certificate, Audit Logs and Allowed IPs
-Use the security tab to download your [certificate](../../cloud/cloud-security.mdx) or determine which addresses are
-allowed to connect your database instance.
+
-
+
+**Download certificate** and **Regenerate certificate** require the **Security admin** add-on — no
+[base preset](../../cloud/cloud-account.mdx#permission-presets) grants it on its own.
+**See audit logs** requires the [**Operator** preset](../../cloud/cloud-account.mdx#permission-presets) or higher.
+Buttons you are not permitted to use are disabled, with a tooltip explaining why.
+
+
+* **Download certificate**
+ Downloads the **Initial Client Certificate** package — a zip archive containing the `.pfx` files.
+ This is an **operator-level** certificate used to perform cluster-wide operations (like creating or deleting databases)
+ and for your first login to RavenDB Studio.
-* **Download Certificate** Click this button to download the **Initial Client Certificate**.
- This is an **operator-level** certificate used to perform cluster-wide operations (like creating/deleting databases) and for your first login to RavenDB Studio.
+ The first time you use it, the portal opens the **Downloading and Installing Initial Certificate** dialog, which walks
+ you through downloading the package and installing it, with instructions for **Windows + Chrome** and
+ **Linux + Chrome**. You can reopen that dialog later from **How to setup certificate?** in the dropdown next to the
+ button.
-* **Regenerate Certificate** Click the dropdown next to the *Download certificate* button to regenerate it.
+* **Regenerate certificate**
+ Click the dropdown next to **Download certificate** and choose **Regenerate certificate**. Use it when your current
+ certificate has expired, or when you want to stop using the one you hold.
Regenerating a certificate creates a new identity. After this operation, you must download and install the new certificate to maintain access via the portal.
@@ -210,6 +275,17 @@ allowed to connect your database instance.
The previous certificate is **not** automatically removed from the cluster by this operation. To revoke old certificates, you must use the RavenDB Studio Certificates view.
+* **Certificate expiration date**
+ The card shows how long the current client certificate remains valid. Cloud client certificates are issued for
+ **five years**, and renewal is handled for you:
+
+ * **60 days** before expiry, the account is emailed a notice stating the expiration date and the date of the
+ automatic renewal.
+ * **30 days** before expiry, the certificate is regenerated automatically.
+
+ An automatic renewal behaves like a manual one: download and install the new certificate to keep your access working,
+ and remove the old certificate from the RavenDB Studio Certificates view when you no longer need it.
+
For maximum security and performance, we recommend using the initial certificate only for setup and emergency access.
@@ -219,21 +295,39 @@ allowed to connect your database instance.
We recommend **generating certificates off-cloud** (on your own machine) and importing them into the Studio via **Settings > Certificates**.
-* **See audit logs**
- Click this button to view audit logs. A popup will show where you have to select a year and month.
- You can download audit logs from there.
- 
+* **See audit logs**
+ Opens the **Select date to load audit logs** dialog. Pick a year and month, then expand a node tag to list the audit
+ log files that node recorded in that month and download them.
-* **Edit**
- Click this button to edit your product's list of Allowed IPs.
+ 
- 
+### Allowed IPs
-
- You can increase your system's security further using this in-depth security measure and restrict access to
- trusted sources, e.g. your application servers.
- More details can be found in the [Security](../cloud-security.mdx#access-your-product) page.
-
+The **Allowed IPs** card determines which addresses are allowed to connect to your database instance, adding an
+important layer of security at the network level. It lists the current entries as **IP Address** and **Alias** pairs.
+A `0.0.0.0/0` (**Allow all**) entry is pinned to the top of the list and flagged with a warning, because it leaves your
+instance reachable from anywhere.
+
+
+Editing the list requires the **Security admin** add-on — no
+[base preset](../../cloud/cloud-account.mdx#permission-presets) grants it on its own. Without it the **Edit** button is
+disabled, with a tooltip explaining why.
+
+
+Click **Edit** to change the list.
+
+
+
+Each row takes an address in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing)
+(for example `192.168.0.0/24`) and a free-text alias. **Add my IP** inserts the address you are currently connecting
+from, **Add new IP** adds an empty row, and the bin button removes a row. Click **Save** to apply your changes, or
+**Cancel** to discard them.
+
+
+You can increase your system's security further using this in-depth security measure and restrict access to
+trusted sources, e.g. your application servers.
+More details can be found in the [Security](../cloud-security.mdx#access-your-product) page.
+
### Manage features
@@ -243,7 +337,7 @@ You can view features available for your product, enable, disable and configure
After enabling features some of them must be configured to work properly.
-
+
Available features are described on [Product Features](../cloud-features.mdx) page.
@@ -255,14 +349,54 @@ Enabling, disabling, and configuring features requires the [**Manager** (or **Ad
You can expand your cluster by adding *more product nodes* to your cluster. This helps improve *High Availability* and *task/load balancing*.
-
+
More details can be found [here](../cloud-scaling.mdx#additional-product-nodes---general).
+### Subscription & support {#subscription-and-support}
+
+The **Subscription & support** card gathers what your product is paying for, which RavenDB build it tracks, and where to
+get help with it.
+
+
+
+#### Subscription details
+
+| Field | Description |
+|---|---|
+| **Payment** | Your payment model — *On-Demand*, *Yearly All Upfront* or *Yearly No Upfront*. See [Pricing, Payment and Billing](../cloud-pricing-payment-billing.mdx). |
+| **Contract** | The date your current contract runs until. Shown only for term contracts. |
+| **Release channel** | The RavenDB release channel this product tracks, as chosen in the [Customize](#d-new-product-customize) stage. |
+
+When a newer release channel than the one your product tracks becomes available, an **Update available** pill appears
+next to the release channel. Clicking it opens the [Support](./cloud-portal-support-tab.mdx#request-support-from-a-product)
+view with this product selected, so you can ask for the upgrade — changing the release channel is not a self-service
+action.
+
+
+For [Microsoft Azure](../cloud-microsoft-azure-marketplace.mdx) and [AWS](../cloud-aws-marketplace.mdx) Marketplace
+accounts the **Payment** and **Contract** rows are not shown, because billing is handled by the provider. Only the
+release channel appears.
+
+
+#### Support & help resources
+
+This part of the card offers direct links to the *Documentation*, *GitHub discussions* and the *Discord community*,
+and a badge showing whether the product is covered by **Paid support** or the **Free tier**.
+
+If your account has an active paid support option, the card also offers **Request support for this instance**, which
+opens the [Support](./cloud-portal-support-tab.mdx#request-support-from-a-product) view with this product already
+selected. Otherwise it links to a comparison of the paid support plans.
+
+
+The support badge and the request/compare panel are shown only to users with the
+[**Support** account role](../../cloud/cloud-account.mdx#account-roles). The three resource links are always available.
+
+
### Maintenance and Danger Zones
You can restart your product nodes, deploy additional tools and terminate your product here.
-
+
* **Maintenance Zone**
Use this tab to restart selected node and deploy RavenDB tools. For *Serverless* products, you can switch to regular deployment.
@@ -270,11 +404,11 @@ You can restart your product nodes, deploy additional tools and terminate your p
Changing your product deployment type is **irreversible**.
-
+
* **Danger Zone**
Use this tab's **Terminate** button to eliminate your cluster.
-
+
Terminating your instance is **irreversible**. Your data and cluster properties will be permanently lost.
@@ -284,4 +418,5 @@ Changing your product deployment type is **irreversible**.
The product view includes a **User Access** widget that lists the account users who have access to this product, together with their access level. If you can manage users, you can change a user's [preset](../cloud-account.mdx#permission-presets) and toggle the **Security admin** add-on directly in the widget, then click **Save changes** — without leaving the product view. The **Account Owner** is always shown with **full access**. Use **Manage in Users & Access** to open the [Users & Access](./cloud-portal-users-and-access-tab.mdx) page for the full user-management view. When no other users have been granted access yet, the widget shows an empty state.
-
+
+
diff --git a/cloud/portal/cloud-portal-support-tab.mdx b/cloud/portal/cloud-portal-support-tab.mdx
index 4d86a4a2a2..ced94d5dc6 100644
--- a/cloud/portal/cloud-portal-support-tab.mdx
+++ b/cloud/portal/cloud-portal-support-tab.mdx
@@ -22,11 +22,13 @@ Use the Support tab to contact our *RavenDB Cloud* support team.
* [The Support Tab](../../cloud/portal/cloud-portal-support-tab.mdx#the-support-tab)
* [Submit a General Support request](../../cloud/portal/cloud-portal-support-tab.mdx#submit-a-general-support-request)
* [Submit a Product-Related Support request](../../cloud/portal/cloud-portal-support-tab.mdx#submit-a-product-related-support-request)
+ * [Resources that may help you](../../cloud/portal/cloud-portal-support-tab.mdx#resources-that-may-help-you)
+ * [Request support from a product](../../cloud/portal/cloud-portal-support-tab.mdx#request-support-from-a-product)
* [Request to enable the Cloud Support option](../../cloud/portal/cloud-portal-support-tab.mdx#request-to-enable-the-cloud-support-option)
## The Support Tab
-
+
The root selection is between submitting a support request regarding a **general** topic or a **product-related** one.
@@ -35,40 +37,84 @@ A user with the account-level [**Support**](../../cloud/cloud-account.mdx#accoun
### Submit a General Support request
-
+
- **1**. Select to raise a general question.
- **2**. Select the issue severity: *Minor*, *Normal*, or *Critical*.
- **3**. Select the expected response time: *Standard*, *Next business day*, or *Within 2 hours*.
- **4**. Enter your support request title.
- **5**. Enter your question.
- **6**. Submit your support request.
+ **1**. Under *Is your question related to one of your products?*, choose **No, general question**.
+ **2**. Select the **Severity**: *Minor*, *Normal*, or *Critical*.
+ **3**. Pass the **Resources that may help you** step — see [below](#resources-that-may-help-you).
+ **4**. Select the **Expected Response Time**: *Standard*, *Next business day*, or *Within 2 hours*.
+ **5**. Enter a **Title**.
+ **6**. Enter your **Message**.
+ **7**. Click **Send request**.
-You can read more about the *Severity* and *Response time* types in the [Support](../../cloud/cloud-support.mdx#response-time-types) page.
+You can read more about the *Severity* and *Response time* types in the [Support](../../cloud/cloud-support.mdx#severity-and-response-time-types) page.
### Submit a Product-Related Support Request
-
+
- **1**. Select to raise a Product-related question.
- **2**. Select the product you relate to.
- **3**. Select the issue severity: *Minor*, *Normal*, or *Critical*.
- **4**. Select the expected response time: *Standard*, *Next business day*, or *Within 2 hours*.
- **5**. Select the issue category.
- **6**. Select the option associated with the instance restart action.
- **7**. Enter your support request title.
- **8**. Enter your question.
- **9**. Submit your support request.
-
-You can read more about the *Severity* and *Response time* types in the [Support](../../cloud/cloud-support.mdx#response-time-types) page.
+ **1**. Under *Is your question related to one of your products?*, choose **Yes**.
+ **2**. Pick the **Relevant product**.
+ **3**. Select the **Severity**: *Minor*, *Normal*, or *Critical*.
+ **4**. Pass the **Resources that may help you** step — see [below](#resources-that-may-help-you).
+ **5**. Select the **Expected Response Time**: *Standard*, *Next business day*, or *Within 2 hours*.
+ **6**. Select the **Issue category**.
+ **7**. Answer *Have you tried restarting your instance?* — **Yes**, **No**, or **Not relevant**.
+ **8**. Enter a **Title**.
+ **9**. Enter your **Message**.
+ **10**. Click **Send request**.
+
+You can read more about the *Severity* and *Response time* types in the [Support](../../cloud/cloud-support.mdx#severity-and-response-time-types) page.
+
+### Resources that may help you
+
+Both flows include a step you cannot skip. After choosing the severity — and, for a product-related request, the
+product — the form shows a **Resources that may help you** panel linking to *GitHub discussions* and the
+*RavenDB documentation*, in case your question is already answered there.
+
+Below it, **Still looking for an answer?** offers a **Proceed to create support request** button. The button is briefly
+disabled and counts down (*"You can proceed within…"*) before it can be clicked.
+
+The rest of the form — starting with the **Expected Response Time** section — only appears once you click that button.
+If you cannot find the response time options, this is why.
+
+### Request support from a product
+
+You do not have to start from the Support view. Every product view carries a
+[**Subscription & support**](../../cloud/portal/cloud-portal-products-tab.mdx#subscription-and-support) card, which offers
+direct links to the *Documentation*, *GitHub discussions* and the *Discord community*, and shows whether the product is
+covered by **Paid support** or the **Free tier**.
+
+* With an **active paid support option**, the panel offers **Request support for this instance**. It takes you to the
+ Support view with the question type set to product-related and **this product already selected**, so you only need to
+ fill in the request itself. You can still change the selected product before submitting.
+* **Without** a paid support option, the panel instead links to a comparison of the paid support plans. See
+ [Request to enable the Cloud Support option](../../cloud/portal/cloud-portal-support-tab.mdx#request-to-enable-the-cloud-support-option)
+ below.
+
+Opening the Support view directly works exactly as before — no product is pre-selected.
+
### Request to enable the Cloud Support option
-
+
+
+If your account is on the **Free** plan, the Support view also shows a **Need some extra care?** panel offering the paid
+support options. It lists what the option includes — *24/7 availability*, *call and e-mail support*, a *2 hour SLA*, and
+coverage for **all products in your account** — with a link to the *Terms of service*.
+
+Two commitments are offered — a **12 month plan** and a **6 month plan** — each shown with its price and commitment
+length.
-To request the **Cloud Support option**, please click the *Request Cloud Support Activation* button.
-This will show you Support Activation Request Form. There you can select type of support you want to activate and send a
-support request to our *RavenDB Cloud* support team with *Request Activation* button.
+Click **Choose plan** on the one you want. An *Upgrade to premium support* dialog opens with a summary of the plan you
+picked, which you confirm with **Send activation request**.
-
+
+
+
+
+
+The paid support option requires at least one **production tier** instance. Its price is a share of your hosting
+cost, with a minimum of **$79/month**.
+
After verification, the support team will add the support option to your account, which
diff --git a/cloud/portal/cloud-portal-users-and-access-tab.mdx b/cloud/portal/cloud-portal-users-and-access-tab.mdx
index 81177d6f89..a746a6342a 100644
--- a/cloud/portal/cloud-portal-users-and-access-tab.mdx
+++ b/cloud/portal/cloud-portal-users-and-access-tab.mdx
@@ -32,7 +32,7 @@ The Users & Access page lists every user on the account. Each row shows the user
Access is shown as two compact chips you can expand — for example *3 roles* and *3 products*. Expanding the product-access chip lists each product the user can access together with its level: the resolved [permission preset](../../cloud/cloud-account.mdx#permission-presets) (*Viewer*, *Operator*, *Manager*, or *Admin*), a **Security admin** badge where that add-on is enabled, or **Custom** for a legacy permission set that does not match any preset. The **Account Owner** is shown with full access to all products. Your own row is displayed the same way.
-
+
You can filter the list by email, by account role, by product access, and by permission level.
@@ -57,7 +57,7 @@ You can read more about *account roles* and *product permissions* on the [Accoun
Click **Invite new user** at the top of the users list to open the invite panel. Both account roles and per-product permissions are set in this single panel.
-
+
**1**. Provide an *email address*.
**2**. Select the user's [account roles](../../cloud/cloud-account.mdx#account-roles).
@@ -68,7 +68,7 @@ Click **Invite new user** at the top of the users list to open the invite panel.
Each row in the users list has action buttons in the **Actions** column.
-
+
* Click **Remove** (the trash icon) to remove an active user from the account.
* Click **Cancel invitation** (the trash icon on a pending row) to withdraw a pending invitation.
@@ -79,7 +79,7 @@ The **Account Owner** row and your own row have no removal button.
Click the **Edit** button on a user's row to open the edit panel. As with the invite panel, account roles and per-product permissions are managed together here.
-
+
**1**. Adjust the user's [account roles](../../cloud/cloud-account.mdx#account-roles).
**2**. Adjust *per-product permissions* using the presets. Each preset shows a short description of what it grants. Products you cannot access yourself are **locked** (see the [subset rule](#who-can-manage-users-and-permissions) above). If you are the **Account Owner**, you can also update the user's **Default access for new products** here.
diff --git a/cloud/portal/cloud-portal.mdx b/cloud/portal/cloud-portal.mdx
index 590cee05cc..a4b553b427 100644
--- a/cloud/portal/cloud-portal.mdx
+++ b/cloud/portal/cloud-portal.mdx
@@ -21,37 +21,79 @@ takes you to your account's Portal, which gives you access to all the different
* In this page:
* [Cloud Portal overview](../../cloud/portal/cloud-portal.mdx#cloud-portal-overview)
+ * [Sidebar views](../../cloud/portal/cloud-portal.mdx#sidebar-views)
+ * [Help center](../../cloud/portal/cloud-portal.mdx#help-center)
+ * [Profile](../../cloud/portal/cloud-portal.mdx#profile)
## Cloud Portal overview
-
+
-* **[The Home Tab](../../cloud/portal/cloud-portal-home-tab.mdx)**
- Use this tab to manage your account and assigned roles, and to view useful resources.
+You navigate the Portal from the **sidebar** on the left. It can be collapsed to icons only, using the control next to
+the logo, to give the current view more room.
-* **[The Products Tab](../../cloud/portal/cloud-portal-products-tab.mdx)**
- Use this tab to [provision new products](../../cloud/portal/cloud-portal-products-tab.mdx#provisioning-a-new-product) and
- [manage existing ones](../../cloud/portal/cloud-portal-products-tab.mdx#managing-an-existing-product).
+At the top of the sidebar, the **account switcher** lets you move between the cloud accounts you have access to. Each
+account is identified by its **domain name**. See
+[Multi-account configuration](../../cloud/cloud-account.mdx#multi-account-configuration).
-* **[The Backups Tab](../../cloud/portal/cloud-portal-backups-tab.mdx)**
- Use this tab to view and restore [mandatory database backups](../../cloud/cloud-backup-and-restore.mdx#the-mandatory-backup-routine)
+### Sidebar views
+
+* **[Home](../../cloud/portal/cloud-portal-home-tab.mdx)**
+ Manage your account and assigned roles, and view useful resources.
+
+* **[Products](../../cloud/portal/cloud-portal-products-tab.mdx)**
+ [Provision new products](../../cloud/portal/cloud-portal-products-tab.mdx#provisioning-a-new-product) and
+ [manage existing ones](../../cloud/portal/cloud-portal-products-tab.mdx#managing-an-existing-product), including their
+ [metrics](../../cloud/portal/cloud-portal-products-tab.mdx#view-the-product-metrics),
+ [cluster health](../../cloud/portal/cloud-portal-products-tab.mdx#view-the-cluster-health) and
+ [alerts](../../cloud/portal/cloud-portal-products-tab.mdx#view-the-alerts).
+
+* **[Backups](../../cloud/portal/cloud-portal-backups-tab.mdx)**
+ View and restore [mandatory database backups](../../cloud/cloud-backup-and-restore.mdx#the-mandatory-backup-routine)
that your instances have created for you.
-* **[The Billing & Costs Tab](../../cloud/portal/cloud-portal-billing-tab.mdx)**
- Use the Billing & Costs tab to view your billing history and expected payments.
+* **[Billing & costs](../../cloud/portal/cloud-portal-billing-tab.mdx)**
+ View your billing history, expected payments and a
+ [breakdown of your costs](../../cloud/portal/cloud-portal-billing-tab.mdx#cost-details).
+
+* **[API](../../cloud/portal/cloud-portal-api-tab.mdx)**
+ Explore the RavenDB Cloud API and manage your API keys.
+
+* **[Users & Access](../../cloud/portal/cloud-portal-users-and-access-tab.mdx)**
+ Invite account members and manage their [account roles](../../cloud/cloud-account.mdx#account-roles) and
+ [per-product permissions](../../cloud/cloud-account.mdx#product-permissions).
+
+* **[Account](../../cloud/portal/cloud-portal-account-tab.mdx)**
+ View and edit your invoices and credit card information.
+
+
+Which views you see depends on your access — for example, *Billing & costs* requires the **Billing**
+[account role](../../cloud/cloud-account.mdx#account-roles), and *Users & Access* requires
+**Account with User Management**. Views you have no role for are not shown.
+
+**Products** is gated differently: it appears if you hold the **Products Creation**
+[account role](../../cloud/cloud-account.mdx#account-roles), or if you have
+[per-product permissions](../../cloud/cloud-account.mdx#product-permissions) on at least one product. The
+**Account Owner** always sees it.
+
+
+### Help center
-* **[The API Tab](../../cloud/portal/cloud-portal-api-tab.mdx)**
- Use the API tab to explore the RavenDB Cloud API and manage your API keys.
+The **Help center** entry at the bottom of the sidebar opens a menu with:
-* **[The Support Tab](../../cloud/portal/cloud-portal-support-tab.mdx)**
- Use this tab to contact Support regarding [general issues](../../cloud/portal/cloud-portal-support-tab.mdx#submit-a-general-support-request),
- [product-specific issues](../../cloud/portal/cloud-portal-support-tab.mdx#submit-a-product-related-support-request) and special requests.
+* **[Support](../../cloud/portal/cloud-portal-support-tab.mdx)** — contact Support regarding
+ [general issues](../../cloud/portal/cloud-portal-support-tab.mdx#submit-a-general-support-request),
+ [product-specific issues](../../cloud/portal/cloud-portal-support-tab.mdx#submit-a-product-related-support-request)
+ and special requests. This entry requires the **Support**
+ [account role](../../cloud/cloud-account.mdx#account-roles); the other three are always available.
+* **Documentation** — this documentation.
+* **Community** — the RavenDB community resources.
+* **[Service status](https://status.ravendb.net/)** — the status of our system, with active and archived incidents.
-* **[The Account Tab](../../cloud/portal/cloud-portal-account-tab.mdx)**
- Use the account tab to view and edit your invoices and credit card information.
+### Profile
-* **[The Service Status Tab](https://status.ravendb.net/)**
- Use this tab to check the status of our system and view active and archived incidents.
+The **profile** entry, also at the bottom of the sidebar, shows your user name and gives you access to your profile
+settings — including [Multi-Factor Authentication](../../cloud/cloud-security.mdx#mfa) — and to **Log out**.
diff --git a/docs/studio/database/indexes/indexing-performance.mdx b/docs/studio/database/indexes/indexing-performance.mdx
index 4620777916..f179d4bb78 100644
--- a/docs/studio/database/indexes/indexing-performance.mdx
+++ b/docs/studio/database/indexes/indexing-performance.mdx
@@ -203,9 +203,9 @@ You can configure [batch stops](../../../studio/database/indexes/indexing-perfor
to break up processes into smaller batches.
* **Cloud server**
Your indexing process will continue until it is finished, but will be broken up into smaller batches and continue when enough CPU credits accumulate.
- This can happen on [basic](/cloud/cloud-instances#basic-grade-production-cluster)-level cloud instances.
- * Unless you're running a [production cloud tier](/cloud/cloud-instances#a-production-cloud-cluster) with CPU priority of [standard](/cloud/cloud-instances#standard-grade-production-cluster)
- or [Performance](/cloud/cloud-instances#performance-grade-production-cluster), your cluster is [burstable and subject to throttling](/cloud/cloud-overview#budget-credits-and-throttling).
+ This can happen on [basic](/cloud/cloud-instances#1-basic-grade-production-cluster)-level cloud instances.
+ * Unless you're running a [production cloud tier](/cloud/cloud-instances#a-production-cloud-cluster) with CPU priority of [standard](/cloud/cloud-instances#2-standard-grade-production-cluster)
+ or [Performance](/cloud/cloud-instances#3-performance-grade-production-cluster), your cluster is [burstable and subject to throttling](/cloud/cloud-overview#budget-credits-and-throttling).
This means that you have CPU credits with limits. If you have reached your credit limit, RavenDB will wait until you've
accumulated enough credits to run another batch process.
This causes indexing to seem slow.
diff --git a/guides/connecting-c-application-to-ravendb-cloud.mdx b/guides/connecting-c-application-to-ravendb-cloud.mdx
index cb312e8d4b..c149654df3 100644
--- a/guides/connecting-c-application-to-ravendb-cloud.mdx
+++ b/guides/connecting-c-application-to-ravendb-cloud.mdx
@@ -64,7 +64,7 @@ We've successfully created a RavenDB Cloud account. Now, let's create a free ins
-If you would like a free instance, don't change anything - just scroll down and click *'Next'(1)*. Enter your account information(2) and then go through billing. Next, you have a *'Customize'* step(3), where you need to put in the display name of your instance. You also need to set the instance as open to the world (Leave 0.0.0.0/0 if you want it to be open to the world) or delete IP 0.0.0.0/0 and click '*Add my IP*', to make this only accessible with your IP. You can also change it later so don't be afraid to delete 0.0.0.0/0. If you want to learn more about CIDR notation, you can read more [here](https://aws.amazon.com/what-is/cidr/). Then, just hit *'Next'*, review the summary and if all looks good, click *'Create'*. For more details on adding a new product, [click here](https://ravendb.net/docs/article-page/csharp/cloud/portal/cloud-portal-products-tab#manage-product-the-security-tab).
+If you would like a free instance, don't change anything - just scroll down and click *'Next'(1)*. Enter your account information(2) and then go through billing. Next, you have a *'Customize'* step(3), where you need to put in the display name of your instance. You also need to set the instance as open to the world (Leave 0.0.0.0/0 if you want it to be open to the world) or delete IP 0.0.0.0/0 and click '*Add my IP*', to make this only accessible with your IP. You can also change it later so don't be afraid to delete 0.0.0.0/0. If you want to learn more about CIDR notation, you can read more [here](https://aws.amazon.com/what-is/cidr/). Then, just hit *'Next'*, review the summary and if all looks good, click *'Create'*. For more details on adding a new product, [click here](https://ravendb.net/docs/article-page/csharp/cloud/portal/cloud-portal-products-tab#provisioning-a-new-product).
diff --git a/guides/connecting-node-js-application-to-ravendb-cloud.mdx b/guides/connecting-node-js-application-to-ravendb-cloud.mdx
index ea096a01c5..7c0538db35 100644
--- a/guides/connecting-node-js-application-to-ravendb-cloud.mdx
+++ b/guides/connecting-node-js-application-to-ravendb-cloud.mdx
@@ -83,7 +83,7 @@ To set up a free instance:
3. In the *'Customize'* step, enter the display name for your instance and configure IP access. Leave `0.0.0.0/0` to allow access from anywhere, or click '*Add my IP*' to restrict access to your IP only. You can change this later. If you want to learn more about CIDR notation, [read more here](https://aws.amazon.com/what-is/cidr/#:~:text=CIDR%20notation%20represents%20an%20IP,1.0%2F22.).
4. Click *'Next'*, review the summary, and click *'Create'*.
-For more details on adding a new product, [click here](https://ravendb.net/docs/article-page/latest/csharp/cloud/portal/cloud-portal-products-tab#manage-product-the-security-tab).
+For more details on adding a new product, [click here](https://ravendb.net/docs/article-page/latest/csharp/cloud/portal/cloud-portal-products-tab#provisioning-a-new-product).
diff --git a/guides/how-to-setup-ravendb-with-asp-net-core-8-application.mdx b/guides/how-to-setup-ravendb-with-asp-net-core-8-application.mdx
index da629e3454..a90a178e6e 100644
--- a/guides/how-to-setup-ravendb-with-asp-net-core-8-application.mdx
+++ b/guides/how-to-setup-ravendb-with-asp-net-core-8-application.mdx
@@ -84,7 +84,7 @@ To get a free instance:
3. On the *'Customize'* step, enter a display name for your instance and set the IP access. Leave `0.0.0.0/0` to allow connections from anywhere, or click *'Add my IP'* to restrict it to your current machine. (`0.0.0.0/0` is CIDR notation meaning all IPv4 addresses; you can change it later.)
4. Click *'Next'*, review the summary, and click *'Create'*
-For more details on adding a new product, [click here](/cloud/portal/cloud-portal-products-tab#manage-product-the-security-tab).
+For more details on adding a new product, [click here](/cloud/portal/cloud-portal-products-tab#provisioning-a-new-product).