Blog

Gavin Pickin

December 15, 2017

Spread the word


Share your thoughts

At Ortus Solutions, we love the holidays, and we wanted to gift you a gift of developer productivity, we will share a few tips and tricks that will keep giving all year around. In this series we'll be giving you 12 ContentBox tips. Keep your eye out for other 12 tips of Christmas series on our blog, including a new one this year, 12 modules of Christmas on ForgeBox.

Day 2 - We're going to look at Permission Groups. In complex apps, managing permissions can be difficult. ContentBox has always given your Users a Role, which includes a set of permissions, and a la carte permissions. Recently, we have added Permission Groups, to allow you to assign groups of permissions to users, in addition to a singular role.

The entire permissions tab for authors has been revamped to allow you better visualization of rules and permissions.

Organizing Permissions

Roles might be setup as Administrator, Editor, User, but some editors might need permissions to some modules and not others. Now, you can setup Permission Groups for each job tasks. 

  • Media Uploader
  • Media Manager
  • Product Admin
  • Order Processor

Using permission groups allows you to easily assign multiple permission groups to users.
Its a useful feature, and we think it will make managing your users and permissions much easier.

Keep an eye out for the rest of our 12 tips of ContentBox Christmas.

 

Add Your Comment

Recent Entries

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.

That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.

Jacob Beers
Jacob Beers
June 04, 2026
One Language, Every Runtime: BoxLang Expands Beyond the Server

One Language, Every Runtime: BoxLang Expands Beyond the Server

Discover how BoxLang’s multi-runtime architecture helps developers build beyond the server with support for serverless functions, desktop applications, CI/CD workflows, Java integrations, containers, runtime management, and more.

Maria Jose Herrera
Maria Jose Herrera
June 04, 2026