DFFS central site
Serve Classic DFFS and its license from one central site collection to every site that uses it. Applies to Classic DFFS v5 with DFFS Installer v2. Using the modern SharePoint Online forms? See the Modern DFFS central site instead: it works differently.
Overview
What the central site is
Normally each site collection that uses Classic DFFS has its own copy of the DFFS package in an SPJS library, its own loader file and its own license. With a central site, one dedicated site collection holds:
- the DFFS package, in
/SPJS/DFFS/, which every form in every site collection loads from; - the license, in a list named
DFFS_Settings; - optional global settings in the same list: a support contact, and CSS and JavaScript that apply to every DFFS form.
Each site collection then only needs DFFS installed in its forms: two small web parts per form, added by the DFFS Installer. There is no loader file to edit per site, and no license to enter per site. To update DFFS everywhere, you upload the new package to the central site once.
The form configurations stay in each site, in the same configuration list as before. So do vLookup configurations. The central site does not hold or share form configurations.
Compared with a per-site install
| Per-site install | Central site | |
|---|---|---|
| DFFS package | In each site’s /SPJS/DFFS/ | Once, on the central site |
| License | In each site’s loader file or License tab | One DFFS_License row on the central site |
| Update DFFS | Upload the package to each site, then update the loader file | Upload the package to the central site |
| CSS and JavaScript for all forms | Per form, or in each site’s loader file | GlobalCustomCSS and GlobalCustomJS on the central site (Enterprise) |
| Form configuration | Stored in the form’s own site in both cases | |
The two models can run side by side. Existing per-site installs keep working, and the installer can move a form from one to the other (Moving forms).
Compared with the Modern DFFS central site
Modern DFFS also has a central site, but it does a different job. If you know that one, note the differences:
- Classic DFFS hosts the code package itself on the central site. Modern DFFS is an SPFx solution installed from the app catalog; its central site holds shared settings and content, not code.
- No reusable content. Classic DFFS has no shared library of rules, snippets or templates; each form’s configuration lives in its own site.
- Fewer settings. Classic DFFS reads six keys from
DFFS_Settings(listed below). There is no default theme, asset library, update-check setting or AI relay. - The path is yours to choose. The default is
/sites/ClassicDFFS_Central, but you can rename it. There is no hub-site lookup: every form uses the one path set in the DFFS files. - A site’s own license wins. If a site has its own license, DFFS uses it and ignores the central one (License order).
Requirements
SharePoint versions
- SharePoint Server 2013, 2016, 2019 and Subscription Edition (on-premises). This is what the central site is built for. The central site must be in the same web application as the sites that use it, because the forms load the package and read
DFFS_Settingsdirectly from it. - SharePoint Online works for classic list forms only, and needs the inline web part option, because a Content Editor web part there cannot link to a file in another site collection. Custom scripts must be allowed on each site while you install DFFS in its forms; once the web parts are added, they can be turned off again.
License
Loading DFFS from a central site requires a Classic DFFS Enterprise license; the installer marks the Central site option with it. The global settings GlobalCustomCSS and GlobalCustomJS also need the Enterprise tier, so they are not available during the 30-day trial (License types).
Who does what
- Creating the central site collection needs a SharePoint administrator (on-premises: a farm administrator, if you use the setup script).
- Installing DFFS in a form needs Design or Owner rights in that form’s site, as before.
Set up the central site
You do this once. The setup script does steps 1 to 3 for you on-premises; the manual steps follow.
With the setup script (on-premises)
Getting the script. Download ClassicDFFS_CentralSite_Setup.zip and unzip it on a SharePoint server. If Windows blocks the script because it was downloaded, run Unblock-File .\New-ClassicDFFSCentralSite.ps1 first.
Run New-ClassicDFFSCentralSite.ps1 in the SharePoint Management Shell as a farm administrator. It creates the site collection, the SPJS library and the DFFS_Settings list, and with -PackagePath it uploads the DFFS package too. It can be run again safely: what already exists is left as it is.
.\New-ClassicDFFSCentralSite.ps1 -WebAppUrl "https://intranet.contoso.com" `
-OwnerAlias "CONTOSO\spadmin" `
-PackagePath "C:\Downloads\DFFS"
| Parameter | Default | Meaning |
|---|---|---|
-WebAppUrl | required | The web application the sites using DFFS are in. |
-OwnerAlias | required | Primary owner of the new site collection. |
-SecondaryOwnerAlias | none | Secondary owner. |
-SiteName | ClassicDFFS_Central | The site’s URL name. If you change it, also change the path in the DFFS files. |
-ManagedPath | sites | The managed path the site is created under. |
-SiteTitle | Classic DFFS Central | The site’s title. |
-Language | 1033 | Language (LCID) of the new site. |
-Template | STS#0 | Site template (Team site). |
-ContentDatabase | the web application’s default | Content database to create the site in. |
-PackagePath | none | The unzipped DFFS folder, or the folder that contains it; uploaded to /SPJS/DFFS/. Checked before anything is created. |
The script does not add the license or set permissions. Continue with step 4 and Permissions.
Step 1: create the site collection
Create a site collection at /sites/ClassicDFFS_Central, in the same web application as the sites that will use it. A team site is fine. You can use another URL; see Using another path.
Step 2: upload the DFFS package
Download DFFS_v5.0.0.0_2026-11-03.zip and unzip it. On the central site, create a document library named SPJS and upload the whole DFFS folder to it, so the files are at /sites/ClassicDFFS_Central/SPJS/DFFS/…. This is the same layout as a per-site install.
Step 3: create the DFFS_Settings list
On the central site, create a custom list named exactly DFFS_Settings, and add one column:
- SettingValue: Multiple lines of text, set to plain text.
Each item is one setting: the built-in Title column holds the key, SettingValue holds the value. (The setup script also renames the Title column to Setting key; this is only a display name and is optional.)
Step 4: add the license
Add an item to DFFS_Settings with Title DFFS_License and the license code in SettingValue. Line breaks in the code are removed when it is read, so a code pasted over several lines still works. Make sure the license is one that is valid in every site collection.
Step 5: add optional settings
Add a support contact and global CSS or JavaScript if you want them; see the keys.
Permissions
Forms read the DFFS files and the DFFS_Settings list as the person using the form. Set the central site’s permissions like this:
- Everyone who uses a DFFS form needs Read on the central site. The simplest way is to add the AD group your users are in (or All authenticated users) to the central site’s Visitors group. The setup script does not do this; it is a manual step. Without it, the form loads without DFFS, or shows DFFS without a license.
- Only administrators should be able to edit the site.
GlobalCustomJSruns in every DFFS form for every user, so edit rights toDFFS_Settingsor theSPJSlibrary amount to running code in all your forms.
The DFFS_Settings list
DFFS reads these keys. The key goes in Title and must be spelled exactly as shown; items with an empty SettingValue are ignored. Values are read each time a form opens, so a change applies the next time a form is loaded.
| Title (key) | SettingValue | Tier |
|---|---|---|
DFFS_License | The license code, used by every form that has no license of its own. | All |
SupportContactName | Name of your internal support contact. | All |
SupportContactEmail | Internal support e-mail address, shown as a mail link. | All |
SupportContactURL | Internal support website, shown as a Support link. | All |
GlobalCustomCSS | CSS added to every DFFS form, after the form’s own Custom CSS. | Enterprise |
GlobalCustomJS | JavaScript run in every DFFS form, before the form’s own Custom JS. | Enterprise |
Support contact
Your internal support contact, shown to users when a form uses the central license. Set the three keys in any combination:
| Key | Example | Shown as |
|---|---|---|
SupportContactName | IT service desk | The name; linked to the e-mail address if one is set |
SupportContactEmail | helpdesk@contoso.com | A mail link (the address is the link text when no name is set) |
SupportContactURL | https://intranet.contoso.com/dffs-help | A Support link that opens in a new tab. Must start with https:// or http://; anything else is ignored |
With all three set, users see Internal support: IT service desk | Support. It appears in three places:
- on the form, after | License is managed centrally in the Enhanced with DFFS line at the bottom;
- in the red invalid-license banner, so users know whom to contact if the central license expires;
- as an Internal support row on the License tab of the configuration.
GlobalCustomCSS
Plain CSS, without a <style> tag. It is added after each form’s own Custom CSS, so for rules of equal weight the global rule wins. Use it for house style that every form should share.
GlobalCustomJS
Plain JavaScript, without a <script> tag. It runs in every DFFS form before the form’s own Custom JS, so functions and variables it defines are available to every form’s Custom JS and rules. An error in it is caught so the form still loads; with DFFS dev mode on, the error is written to the browser console.
// GlobalCustomJS: a helper every form can call from its own Custom JS
function contosoFormatProjectNo(v) {
return "PRJ-" + String(v).padStart(5, "0");
}
Test changes to GlobalCustomJS on one form first: a mistake here reaches every form at once.
Using another path
The default central site is /sites/ClassicDFFS_Central. To use another URL, change the path in these three files in the DFFS package before you upload it:
| File | Change |
|---|---|
DFFS/loader/DFFS_loader_v5.html | var dffs_central_site_url = "/sites/ClassicDFFS_Central"; at the top |
DFFS/installer/DFFS_Installer_v2.html | var dffs_central_site_url = "/sites/ClassicDFFS_Central"; |
DFFS/loader/DFFS_loader_v5_bootstrap.html | var central = "/sites/ClassicDFFS_Central"; |
Use the server-relative path, without a trailing slash. All three must match.
Make the same three changes each time you upload a new DFFS package. Forms installed with the inline web part have the path written into their web part, so reinstall those forms after you change it.
Install DFFS in the forms
Do this in each site collection that should use the central site.
Step 1: open the installer
Create a web part page in the site (Site contents → Site Pages → New → Web Part Page), add a Content Editor web part, and set its Content Link to:
/sites/ClassicDFFS_Central/SPJS/DFFS/installer/DFFS_Installer_v2.html
The installer is stored on the central site but runs on this page, so it installs into this site’s forms.
SharePoint Online: a Content Link cannot point to another site collection there. Create an SPJS library in this site, upload DFFS_Installer_v2.html to /SPJS/DFFS/installer/, and link to that copy instead.
Step 2: choose Central site
At the top, under Where do the forms load DFFS from?, the installer shows two sources: This site (a package in this site’s own SPJS library) and Central site, marked Enterprise license and linking to this page. It checks which of them exists and dims the one it cannot find. Choose Central site.
If Central site is dimmed, the installer cannot reach DFFS_loader_v5.html on the central site: check the path, that the package is uploaded, and that you have Read rights there (Troubleshooting).
Step 3: install in a form
On the Install DFFS in a form tab, pick the list and click Install DFFS. The installer adds two Content Editor web parts to the list’s forms, [DFFS by SPJS] - Overlay and [DFFS by SPJS] - Code, linked to the loaders on the central site, and sets the content types’ form URLs.
Then open the form and configure it as usual. The configuration opens on the form page itself (with an Opening the DFFS configuration… screen while it loads), and is saved in this site.
The inline web part option
With Central site chosen, the installer shows the option Use one inline web part instead of two Content Link web parts. It installs a single web part, [DFFS by SPJS] - Bootstrap, that fetches the two central loaders with a small script instead of Content Links.
- Turn it on for SharePoint Online, where the two Content Link web parts cannot load files from another site collection. The installer marks it Recommended on SharePoint Online there.
- Leave it off on-premises when the central site is in the same web application. The two Content Link web parts are the standard setup and are easier to troubleshoot.
- Turn it on if a form shows “Cannot retrieve the URL specified in the Content Link property”.
The option applies to forms you install or reinstall after setting it.

Moving forms between local and central
The Review installations / reinstall tab lists every DFFS form in the site, with the DFFS version it was last saved with and where it loads DFFS from: This site, Central site or Central site (inline web part). Reinstall installs DFFS in a form again from the source selected at the top, so you can move a form from its local package to the central site, or back.
The form’s configuration is not changed by a reinstall. If the site has its own license, remember that it keeps winning over the central one (License order).
Updating DFFS
Upload the new DFFS package to /SPJS/DFFS/ on the central site, replacing the old files (and, if you use another path, make the three path changes first). Every form that loads from the central site uses the new version the next time it is opened. There is no loader file to update in each site.
The loaders request the files with a version number in the URL, so browsers load the new files instead of cached copies.
Licensing
License types for a central site
A central site needs a Classic DFFS Enterprise license. It is bound to the central site, so one license, read from the central site, covers every site that loads DFFS from it. This works for both the online and the offline (DFFS5OFFLINE::…) license. A license bound to the central site is only accepted when it is itself an Enterprise license; otherwise the form shows A DFFS license bound to the central site requires an Enterprise license (Tier 3).
The central license is checked in every site collection that uses it. An existing license that covers several sites (such as a Company, Department, Division, Corporate or OEM license) is also accepted from the central site, at its own tier; the Enterprise features need an Enterprise license. A license for a single site collection belongs on that site’s License tab instead: on the central site it would be valid only in that one site collection, and every other site would show the red invalid-license banner.
An online license is checked against spjs.blob.core.windows.net, so the browsers using the forms need access to it. For a network without internet access, use an offline license.
License order
A form uses the first license it finds:
- a license set in the loader file (
dffs_master_licensecode; per-site installs only); - the site’s own license, entered on the License tab of the DFFS configuration;
- the central
DFFS_License.
So a site that already has a license keeps using it after you move its forms to the central site. To use the central license there, remove the site’s own license on the License tab.
When the central license is used, the License tab in the configuration says managed centrally in the DFFS_Settings list on the central site, and the top of the configuration shows managed centrally after the license holder’s name.
Checking that it works
- Open a form in a site that uses the central site. The Enhanced with DFFS line at the bottom should read | License is managed centrally, followed by your support contact if you set one.
- Open the DFFS configuration for the form and look at the License tab: it should show the central license as managed centrally.
- Open the form as an ordinary user, not an administrator, to check that users can read the central site.
- If you use
GlobalCustomCSSorGlobalCustomJS, check that they take effect in a form.

Troubleshooting
| What you see | Cause and fix |
|---|---|
| The installer dims Central site. | It cannot load /SPJS/DFFS/loader/DFFS_loader_v5.html from the central site. Check the path in DFFS_Installer_v2.html, that the package is uploaded, and that you have Read rights on the central site. |
| “Cannot retrieve the URL specified in the Content Link property” in a form. | The Content Editor web part cannot link to the central site (always the case on SharePoint Online). Reinstall the form with the inline web part option. |
| The form works for administrators but not for other users. | Users lack Read rights on the central site. See Permissions. |
| The form shows the invalid-license banner in some site collections only. | The license is bound to one site collection. Use a license valid in every site. |
| A form ignores the central license. | The site has its own license, which wins. Remove it on the License tab (License order). |
No license at all, although DFFS_License is set. | The form could not read DFFS_Settings. If the central site cannot be reached, the form runs as if there were no central settings. Check the list name, the SettingValue column name, the key spelling and Read rights. |
GlobalCustomCSS or GlobalCustomJS has no effect. | Both need the Enterprise tier. Check the tier on the License tab and the key spelling. For JavaScript errors, turn on DFFS dev mode and look in the browser console. |
| Forms broke after moving the central site. | Make the three path changes, upload the files again, and reinstall forms that use the inline web part. |