Answered

How to See a List of All Power Apps - in all Environments - when App is shared to a user, but they don't have Environment Maker on the Environment

(0) Share

Report

Posted on by DS2

293

We have a non-Dataverse production environment, where users are not given Environment Maker permission (we don't want them creating their own apps here), but have Power Apps shared to them that exist on this environment. If users don't have Environment Maker, they don't see that Environment when they go to "Power Apps" and therefore don't see the list of Apps under that Environment

As not Makers, can't see environment with Apps that have been shared with them in that environment:
Environment List.jpg

How can users see all the Apps that have been shared with them?
Is there a way to generate a list for them?
I see that under Office.com > Power Apps > Apps that there is an "All Apps" Link but am unsure exactly how the results are generated when that Link is clicked:
All Apps.jpg

Users are not happy having to remember all the links to the Apps that they have access to. This is also the case in Dataverse environments where they may have only "Basic User" which does not allow access to the environment to create things in it. They can't see their list of Apps.

Is there a solution where in one place users can see all the Apps to which they have access?

Categories:

Building Power Apps

I have the same question (0)

All responses (8)

Answers (1)

v-xiaochen-msft on at

Like (0)

Report

Hi @DS2 ,

Please copy the url of the environment and the user can log in it and see apps to which they have access.

Best Regards,

Wearsky

Was this reply helpful? Yes No
DS2 293 on at

Like (0)

Report

@v-xiaochen-msft - This is for a user, though and not a environment maker. Unless you have rights to create resources in an environment, users can't see the environment to find their apps in it.
We have users that have had a Power App shared to them in an environment (non-Dataverse). They do not have Environment Maker to see the environment - so logging into the environment will not work for them.
How can users see all the Apps that are shared with them when they don't have permissions to the environments (environment maker)? Thanks!

Was this reply helpful? Yes No
Verified answer

v-xiaochen-msft on at

Like (1)

Report

Hi @DS2 ,

If you are the env maker, you can switch the environment from here.

If you are a basic user, usually you cannot see the environment from here.

However, it does not mean that the basic user cannot access the environment.

Actually, basic users should be able to access the environment directly via URL.

The user who has Env maker role can access the environment and copy the url and send the url to the basic users.

Then the basic users should be access the environment via the url rather than using Environment selector in the upper right corner.

Hope it makes sense.

Best Regards,

Wearsky

Was this reply helpful? Yes No
DS2 293 on at

Like (0)

Report

Oh, that is good to know, thank you, @v-xiaochen-msft - how do you get the environment URL for a non-Dataverse environment, do you open it up in Power Apps through the Environment selector?
Thanks!

Was this reply helpful? Yes No
v-xiaochen-msft on at

Like (1)

Report

Hi @DS2 ,

I don't have a non-dataverse environment, but I think it's the same.

Best Regards,

Wearsky

Was this reply helpful? Yes No
DS2 293 on at

Like (0)

Report

Hi @v-xiaochen-msft - thanks, but the fix you put forward into giving an end user the environment URL that they don't have Environment Maker on doesn't work, unfortunately. This is a non-Dataverse environment and by accessing the URL, they get a "don't have access to permission "CanEdit"" error - which makes sense, as they don't have access to Environment Maker.

Was this reply helpful? Yes No
v-xiaochen-msft on at

Like (1)

Report

Hi @DS2 ,

It appears that environments with databases behave differently than non-database environments.

I just created a non-database environment and reproduced the issue, and it reported the same error.

One method is for the admin to create a blank app in the non-database environment and share it with the user as co-owner. Then please wait a few minutes for the user to access the environment. The disadvantage of this method is that he can edit the blank app.

Another way is to find all the apps that the user has access to in Teams.

The disadvantage is that it shows the app for all environments, and the app will be opened in Teams.

The third method is to install the powerapps for windows app.

It can filter the apps for the non-database environment.

https://learn.microsoft.com/en-us/power-apps/mobile/windows-app-install

Hope it helps.

Best Regards,

Wearsky

Was this reply helpful? Yes No
DS2 293 on at

Like (0)

Report

Thanks @v-xiaochen-msft - I wish Microsoft would stop tying the ability to see environments through the environment selector to the Environment Maker role - if a user has a Power App shared with them in an environment, they should be able to see that environment.
For us, we don't use the apps in Teams, many users use their computers (so not mobile) and creating a Power App to share co-ownership with would be quite clunky and would require us to keep a list of people with apps shared to them, with someone maintaining that.
I sure appreciate your looking into this for us, though - we are grateful and thank you.

Was this reply helpful? Yes No