Deployment Guide – netDocShare app for Microsoft 365 SharePoint Online / SharePoint Server 2019 / SharePoint Server 2016

This deployment guide assumes that the end user has the appropriate level of permissions to access and add/remove apps from the root site collection’s App Catalog. If you do not have these levels of permissions, please contact your Office 365 tenant’s global administrator and ask for Root site collection Administrator access.

This guide is meant to cover the deployment process of SharePoint Framework (SPFx) WebParts on various environments. If you would like further assistance with using and configuring the individual SPFx WebParts, please see our documentation entitled “netDocShare WebParts – Power User Guide”. This guide does NOT cover installation and usage of the netDocShare Teams app. For more info about this, please request documentation specifically for the Teams App.

Note: SPFx WebParts are not compatible with on-premises SharePoint Server 2013, 2010, 2007 or 2003 versions. SPFx specifically requires the “Feature Pack 2” update that comes with SharePoint 2016. We provide a Visual WebPart sandbox solution package for on-premises SharePoint Server 2013 environment.

Site Collection Libraries MUST be able to host JSON and JS files or else deployment will fail. Any security measures that block Popups or iFrames must be turned off as our authentication uses these resources. There is an auth option for users who cannot turn off iFrame blocking, please see the auth section for more info.

Supported Browsers:

  • Microsoft Edge
  • Google Chrome (latest released version)
  • Mozilla Firefox (latest released version plus immediate previous version)
  • Apple Safari (latest released version)
  • Internet Explorer 11 (limited support only. IE11 Protected Mode is not supported)

Not Supported Browsers:

  • Internet Explorer 10
  • Internet Explorer 9
  • Internet Explorer 8
  • Internet Explorer 7
  • Internet Explorer 6

The SPFx framework uses SharePoint App Catalog as a container for deployment. Once you are logged in as an Admin user, navigate to the App Catalog of the site collection where you wish to deploy the WebParts. In the SharePoint Administrator center, click Classic features > Apps > App Catalog.

If your SharePoint site collection does not have an App Catalog, you will be guided through a process to create one. Please follow the instructions and create the appropriate App Catalog. This is required for the App to be deployed to the site collection. Once you have created and/or navigated to the location of the App Catalog, you should see a screen like this:

From here, click on Apps for SharePoint and click “Upload” to directly upload “netDocShare.sppkg” file.

All netDocShare assets should automatically be deployed into the same SharePoint location typically found here – https://{your-tenantname}{WebPart GUID}

SharePoint On-Premises

For SharePoint On-Prem, instead of manually deploying to the app catalog, you will use a PowerShell script that will automatically deploy to the App Catalog and also deploy the required assets to the appropriate libraries. Please see the section entitled “Deploying on SharePoint On-Premises” for more information.

Make sure that you have the required admin privileges on your tenant to be able to add / remove apps from the App catalog and / or create the app catalog itself. See the previous section for further instructions.

Drag & drop “netDocShare.sppkg” file or click “+new” to browse and pick your file. Once the upload completes, your screen should look like this:

Note: Please check the box in the dialog above or else you will have to manually
add the app to each site collection.

Eventually, the files will be stored in this location:

https://{your-tenantname}{WebPart GUID}

Once the deploy is successful, please navigate to the location specified above where the app assets are deployed. Take the netDocShareLicenseKey.txt file provided and simply drop the file into this library. This should now enable your netDocShare license with the specific features you have requested. For more information on licensing, please consult our Power User Guide.

If your SPO environment follows a similar structure to the link above, you will need no further action to complete the deploy. However, if it does not, then you will have to run the included PowerShell install script to make sure that your assets are deployed to the correct location. We have included a convenient install script (install.ps1) to help you ensure that your deployment is successful regardless of the environment type.

If you would like to deploy your assets to a custom location OR your app catalog has an atypical name/structure, you can use our installation script to automatically install the sppkg and deploy the required assets to a location of your choice. Simply execute the script (install.ps1) that is packaged together with the sppkg file and answer the prompts to let the script determine where to deploy the assets. If you do not take this step, your installed webparts may have difficulty retrieving scripts or assets from the correct location.

Please note the location of your deployed assets folder. For SharePoint Online, this will often include the ID of the app. This ID will show up in the App Catalog’s list of apps after deploying the sppkg as in the screenshot above. This value needs to be used later when setting up webparts. It will be used in the config value named “assetPath”, which is required to retrieve static assets and also query licensing information. Your assetPath should look like


While SPFx is meant to be compatible with both modern and classic pages, the experience might be slightly different for each one. Once “netDocShare.sppkg” has been deployed, it is referred to as an “App” by SharePoint. You can now go to any page on the site collection and add this app to the site collection, which will, in turn, make the WebParts available for use in the insert WebPart menu.

Note: Make sure that the page created for the webpart is specifically a “webpart page” instead of “wiki page,” which is the default option. Clicking “new” to create a new page will default to wiki page.

Modern Page – Adding the App

This step can be skipped if you have checked the “Make this solution available to all sites” checkbox during deploy

Navigate to your site’s Site Contents page and click the +New button, then select App

If you have followed the instructions above for deploying “netDocShare.sppkg” file to the Site collection App Catalog, then the app that you added should be available under the “From your Organization” tab on the left side

Add the App from here and it will be available for all users on that specific site collection

Note: The screenshot above is showing “You can’t add this app here” because it has already been added

If you are unable to see the app, this means that the App Catalog where the app has been deployed and the current site collection are disconnected from each other

If you can see the app, but trying to add it causes an error, this generally means that you are logged into an account that does not have the correct permissions or the site collection has not been configured to accept apps. In this case, please speak to your SharePoint Administrator to enable apps.

Create a new site page or navigate to the page you want to add the WebPart. Upon entry, you should already be in “edit” mode. Click the + button to add a new WebPart to the page.

There should be a dropdown menu that opens and should contain the WebPart that you have added to the site via Apps

Navigate to your site’s Site Contents page and click the “add an app” button

From here, you will navigate to a page that looks the same as the modern version, choose “From Your Organization” and look for your app on this list. Add the app and your SPFx WebParts should become available once you try to add them to a site page.

Create a new site page or navigate to the page you want to add the WebPart. Click on the “Edit” button on the top right or open the page ribbon by clicking the “Page” button on the top left and choose the first tile “Edit”.

Once you are in edit mode, now there should be a tab named “Insert” on the ribbon. Click on it and choose to add a “WebPart”

By default, netDocShare WebParts will appear under “netDocShare”.

The process for adding webparts in On-Prem site collections is identical to the process for classic sites as older sites are considered to be classic.

Deploying to an On-Prem environment means that you must pay close attention to SharePoint Server versions to ensure compatibility. netDocShare SPFx WebParts can only be configured for on-premises SharePoint Server 2016 or 2019 and for SharePoint Online. For on-premises SharePoint Server 2016/2019, the update called “Feature Pack 2” must be installed on the SharePoint Server in order for the site collection to recognize and validate the “netDocShare.sppkg” file that we are deploying. Here are the general guidelines on compatibilities between the SharePoint version and what SPFx version should be used:

SharePoint Online: Can use latest SPFx version

SharePoint 2019 On-Prem: Use SPFx version 1.4.1 or earlier

SharePoint 2016 On-Prem: Use SPFx version 1.1.0

SharePoint 2013 On-Prem: Please contact us for a Visual WebPart Farm Solution

Once the SharePoint Server farm is configured to enable app deployment and usage, the process to add the SPFx WebParts project should be like deploying in SharePoint Online. If your SharePoint Server does not have apps enabled, ensure all pre-requisites are completed before any apps like netDocShare is deployed.

Note: Site Collection Libraries MUST be able to host JSON and js files or else deployment will fail. Any security measures that block Popups or iFrames must be turned off as our authentication uses these resources.

Note: If you have attempted to add the netDocShare app, but you get the message below, that means that your server is not yet set up to enable app usage.

There may be several blockers that affect whether your users can add apps to a site collection or not. Please contact your SharePoint farm administrator to troubleshoot these points if you are having issues but here are a few helpful tips:

Make sure Apps are enabled in your farm

Configure the subscription settings service application

Configure the user permission and groups

Make sure the App Management Service application is associated with the SharePoint web application

Configure App URLs

Configure SSL for NetDocuments Authentication (requires HTTPS)

Installing the App into your App Catalog

Once deployed, you can check in your site Assets library where you will find the webpart assets as pictured below

Then, it will create a custom list in the root site collection where it will deploy all the files required to load the webparts

Due to the lower version of this SPFx project, SPFx is unable to automatically deploy client-side assets to the App Catalog site collection

Our On-Prem deployment package will generally include a SharePoint Management PowerShell script that will execute an automatic deploy. You can recognize this file by its name: “install.ps1”. Here is a general breakdown view of the package contents:

The script will first install the sppkg to your site’s App Catalog

In order to begin the process, please edit the file “install.ps1” file using a text editor (such as notepad) and replace the values on the first 3 lines with values that correspond to your particular site collection. These values are highlighted in the text and screenshot below (in case you cannot see in the screenshot):

$appCatalogUrl = “https://klstsp16/sites/AppCatalog

$appLibFolderPath = “AppCatalog”

$assetSiteUrl = “https://klstsp16

Once these values have been customized. Please execute the file by opening SharePoint Management Shell, navigating to the deploy folder and running “install.ps1”. Please ensure that this file remains in its default location in the deployment package.

Once the app has been deployed to the App Catalog, now it can be added to any site collection by visiting the “Site Contents” of your site collection and selecting “Add an app…”

Please select the file, click on the Files tab in the top ribbon and click the “Deploy” button. This will deploy the package to the site collection that you have specified. It should look something like this:

Upon successful install, the script will automatically open a browser page leading to your App Catalog where the sppkg has been uploaded. Here, you should see a new sppkg file called “netDocShare” should be automatically uploaded

Once netDocShare has been successfully added, you should be able to create new webparts using netDocShare. Please see our “netDocShare Webparts: Power User Guide” to learn more about how to create, configure and update webparts.

If there is some problem with our automatic install script, we have also included instructions in a section below to manually deploy the sppkg and its required assets.

Manual Deploy

Go to “start” on your computer to open your SharePoint Central Administration Page

Navigate to Apps > Manage App Catalog.

Make sure that the correct site collection name is selected in “web application”, on the top right of the page

If your site collection does not already have an App Catalog, pick the option to create a new app catalog site. Once you have filled in the form to create the App Catalog, navigate to it and you should arrive at a familiar page:

Click on “Apps for SharePoint” and add a new document to this list. Select “netDocShare.sppkg” file and upload it. Now, your new WebParts should be available to use for any user in this site collection.

Adding the WebParts

Note: Make sure that the page created for the webpart is specifically a “webpart page” instead of “wiki page,” which is the default option. Clicking “new” to create a new page will default to wiki page.

Please note the the names and functionalities of webparts may vary depending on the version of netDocShare. For example, on SharePoint On-Premises 2016, instead of differently named webparts, there is a single universal webpart named “DocumentViewer” which can be converted to all other webparts using configuration.

Navigate to the site collection where you would like to use the Web parts

Navigate to Site Contents and choose “Add an app”.

The app that you added through the admin deployment should be available here. Click on it to add it to Site Contents. *Note: Adding the app should be a similar process to SharePoint Online for Classic pages.

Now navigate to the page where you want to add the webpart and click “Edit”.

Click within the box you would like to add the webpart to and click “Insert” and “Web Part”.

netDocShare WebParts should appear under the “Other” folder in categories, unless you have specified some other way of populating the WebPart.

We are providing a convenient PowerShell script for users to install their sppkg and assets. This install script will come together with the deployment package and offers a single solution for multiple environment types.

For SharePoint Online, assets are generally automatically deployed unless there is an irregularity in how the App Catalog is structured. Please see the final note in the “Deploying to SharePoint Online section.” For On-Premises SharePoint environments, asset deployment works a bit differently.

For Users who would prefer to manually deploy assets after deploying “netDocShare.sppkg” to the App Catalog, please follow the instructions below.

Using the Site Assets library is generally recommended as it is common among all site collections.

Now, you must create this directory and populate it with the assets that the WebPart needs to function. Its recommended to create a folder named “netDocShare” in order to keep different app assets separate

Copy any applicable Json and JS files required to load the WebPart.

Also copy any static assets such as icons or fonts into this folder. It should look something like this:

Finally, you can see that we have created this directory in the Site Collection’s “Site Assets” library within a folder we created called “netDocShare”. In the image below, you can see our WebPart retrieving icons from this location in the highlighted src link.

In order to properly retrieve these assets, a config value called “assetPath” must be included in each webpart config. Your assetPath should look like: https://{yourSharepointTenant}/SiteAssets/netdocShare/folderIcons/.

This path must point to the location where your JS files and static assets have been deployed on SharePoint.

In this step, you are updating the spkg file. This is one of the last steps in the deployment process. Here all you need to do is backup the current spkg file if applicable, and then delete it. If backing up, all that is necessary is to download the current file using the context menu depicted in the figure below. Similarly, the delete option can also be found in the same context menu. Once that is complete, click the “upload’ button towards the top of the screen, and pick your newly created .spkg file.

Whether you are deploying to a modern page (SPO) or classic page (SPO) on SharePoint Online or SharePoint Server 2016/2019 on-Premises, the WebPart configuration process should remain the same. When you have added a WebPart in “Edit Mode”, each WebPart will have a small individual “Edit web part” button either on the top right-hand side or top left-hand side. Clicking this button will open a panel on the right side of the screen where you can input configurations.

Note: Make sure that the page created for the webpart is specifically a “webpart page” instead of “wiki page,” which is the default option. Clicking “new” to create a new page will default to wiki page. Using netDocShare webparts on a wiki page is generally supported but may result in unexpected behavior in some situations.

Modern pages have a special functionality which will automatically open the config builder in a popup window and import all existing settings to edit.

Clicking “Open config builder” will open a popup window in which you currently existing settings will be automatically imported for you to edit and update.

For classic, make sure to find the ribbon on the top and click Page > “Edit” to activate edit mode. Then find the individual dropdown menu on the top right of each WebPart:

Different netDocShare WebParts have many different properties/settings that can be configured easily by using the netDocShare JSON Config Editor. You can enter your desired configs into the editor, and it will generate a piece of text that you can copy/paste into the WebPart JSON Settings. To see a list of all supported properties and related values refer to the document “NetDocuments SPFx WebParts User Guide”.

Our webparts support the usage of CollabSpaces from  CollabSpaces are like workspaces and ShareSpaces; The major difference is that CollabSpaces can allow users external to NetDocuments to have access to the documents inside the CollabSpace.

CollabSpaces can be displayed in normal or treeview using the “primarySource” value in the configs and inputting the ID and using “collabspace” as type. You can read more about this in the documentation named “netDocShare Webparts – Power User Guide”. To give access to external users, a few SharePoint-based permission tasks need to be done.

  1. Firstly, the external user must be added to the group that the CollabSpace is shared with on This will send an email to the user and allow them access the NetDocuments website through a special external user login.
  2. In order to view the content on SharePoint, the user must first be added to the site collection where the webpart is located.
  3. Finally, the external user must ALSO be added to the App Catalog site collection where the App is deployed.

Upon giving the correct permissions, external users will have access to a specific webpart where they can see and interact with CollabSpace contents. The external users should be locked out of every other view except for the CollabSpace that we have allowed them to view. If the external user is removed from the group, they will continue to have access to the CollabSpace until their access token expires, which should generally be 30-40 minutes.

Note: Site Collection Libraries MUST be able to host JSON and js files or else deployment will fail. Any security measures that block Popups or iFrames must be turned off as our authentication uses these resources.

Occasionally, we may provide an update package that improves functionality or adds new features to the netDocShare product. In this case, users will need to deploy the new sppkg file using the steps below. Note that this process should not disturb webparts that have already been set up using our previous build.

SharePoint Online

Simply delete the previous .sppkg file from your App Catalog’s list of apps. And then upload the newest sppkg that we have provided. No other action needs to be taken. The update will apply immediately to all webparts created using netDocShare. During the time when the sppkg is deleted, users will not be able to use the webparts. Please ensure that you have backed up the previous sppkg file before deleting in case any errors or issues occur.

SharePoint On Prem

After receiving our deploy package, please go through the same process found in the section entitled “Deploying to SharePoint On-Premises”. As a summary:

  1. Delete the previous sppkg file from the app catalog
  2. Run the ps1 install file after changing the library locations to reference your desired deploy location
  3. The script will open your app catalog. Click on the netDocShare package and select the “Deploy” option from the top ribbon
  4. There is no need to re-add the app to your site collection as it is already added. Simply visit your webpart page to see the updates

Please be aware that there may be invisible webparts on existing page webpart pages. These invisible web parts are created when a user does not finish the set-up process of a new webpart. This may cause authorization issues because invisible webparts are also loading code. You can delete these webparts by navigating to Site contents > Site Pages, and click on the page that you wish to check. Once there, go to properties, and click the link “open webpart page in maintenance view”.

Starting from version 2.4.1, we are introducing a new method of authentication which will make it easier for both administrators and users to authenticate with the NetDocuments API. As mentioned above, we have taken steps to ensure that webparts using the previous system are NOT affected.

The major change includes the removal of reliance on having an auth page created on your SharePoint site collection. For the foreseeable future, you may continue to use the auth-page-based authentication system but please be aware that a much easier system can be implemented with minimal time and complexity. Please see the new authentication section in our Power user guide for more information.