Merge pull request #11005 from MicrosoftDocs/matp-uuf-399801

Adding link per UUF 399801

Author: Mattp123

powerapps-docs/maker/model-driven-apps/privileges-required-customization.md

@@ -2,7 +2,7 @@
 title: "Privileges required for customizing apps build on Dataverse | MicrosoftDocs"
 description: Understand the privileges required to apps built on Dataverse
 ms.custom: ""
-ms.date: 01/21/2025
+ms.date: 04/14/2025
 ms.reviewer: "matp"
 ms.topic: "conceptual"
 ms.subservice: mda-maker
@@ -29,7 +29,11 @@ Anyone who customizes have at least the system customizer security role associat
 |Has full permission to customize the system|Has full permission to customize the system|  
 |Can view all data in the system|Can view all custom tables in the system but only view rows (records) in the account, contact, and activity tables that they create|  
 
-The difference between the system administrator and system customizer security roles is that a system administrator has read privileges on most records in the system and can see everything. Assign the system customizer role to someone who needs to perform customization tasks and has access to all the custom tables but only has access to the account, contact, and activity rows (records) they create. However, testing is an important part of customizing the system. If system customizers can’t see any data, they need to create rows (records) to test their customizations. By default, system customizers have full access to custom tables. If you want to have the same limitations that exist for system tables, you need to adjust the system customizer security role so that the access level is **User** rather than **Organization** for custom tables.  
+The difference between the system administrator and system customizer security roles is that a system administrator has read privileges on most records in the system and can see everything. Assign the system customizer role to someone who needs to perform customization tasks and has access to all the custom tables but only has access to the account, contact, and activity rows (records) they create. However, testing is an important part of customizing the system. If system customizers can’t see any data, they need to create rows (records) to test their customizations. By default, system customizers have full access to custom tables. If you want to have the same limitations that exist for system tables, you need to adjust the system customizer security role so that the access level is **User** rather than **Organization** for custom tables. 
+
+### Add a security role to a user
+
+For information about how a Power Platform admin can add a security role to a user, go to [Add users to a security role](/power-platform/admin/security-roles-privileges?tabs=new#add-users-to-a-security-role)
 
 ## Delegate customization tasks