Agencies & network · Advanced · 0:45 min
Packages & features per project
Presets full / content / minimal, individual features, blocks and integrators.
Goal
Every website gets exactly the feature set the project calls for – controlled by the agency, not the client.
Prerequisites
- Access to the installation’s configuration (SFTP/SSH or deploy).
Step by step
Transcript: every step matches one subtitle in the video.
- Every website has a feature set: preset “full”, “content” or “minimal” plus individual switches.
- The agency sets it in config/sites/{website}.php – customers cannot change it.
- In every website, Grundeinstellungen › Systeminfo shows what is switched on or off there.
- Disabled features lock menus, permissions, API and MCP – even for the website’s own admins.
- All switches and examples: technical documentation › features & extensions.
Commands & configuration
// config/sites/kunde.php (Hauptwebsite: config/config.local.php)
'preset' => 'content', // full | content | minimal
'features' => ['data.schema' => false, 'languages' => true],
'blocks' => ['deny' => ['video']],
'integrators' => ['team@agentur.de'], // diese Konten sehen immer alles
Tips & pitfalls
Tip
Network accounts and integrators always see everything – use a normal account to test the client’s view.
Watch out
Locked block types stay editable in existing pages but cannot be inserted again.