Restrict SharePoint Online List Access for a Power Apps Canvas App
Question details
Control access to SharePoint lists used by a canvas app while allowing employees to submit and view records through the app.

- Product
- Microsoft Power Apps and SharePoint Online
- Device & OS
- not provided
- Scenario
- A canvas app uses SharePoint lists for approximately 10,000 employees, who should use the app rather than browse the site or lists directly.
- Observed behavior
- The desired design allows authorized app operations without granting employees direct access to browse the underlying SharePoint lists.
Identify which records each user must create or view, and review the app's SharePoint connections and existing site, list, group, and sharing-link permissions. Test the design with representative employee accounts before deploying it broadly.
Use an authorized backend to mediate SharePoint access
Use this architecture when employees must not have direct access to the underlying SharePoint lists.
A canvas app that connects directly to SharePoint generally relies on the user's SharePoint permissions. Hiding the site or list does not prevent a user with permission from reaching data through a URL or API.
A mediated design uses a backend with its own authorized connection. The backend must authenticate callers and enforce which records and operations each caller is allowed to access.
Document the allowed submit and view operations for each user role, including whether users can see only their own records or records belonging to a team.
In your Power Platform environment, use an appropriately secured service or flow to perform the permitted SharePoint operations with a controlled connection. Configure it to validate caller identity, input, and record-level authorization on every request.
In Power Apps Studio, replace direct SharePoint data operations with calls to the protected backend. Remove direct SharePoint connections that employees no longer need.
In SharePoint, review site and list permissions, inherited access, groups, and sharing links. Remove employee access that is not required while retaining the backend's necessary access.
Sign in with test employee accounts and try submitting and viewing records in the app. Also test direct list URLs, sharing links, and SharePoint API requests, including requests for another user's records.

Apply least-privilege SharePoint permissions for direct connections
Use this approach when direct SharePoint access is acceptable but users should have only the permissions needed by the app.
Work with Office documents in WPS Office
WPS Office is a free, lightweight, easy-to-use Office alternative with a familiar interface and Microsoft Office format compatibility for a smoother migration. It does not replace Power Apps or enforce SharePoint access controls.

Frequently Asked Questions
Can I hide a SharePoint list and still let the app use it?
Hiding a list is not a security boundary. If the app connects directly using a user's SharePoint permissions, that user may still reach permitted data through a direct URL or API.
Where can I limit users to their own SharePoint list items?
Open the list, then go to Settings > List settings > Advanced settings and review the item-level permissions. Test the setting with non-admin accounts and confirm it matches the app's viewing and editing requirements.
Does sharing the canvas app automatically secure its SharePoint data?
No. App sharing and SharePoint data permissions must both be reviewed. Test access through the app as well as through direct list URLs, sharing links, and APIs.
What should I test before deploying to 10,000 employees?
Test representative user permissions, backend authorization, expected traffic, list sizes, and app queries. In Power Apps Studio, review delegation warnings and verify that queries return the intended records.




