---
title: Backend Module
url: "https://b13.com/products/vg-wort-pro-for-typo3/documentation/backend-module"
date: 2026-09-19
modified: 2026-09-19
lastUpdated: 2026-09-19
---

# Backend Module

![Black icon featuring a stylized letter "A" with sparkles, set against a light blue and green abstract background.](https://b13.com/fileadmin/_processed_/c/d/csm_sharing-ext-VGWortPro-S_9821f76de1.webp)

 Documentation
===============

 TYPO3 Extension “VG Wort Pro”
 Version 0.10.0 (2026-09-19)

  **Web > VG Wort**, one module with five views you pick from, plus the sync review it opens on its own. It always works on the site of the page selected in the page tree, and on **live data**—if you are in a workspace it says so rather than showing you something that is not what gets reported.

| View | What it is for |
|---|---|
| Pool Management | Pool statistics, CSV upload, ordering through the API, retiring a rejected pixel |
| Assigned Pixels | Every page that has a pixel, with CSV export |
| Pages Without Pixel | Content pages that have none yet |
| Authors | Author records, card numbers, verification |
| Text Registration | Prepare, review, submit; the sync and its discrepancy review |

   Elsewhere in the backend
--------------------------

**Web > Info > VG Wort Tracking Overview** lists all pages with their pixel codes. It comes from the free extension.

**Dashboard widget**—available when `typo3/cms-dashboard` is installed; without it the widget is simply not registered and nothing else changes. It shows pages without a pixel, unverified authors, texts below 1,800 characters, and the pool level, each linking into the matching module view. On a multi-site installation its settings (gear icon) set a custom title and restrict it to one site.

  ![The VG Wort status widget on the TYPO3 dashboard: four items needing attention, listed underneath — two pages without a counting pixel, one author needing verification, one page too short for VG Wort, and a pixel pool running low with six left.](https://b13.com/fileadmin/_processed_/5/f/csm_Documentation-Images-dashboard-widget_9600947a25.webp)

   Permissions
-------------

Six actions are gated by Page TSconfig. Admins have all of them.

| Permission | Lets an editor |
|---|---|
| `permissions.vgwort.upload_pixels` | Upload a CSV into the pool |
| `permissions.vgwort.order_pixels` | Order pixels through the API |
| `permissions.vgwort.submit_to_api` | Send a report to VG Wort |
| `permissions.vgwort.validate_author` | Verify a card number against VG Wort |
| `permissions.vgwort.sync_registrations` | Read existing reports back |
| `permissions.vgwort.deactivate_pixels` | Retire a pixel after a rejection |

     Copy

```
permissions.vgwort.upload_pixels = 1
permissions.vgwort.order_pixels = 1
permissions.vgwort.submit_to_api = 1
permissions.vgwort.validate_author = 1
permissions.vgwort.sync_registrations = 1
permissions.vgwort.deactivate_pixels = 1
```

  ###  How to delegate this sensibly

**Without any of these permissions an editor can still do most of the work**: open the module, assign pixels and authors, prepare and edit texts, maintain author records. What they cannot do is anything that leaves the installation or cannot be undone.

That is the line worth keeping. The three that deserve thought:

- **`submit_to_api`** sends something that can never be corrected. Give it to the people who know the text is finished.
- **`deactivate_pixels`** retires a pixel permanently. It exists because VG Wort’s rejection arrives by e-mail—so whoever reads that mailbox should hold this permission, and nobody else needs it.
- **`order_pixels`** spends nothing, but a pool of ten thousand unused pixels is its own kind of mess.

Page permissions apply on top of all of this: every action that reaches a page checks that the backend user may edit it, including the ones that reach pages without opening them.

 Backend Module