User Roles

There are currently six roles a user can have within the Berkeley Bridge server. A user may only have one role.

The roles explained:

A guest role

may only access models which are either set to anonymously accessible, or are within a domain that the user is also connected to
may not save sessions (cases) on the server, and has no access to any other user’s sessions
may not publish any models
may not access the webadmin
may not view any Management Information System (MIS) data stored.

A user role

may only access models which are either set to anonymously accessible, or are within a domain that the user is also connected to, or have published themselves
may save sessions (cases) on the server (if the server allows sessions at all), but has no access to any other user’s sessions
may publish models, as long as they haven’t reached the quota set in the ‘Own models’ field
may access the webadmin, but will be limited to only administrating their own account
may only view Management Information System (MIS) data stored during their own sessions.

A manager role

may only access models which are either set to anonymously accessible, or are within a domain that the user is also connected to, or have published themselves
may save sessions (cases) on the server (if the server allows sessions at all), and may access any other user’s sessions
may publish models, as long as they haven’t reached the quota set in the ‘Own models’ field
may access the webadmin, but will be limited to only administrating their own account
may only view Management Information System (MIS) data stored during their own sessions.

An administrator

may only access models which are either set to anonymously accessible, or are within a domain that the user is also connected to, or have published themselves
may save sessions (cases) on the server (if the server allows sessions at all), and may access any other user’s sessions if the server has been set to allow it
may publish models, as long as they haven’t reached the quota set in the ‘Own models’ field
may access the webadmin with full access
may only view Management Information System (MIS) data stored during their own sessions.

A viewer

may not access any models or sessions
may not publish any models
may not access the webadmin
may view all Management Information System (MIS) data stored by any other user on models which the viewer has access to via a domain.

A vieweradmin

may not access any models or sessions
may not publish any models
may not access the webadmin
may view all Management Information System (MIS) data stored by any other user on models which the viewer has access to via a domain
may create shared custom views in the Management Information System Dashboard (MID) forcing other viewers on the same server to see that view. They can even force the view to override other user’s default view.