The Basic Meeting List Toolbox

BMLT Roles

When adding new users to the BMLT system it is useful to consider the hierarchical permissions structure underlying the design.

There are several specific roles to configure in the BMLT: Server Administrator, Service Body Administrator, Meeting List Editor and Observer.

Let’s look at what each role is for and the corresponding privileges or permissions those roles have.

Here is an interactive page that will illustrate the roles of various admins.

Server Administrator

This role has the most responsibility initially to set up the Service Body Administrators and other users within the system. This is the only user that has permission to create users and Service bodies. It is also the only user that can edit formats.

They may also be responsible for adding Regions and Areas initially. As time passes it may become necessary to rename or even remove Regions and/or Areas. There may also be the occasional requirement to add more administrators, users and more likely to reset the existing user’s passwords.

The Server Administrator has full permissions for all of the server. It is a very powerful login that should not be used for regular meeting list administration.

Service Body Administrator

When setting up a meetings list structure it is usually necessary to break the meetings up into specific Areas.

The Service Body Administrator is the person (or persons) responsible for adding/removing the Region’s Area committees to which meetings will be added as part of the service structure.

Therefore the Service Body Administrator has the ability to add new service committees, be they regional or area level and set them up in a hierarchy as required.

It is possible to assign a Service Body Administrator as a “Guest” (by including them via a checkbox in the Service Body Administration screen). In this case, the Service Body Administrator cannot edit the actual Service Body Information, but they can edit all of the meetings in that Service Body.

Service Body Administrators can edit meeting data, and, if assigned as a Principal Administrator, Service body data. Their ability to edit is restricted by the permissions assigned to them.

Service Body Observer

This is used for Service Teams, such as Helpline volunteers. Observers are allowed to see fields marked as “Hidden,” and that do not show up in regular meeting searches. For example, you may have a contact associated with meetings. You don’t want this to appear in regular searches (indeed, in some nations, it would be illegal to display personal data). However, Helpline volunteers may be empowered to contact these people and ask for assistance with newcomers.

If the Helpline volunteer is an Observer, then they can get the contact for that meeting.

Observers cannot modify any information. They can only see hidden data, as assigned by their affiliation with a Service body.


PDF Document That Outlines How the Various Structures and User Roles Work.

(NOTE: The “Meeting Editor” role no longer exists. It was determined to be useless and confusing)