🌍
English
Differences
This shows you the differences between two versions of the page.
|
user_documentation:permissions_management [2007/08/02 12:12] 134.245.216.35 fixed example description of {animals} to "already public" |
user_documentation:permissions_management [2011/09/16 14:07] (current) mixedbredie [Album Permission Status] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | Administrators can forbid access to categories for users. This is what we call //permissions// or //authorizations// in PhpWebGallery. Categories can be //public// or //private//. Permissions can only be set for private categories. | + | ====== Album Permission Status ====== |
| + | Administrators can forbid access to albums for users using //permissions//. Albums can be //public// or //private//. Permissions can only be set for private albums. | ||
| - | ==== Categories access status ==== | + | Prior to Piwigo 2.2, //albums// were known as //categories//. This is just a change of name and the concept and functionality remains exactly the same. |
| - | === Editing status === | + | === Editing permission status === |
| - | So, the first is to make the desired categories private. You have two ways for switching categories to private : | + | The first step is to make the desired albums private. You have two ways of switching the album from public to private: |
| - | - by editing a single category : [administration panel >> Categories >> Manage >> edit] | + | - by editing a single album: [Administration > Albums > Manage > edit] |
| - | - by setting options to your whole category tree : [administration panel >> Categories >> Public/Private] | + | - by setting options to your whole album tree: [Administration > Albums > Public/Private] |
| === Default status === | === Default status === | ||
| - | At creation, a category can be public or private, depending on configuration and parent category : | + | At creation an album can be public or private depending on configuration and parent album: |
| - | * status = ''$conf['newcat_default_status']'' if parent category is //public//. This configuration parameter must be set in ''include/config.inc.php'' file. | + | * status = ''$conf['newcat_default_status']'' if the parent album is //public//. This configuration parameter must be set in the ''include/config.inc.php'' file. |
| - | * status = //private// if parent category is //private// | + | * status = //private// if the parent album is //private// |
| === Status modification rules === | === Status modification rules === | ||
| - | When editing category access status, automatic rules are applied : | + | When editing album access status, automatic rules are applied : |
| - | * if status goes from //public// to //private//, all child categories become //private// | + | * if status goes from //public// to //private//, all child albums become //private// |
| - | * if status foes from //private// to //public//, all parent categories become //public//. We are not talking about cousins, but parents to the root of categories. | + | * if status goes from //private// to //public//, all parent albums become //public//. We are not talking about cousins, but parents to the root of albums. |
| === Example === | === Example === | ||
| - | Let's give a simple example, shown in next screenshots. At beginning, all categories are public : | + | Let's have an example, shown in next screenshots. At beginning, all albums (categories on screenshots) are public: |
| - | {{ permissions_example_1.png |At beginning, all categories are public}} | + | {{en:user_documentation: permissions_example_1.png |At beginning, all albums are public}} |
| - | Then you decide to set {animals >> cat} (the selected category above) to //private// | + | Then you decide to set {animals >> cat} (the selected album above) to //private// |
| - | {{ permissions_example_2.png |All children categories become private}} | + | {{en:user_documentation: permissions_example_2.png |All children albums become private}} |
| - | All children categories become //private// automatically. Then, you decide that {animals >> cat >> 8 weeks} must in fact be //public// : | + | All children albums become //private// automatically. Then, you decide that {animals >> cat >> 8 weeks} must in fact be //public// : |
| - | {{ permissions_example_3.png |All parent categories become public}} | + | {{en:user_documentation: permissions_example_3.png |All parent albums become public}} |
| - | All parent categories become //public// automatically. The parent categories of {animals >> cat >> 8 weeks} are {animals >> cat} (previously //private//) and {animals} (which was already //public//) | + | All parent albums become //public// automatically. The parent albums of {animals >> cat >> 8 weeks} are {animals >> cat} (previously //private//) and {animals} (which was already //public//) |
| ==== Users permissions ==== | ==== Users permissions ==== | ||
| - | Permissions are managed by group or by user. For a private category, permissions tell whether the user (or users belonging to the group) can reach the category. | + | Permissions are managed by group or by user. For a private album, permissions tell whether the user (or users belonging to the group) can view the album. |
| === Administration screens === | === Administration screens === | ||
| Line 49: | Line 50: | ||
| Two screens let you modify permissions : | Two screens let you modify permissions : | ||
| - | * [administration panel >> Permissions >> users] : for a particular user, lists all private categories separated in two boxes : authorized on the left, forbidden on the right. You can also enter this permissions management screen by screen [administration panel >> Identification >> users] and use link to permissions in the users list. | + | * [Administration > Users > Manage] : for a given user, click on the //permissions// icon, you will then see the list of all private albums separated in two boxes: authorized on the left and forbidden on the right. |
| - | * [administration panel >> Permissions >> groups] : for a particular group, lists all private categories the same way as for users. | + | * [Administration > Users > Groups] : for a give group, click on the //permissions// icon, you will then see the list all private albums the same way as for users. |
| === Permissions Rules === | === Permissions Rules === | ||
| - | Here follows a list a rules used by PhpWebGallery concerning permissions | + | Here follows a list a rules used: |
| - | * for a group or a user, forbidding a category makes all child categories forbidden | + | * for a group or a user, forbidding an album makes all child albums forbidden |
| - | * for a group or a user, authorizing a category makes all parent categories authorized | + | * for a group or a user, authorizing an album makes all parent albums authorized |
| - | * for a group, authorizing a category makes this category authorized to all members of the group (same effect for parent categories thanks to previous rule) | + | * for a group, authorizing an album makes this album authorized to all members of the group (same effect for parent albums thanks to previous rule) |
| - | * a user can reach a private category if he's authorized to **or** if he belongs to any group authorized to reach the category | + | * a user can reach a private album if he's authorized to **or** if he belongs to any group authorized to reach the album |
| * denying a user from a group makes the user lose all authorizations won by belonging to this group | * denying a user from a group makes the user lose all authorizations won by belonging to this group | ||
| * a new user has no permission | * a new user has no permission | ||