---
url: 'https://dxpr.com/hc/documentation/learn-dxpr-builder/licensing/profiles'
title: 'Builder profiles | DXPR'
author:
  name: docs-sync
  url: 'https://dxpr.com/users/docs-sync'
date: '2026-10-23T14:31:17+00:00'
copyright: 'Copyright DXPR. All rights reserved.'
type: article
summary: 'Limit elements, blocks, views, templates and icon sets per role'
tags:
  - 'Control who can do what'
image: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
published: true
og:
  site_name: DXPR
  updated_time: '2026-10-23T14:31:17+0000'
  'image:alt': 'DXPR, powered by Drupal: AI-powered Drupal for marketers.'
schema:
  '@context': 'https://schema.org'
  '@graph':
    -
      mainEntity: {  }
    -
      '@type': TechArticle
      headline: 'Builder profiles'
      description: 'Limit elements, blocks, views, templates and icon sets per role'
      image:
        '@type': ImageObject
        url: 'https://dxpr.com/themes/custom/dxpr_com/images/dxpr-share-card.jpg'
        width: '1200'
        height: '630'
      datePublished: '2026-10-23T14:31:17+0000'
      dateModified: '2026-10-23T14:31:17+0000'
      author:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
        url: 'https://dxpr.com/'
        logo:
          '@type': ImageObject
          url: 'https://dxpr.com/themes/custom/dxpr_com/dxpr-logo-dark.svg'
          width: '1348'
          height: '501'
      publisher:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
        url: 'https://dxpr.com/'
        logo:
          '@type': ImageObject
          url: 'https://dxpr.com/themes/custom/dxpr_com/dxpr-logo-dark.svg'
          width: '1348'
          height: '501'
      mainEntityOfPage: 'https://dxpr.com/hc/documentation/learn-dxpr-builder/licensing/profiles'
      articleSection: 'Control who can do what'
    -
      '@type': WebPage
      '@id': 'https://dxpr.com/hc/documentation/learn-dxpr-builder/licensing/profiles'
      description: 'Limit elements, blocks, views, templates and icon sets per role'
      breadcrumb:
        '@type': BreadcrumbList
        itemListElement:
          -
            '@type': ListItem
            position: 1
            name: Home
            item: 'https://dxpr.com/'
      publisher:
        '@type': Organization
        '@id': 'https://dxpr.com/#organization'
        name: DXPR
      inLanguage: en
---
[Help Center](/hc)/[Documentation](/hc/documentation) /[Learn DXPR Builder](/hc/documentation/learn-dxpr-builder) /[Manage the site](/hc/documentation/learn-dxpr-builder/manage) /[Control who can do what](/hc/documentation/learn-dxpr-builder/manage/access) # Builder profiles.

Limit elements, blocks, views, templates and icon sets per role

 Learn DXPR BuilderManage the siteControl who can do what

   ## In this guide

 Related guides

- [User profiles](/hc/documentation/learn-dxpr-builder/admin/user-profiles-admin)
- [Managing licences](/hc/documentation/learn-dxpr-builder/licensing/managing-licences)

A builder profile decides what people with certain roles see in DXPR Builder. You can give content editors a short list of elements and keep everything for site administrators. Profiles change what editors see, not how many licences you use. This page explains how profiles work; the [User profiles](/hc/documentation/learn-dxpr-builder/admin/user-profiles-admin)page shows how to create one.

## What a profile controls

- **Start editor when page loads**: whether the editing controls show at once, or only after a click on the eye icon of the main container.
- **Control bars**: where editors find the control bar of an element.
- **Elements**: which elements the element picker offers.
- **Blocks** and **Views**: which Drupal blocks and Views displays editors can place.
- **Page templates** and **Global user templates**: which templates editors can insert.
- **Icon sets**: which icon sets the icon pickers offer.
- **Text editor buttons (inline editing)** and **Text editor buttons (modal editing)**: the text editor toolbars.

Newly created blocks, views displays and templates stay hidden from a profile until you tick them, or tick **Check/Uncheck all** for that group.

## Which profile applies

Each profile lists the **Roles** it applies to. When an editor opens a page, DXPR Builder walks the enabled profiles from the lowest **Weight** to the highest. The first profile that shares a role with the editor applies. If no profile matches, the editor sees every element, block, view, template and icon set.

A field can also force one profile for everyone who edits it: the **Editing Profile** setting of the **DXPR Builder** formatter, under **Manage display**of the content type.

## Profiles and licences

Profiles do not lower your licence count. Every account with the **Edit with DXPR Builder**permission uses a licence, whatever its profile shows. To stop an account from counting, take away the permission or exclude the account, as [Keep your editors within your licence](/hc/documentation/learn-dxpr-builder/licensing/managing-licences)explains.

## Plan a profile per role

- **Content marketers** build pages from approved parts: give them Text, Image, Button, Card and Video, the page templates you approve and a short inline toolbar.
- **Webmasters** set up layouts: tick **Check/Uncheck all** in every group, so new blocks, views and templates appear for them automatically.

Managing profiles needs the **Administer dxpr builder profile** permission.

## What's next?

- [User profiles](/hc/documentation/learn-dxpr-builder/admin/user-profiles-admin): create and edit a profile
- [Keep your editors within your licence](/hc/documentation/learn-dxpr-builder/licensing/managing-licences): control who uses a licence