User Groups

part of the ArsDigita Community System by Philip Greenspun

The Big Idea

There are many applications of the ArsDigita Community System in which we need to lump users together. If we accomplish that lumping with a common mechanism, then we can build common user and admin tools that don't have to be separately debugged for each installation.

Data Model Tour

These are the tables that hold user group information:

System-defined Groups

There are a bunch of places within the ArsDigita Community System where users need to be lumped together. Sadly, some of these subsystems predate the users group module and use their own mapping tables.

An example of something done consistently, however, is the recording of whether or not a user is a system administrator of this site (tested with the Tcl procedure ad_administrator_p). There is a user group type of "system". One group of this type is pre-defined: "administrators".

Example Applications

Cisco sets up an ArsDigita Community System to support customers who've purchased routers. Cisco would create a user group type of "company" and then a user group of that type for each customer, e.g., "Hewlett Packard" would be a user group and all the hp.com users would be members of that group. The grouping mechanism would let Cisco ask for "all trouble tickets opened by HP employees". The grouping mechanism would let Cisco offer online prices with the HP discount to anyone logged in who was recorded as a member of the HP group.

A university running one big ACS would have user group types of "committee" and "course". All the administrators on a committee would be in a user group of type "committeee". All the students and teachers in a particular course would be lumped together in a user group and could have a private discussion group. The teachers would have a different role within the user group and hence would have more access privileges.

Group login

More Information


philg@mit.edu