Permission presets - UI and exportable presets

TYPO3 Association Community Budget Ideas 2025 Q3
1

Idea Title

Permission presets - UI and exportable presets

What is my idea about? What is the problem we are solving?

This idea continues the ACL development we initiated last year. Our goal is to introduce an improved, user-friendly UI for managing permission presets (ACL presets) in TYPO3.

Currently, defining and maintaining permission rules requires technical knowledge, which creates a barrier for non-technical users like editors or project managers. There’s also no easy way for editors to reuse or export ACL configurations across instances. We’re solving this by enabling users to create, manage, and export permission presets directly in the TYPO3 backend UI, making permission management intuitive, repeatable, and sharable without developer involvement.

What we want to achieve by the end of Q3 2025?

By the end of Q3 2025, we want to deliver:

  • Improvement to ACL module in the TYPO3 backend for creating, modifying, and organizing presets with cooperation of TYPO3 UX team.

  • Support for creating and exporting presets (e.g., YAML) to enable sharing and versioning.

  • Option to start from default templates or build custom presets from scratch.

  • A focus on accessibility for non-technical users, enabling project managers or editors to export and reuse in another TYPO3 instance or extension

What is the potential impact of my idea for the overall goal?

  • Agencies will benefit from reusable and deployable permission sets across projects.

  • Editors and PMs will gain autonomy over access management.

  • Open source contributors can share ready-made role presets as templates.

The solution promotes best practices in access control and supports TYPO3’s role as an enterprise-ready CMS with powerful administration tools.

How does my Idea align with the strategic goals for TYPO3 v14.

Strategic Goal 2 — Reducing Complexity: By introducing a clear, modern UI for ACL presets, we simplify permission management and make it accessible to non-technical users.

Strategic Goal 4 — Improve Customer-Oriented Communication: The UI promotes better backend experience and clearer workflows, aligned with best practices.

Strategic Goal 8 — High ROI Through Easy Maintenance: Exportable and reusable presets reduce setup time and simplify long-term maintenance and updates across projects.

Which budget do we need for this idea?

10000 Euro

My Name

Łukasz Uznański

1 Like
2

Hi @lukaszuznanski,

I wonder what the exact roadmap of this would be an how this differentiate to the budget request from last year, which resulted in existing core patch, already receiving a lot of work from the initial author as well as Stefan and myself. Shouldn’t we focus on finalizing this patch instead?

Best,
Oli

1 Like
3

This budget proposal aims to expand on the previously mentioned feature. Last year’s budget idea serves as the foundation for this initiative, and would be the best if it’s merged. In this idea, I would like to improve the accessibility and ease of use of preset management for non-technical TYPO3 backend users (until now, managing presets has required developer or integrator knowledge).

4

Just to make sure I understand correctly: this budget request builds on the patch from last year, right? If so, it sounds like finalizing that patch would be a necessary first step, since it’s not ready to be merged yet. Do you know who would take the lead on that work? And would the effort to complete the existing patch also be part of this budget?
Also, have you had a chance to talk to the initial author or anyone else who was involved in the original patch?

5

Yes, that patch should be merged ASAP. I’m in contact with the original patch author, but he said that the core team has taken over the patch and recommended not to continue working on it independently. Tomek, original author is willing to support with merge of that patch.