diff --git a/docs/kv-service/use-cases.md b/docs/kv-service/use-cases.md
new file mode 100644
index 0000000..cbb1278
--- /dev/null
+++ b/docs/kv-service/use-cases.md
@@ -0,0 +1,19 @@
+---
+id: kv-use-cases
+title: Use Cases
+sidebar_position: 7
+---
+
+KVService works as a general key-value store. It can be used in many different scenarios. This page lists some of the use cases.
+
+## KVService as a persistence storage
+
+You can use KVService to store the data that needs cross-session persistence.
+
+For example, you can store the user's avatar, nick name, bio, show/hide status of NFT list, or order of these contents, under your web3 app's scenarios.
+
+Using KVservices gives you some benefits:
+
+- The change made by user is verifiable by other user / applications, aka platform-independent. No one (except the user himself) can change the data without a valid signature.
+- The data is stored in a decentralized way, no matter where this data is actually stored. User always has a choice to move their data to other (or self-hosted) platforms.
+  > The actual "migration" function is still under development.
diff --git a/sidebars.js b/sidebars.js
index bff15ac..b97e309 100644
--- a/sidebars.js
+++ b/sidebars.js
@@ -25,7 +25,7 @@ module.exports = {
         type: 'category',
         label: 'KVService',
         collapsed: true,
-        items: ['kv-service/kv-intro']
+        items: ['kv-service/kv-intro', 'kv-service/kv-faq', 'kv-service/kv-use-cases', 'kv-service/kv-api']
       }, {
         type: 'category',
         label: 'RelationService',