diff --git a/TeSS_docs/_toc.yml b/TeSS_docs/_toc.yml
index e325a94..f29de8d 100644
--- a/TeSS_docs/_toc.yml
+++ b/TeSS_docs/_toc.yml
@@ -46,6 +46,7 @@ parts:
       - file: content/collections
       - file: content/workflows
       - file: content/learning-paths
+    - file: content/curation
   - caption: Developers
     chapters:
     - file: developers/code-data
diff --git a/TeSS_docs/content/curation.md b/TeSS_docs/content/curation.md
new file mode 100644
index 0000000..0562fd8
--- /dev/null
+++ b/TeSS_docs/content/curation.md
@@ -0,0 +1,33 @@
+# Content Curation
+
+## Prerequisites
+
+Ask your TeSS administrator if the `material_under_admin_approval` or `event_under_admin_approval` features are enabled.
+
+To see if your TeSS instance is supporting this feature, if you [manually register](./manual) a training material or event, the message *'This material/event will need to be approved by an administrator before being public'* is shown on the top of the form like the following screenshot:
+
+![Information about a material that needs curation](../images/content/material_alert_new.png)
+
+## How are training resources curated in TeSS?
+
+When [prerequisites](#prerequisites) are met, any added training material or event (either [manually](./manual) or [automatically](./auto)) will be **by default** subject to verification and thus, not publicly shown in your TeSS instance. Your resource will be marked with an 'Approval status' set to 'Requested', as shown below:
+
+![A material with requested view](../images/content/material_requested_view.png)
+
+Once a resource is registered or ingested, the curation/verification can be made by 'administrators','curators' or 'space administrators', which are specific TeSS user roles (generally speaking, *curators*). Space administrators can only see resources from their space.
+
+*Curators* can then have access to a dashboard to review the newly registered resources by accessing the `your-tess-instance-website.org/curate/resources` page, which can be also found by clicking on the dropdown menu of the user profile on the top-right of the page once logged in > 'Curate resources'.
+
+In the dashboard, *curators* can filter resources by Type (material, event), User, [Provider](../accounts/provider), [Space](../spaces/intro-spaces), and Approval Status. 'Approve All Filtered' and 'Reject All Filtered' buttons can be found at the bottom of the page to allow approval or rejection of the filtered resources. For example, if you have a new Content Provider adding thousands of already curated materials, you can filter the list by their name and approve them all in a few clicks only.
+
+![Curation dashboard](../images/content/curate_resources.png)
+
+## How to revoke the approval status of a resource?
+
+A *curator* may have misclicked the 'Approve' button, they may come back to their decision by editing the resource manually, scroll down, and change the 'Approval status' field to 'Requested'.
+
+---
+
+## Developer source
+
+See pull request [#1382](https://github.com/ElixirTeSS/TeSS/pull/1382).
diff --git a/TeSS_docs/images/content/curate_resources.png b/TeSS_docs/images/content/curate_resources.png
new file mode 100644
index 0000000..e8b4293
Binary files /dev/null and b/TeSS_docs/images/content/curate_resources.png differ
diff --git a/TeSS_docs/images/content/material_alert_new.png b/TeSS_docs/images/content/material_alert_new.png
new file mode 100644
index 0000000..c2645e0
Binary files /dev/null and b/TeSS_docs/images/content/material_alert_new.png differ
diff --git a/TeSS_docs/images/content/material_requested_view.png b/TeSS_docs/images/content/material_requested_view.png
new file mode 100644
index 0000000..990d451
Binary files /dev/null and b/TeSS_docs/images/content/material_requested_view.png differ