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

BoxLang 3.4 Blog Series Part 2: Revamped Human in The Loop HITL

BoxLang 3.4 Blog Series Part 2: Revamped Human in The Loop HITL

HumanInTheLoopMiddleware used to do everything itself: decide which tool calls needed approval, present the request, and wait for a decision. In 3.4.0, that logic has been pulled apart into a real subsystem, and the piece developers will feel the most is that a human's "always allow this" now actually means always.

Luis Majano
Luis Majano
September 05, 2026
BoxLang 3.4 Blog Series Part I: Gateways, One Interface, Any Platform

BoxLang 3.4 Blog Series Part I: Gateways, One Interface, Any Platform

Every AI agent that touches something real eventually needs a human in the loop. Someone has to approve the delete, confirm the wire transfer, or just say "go ahead" before a tool call runs. The question BoxLang AI 3.4.0 answers is: approve it how? A terminal prompt? A webhook? A Slack button?

Luis Majano
Luis Majano
September 04, 2026