diff --git a/sources/platform/actors/development/actor_definition/dataset_schema/multiple_datasets.md b/sources/platform/actors/development/actor_definition/dataset_schema/multiple_datasets.md
new file mode 100644
index 0000000000..80f5abf4a4
--- /dev/null
+++ b/sources/platform/actors/development/actor_definition/dataset_schema/multiple_datasets.md
@@ -0,0 +1,108 @@
+---
+title: Multiple datasets
+description: Learn how to use multiple datasets within your Actors to organize and store different types of data separately.
+slug: /actors/development/actor-definition/dataset-schema/multiple-datasets
+---
+
+**Specify datasets with different structure.**
+
+---
+
+Some Actors produce data with different structure. In some cases, it's convenient to store the data in separate datasets, instead of pushing all data to the default one. Multiple datasets allow to specify those datasets upfront and enforce validation rules.
+
+New datasets are created when the run starts, and follow it's data-retention.
+
+
+## Defining multiple datasets
+
+The multiple datasets may defined in Actor schema using `datasets` object:
+
+```json title=".actor/actor.json"
+{
+    "actorSpecification": 1,
+    "name": "this-is-e-commerce-scraper",
+    "title": "E-Commerce Scraper",
+    "version": "1.0.0",
+    "storages": {
+        "datasets": {
+            "default": "./products_dataset_schema.json",
+            "categories": "./categories_dataset_schema.json"
+        }
+    }
+}
+```
+Schemas of individual datasets can be provided as a file reference or inlined.
+
+The keys of the `datasets` objects are **aliases**, which can be used to refer to the specific datasets. In the example above, we have two datasets, aliased as `default` and `categories`.
+
+:::info
+
+Alias and **name** are not the same thing. Named datasets have specific behavior in Apify platform (eg, the automatic data retention policy does not apply to them). Aliased datasets follow the data retention of their respective run. Aliases stay local to the run they belong to.
+
+:::
+
+The `datasets` object has to contain the `default` alias.
+
+The `datasets` and `dataset` objects are mutually exclusive, the schema can only contain one.
+
+## Accessing the datasets in Actor code
+
+Mapping of aliases to the IDs is passed to the Actor in JSON encoded `ACTOR_STORAGES_JSON` environment variable.
+
+```javascript
+const storageIds = JSON.parse(process.env.ACTOR_STORAGES_JSON)
+const defaultDataset = await Actor.openDataset();
+// For the default dataset, it's also possible to use the following syntax:
+// const defaultDataset = await Actor.openDataset(storageIds.datasets.default);
+const categoriesDataset = await Actor.openDataset(storageIds.datasets.categories);
+
+```
+
+```sh
+echo $ACTOR_STORAGES_JSON | jq '.datasets.categories'
+```
+
+Support for JS and Python SDKs is incoming, the expected syntax is following:
+
+```javascript
+const categoriesDataset = await Actor.openDataset({alias: 'categories'});
+```
+
+```python
+categories_dataset = await Actor.open_dataset(alias='categories')
+```
+
+## Showing data to users
+
+### Run Storages tab
+
+The Storage tab of Actor run view is displaying all the dataset defined by Actor and datasets that were used by the run (up to some limit).
+
+This makes the data accessible, but not very user-friendly. To make the datasets more accessible to users, use output schema.
+
+### Output schema
+
+Actors with output schema can refer to the datasets through variables using aliases:
+
+```json
+{
+    "actorOutputSchemaVersion": 1,
+    "title": "Output schema",
+    "properties": {
+        "products": {
+            "type": "string",
+            "title": "Products",
+            "template": "{{storages.datasets.default.apiUrl}}/items"
+        },
+        "categories": {
+            "type": "string",
+            "title": "Categories",
+            "template": "{{storages.datasets.categories.apiUrl}}/items"
+        }
+    }
+}
+```
+
+## Billing implications
+
+The `apify-default-dataset-item` synthetic event is only charged for items in dataset aliased as `default`. Charging for items in other datasets needs to be implemented in the Actor code.
diff --git a/sources/platform/actors/development/programming_interface/environment_variables.md b/sources/platform/actors/development/programming_interface/environment_variables.md
index b295748a64..92df9b7955 100644
--- a/sources/platform/actors/development/programming_interface/environment_variables.md
+++ b/sources/platform/actors/development/programming_interface/environment_variables.md
@@ -44,6 +44,7 @@ Here's a table of key system environment variables:
 | `ACTOR_BUILD_TAGS` | A comma-separated list of tags of the Actor build used in the run. Note that this environment variable is assigned at the time of start of the Actor and doesn't change over time, even if the assigned build tags change. |
 | `ACTOR_TASK_ID` | ID of the Actor task. Empty if Actor is run outside of any task, e.g. directly using the API. |
 | `ACTOR_EVENTS_WEBSOCKET_URL` | Websocket URL where Actor may listen for [events](/platform/actors/development/programming-interface/system-events) from Actor platform. |
+| `ACTOR_STORAGES_JSON` | JSON encoded unique identifiers of storages associated with the current Actor run |
 | `ACTOR_DEFAULT_DATASET_ID` | Unique identifier for the default dataset associated with the current Actor run. |
 | `ACTOR_DEFAULT_KEY_VALUE_STORE_ID` | Unique identifier for the default key-value store associated with the current Actor run. |
 | `ACTOR_DEFAULT_REQUEST_QUEUE_ID` | Unique identifier for the default request queue associated with the current Actor run. |