Modern DFFS Enterprise
One control plane for every form in your tenant.
Modern DFFS Enterprise turns DFFS from a per-form tool into a governed platform. Manage your license, your code, your branding, your shared content, and your AI — once, centrally, applied everywhere — all from a single SharePoint site that only IT controls.
The problem
Every form becomes its own island
As DFFS spreads across your tenant, every form gets its own license, its own custom code, its own theme, its own copies of shared content. A branding change means touching dozens of forms. A compliance update means chasing form owners. A license renewal means hunting down every site.
Enterprise removes the islands.
The ModernDFFS_Central site
A single tenant-wide control point
One SharePoint site (/sites/ModernDFFS_Central) holds your settings and shared library, and every form in the tenant reads from it.
Central license
The license code lives in one place. Forms fall back to the central license automatically and show a “License managed centrally ✓” badge. One renewal, one key, the whole tenant.
Global Custom JS
JavaScript prepended to every form’s Custom JS before it runs. Roll out a tenant-wide helper library, audit hook, or compliance script from one place.
Global Custom CSS
CSS injected into every form across the tenant. Enforce a corporate look without touching individual forms.
Default tenant theme
A single theme applied everywhere — and it hides the per-form Theme Builder, so branding stays consistent and on-brand by default.
Centrally-governed Reusable Content
Shared HTML blocks, Custom JS and CSS snippets are managed centrally and linked into forms, not copied. Update the source once and every form updates automatically.
AI Enterprise relay
Route AI requests through your own relay service. No user ever handles an API key — your IT team manages the provider and credentials centrally.
Governance, in practice
Legal approves the disclaimer text once. IT manages the privacy banner centrally. Compliance owns the audit-trail notice. Reusable Content is how all of that scales — without chasing individual form owners. When something has to be right on every form, Enterprise is how you guarantee it: define it centrally, link it everywhere, and update it in one move.
Security & compliance
First-party by design
First-party assets only
Reusable Content JS and CSS references are restricted to your own DFFS_Assets document libraries (central or local). External / third-party CDN URLs are deliberately rejected — keeping every referenced asset first-party and your Content Security Policy straightforward.
AI traffic never leaves your network
Route every AI request through your own relay endpoint, so individual users never handle credentials and nothing reaches SPJSWorks infrastructure. Front it with Azure OpenAI (Managed Identity means no API key exists at all, and private endpoints are supported), Claude, OpenAI, Gemini / Vertex AI, AWS Bedrock — or a self-hosted model on an internal host. The AI endpoint never needs to be reachable from the internet, so fully air-gapped inference is supported, and any zero-data-retention agreement you hold with a provider applies end to end. Relay setup guide →
Internal support contact
Replace the SPJSWorks link in license and error banners with your own help desk — name, email, or URL — so users contact the right people inside your organization. Uniquely among the central settings, this one keeps working even after a license expires or is downgraded, because that is exactly the moment a user sees the banner and needs to know who to ask.
Data stays in your tenant
Forms, configuration, and content live in your SharePoint — no external CMS, file shares, or proprietary storage. No Graph or tenant API permissions are requested.
Running a vendor security review?
The Architecture & Security Overview documents the full architecture, every external connection the product makes, the security model, and the shared-responsibility split — with a pre-answered security questionnaire in Appendix A.
How the central license works
Tenant-scale licensing, no per-site admin
The license is bound to your organization and validated automatically when a form loads — no per-site license list to maintain.
Binding is done by tenant ID (a tenant-wide GUID) or by site collection URL, depending on your agreement. The bound value is encrypted inside the license code and checked on load, so the license can’t be reused outside your environment.
Issuing a license uses a simple challenge-response: you send us your tenant ID or site URL (as an encoded string), and we return a license code scoped to it.
Forms across the tenant fall back to the central license automatically and display a “License managed centrally ✓” badge.
What the entitlement covers
Central features follow the license, automatically
Everything that reads the central site is Enterprise only: reusable content, the default tenant theme, global Custom CSS and JavaScript, the managed AI relay, and cross-site-collection Related Items. This is checked every time a form loads — it isn’t just hidden in the configuration UI.
Not on Enterprise? Nothing is requested
A site that isn’t licensed for Enterprise never contacts the central site at all — not to read settings, not even to check whether it exists. If an Essentials or Professional site has no ModernDFFS_Central in the tenant, nothing appears in the browser console, because nothing was ever asked for.
If the license lapses, central stops
An expired license, a downgrade to Professional, a trial that has run out, or a maintenance cap that drops a site to Essentials — in every case the site stops using the central site on the next form load. The central site is usually still there and perfectly readable; DFFS stops reading it because the entitlement is gone, not the site.
Your forms keep working
Reusable content elements, the global theme and global CSS/JS stop applying, and cross-site Related Items elements stop rendering. The form itself keeps rendering and keeps saving. Nothing is deleted, nothing is rewritten, and no configuration is lost in the meantime.
Renew and it all comes back
Because nothing was removed while the license was lapsed, re-licensing to Enterprise restores everything on the next form load. There is no re-import, no reconfiguration, and no restore step.
Setting it up is an afternoon, not a project
The central site is an ordinary SharePoint site holding a few lists. A supplied PowerShell script creates the site and every list for you — and it’s idempotent, so re-running it is safe — or you can follow the manual steps if you’d rather not run a script. Either way you own the site outright; there is no external service and nothing leaves your tenant. And it doesn’t have to be tenant-wide: point it at a division’s hubsite and only the sites joined to that hub use it, so one team can adopt central governance without waiting for the whole company. Central site setup guide →
“Why doesn’t our Professional site pick up the global CSS we set centrally?”
Because it is working as designed — global CSS/JS, the default theme, centrally-governed reusable content, the AI relay and cross-site Related Items are Enterprise features, and a non-Enterprise site doesn’t read the central site at all. They are also not available as Professional add-ons, unlike Theme Builder, the AI Assistant and Print to PDF. Compare editions →
Ready to govern DFFS at tenant scale?
Let’s talk about your environment and map out a central deployment. Or start a free trial and explore Enterprise features with a trial upgrade.