diff --git a/docs/en/tutorials/microservice/part-03.md b/docs/en/tutorials/microservice/part-03.md
index 31491ef004..688b7f0771 100644
--- a/docs/en/tutorials/microservice/part-03.md
+++ b/docs/en/tutorials/microservice/part-03.md
@@ -117,6 +117,8 @@ After the application is started, you can right-click and [Browse](../../studio/
 
 > If you can't see the *Products* menu item, you need to grant the `CatalogService` *Product* permission to the *admin* role. You can do this by navigating to *Identity Management* -> *Roles* and editing the *admin* role. Alternatively, you can restart the *CloudCrm.AdministrationService* application to automatically seed all permissions for the *admin* role.
 
+> When we create `Catalog` microservice, the `CatalogService` API scope is also created automatically if the "Enable integration" option is selected. You can verify the new scope in the `CloudCrm.IdentityService` module (.NET solution), in the `CloudCrm.IdentityService` project within the `OpenIddictDataSeeder` class's `CreateApiScopesAsync` method. If you are already logged in to the application, you may need to log out and log back in to reauthorize with the newly created API scope.
+
 You can open the Sql Server Management Studio to see the created tables and data:
 
 ![sql-server-management-studio-products](images/sql-server-management-studio-products.png)