How to Create a Security Role From a Copy
In part 5 of her series on Dataverse security, UG Expert Kylie Kiser explains how to create a security role.
This episode is sponsored by the AI Copilot Summit NA, taking place March 17-19, 2025 in San Diego, California.
Key Takeaways
- Copy vs. out-of-the-box: Kylie recommends creating a security role as a copy, in most cases, to add it to a solution. This is because the out-of-the-box roles have a lot of permissions that you need. Microsoft could change the out-of-the-box security roles at any time so those updates would override your changes.
- Making a copy: Returning to the Power Platform Admin Center, Kylie navigates to the environments page, selects “security roles,” and creates a test copy of the salesperson security role, which she previously worked with.
- Dangerous permissions: When editing a copy for a security role, remember to remove “dangerous permissions” that you don’t want users to have access to. For instance, you likely don’t want users deleting accounts, sharing records, or exporting data.
- Modern security role editor: Going into this feature, its default setting only shows the assigned tables. Viewing the core ones, Kylie notes reviews the capabilities of the test user. She continues adjusting permissions and editing columns then saves her adjustments to ensure they only have the permissions she wants them to have.
- Applying to a solution: Return to the maker portal and ensure you’re in the correct environment to create a solution. Select any publisher, then add existing, and add the security role.
AI Copilot Summit NA is an AI-first event to define the opportunities, impact, and outcomes possible with Microsoft Copilot for mid-market & enterprise companies. Register now to attend AI Copilot Summit in San Diego, CA from March 17-19, 2025.
