privacy_stp10

We are in the Album list management available from the menu using <em>Albums » Manage</em><br><br>Edit on album by hovering it and then click on Edit.

privacy_stp12

On that page, you can choose if the album will be available for anyone or will be restricted to some users

privacy_stp14

Then users and groups of users can be granted to access to the album.

privacy_stp15

Just before explaining the groups, a pro tip: here is the link to a page to set as private/public several albums at once. Click on it

privacy_stp17

A group in Piwigo is just a set of users: so groups make it easier to manage album permissions, and to manage users' properties. Here is the page where you can manage groups, i.e. rename, merge, duplicate, delete them. You also can set one or more groups as "default group" which means that newly registered users will be associate to those default groups.

privacy_stp19

Here you can quickly edit a single user by hovering over it and then click on the Edit link.<br><br>You can select multiple users and edit them at once by then choosing an Action to apply.

privacy_stp20

Now you know how to keep your photos private, but you may wonder about how to protect your public photos. You might first think about blocking the visitor to download the photo: you can't, because the web has been created that way (the browser of the visitor download all the resources displayed and more). The right-click can be disabled, a blank layer can be put on top of the photo etc but it will not disable the download. Full webpages can be saved by any web browser.

privacy_stp22

<em>For Advanced Users</em><br><br>In Piwigo, you can protect the original photos using your local configuration. Use the variable $conf['original_url_protection']: by default empty, you set the value to "images" to protect only the photos or "all" to protect also all type of media, which can be ressource consumming or might simply don't work on your server.<br><br>This option works for public and private content. This option currently requires you to deny the acces to the folders /upload and /galleries, by using an .htaccess file (usually a text file with "Deny from all" for content) or the server configurations.<br><br>Please note that filenames of photos uploaded using other method than FTP are <b>randomized</b>, so they are impossible to guess: that filename and so the path to the original photo can be known only if the visitor has access to a resized version of that photo, like the thumbnail. $conf['original_url_protection'] and denying access to the folders /upload and /galleries are meant to avoid that case.

privacy_stp3

Take a moment to read the information below.

privacy_stp5

Below is explained how you can manage the Groups.<br>Those permissions are only for the access of the photos and the albums, when browsing on the public part or for the external applications. We will see later other protections, but let's now practice!

privacy_stp7

... or you can do that later one, here in the Batch Manager in Global Mode.<br><br>This is the page <em>Photos » Recent photos</em>, so the filter "Last Import" is set.

privacy_stp9

... and select the action "Who can see the photos?". Now you can change the privacy level of the selected photos.<br><br>But you can also do that for a specific photo, on its edit page. You can access to it from the public part, or from here.<br><br>Now, I will show you the other system of permission per album based on the groups and users.

privacy_title10

Album permissions

privacy_title12

Album permissions

privacy_title17

Groups

privacy_title19

Users

privacy_title20

Public photos

privacy_title22

Local Config: Original protection

privacy_title3

Permissions

privacy_title5

Permissions > Groups

privacy_title7

Privacy Level

privacy_title9

Privacy Level