Feedback comments

Author: Karuna-Mendix

content/en/docs/howto/monitoring-troubleshooting/populate-user-type.md

@@ -32,16 +32,28 @@ This approach is for end-users who are already set up in your app. For new end-u
 
 Outlined below is an example of a module that can be used to update UserType attribute. You will need to adapt the module logic for classifying your own internal and external end-users. 
 
+### Assigning UserType for Existing Users of IAM Modules
+
+The simplest method to set the user type is by using the IAM modules, which require only configuration without the need to develop a microflow. Alternatively, you can build a custom microflow as described in the [Populating UserType for Existing Users of an App](#using-microflow) section below.
+
+When connecting your app with an IdP, set up the user type through the capabilities of the OIDC SSO, SCIM, or SAML module. The user type is now configured in the User Provisioning, which is integrated into the OIDC SSO, SCIM, and SAML modules. This means you can directly configure end-users of your application as `internal` or `external` in the **User Provisioning** tab of your app. Based on this configuration, users are updated each time they log in. These modules allow you to set the user type per IdP as the source of your end-users, assuming that separate IdPs are used for `internal` and `external` users.
+
+For more information, refer to the User Provisioning section of the following modules:
+
+* [OIDC SSO](/appstore/modules/oidc/#custom-provisioning-rt)
+* [SAML](/appstore/modules/saml/#custom-provisioning-rt)
+* [SCIM](/appstore/modules/scim/#user-provisioning)
+
 ### Domain model
 
-In the example below, our aim is to update UserType attribute of UserReportInfo entity. However, the entity `UserReportInfo` is protected in the System module and has no access rules. As a result, it cannot be exposed directly in the UI pages. 
+In the example below, our aim is to update UserType attribute of `UserReportInfo` entity. However, the entity `UserReportInfo` is protected in the System module and has no access rules. As a result, it cannot be exposed directly in the UI pages. 
 Therefore, the approach we take is to create a new non-persistable entity, `UserTypeReport`, which we will populate based on the values of `UserReportInfo` to show in the UI.
 
 {{< figure src="/attachments/howto/monitoring-troubleshooting/populate-user-type/usertypereport.png" class="no-border" >}}
 
 {{< figure src="/attachments/howto/monitoring-troubleshooting/populate-user-type/usertypereport-properties.png" class="no-border" >}}
 
-### Populating **UserType** for Existing Users of an App
+### Populating **UserType** for Existing Users of an App {#using-microflow}
 
 1. Create a microflow `User_RetrieveOrCreateUserReportInfo` which will ensure that a `UserReportInfo` object exists for a given `User`.
 
@@ -75,9 +87,3 @@ Therefore, the approach we take is to create a new non-persistable entity, `User
     {{< figure src="/attachments/howto/monitoring-troubleshooting/populate-user-type/user-type-report.png" class="no-border" >}}
 
 7. The report can be exported into an Excel file.
-
-### Assigning UserType for Existing Users of an IAM Modules
-
-When connecting your app with an IdP, the easiest way to set up the user type is through the capabilities of the OIDC SSO, SCIM, or SAML module. The user type is now configured in the User Commons, which is integrated into the OIDC SSO, SCIM, and SAML modules. This means you can directly configure end-users of your application as `internal` or `external` in the **User Provisioning** tab of your app. Based on this configuration, users are updated each time they log in.
-
-For more information, see the User Provisioning section of the [OIDC SSO](/appstore/modules/oidc/#custom-provisioning-rt), [SAML](/appstore/modules/saml/#custom-provisioning-rt) or [SCIM](/appstore/modules/scim/#user-provisioning) modules.