diff --git a/docs/assets/operation_center/FAQ/Assets_timeline.png b/docs/assets/operation_center/FAQ/Assets_timeline.png
new file mode 100644
index 0000000000..bf8af2ca26
Binary files /dev/null and b/docs/assets/operation_center/FAQ/Assets_timeline.png differ
diff --git a/docs/xdr/FAQ/Assets_qa.md b/docs/xdr/FAQ/Assets_qa.md
new file mode 100644
index 0000000000..0dfb0b82f3
--- /dev/null
+++ b/docs/xdr/FAQ/Assets_qa.md
@@ -0,0 +1,50 @@
+## How to get the source of a discovered asset ?
+
+In the Asset timeline, events that triggered an asset detection will be displayed.
+
+**Steps:** Go to assets page, click on an asset then click on `See trigger event`.
+![Assets_timeline](/assets/operation_center/FAQ/Assets_timeline.png){: style="max-width:80%"}
+
+The details of the event will be displayed in the events page.
+
+## Can a same asset be discovered by two different intakes ?
+
+Only `account`, `host` and `network` will be taken into account in asset detection.
+
+However, the information of the intake associated can be found by clicking on an event in the timeline.
+
+!!! note
+     For example, a source IP is a field that will be discovered as an atom extracted from an event.
+     This atom can be attached to one or several assets (seen in the Atoms tab).
+     Please consult [this documentation about atoms](https://docs.sekoia.io/xdr/features/collect/assets/#what-is-an-atom).
+
+## Is there any impact on the assets set as "Reviewed" ?
+
+There is no impact. However, it is useful in order to clearly identify and confirm the assets used.
+
+## Is there any mechanism that automatically delete an asset if no events have been triggered after a given period ?
+
+Asset management is crucial and it is important to manually monitor your assets frequently in order to have a clear view of their activities and validity.
+
+## Are there any assets duplicates ?
+
+It is possible to have asset duplicates originated from two different sources.
+
+For example: 
+
+1. The first asset discovered as **Marcel** is detected from an email.
+2. The second asset discovered as **Marcel (Paris)** is detected from another service account.
+
+Therefore, the same user will be displayed in the two assets.
+
+## Can assets be created manually and also discovered automatically ?
+
+It is possible to have assets created both manually and automatically. 
+
+We suggest to users to manage their assets and keep the ones that are relevant.
+
+## How are assets' duplicates managed ?
+
+Assets are being enriched and updated according to detection rules.
+
+Please find more information [here](https://docs.sekoia.io/xdr/features/collect/assets/#asset-discovery-rules).
diff --git a/docs/xdr/features/collect/assets.md b/docs/xdr/features/collect/assets.md
index 5d809d86aa..9b5828b9eb 100644
--- a/docs/xdr/features/collect/assets.md
+++ b/docs/xdr/features/collect/assets.md
@@ -170,3 +170,5 @@ This rule creates a new asset for every unseen `host.name`. It attaches the `ipv
 ### Discover unique Accounts
 
 This rule creates a new asset for every unseen `user.name`. It attaches the `user.email` and `user.id` event field values as detection property of the newly created asset.
+
+Questions? Please read our [FAQ](../../FAQ/Assets_qa.md).
diff --git a/mkdocs.yml b/mkdocs.yml
index 5a4bc1e052..775f931993 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -353,6 +353,7 @@ nav:
       - Events QA: xdr/FAQ/Events_qa.md
       - Facing issues with logs collection: xdr/FAQ/Log_collection_Troubleshoot.md
     - Rules: xdr/FAQ/Rules_qa.md
+    - Assets: xdr/FAQ/Assets_qa.md
     - Sekoia.io Endpoint agent: xdr/FAQ/SEKOIA_Endpoint_Agent.md
     - Datetime representation: xdr/FAQ/datetime.md
   - Develop: