Pro and Business
The Pro add-on extends the free plugin with named environments, certificate authentication, form-builder integrations, multisite support and priority support. It is licensed per site with an offline token, sold on invoice by WOODS Business Solutions and never distributed through WordPress.org. The Business tier adds visitor sign-in bound to a Dataverse contact, own-records views and access rules.
Installing and activating a license
- Install and activate WBS Connect for Dataverse Pro next to the free plugin (1.1.0 or newer). Without the free plugin the add-on stays idle and shows a notice.
- Open Dataverse Connect, License and paste the token you received by email. Save.
- The tab shows the plan, the licensed number of sites, the expiry date and the site the token is bound to.
License checks run offline: the token is a signed JWS the plugin verifies with an embedded public key. No data leaves your site and no activation server is involved. A token bound to a host validates only on that host; a token without a host binding works anywhere. The seat count is shown for reference; offline tokens cannot count installs.
After the expiry date there is a 14-day grace period in which Pro features keep working and a renewal notice appears on the plugin's own screens. After that, Pro features switch off cleanly: collections and forms fall back to the default connection, the integrations unhook, and the site keeps working with the free feature set. To move a license, remove it on the License tab and paste the token on the new site.
Environments
The Connection tab of the free plugin remains the Default environment. The Environments tab adds named connections, each with:
| Field | Meaning |
|---|---|
| Slug | The key collections and forms select the environment by, for example staging. |
| Label | Display name. |
| Tenant id, Client id, Environment URL | As on the Connection tab. Required. |
| Auth | Client secret or Certificate. |
| Client secret | For secret auth; stored write-only, never shown again. |
| Certificate (PEM), Private key (PEM) | For certificate auth; the key is write-only. |
Every environment has its own Test connection button. On the collection and form editors an Environment select appears; a collection or form pointed at an environment reads and writes there, with its own token and cache keys. Unknown slugs fall back to the default connection. Typical use: a dev, test and prod environment behind one WordPress site, or one site serving records from two tenants.
Certificate authentication
For environments with Auth set to Certificate the token request uses the client-assertion flow instead of a secret: the plugin signs a short-lived JWT (RS256, ten minutes, with the certificate thumbprint in the header) with the private key and sends it as client_assertion. Upload the public certificate to the app registration under Certificates & secrets, then paste certificate and key in PEM form into the environment. PHP needs the OpenSSL extension. A signing failure surfaces as a normal token error and never fatals.
Form-builder integrations
Each integration maps a source form to a form configured on the Forms tab and pushes the submitted values through the free plugin's create pipeline, so relate-to binding, sanitization and the wbs_dataverse_connect_form_record filter keep working. Submitted field names or labels are lowercased, spaces become underscores, and the result is matched against the form's field names. Failures are logged and never block the source form's own flow.
| Builder | How to map |
|---|---|
| Contact Form 7 | Add wbsdvc_form: <key> under the form's Additional Settings. Runs before CF7 sends its mail. |
| Gravity Forms | Set Dataverse form key in the form settings (a field the add-on adds, GF 2.5 or newer). Runs after submission. |
| WBS Forms | Map WBS Forms form ids to form keys under Integrations on the License tab, one id = key per line. |
The free plugin's own WBS Forms bridge (typed mapping per form slug, see Forms) does not need Pro; the Pro integration is the no-code alternative that reuses a Forms-tab configuration.
Multisite
Network-activate the add-on to store the license as a network option every subsite reads; the free plugin's collections, forms and the Pro environments stay per site. Grace and lapsed notices mirror to the network admin. Per-site activation with a per-site license works as well.
Business tier
The Business tier adds visitor accounts to the same add-on (Pro 1.1.0, needs the free plugin 1.5.1 or newer). It builds on three free-plugin hooks (wbs_dataverse_connect_access_filter, wbs_dataverse_connect_can_view, wbs_dataverse_connect_denied_notice), so every restriction applies to grids, direct links, media and update forms alike. A Business or Enterprise license switches it on; the Visitors tab under Dataverse Connect holds the settings. What it does:
- Visitor sign-in bound to a Dataverse contact. A WordPress user is matched to a contact by email (default), by a column holding the username, or by a custom filter. Optionally the contact is created on registration and kept in sync on profile changes; a Boolean column on the contact can refuse sign-in.
- My records. A
[wbsdvc_my_records]shortcode with the attributes of[wbsdvc_collection]that restricts a collection to records whose owner column points at the visitor's contact, plus[wbsdvc_my_profile]for an update-mode form over the contact itself,[wbsdvc_sign_in]and[wbsdvc_bound_value column="fullname"]for greetings. Blocks for my records and my profile. - Access rules per collection and form. Public, login required, or bound contact required, with an owner column and an own-only switch. Restricted collections fail closed: without a license they render the sign-in notice, never the data, and the restriction applies to the grid, direct links, media and update forms alike.
Without a Business license every access rule fails closed: restricted collections and forms render the sign-in notice, never the data, and the site otherwise behaves like the free plugin. Pricing is on the product page. The Enterprise tier (Entra External ID sign-in, 15 sites, response-time SLA) is planned after Business and available on request.
Support
Email support@woods.consulting from the address the license was issued to, with the site URL and the license state shown on the License tab. Priority support is part of every paid tier.