---
title: Configure WYSIWYG toolbars
slug: editorial/configure-wysiwyg-toolbars
createdAt: 2026-10-30T09:10:51.514Z
---

## Summary

Admins can define their own toolbars for WYSIWYG fields (ACF field type "Wysiwyg Editor"), so editors only see the formatting buttons a field needs — e.g. only bold, italic, lists and link in an infobox.

## Preconditions

- Have the 'Administrator' role in your Purple Hub
- Have the 'ACF' plugin enabled in your Purple Hub

## How to configure

1. Go to **ACF** → **WYSIWYG Toolbars**.
2. Click **Add toolbar** and enter a **Name**, e.g. "Infobox".
3. Below **Buttons**, select the buttons the toolbar should show. Drag the selected buttons to change their order, and add a **Divider** to separate groups of buttons. A toolbar without buttons gives an editor without a toolbar.
4. Click **Save**.
5. Below **Preview**, check how every saved toolbar looks to editors, followed by the builtin toolbars "Full" and "Basic". The previews update after saving; nothing typed into them is stored.
6. Go to **ACF** → **Field Groups**, open the field group with the WYSIWYG field, and select the toolbar in the field's **Toolbar** setting. Your own toolbars are listed as "Custom: …" next to "Builtin: Full" and "Builtin: Basic".

Besides the WordPress buttons, the list offers buttons that active plugins add to the editor, e.g. **Editorial comment (Oasis Workflow)**. If such a plugin is deactivated later, its button stays in the toolbar, marked "(currently not available)".

::Image[]{src="https://api.archbee.com/api/optimize/ygR6KtT9QI_R0u3uKTJsm/F8CB9BYuMn5hHjG4erTmS_archbee-hub-1860-01-toolbars-page.png" size="80" caption="configuring custom toolbars" isUploading="false" width="1310" height="520" darkWidth="1310" darkHeight="520" showCaption="true"}

::Image[]{src="https://api.archbee.com/api/optimize/ygR6KtT9QI_R0u3uKTJsm/G4tDHtqdFOYDLN6_IW8nF_archbee-hub-1860-02-preview.png" size="80" caption="previews of custom toolbars" isUploading="false" width="1310" height="580" darkWidth="1310" darkHeight="580" showCaption="true"}

## Rules for toolbars

- The name identifies the toolbar in every field that uses it. A toolbar that is still used by a WYSIWYG field can therefore not be renamed or removed — switch the fields to another toolbar first. The page lists the fields that still use it.
- "Full" and "Basic" are reserved, names must be unique, and a name needs at least one letter or digit.

:::hint{type="warning"}
**Warning:** A toolbar only hides buttons, it does not restrict the content: keyboard shortcuts and pasted text still bring in other formatting, and the Text tab accepts any HTML. For fields whose formatting must stay restricted, also set the field's **Tabs** setting to "Visual Only".
:::

## Copying toolbars to another Purple Hub

In **Settings** → **Copy Setup**, the toolbars are a set of their own, **WYSIWYG Toolbars**. Copy it together with the field groups whose fields use these toolbars. An import never removes a toolbar that a field of the target Purple Hub still uses.