Permissions
DXPR Builder defines three permissions in
dxpr_builder.permissions.yml. Grant them at People >
Permissions (/admin/people/permissions). Two admin pages and the
media browser route use core permissions instead; they are listed
below.
Permission reference
| Permission | Machine name | What it unlocks |
|---|---|---|
| Administer DXPR Builder configuration | administer dxpr builder configuration |
The DXPR Studio menu and the General Settings, AI, Content Items, Migrations and User Licenses pages |
| Edit with DXPR Builder | edit with dxpr builder |
The editor on content the user may update, the editor's AI routes and the user's own editor settings |
| Administer dxpr builder profile | administer dxpr_builder_profile |
The User Profiles page: create, edit and delete builder profiles |
The first two are marked restrict access, so the Permissions page
shows a security warning next to them. The Administrator role has
every permission, as with any module.
Permissions from Drupal core that the module checks:
| Permission | Where |
|---|---|
administer site configuration |
The Page Templates and User Templates admin pages |
view media |
The Media Library dialog the editor opens (/dxpr_builder/media-library) |
Role recommendations
Content editors
Grant Edit with DXPR Builder. Editors also need permission to update the content they work on, such as Basic page: Edit any content. The elements, templates and text editor buttons they see come from the builder profile assigned to their role.
Site builders and webmasters
Grant Edit with DXPR Builder and Administer dxpr builder
profile. They can then decide what each role sees. The DXPR Studio
menu needs Administer DXPR Builder configuration, so without it
they reach profiles at /admin/dxpr_studio/dxpr_builder/profile.
Administrators
Grant all three, plus Administer site configuration for the template pages. Administrators manage the settings, AI, licences and templates.
Profile-based limits
Builder profiles narrow what a role sees inside the editor. Create
them at DXPR Studio > DXPR Builder > User Profiles
(/admin/dxpr_studio/dxpr_builder/profile) and assign them to roles
under Roles on the profile form. A profile sets:
- Elements: the content and layout elements in the picker;
- Blocks and Views: the Drupal blocks and views offered as elements;
- Page templates and Global user templates;
- Icon sets;
- Text editor buttons (inline editing) and Text editor buttons (modal editing);
- Start editor when page loads;
- Control bars: where editors find an element's control bar, unless they choose for themselves under Editor settings;
- Weight: when several enabled profiles share a role, the one with the lowest weight applies.
See User profiles for details.
Where the editor appears
Permissions alone do not show the editor. It runs only on fields whose view display uses the DXPR Builder formatter. Set it at Structure > Content types, then Manage display for the type. See Content types.
Licences
Every account in a role with Edit with DXPR Builder counts as a licence, and user 1 always counts. Accounts are counted by email address across the sites that use your product key. To free a licence, use Exclude from editing at DXPR Studio > DXPR Builder > User Licenses.
See User licences for licence management.