For a fictional community workshop page, contributors need headings, lists, links, and a divider before the accessibility instructions. They do not need permission to paste an entire scripted web page. Configure the permitted task, then test it with the contributor's actual role.
Identify the format used by the content field
Open the content edit form and note the format selected beneath the formatted text field. A site can have several formats with different permissions and filters, so an administrator's editor may differ from a contributor's editor.
An administrator can review them at:
Configuration > Content authoring
> Text formats and editors
/admin/config/content/formats
Configure the format the workshop field actually uses. Changing a different format can leave the field unchanged while unexpectedly affecting other content. Drupal's configuration guide uses Basic HTML as its example; your installation may have different format names. Configuration steps
Align the toolbar with permitted content
Review the selected editor and its active toolbar. Modern Drupal installations can use the core CKEditor 5 module for visual rich text editing. Check your site's installed version and available plugins before applying instructions written for CKEditor 4. Core CKEditor 5 module
In the workshop example, the editor must be able to create a divider, and the text format must permit the resulting <hr> element. The official configuration walkthrough demonstrates adding the horizontal-line button and checking that <hr> is present in the allowed HTML settings. Its screenshots and editor label may differ from your installed version.
Save the format configuration, then return to the actual content field. Do not assume that a source-editing control, if available, turns off the format's filtering. The intended saved result is simple:
<h2>Before you arrive</h2>
<p>Bring the booking confirmation.</p>
<hr>
<h2>Accessibility</h2>
<p>Use the entrance beside the courtyard.</p>
These are illustrative workshop instructions. Replace them with confirmed venue details before publication. Check that your chosen heading level fits the surrounding page and that the divider adds a useful separation rather than carrying information on its own.
Test with the role that will maintain the page
Each text format has an associated permission. A permissive format should only be available to users trusted to supply that content. Granting Full HTML broadly to make one missing element survive changes the site's content boundary far beyond this workshop page. Format permissions and filtering
Use a development environment or a dedicated test account with the intended contributor role. Confirm that it can select the approved format, create the supported divider, save the draft, and reopen it. An administrator successfully saving markup does not establish that the contributor can perform the same task.
If the editor lacks the control, inspect the toolbar configuration and installed plugin. If the control works during editing but its markup disappears after saving, inspect the format and filters. If saved markup remains but the divider is invisible on the rendered page, inspect the theme's styling. Those observations point to different layers of the system.
Keep field content separate from theme templates
Text-format settings affect formatted content fields. Twig templates and their attribute objects belong to the theme layer; Drupal Twig attributes covers that separate job. Editing a page's body is not the place to change the site's wrapper markup or global layout.
Finish with the saved workshop page open as an ordinary reader. Check the accessibility instructions, the entrance description, the links, and the visible separation. Keep the authoritative content in Drupal, where the assigned contributor can reopen and maintain it under the intended format.