4.7.4 Defining and re-defining roles
Some roles in BSCW are already predefined by the system, e.g. Manager, Member or Anonymous Member. These roles may be applied to all BSCW objects and thus may be assigned anywhere.
In addition, you may define new roles if you need them for a specific application. Examples would be Teacher, Student or Guest. You proceed as follows:
- Choose
in the action menu of the object, for which you want to define
the new role. If this object should be a folder, the new role is also
valid for all objects contained in the folder. - Enter the name of the new role in the ‘Add Role’ form. Choose a template for your new role and/or select certain action groups to be allowed for the new role by checking the respective check boxes.
- Confirm with [OK] or click [Edit Role ...], to carry out more fine-grained modifications of the new role on the level of single actions (cf. ‘Edit Role’ further below).
User-defined roles are restricted to the scope of the respective object and may only be used within this scope.
Predefined as well as user-defined roles are called normal roles since they may be assigned without restrictions within their respective scope. Besides, there are also special roles that may only be assigned to users with restrictions or that are inherited in a special way. Only system administrators may define (or remove) special roles. Examples for special roles are Owner and Creator.
All roles (normal roles as well as special roles) may be redefined.
- Choose
in the action menu of the object for which you want to change role
definitions. - Select the role that you want to change and confirm with [OK]. At this point, you may also reset all role changes carried out for this object so far by clicking [Reset All Roles].
- In the subsequent form, you select all actions that should be allowed for the changed role and confirm with [OK]. In case the edited role is a user-defined role, you may delete the role definition altogether by clicking [Remove Role].
The changed role definitions are valid within the scope of the object where they have been changed, but not outside! This means that there may be different roles with the same name, but different scopes, i.e. Members in two different workspaces may have quite different access rights.