User management

The window called ‘Users’ is divided into four panes:

  • Users
  • Domains
  • Models
  • Libraries

This is the ‘User management’ window:


In the left column, under ‘Users’, you can create users who are to access the models. By right-clicking in the column “Users” you can choose “Add user”. The right mouse button menu is also used to edit or delete users. You also can use the buttons on the top of the column.

After having created a user you can set his or her user name (“login”) and password (“Password”) and his or her full name (“FullName”). You need to provide the email address of the user to let the user be able to use the ‘forgot password’ functionality.

The option “Own models’ shows how many different models the user can publish to the web.

The Role defines what a user can do:

  • guest: may access models
  • user: may publish, access and administer a number of own models
  • manager: may publish and access models and may access sessions from other users of those models
  • administrator: all rights except viewer rights
  • viewer: view Management Information System (MIS) data
  • vieweradmin: same as viewer, but can also force shared Management Information System Dashboard (MID) views with other viewer’s

For a more complete overview of the roles, you can go here: User Roles

User dialog
User dialog


The right-hand column, under ‘Models’ allows you to manually add models to be available on the web. You may also edit, delete or clone models.

In the next window you may add a Description for the model and specify where the model resides physically (‘Path’).

Model dialog
Model dialog

Here are some advanced and optional settings:

is an option only used when communicating with other applications or databases. Press Update if you have selected the file.
Form template
gives the possibility of styling the model in the browser with a custom template. Defaults to ‘baseform.html’ in the HTML-directory.
Jump template
is a similar function is served by ‘Jump template’, defining the structure of the jumplist the modelling author has defined (e.g. as a radiogroup versus a drop-down list). Defaults to ‘jumplist.txt’ in the HTML-directory.
This options tells the server how to translate dates, e.g. 1 to January or Janvier.
Hide from menu
If you do not want a model to show up in the model-menu of a user.
Automatically generate jumplist
Each time a new case is started, the server tries to run through the model without giving any inputs. If your model accepts that, the jumplist is automatically created. After the run, the case starts at the beginning.
Force restart with new session
Force that each time a case is opened, it starts at the beginning.
Save mode
The save mode is set in the main settings; here you can override that setting for just this model.
Maintained by
lets you manually assign an ‘owner’ to the model. The owner may update the model using Project > Publish in the Berkeley Studio and may get an overview of all cases that have been made on the basis of  the model. When ‘nobody’ is listed as the maintainer nobody may update the model by means of ‘publishing’. When a model has initially been published the user publishing the model will also be the maintainer until changed here.
lets the model be anonymously accessed. This option can also be set if you publish a model with the Studio.


The libraries are stored on the server, they can be managed just like models. Libraries have a description, a file and an owner.




The middle pane of the 'User management’-window lets you define which users have access to which models. This is done by domains. A domain is just a layer to help maintain access. You can add users and models to a domain. Each user has access to all the models in the domain. Just click on the arrows to add or remove users and models from a selected domain.

If a user is the owner of a model, he still gets access, no matter how the domains are set.

If a model is anonymous, all users can access that model, no matter how the domains are set.

CSV Import

Import a domain full of users from a CSV file. The first line of the CSV is ignored. The CSV-file needs to be saved using the comma as a separation character, with columns being username,email,fullname,domain,password.

NOTE version 4.5 of the Berkeley Webserver did not expect an emailadres, so it was: username,fullname,domain,password back in those days


If you press this button, you can select a login.xml file from another server. You can select all the desired users, and they will be imported, as long as the username does not already exist.


You can also generate a bunch of users:

Randomly generate users
Randomly generate users

In the dialog for generating users, you can enter a prefix to be used for username and password. Fill in the number of users in the field labelled ‘repeat’. If you fill in a filename next to ‘Export to’, the created users will be stored in a CSV file of that name next to the server, as a list of comma-separated username and password, i.e. username,password.