cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

System Customizer Security role concern and solutions

After researching the error "Publishing all customizations failed."  when a user tried to click the "Publish" option when exporting their solution, I found that giving them "System Customizer" role resolved it.. 

The issue is, that security role is too powerful for regular users.
I have a test account that I gave that security role to and found that not only could it not publish solutions without the errors. But it could also edit existing solutions in the environment and make changes to unmanaged items.

 

Any ideas how I could give regular users rights to click the "Publish" option when exporting their solutions without generating the error, while also preventing them from editing existing solutions?

1 ACCEPTED SOLUTION

Accepted Solutions

I tested this based on the error messages that "Publish All" gives when using Environment Maker role. In my simple demo environment with a very basic solution containing one custom table and a couple of apps, the write privileges that I had to add were these 4: entity, field, relationship, view.

jukkaniiranen_0-1665423892779.png


Will this work for everyone and everywhere? Not so sure. Obviously this isn't quite the way Microsoft has intended the security model to work. As Chris mentioned earlier, there isn't an ownership concept on the Dataverse metadata level - meaning it's all organization owned and not user owned.

View solution in original post

11 REPLIES 11
ChrisPiasecki
Most Valuable Professional
Most Valuable Professional

Hi @ShaneMeisnerTH,

 

You can't selectively control whose unmanaged components solutions one can edit because there is no ownership assigned to most metadata (e.g. Tables).

 

The recommended approach is to have a separate development environment for customizing the specific solution(s) with only granting access to the makers who should be working on that solution.

 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.
Chris

 @ChrisPiasecki  .. Thanks for replying.. Through testing we did find that those with "Environment maker" security role can only see and edit their own solutions and they can export and import into different environments with that same role.

The issue is if, during exporting, they click the Publish button, it generates an error that they don't have the right permissions. 

Trying to find the appropriate setting that we could create a Custom security role that would give all the rights of Environment Maker, and enough of the System customizer role to publish, without the ability to edit other Solutions.

Hi @ShaneMeisnerTH,

 

What is the exact error you are seeing? Note that Environment Maker will be able to modify their own apps, flows, connections, and gateways, and share these resources.

 

Environment makers do not have privileges to create/modify Dataverse specific components such as tables, views, etc.

 

Does your solution contain any Dataverse specific components like a table? If so, you'll need to remove those components from your solution, or you'll need the system Customizer role.

 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.
Chris

The error they get is :

Publishing all customizations failed. SecLib::CheckPrivilege failed. User: , PrivilegeName: prvWriteEntity, PrivilegeId: , Required Depth: Basic, BusinessUnitId: , MetadataCache Privileges Count: 4126, User Privileges Count: 1133

We've tested just creating a flow in a new solution and exporting that Solution and get the same error when they click the "Publish" Icon:

ShaneMeisnerTH_0-1665420691462.png

As I mentioned, all results I found to resolve that error were to grant them "System Customizer" or "System Administrator" Security roles, both have way too much power for "Citizen Developers" ..

This is why I think a Customized Security role would work..
If I could just figure out what setting would allow them to Publish, without the ability to Edit existing Solutions that they didn't create.. 

I tested this based on the error messages that "Publish All" gives when using Environment Maker role. In my simple demo environment with a very basic solution containing one custom table and a couple of apps, the write privileges that I had to add were these 4: entity, field, relationship, view.

jukkaniiranen_0-1665423892779.png


Will this work for everyone and everywhere? Not so sure. Obviously this isn't quite the way Microsoft has intended the security model to work. As Chris mentioned earlier, there isn't an ownership concept on the Dataverse metadata level - meaning it's all organization owned and not user owned.

Hi @ShaneMeisnerTH,

 

The privilege lacking is write access to the Entity table, which is expected as I mentioned the Environment Maker doesn't have the privileges on those Dataverse metadata tables (table, view, field, relationship, etc.).

 

Creating a custom security role won't help you here because the permission scope can only be set to organization or none for those tables, which means you can either modify ALL of the metadata types or none at all. They would be able to modify the metadata created by others, which is not the granular access you're looking for. When you publish, you're effectively making changes (write) on the different components in the solution visible to everyone. 

 

Separate environments is the simplest way to prevent others from messing with other people's solutions, and is a common pattern.

 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.
Chris

@jukka-niiranen and @ChrisPiasecki 
Thanks for your help.
I made a copy of the Existing Environment Maker Security role and made the changes Jukka mentioned.

I then removed Environment Maker role from my test account and added the Customized role.

My test user now was able to create a new Solution, add a App/Flow and during export I was able to publish with no errors!

 

I tried to open other solutions in that environment that it didn't create and I get errors, like I did with just the Environment Maker role:

ShaneMeisnerTH_0-1665430823655.png

I'll to do some more testing, but for now it looks like what jukka posted works as we need.

Last thing I wanted to do was manually export all solutions 18,000+ user might create.. and Also didn't want to create hundreds of different environments just to make sure people didn't edit solutions they shouldn't.

Hi @ShaneMeisnerTH,

 

Just be aware that it doesn't stop someone from modifying those components directly outside the solution in the maker portal (via the Dataverse > Tables tab), or simply adding the components to their own solution, modifying them, and exporting them. Preventing the users from modying the solution container of others and exporting solution is a moot point when those other workarounds exist.

 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.
Chris

Thanks @ChrisPiasecki  .. Right now our concern is allowing Citizen Developers the ability to export their Solution form the Power App interface and importing it into the correct environment, without being able to edit solutions they didn't create.
I started n July to help them cleanup their Power Platform environment as they have 400+ Apps, and 1500+ Flows all in the Default Environment.
There are currently only 6 Premium Licensed users, with 4 of those being our team( 2 Admins and 2 Service Accounts). All the Citizen developers we've worked with either use SharePoint or SQL for data and we are not promoting Dataverse at this time due to the extra cost of licensing.
If in the future we decide to start using Dataverse more, then we will have to revisit this "fix". But for now this will do the trick.

Helpful resources

Announcements

Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Summer of Solutions | Week 4 Results | Winners will be posted on July 24th

We are excited to announce the Summer of Solutions Challenge!   This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions in the Forums to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersNumber of SolutionsSuper UsersNumber of Solutions @anandm08  23 @WarrenBelz  31 @DBO_DV  10 @Amik  19 AmínAA 6 @mmbr1606  12 @rzuber  4 @happyume  7 @Giraldoj  3@ANB 6 (tie)   @SpongYe  6 (tie)     Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Community MembersSolutionsSuper UsersSolutions @anandm08  10@WarrenBelz 25 @DBO_DV  6@mmbr1606 14 @AmínAA 4 @Amik  12 @royg  3 @ANB  10 @AllanDeCastro  2 @SunilPashikanti  5 @Michaelfp  2 @FLMike  5 @eduardo_izzo  2   Meekou 2   @rzuber  2   @Velegandla  2     @PowerPlatform-P  2   @Micaiah  2     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 3:Community MembersSolutionsSuper UsersSolutionsPower Apps anandm0861WarrenBelz86DBO_DV25Amik66Michaelfp13mmbr160647Giraldoj13FLMike31AmínAA13SpongYe27     Week 4 Results: Congratulations to the Week 4 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Week 4:Community MembersSolutionsSuper UsersSolutionsPower Apps DBO-DV21WarranBelz26Giraldoj7mmbr160618Muzammmil_0695067Amik14samfawzi_acml6FLMike12tzuber6ANB8   SunilPashikanti8

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to https://aka.ms/PPCommSupport.   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages