Licensing overview
Your DXPR Builder subscription sets two limits: how many people can edit with the builder and how many content items they can build. You need a product key from dxpr.com, also on the free tier. Use the table to find the page for your task.
| I want to ... | Use | Needs |
|---|---|---|
| activate DXPR Builder with my product key | General settings | a product key from dxpr.com |
| see who uses a licence, or free one | User licences | the Administer DXPR Builder configuration permission |
| keep my editors within my subscription | Managing licences | access to People > Permissions |
| use one product key on several sites | Multi-site licensing | the same key on every site |
| know what each tier includes | Feature comparison | nothing |
| give each role its own editor options | Builder profiles | the Administer dxpr builder profile permission |
| fix a licence warning or a rejected key | Licence and product key errors | the message you see |
How licensing works
DXPR Builder counts two things:
- User licences: every Drupal account with the Edit with DXPR Builder permission uses one licence. Blocked accounts and accounts excluded from editing do not count. One email address counts once, however many sites it edits on.
- Content items: every entity, and every translation of it, whose content type or block type shows a field with the DXPR Builder formatter. Items of those types count even before anyone edits them.
The free tier allows one editor and 100 content items. The one editor is the first account of the site, the one created during installation. Paid tiers raise both limits; see dxpr.com/pricing for the current plans.
When a limit is reached, the editor does not load for the extra editors or content items, and a warning explains why. Visitors still see every published page.
What the product key contains
The product key is a JSON Web Token. It carries your DXPR account and your tier. The limits themselves come from dxpr.com: your site asks for them once a day, or every 30 minutes while that check fails. The editor also sends the key each time it loads from the DXPR CDN, so an invalid key stops the editor at once.
Getting a product key
Sign in at dxpr.com/getting-started to find your product key. The Find your product key link on the settings page goes there too. Then paste the key in the License section of General settings.
What's next?
- Managing licences: keep your editors within your subscription
- Licence and product key errors: solve licence warnings