Examples Templates Store Pricing Docs Turbo CSS Blog Boomla WishList Introducing Turbo UI Named buckets Turbo CSS is Tailwind CSS on steroids Introducing Turbo CSS, the most advanced web-design language Calculate how much storage you use Better login system Collaboration settings Filesystem and Database are not cutting the problem space right What I'm working on 64bit File node IDs New how-to videos Creating buttons gets easier Introducing reusable components HTTPS by default Introducing the Boomla Theme CDN for faster pageloads Write your own website builder on top of Boomla On On composition Shared admin access A fresh config editor Building a multi-purpose theme A filesystem to replace your CMS New file link type: scope Mobile editing support Inline file wrapping changed Package sandboxing New PHP-like JavaScript engine [sjs-4e] Send emails to the website owner New JavaScript engine [sjs-4] A better editing experience New email service provider Glossary and other changes New panel changes Improved registration flow Boomla goes multiplayer Using local dev tools Why Boomla doesn't need Git File Panel Let's build a community Automatic updates Improved sjs-3 API New Frontend CSS modules Work offline with Boomla Faster page loads via caching Drag & drop supercharged Supporting CommonJS modules  Paranoid about loosing data IDE usability improvements Simple App install flow Meetups in Budapest Goodbye broken links Flow control from user space Customizing apps Contextmenu support for apps Deprecating the .Class file Hello Changelog Embedding 3rd party plugins Introducing Tools Installing apps just got amazing Public beta Host on our servers Simple deploy with push/pull Version Control for the Web 350M files on a 1TB disk 2 weeks in review
Control Panel

Shared admin access


As of now, you can share admin access to a website branch, website group or your entire account.

There is no user interface yet for this on the Control Panel, so you have to shoot me an email and I'll manually set it up for you. That's because it was an urgent requirement by the heaviest Boomla developer Bernát, and I wanted to provide him with a solution but I really have my focus elsewhere for now. I'll roll out a user interface once it's actually used.


Role based

It is a role based access control mechanism.

There is the account admin role, which let's you basically do anything the account owner can, except for changing their email and password, or removing the account. An account admin can create websites, change their settings, install packages on any of them, etc.

The website group admin role can do anything within the website group. It can edit the websites, install packages, work with branches and change the website settings. It can not remove the website group itself though.

A branch admin works similarly, but bound to a single branch. It can edit the website (branch), install packages, change its settings, but it can not create new branches or remove the branch.

If your use case is not covered by the above roles, get in touch so we can create a new role for you.


you can follow me on Twitter