How does solution artifacts permission/visibility works

(1) Share

Report

Posted on by Rohit4044041

286

Hello

I have been trying to find answer to this for sometime now. Please see below two screens logged in by two different users. First user is the one who created solution and then artifacts such as PowerApps , Automate, Variables, Service connection etc.

User1 then made user2 owner of PowerApps and automates. All good.

My research said there is no permissions defined at solutions level. However, as we see when user2 logs in and opens solution there is no environment variable listed (though it can be seen by user 1)

Question 1: how can environment variable be made available to other users to consume them (within same solution) . Currently user2 cannot see the variables even when user2 is owner on PowerApps and tries to add the datasource from exisiting env varaible.

question 2: When does connection reference becomes available to user2. As we see there are lesser connection references . initially there were zero. Once user 2 started editing automate and PowerApps, connection reference started appearing in solutions screen . (still few references are missing). These connection reference were created by User1.

Would really appreciate your thoughts.

Categories:

Building Power Apps

IMG-20240812-WA00...

I have the same question (0)

All responses (4)

Answers (1)

Suggested answer

Michael E. Gernaey 53,488 Super User 2025 Season 2 on at

Like (1)

Report

Hi

Something else is going on. But I cannot verify they are in the same solution

1) I cannot see the environment

2) when is the last time it was published

3) and this is important.

If the person on the left has it opened AND the person on the right verify its truly the same app, opened at the same time.

As long as the person on the right has Customizer etc etc it should work.

Do a test if able

Set the person on the Right, to SysAdmin, Basic User.

have them reload the project.. does everything show up? If not then its a different issue than permissions.

Was this reply helpful? Yes No
Rohit4044041 286 on at

Like (1)

Report

@Flmike Thank you for your response.

1. Yes, its same environment

2. Yes, its same solution.

3. Yes, its the same Powerapp

Powerapp was published latest last week.

I agree, its not an issue with permission. There is some other mechanism to make the variable and connection reference available to everyone having access to solution(?)/ Powerapp

Unfortunately its prod environment so I cant get sys admin role for these accounts.

Both users have got same environment level aceess role and license

I have another M365 tenant. Let me do some experiments there.

Was this reply helpful? Yes No
Verified answer

Rohit4044041 286 on at

Like (1)

Report

Turned out that the user who was not seeing Env variable was not having "Basic user" role , though they had "System customizer" role. Once Basic user was assigned, Env variables started appearing.

Was this reply helpful? Yes No
Suggested answer

Michael E. Gernaey 53,488 Super User 2025 Season 2 on at

Like (1)

Report

So it was what I suggested initially in my response, which would be the answer.

Was this reply helpful? Yes No