Insufficient permissions to view or create flows in the environment in versions 2.55 and 2.56

(4) Share

Report

Posted on by John_Mavridis Microsoft Employee

In versions 2.55 and 2.56 of Power Automate for desktop, if a message appears in your console, indicating that you don't have sufficient permissions to view or create flows in an environment, two permissions might be missing from your security role:

Organization access must be provided to the Read privilege of your respective custom security role on the Tag table, and
User access must be provided to the Read privilege on the Tagged Process table respectively in Dataverse.

Please contact your administrator to provide you the above permissions through the Power Platform Admin Center.

Categories:

Power Automate Desktop

I have the same question (2)

All responses (10)

Answers (0)

WM-08050115-0 4 on at

Like (1)

Report

Hi,

How can I grant these permissions, I am admin on PowerPlatform

Was this reply helpful? Yes No
John_Mavridis Microsoft Employee on at

Like (1)

Report

As an admin, you can navigate to:
Environments | Power Platform admin center

Select the environment where the error occurs, then navigate to:
Settings > Users + Permissions > Security roles

Select the security role that needs to be edited, then proceed with the steps above.

Was this reply helpful? Yes No
sripriyan 11 on at

Like (1)

Report

This message appears to all our users in the default environment where the above security roles are defined as required (as part of Env. maker role). Users are able to create and edit flows. But still see the warning. What should be done? Thank you!

Was this reply helpful? Yes No
John_Mavridis Microsoft Employee on at

Like (2)

Report

The banner with the warning message is displayed to all users working with versions 2.55 and 2.56 for awareness purposes. If you don't face any issues with your flows, you're not affected by this and can ignore the warning.

Was this reply helpful? Yes No
flali 6 on at

Like (1)

Report

Does this issue mean that in Ver.2.55 and later, there are users who are unable to create, save, or run flows?
If this occurs, will the problem be resolved by granting the user Environment Maker permissions?
Or will users who are experiencing this issue be unable to create, save, or run flows until the problem is fixed?

Was this reply helpful? Yes No
John_Mavridis Microsoft Employee on at

Like (1)

Report

Only users with custom roles might be affected by this issue in versions 2.55 and 2.56, with the list of desktop flows in the console not being visible to them.

The steps in the post explain how you can grant the proper permissions to the said custom role, in order to mitigate the issue. Indeed, these permissions are already granted by default to the Environment Maker role, so alternatively, granting this role to affected users will also resolve the problem.

Was this reply helpful? Yes No
Suggested answer

Walid Moheyeldin 8 on at

Like (1)

Report

Your administrator needs to adjust your custom security role by Grant Read privilege on the "Tag" table with Organization level access, and Grant Read privilege on the "Tagged Process" table with User level access.
These permissions can be configured via the Power Platform Admin Center by editing the appropriate security role assigned to your user.

Be sure to reach out to your environment admin to update the role accordingly. Once these permissions are in place, the issue should be resolved.

Was this reply helpful? Yes No
CU12050630-0 4 on at

Like (0)

Report

Power Platform 관리 센터를 통해 위의 권한을 제공하려면 관리자에게 문의하십시오.

관리자는 회사 관리자를 이야기 하는건지, 권한 받기위한 작업이 무엇인지 궁금합니다.

위 내용은 두리뭉실하고 난해하여 어떤 활동이 필요한지 모르겠습니다.

Was this reply helpful? Yes No
NijasWinum 6 on at

Like (0)

Report

Insufficient permissions to view or create flows in the environment in versions 2.55 and 2.56

im still facing issues after i have made a custom security role with the correct permissions, and have assigned it to the correct user, and put the env maker role on the user aswell

any suggestions?

regards Nijas

Was this reply helpful? Yes No
John_Mavridis Microsoft Employee on at

Like (0)

Report

From version 2.57 and on, the behavior on tag-related permissions has been adjusted so that they become optional, and so that users with custom roles are still able to view their flows even without these permissions in place.

Was this reply helpful? Yes No