It is now finally possible to add, remove and manage apps for each “Site Collection” in SharePoint Online. As each Project Online “PWA” is its own “Site Collection”, this now means that you can give the full app control to your PMO and/or PWA administrator. In summary it means that each project portal (PWA) gets their own blank catalog for apps that should be allowed and available to the specific PWA users. I would highly recommended using this approach in cases where you have test/dev, pre-production and production PWAs.
Here are the basic steps to get your new PWA app catalog up and running:
Step 1: Connect to SharePoint Online as an Administrator (using PowerShell)
$adminUPN="<the full email address of a SharePoint administrator account, example: firstname.lastname@example.org>" $orgName="<name of your Office 365 organization, example: contosotoycompany>" $userCredential = Get-Credential -UserName $adminUPN -Message "Type the password." Connect-SPOService -Url https://365projectum-admin.sharepoint.com -Credential $userCredential
Step 2: Allow the PWA Site Collection to get its own App Catalog
Add-SPOSiteCollectionAppCatalog -Site URL-TO-TARGET-SITE-COLLECTION
Step 3: Find you PWA App Catalog by navigating to your PWA “Site Contents” area
Step 4: Upload your apps and add-ins to your newly created catalog and they will be ready for deployment within the PWA Site Collection.
To learn more about this update read the official guide here:
Manage the Site Collection App Catalog (Link)
As a SharePoint Online site collection owner, after adding your site to the allowed list and enabling the Site Collection App Catalog feature on your site, you can use it to upload any custom SharePoint Framework components that you or your organization develop. Uploading custom components isn’t much more complicated than uploading a document to a library and setting some properties. You can use the Site Collection App Catalog to install custom components on your sites for users (also called app deployment).
If you upload a component marked for Tenant-Scoped deployment it will be available for all sub-sites of the target site collection without needing to be installed first.
For information about building modern Web Parts using the SharePoint Framework, see Overview of the SharePoint Framework.
Your tenant administrator must add your site to the allowed list before the Site Collection App Catalog feature is available. Users with the Manage Web Site permission are then able to upload SharePoint Framework components to the Site Collection App Catalog and make them available to the site by deploying and installing them.
When a component exists in both the tenant’s app catalog and the Site Collection App Catalog the version in the Site Collection App Catalog will take precedence whether it is an older or newer version.
The first step is to add the Site Collection to the tenant’s allow list if it hasn’t already been added. Adding a Site Collection to the list enables the Site Collection App Catalog feature on the site, and also authorizes its use. In the future you can remove a site from the list to disable the feature.
- Follow the instructions in Connect to SharePoint Online PowerShell.
- Run the following command at the SharePoint Online Management Shell command prompt:Add-SPOSiteCollectionAppCatalog -Site URL-TO-TARGET-SITE-COLLECTION
To find the Site Collection App Catalog after it’s been created, go to the Site Contents page of your site. You will see the Apps for SharePoint document library available, this is your Site Collection App Catalog.
- Select New and browse to the app you want upload, or drag the app into the library.
- You’re prompted to trust the app and deploy it. If you don’t deploy the app right now you can do this later from the Ribbon menu.
- Optional: To help identify and use the app later right-click the app and click Properties.
- In the properties dialog form, you can change the Name for the app and enter optional information like a description, images, category, publisher, and support URL. Follow the instructions on the screen for details like image size.
- Make sure the Enabled check box is selected so that the app can be installed in the site.
- If it appears, in the Hosting Licenses box, specify the number of licenses you think you will need.
- Select Save.
To make any Web Parts or App Parts in the app you are using available to page authors the app must be installed in the site after uploading it.
You can deploy custom SharePoint Framework componentsusing the Site Collection App Catalog. Follow the steps in Add an app to a site to install your component on your site after it is deployed from the Site Collection App Catalog.
If you no longer want a specific component to be available for users to install, you can remove it from the app catalog. Any instances of the component that have already been added to sites by users will remain, but the component will no longer be available for users to add to additional sites.
- On the App Catalog site, select the Apps for SharePoint list.
- Right-click the component that you want to remove and click Delete.
- In the dialog box, click OK to confirm that you want to send the item to the site Recycle Bin.
Removing a Site Collection from the allow list will cause several things to happen:
- Users will no longer be able to add new SharePoint Framework components to the Site Collection App Catalog.
- Components in use that are provided by items in the Site Collection App Catalog will stop working.
- Follow the instructions to Connect to SharePoint Online PowerShell.
- Run the following command at the SharePoint Online Management Shell command prompt:Remove-SPOSiteCollectionAppCatalog -Site URL-TO-TARGET-SITE-COLLECTION
I downloaded the latest copy of SharePoint Online Management Shell. Ran the scripts, but got an “Unknown Error” when running the Add-SPOSiteCollectionAppCatalog commandlet.
Add-SPOSiteCollectionAppCatalog : Unknown Error
At line:1 char:1
+ Add-SPOSiteCollectionAppCatalog -Site https://*********.sharepoint.co …
+ CategoryInfo : NotSpecified: (:) [Add-SPOSiteCollectionAppCatalog], ServerException
+ FullyQualifiedErrorId : Microsoft.SharePoint.Client.ServerException,Microsoft.Online.SharePoint.PowerShell.AddSi
Sorry for a late reply. Are you still struggling? Try running it in Powershell ISE – that worked for me.