cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Advocate II
Advocate II

Access to the environment legacy-7ee232c1-3044-4917-af45-154a5be230a9 is denied - when creating flow

We have 2 environments. One is in the new Common Data Service 2.0, and my users can't create Flows. They can edit the ones I have created, but can't save any new ones. Seems some permission isn't set - but I can't find anything else to give them. They currently have all permissions in the environment. Any ideas?

 

3 REPLIES 3
Highlighted
Community Support
Community Support

Re: Access to the environment legacy-7ee232c1-3044-4917-af45-154a5be230a9 is denied - when creating

Hi @barlowse,

 

What environment role have granted to users?

Have you shared the flows with them?

Please check the following doc for a reference:

https://docs.microsoft.com/en-us/flow/environments-overview-admin

 

Best regards,

Mabel

Community Support Team _ Mabel Mao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted
Administrator
Administrator

Re: Access to the environment legacy-7ee232c1-3044-4917-af45-154a5be230a9 is denied - when creating

Hello, @barlowse!

Thank you for posting on the Flow Community Forum! Have you had an opportunity to apply @v-yamao-msft‘s recommendation to adapt your Flow? If yes, and you find that solution to be satisfactory, please go ahead and click “Accept as Solution” so that this thread will be marked for other users to easily identify!

Thank you for being an active member of the Flow Community!

-Gabriel
Flow Community Manager

-Gabriel
Microsoft Power Automate Community Manager
Are YOU a member of your local Power Automate User Group?
Fill out This Form to claim your Community User Group Member Badge!
Highlighted
Advocate II
Advocate II

Re: Access to the environment legacy-7ee232c1-3044-4917-af45-154a5be230a9 is denied - when creating

I had shared the Flows with my colleagues. What turned out to be the issue was a permission setting. I created a new security role by copying the default Environment Maker - and setting the Business Process Flow options to all on. Then assigned this role to my engineers. 

 

Helpful resources

Announcements
firstImage

Now Live: Power Virtual Agents Community!

We are excited to announce the launch of Power Virtual Agents Community. Check it out now!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

Top Solution Authors
Top Kudoed Authors
Users online (9,799)