1. Getting Started

Requirements

• Microsoft 365 with SharePoint Online. SharePoint Server on-premises is not supported.
• A current browser: Microsoft Edge, Google Chrome, Mozilla Firefox, or Safari.
• Permission to deploy the package to the tenant app catalog.
• Site owner permission on the subsite where the page will live.

Deploy the app

The package is one SharePoint Framework web part. It runs on a modern SharePoint page, as a full-page app, and in Microsoft Teams as a channel tab or a personal app.

• Install Permissions Manager 365 on its own SharePoint subsite.
• Create or edit a modern page, add the web part, and publish the page. In page edit mode the app asks you to publish before it will run.
• People open the app from that SharePoint URL.

Add it to Microsoft Teams

• A Teams channel tab uses the SharePoint site behind that team. Finish setup on that site before using the tab.
• The personal app uses the same web part on the person’s SharePoint host.

First-time setup

A site owner runs setup once. Setup creates two hidden lists on the host site:

• PM365Settings stores appearance, language, app admins, and the license key.
• PM365Sites stores one row per site: URL, title, parent, and source, plus the inspection summary.

Role assignments are not stored in either list. Create the settings list is safe to run more than once. When both lists exist, Settings shows the site as ready.

Both lists then use unique permissions. The site owners group has full control. Each app admin has edit. Other people on the host site do not have access to the lists. If the signed-in account cannot change those permissions, the lists are left as they are and a site owner needs to open the app before a new app admin can read them.

Allow items from this list to appear in search results is the SharePoint search setting for the settings list. It is off by default.