(Article content moved to a template) |
(Template contents expanded) |
||
| Line 4: | Line 4: | ||
=== Example 1 === | === Example 1 === | ||
If you want to restrict the upload, renaming, or deletion of files in the <code>Logos</code> folder of the resource type <code>Images</code>, use the following ACL settings. | If you want to restrict the upload, renaming, or deletion of files in the <code>Logos</code> folder of the resource type <code>Images</code>, use the following ACL settings. | ||
| + | |||
| + | {{{example1}}} | ||
| + | |||
| + | This example only refers to file operations in the <code>/Logos</code> folder. It does not restrict operations on the folder, so the user can delete or rename it. In order to limit users' ability to modify the folder itself (not its contents), you should change permissions in the parent folder. | ||
| + | |||
| + | ==== Example 2 ==== | ||
| + | The following settings restrict folder operations for the <code>Images</code> resource type. | ||
| + | |||
| + | {{{example2}}} | ||
| + | |||
| + | Now a user can view and create a folder, but he will be unable to rename or delete it. | ||
Revision as of 09:29, 31 March 2011
Access Control List Examples
Have a look at the following examples that present various permission configurations in order to learn more about using Access Control Lists in CKFinder.
Example 1
If you want to restrict the upload, renaming, or deletion of files in the Logos folder of the resource type Images, use the following ACL settings.
{{{example1}}}
This example only refers to file operations in the /Logos folder. It does not restrict operations on the folder, so the user can delete or rename it. In order to limit users' ability to modify the folder itself (not its contents), you should change permissions in the parent folder.
Example 2
The following settings restrict folder operations for the Images resource type.
{{{example2}}}
Now a user can view and create a folder, but he will be unable to rename or delete it.