personnel for TYPO3

personnel organises staff directories as a dedicated data model

Team pages, contact lists and department directories are standard on corporate websites but cannot sensibly be maintained as content elements. Anyone managing 50 employees with name, role, photo, phone, email, LinkedIn, department and location needs a dedicated data model. The personnel extension delivers exactly that: a clean table for people, linked to departments and locations, served through configurable Fluid templates. On every mid-sized TYPO3 project with a corporate presence, this requirement comes up repeatedly, and personnel is one of the established solutions for it. Alternatives like tt_address often fall short because they lack the department structure, the filter logic and the clean frontend integration.

Typical use cases are law firms, agencies and universities

Law firms are a classic use case. A firm with 30 lawyers and 10 paralegals needs a team page with filtering by area of law (labour law, tax law, inheritance law), by location (Berlin, Munich, Frankfurt) and by role (partner, associate, trainee). personnel delivers the data model, and with a few Fluid adjustments the extension can be turned into a full firm directory. Each lawyer profile additionally contains the bar admission, memberships and published articles, so that clients can find the right contact at a glance.

Agencies and consultancies use personnel for team pages with short biographies, areas of expertise and contact links. Here it is less about filtering and more about presentation: large portraits, quotes, LinkedIn buttons and internal links to case studies the person has contributed to. The team page becomes a showroom, and personnel delivers the data model without every employee needing a dedicated content element.

Universities and research institutions have a different requirement: employees are often linked to institutes, chairs and research projects. personnel then becomes the master data model referenced by news articles, publication lists and events. The person does not only appear on a team page but also as an author in publications and as a contact on research projects. This turns the extension into a central person database used by several sub-extensions in parallel, delivering consistent profiles over many years.

Technical architecture is Extbase-based with relations to department and location

personnel defines three central tables: tx_personnel_domain_model_personnel, tx_personnel_domain_model_department and tx_personnel_domain_model_location. A person is linked through foreign_field or an MM relation to one or more departments, plus a location. The database schema therefore models a typical matrix organisation.

The fields on a person cover the standard attributes: title, first name, last name, role, short description, phone, mobile, fax, email, address, profile picture (FAL), social media links. Through TCA overrides, additional fields such as areas of expertise, certifications or languages can be added without forking the extension.

The plug-in renders through Fluid templates from the extension directory. The standard variants are list, detail and filter view. Anyone building on grid systems such as CSS Grid or Flexbox overrides the list template in their own package. For filtering and search, the extension uses Extbase repositories with query builder filters that can be configured through TypoScript. A typical Gosign implementation offers a full-text search over name and role combined with select filters for department and location, so that users can find the right contact among 200 employees in a few clicks.

Common problems involve GDPR (UK: UK GDPR), image rights and multilingual content

The first and most important support topic is GDPR. Employee data is personal data, and publication requires either consent or a legitimate interest. Anyone working with photos, direct dial numbers and private mobile numbers needs a clean process: document consent, on-off switch per person, automatic removal after the person leaves the company. personnel does not ship an audit log by default, but the workflow can be modelled with custom forms and an additional consent field. On departure from the company, the record should not simply be deleted but deactivated through a soft delete mechanism, so that old news articles still resolve correctly.

The second topic is image rights. Profile pictures live in FAL and are delivered through variants per display. What matters is that the copyright and the consent of the employee are documented, especially when the image is also used as a teaser in news articles or on social media. We recommend consistently maintaining the FAL fields “photographer” and “licence”.

Thirdly, multilingual content is a practical problem. A person has one name, but their role and short biography differ between languages. personnel supports the TYPO3 standard for translations, but many projects forget to localise the department and location records as well, which leads to mixed language output.

Migration to TYPO3 v12 requires an Extbase update and a TCA review

personnel is available in the TER for several TYPO3 versions. On the upgrade of a v10 or v11 installation, the Extbase repositories have to be moved to the current persistence API, and the TCA structure should be checked for type incompatibilities (especially with “passthrough” and “none” fields, which are validated more strictly in v12).

Gosign often migrates personnel installations as part of a team page refactor. In the same step, we check whether the dataset can be lifted to a more modern Person schema (with JSON-LD markup), whether filter and search scale with large datasets and whether the team page is delivered responsively and accessibly. For projects with very large datasets (several thousand people), it is also worth looking at indexing and lazy loading, so that the list view does not become a bottleneck on mobile devices. For particularly complex team structures, we occasionally replace personnel with a custom Extbase model, when the standard field structure does not suffice or a connection to an external HR system is required.