of the object for which you want to define a new role.
If this is a folder, the new role also applies to the contents of the folder.
Some roles in BSCW are already predefined by the system such as Manager, Member or Restricted Member. These roles may be assigned to users for all BSCW objects and may therefore be used everywhere.
In addition, you can define new roles if you need them for a specific application. Examples would be teacher, student or guest. To do this, proceed as follows:
•In the Members menu, select of the object for which you want to define a new role.
If this is a folder, the new role also applies to the contents of the folder.
•In the 'New role' form, enter the name for the new role. Now you define which access rights future role owners should have and which not. You have two options for this:
•You can fall back on roles that are already defined in the current workspace. To do this, select a role template from the list of existing roles and check the box next to it. You can then adapt the role template to your needs with [Change role...].
•You can also compile the access rights of the new role completely new. To
do so, deselect the use of a role template and mark the action groups to which
the role owners should be authorized. All BSCW actions that are subject to
access control are divided into action groups. In the following, the action
groups are listed with some typical
examples:
Read: Open, Copy
Read (erw.): More
information
New:
Upload Document, New Note, New URL
New (erw.): New folder, New discussion
forum
Modify: Change Properties, Lock,
Put under version control
Modify (Enhanced): Remove, Delete
versions
Share: Add
member, Remove member
Share
(Enhanced): New Role, Change Role, Upload by email
Edit: Cut, Edit note
Blog: New blog entry, Change blog
Select [Change Role...] to view all
action groups in detail - those you have checked as well as those you have not
checked.
•Confirm with [OK] if you are satisfied with the action groups you have selected or click on [Change role ...] to make necessary fine adjustments to the newly defined role on action level (cf. below under ).
Self-defined roles are limited to the scope of the object in question and can only be used there.
Both predefined and self-defined roles are called normal roles because they can be assigned without restrictions in their scope. In addition, there are also special roles that can only be assigned to other users in a restricted manner or inherit in a special way. Only system administrators can redefine (or delete) special roles. Examples of special roles are owner and creator.
All roles (normal roles as well as special roles) can be changed for any objects.
•To do this, select 
in the Members menu of the object for which you want
to change roles.
•Select the role you want to change and confirm with [OK]. At this point, any role changes already made can also be undone in their entirety for the object with [Reset all role changes].
•In the following form, select those actions that should be allowed for the changed role and confirm with [OK]. If it is a self-defined role, it can also be deleted here with [Remove role].
Note: If the action 'Cut' is allowed for a role, the action 'Remove' is also automatically allowed, even if it has not been checked. This is because an object can be removed from the clipboard without any further restrictions after it has been cut. The action 'Cut' therefore indirectly includes the action 'Remove'.
The changed role definitions apply to the scope of the object where they were changed, but not outside! This means that there can be different roles with the same name in different scopes, i.e. members in two workspaces may well have different access rights.