How to set up an External developer to edit an existing powerapp

Like (1) Share

Report

Posted on 2 Sep 2021 15:36:56 by Elia

Hi all,

We are thinking on hiring an external developer to modify one of our PowerApps, to create integration with Flow, create the lists in Sharepoint that will connect with the app, etc..

We are not tech savies, nor very experience with managing Sharepoint, and we are concerned of putting in risk our sharepoint by giving too much access and permissions to the external developer.

Additionally, I assume he will require an organization email to log into the organization environment?

I am very lost here. Any help will be very much appreciated. How is this normally done?

Thanks!

All responses (2)

Answers (0)

BCLS776 8,988 Super User 2025 Season 1 on 02 Sep 2021 at 18:56:34

Like (2)

Report
Re: How to set up an External developer to edit an existing powerapp

In addition to the technical options that @mgrachii mentions, don't forget some security and commercial practices that can help:
Security background checks
Non-disclosure & non-competition agreements
Clear definition of ownership of intellectual property resulting from the work
Proper oversight
You don't need to know everything about the technical aspects of the work they are doing, but you need to able to ask enough questions to ensure it is being done properly.

Hope that helps,
Bryan
mgrachii 206 on 02 Sep 2021 at 18:31:07

Like (1)

Report

Re: How to set up an External developer to edit an existing powerapp

Hi Elia,
There are a couple of options, does the developer have an office 365 susbcription on their own?

They can develop the App, the flows and create the list on their end and then just import all of that into your tenant. Depending in the complexity of the development this may take a bit of time.

The other option is creating a Dev SharePoint site that will have only the lists that relate to development and then they develop everything using this dev site. Once all is done you can have a session to share screen and change the data source to the actual SharePoint site. This can be a bit difficult sometimes, I've done it with some clients I've worked with and sometimes it takes some time to complete and test everything, but at the end it works.

The other option is that you can share just the list to the developer and not the whole Site.

And you are right, if you want them to develop the flows and apps inside your tenant then it's best if you create an account for them, but more of a "generic" account for automations, that you can use for other things that you will develop in the future and you can use the licenses for different things.

Hope this helps a bit, if there is something I can clarify further, let me know.