Differences

This shows you the differences between two versions of the page.

3.1.1:acl [2010/06/22 11:08]
Stephan Tittel
3.1.1:acl [2010/09/16 13:13] (current)
Line 1: Line 1:
 +====== Managing access permissions ======
 +docendo distinguishes between read and write access permissions to resources.
 +
 +**Read access** permission to a resource grants:
 +  * previewing the resource
 +  * finding it with the [[.:search|search function]]
 +  * importing the resource in the [[.:course_editor|course editor]] (if the resource is a course, section or question)
 +  * adding the resource to a [[.:section_editor|section]], [[.:glossary_editor|glossary entry]], [[.:table_editor|table]] or [[.:question_editor|question]] (if it is a media resource)
 +
 +**Write access** permission to a resource grants:
 +  * all permissions gained by having read access to it
 +  * editing the resource and its [[.:metadata_editor|metadata]]
 +  * [[.:version_control|creating new versions]] of the resource
 +  * managing the access permissions of the resource
 +
 +<box 751px round blue>{{.:screenshots:contextmenu_acl.png|Context menu / edit access permissions}}</box|Screenshot: Context menu / edit access permissions>
 +
 +<note tip>As a creator (i.e. owner) of a resource you automatically gain read and write access to it. Resources of other users that you have explicitly read or write permission on can be when filtering for the respective authoring group in the [[.:browser|Resource Browser]].</note>
 +
 +<box 230px right round blue>{{.:screenshots:acl_list.png?200|List of defined access permissions}}</box|Screenshot: List of defined access permissions>
 +
 +Depending on the configuration of your docendo server, there may be an instance-wide **general read permission** for all users to all resources. This specifically is useful to boost sharing and re-using of resources. If this general read permission is not set and you want to share a resource, you  explicitly have to create an access permission.
 +
 +To do so, go to the [[.:browser|Resource Browser]], locate the resource you want to share and from the actions menu of the resource, select the {{.:icons:key.png|Access permissions}} symbol (see topmost screenshot). You will then see the list of currently defined access permissions of this resource, which initially will be empty. This list enables you to edit or remove existing access permissions later on (see screenshot to the right). In order to create a new access permission, click on the {{.:icons:key_add.png|Icon: create access control }} icon above the list. This will open the access permission editor.
 +
 +
 +===== The access permission editor =====
 +
 +<box 230px right round blue>
 +{{.:screenshots:acl_edit.png?200|Access permission editor}}
 +</box|Screenshot: Access permission editor>
 +
 +When creating an access permission to a resource, you have the options to
 +  - set **whom** to grant access. This can either be a group of users or a specific user. The editor will show a drop-down list of all groups to choose from. If you want to grant permission to a specific user, you will have to know the corresponding user ID.
 +  - set **what** to grant (write access or not). Read access is assumed fix, otherwise you wouldn't want to create a permission.
 +  - let this permission be **recursively** created for all resources contained in the one you are currently granting access to. This of course only makes sense for resources that may contain other resources (e.g. courses or sections). For other resources (like media resources) this option has no effect.
 +
 +<note important>The option to create an access permission recursively for all contained resources traverses the resource only at its current state to find the contained resources. That means, that if e.g. you do this on a course and later on add a new section to this course, the new section will not be encompassed be the access permission. In this case, you can (after having added the section) re-open the access permission editor, select the "recurse" option again and save. The new section will then be affected be the permission.</note>
 
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki