Each visitor of your gallery is a member of at least one group. In Coppermine, you don't assign individual permissions per user, but per group membership. There is a number of built-in groups that can't be deleted, and an infinite number of custom groups that can be defined by the admin.
This is where you define what members of a user group can and can't do. In Coppermine, you don't assign privileges to individual users, but to groups. Users can be in various groups, so you can determine granular levels of permissions.
Out of the box there are four groups in Coppermine. You can rename them just as well as you can rename custom groups, but it's recommended to leave them they way they are by default. This will make upgrades easier and help you administer and maintain your gallery. End users usually don't see the name of the group they are in, so you don't have to provide other group names.
However, if you choose to rename a group, just change the name and submit the group control panel form by clicking on "Apply modifications".
There are two types of groups in Coppermine: those that come with it out of the box (default groups) and custom user groups. The ones that come with Coppermine by default ("Administrators", "Registered", "Guests") can not be deleted.
Users can be member of several groups - privileges inherited from the group accumulate. This means that the least restrictive permission/setting is being taken into account.
User "Linus" is member of the "registered" group as primary group and additionally member of the custom user groups "Cartoonists" and "Photographers". Members of the group "registered" are allowed to send ecards, but are not allowed to rate nor to post comments. They are not allowed to have a personal gallery neither. Members of the "Cartoonists" group are allowed to comment, send ecards and rate. Members of the group "Photographers" are not allowed to comment, to send ecards nor to rate, but they are allowed to have personal galleries. Subsequently, the user "Linus" would have the privilege to send ecards (inherited from membership in the group "registered"); he would be allowed to post comments and rate files (inherited from membership in the group "Cartoonists"). Additionally, "Linus" would have the privilege to have a personal gallery (inherited from membership int the group "Photographers"). The fact that members of the group "Photographers" are not allowed to rate, send ecards or post comments would not be taken into account, since membership inside the other two groups that grant those privileges would override the more restrictive settings for the group "Photographers".
By default (after initial installation), there is only one user who resides in the Administrators group: the admin account you set up during initial install. You can later add other users to the administrators group (using the user control panel), but you have to keep in mind that all other members of this group have exactly the same privileges the original admin has: they could ruin your entire gallery in a couple of mouse clicks. It's strongly recommended to only assign others admin privileges that you fully trust.
By default, there is no user inside the "Registered" group. This will change as soon as you allow registration and members come in. All new users who get created (either by completing the login form or when they are created by an admin) reside in the "Registered" group (as primary group) no matter what.
Use the anonymous group to define what non-registered users can and can't do. Quota and "Personal gallery" are meaningless for anonymous users. You can not (and mustn't try) to assign existing users to the "anonymous" group - being a registered user automatically keeps them from being a member of the "Anonymous" group.
You can create groups as you see fit. Make sure to come up with a naming scheme that makes sense in the first place. It's advisable to start with a minimum set of custom groups and only add them later if you must.
The disk quota applies only for groups where "Personal gallery" has been set to "Allowed". Both files uploaded by a user into his personal gallery as well as files uploaded to public galleries are included in the quota. The quota applies to each member of the group. Set the quota to a value that actually makes sense - setting it to several terrabytes does not make sense and may lead to funny side-effects.
Permissions control what the user is allowed to do in the gallery (Rating/Sending Ecards/Posting Comments).
Bear in mind that if a user is a member of a group where "Rating", "Comments" or "Public albums upload" is set "YES", s/he will have the right to perform these operations only in albums where they are allowed. ( ie. uploading files will only be possible in albums where "Visitors can upload files" has been set to YES using the album properties screen of particular albums.)
Think of the setting "Public albums upload" as a general switch that determines if members of a particular group are allowed to upload to public albums (i.e. albums that the admin created) at all. Setting this to "Yes" will not immediately grant users access to upload to all public albums, but only to the albums that you explicitely specified upload permissions using the album properties dialog of a particular public album you want to allow user uploads to.
If "Personal gallery" is set to Allowed, the members of the group will be able to have their own gallery in the "User galleries" category where they will be able to create their own albums.
If "Approval" is set to NO, files uploaded by members of the group in albums created in their own gallery won't need to be approved by the admin. If "Approval" is set to YES, the users in the particular group will be able to upload, however the uploaded files will only be shown after the admin (you) has approved them.
For each group, you can set the group's access level to:
The setting here for the guest/anonymous group is the same as the setting "Allow unlogged users access" on the Gallery Configuration page under "User Settings". If you update the option here, it will update the configuration setting and vice versa.
The link "Assigned album(s)" will let you display what albums are assigned exclusively to members of a particular group. To make this absolutely clear: this feature does not allow you to actually assign albums to groups, it just displays those assignements. To actually assign albums to particular groups, use the album properties dialog of individual albums.
To create a custom user group, click on the "Create new group" button located at the bottom of the "Groups" control panel. A new table row will appear at the bottom of the table with a blank name. It has not been saved yet - you will have to at least assign a unique name for it. Change any of the other properties of your new group and finally click the "Apply modifications" button.
It is recommended to only use web-safe alpha-numeric characters for group names (plus underscore and minus).
You can not delete the four pre-defined groups ("Administrators", "Registered", "Guests"). All other (custom) groups can be deleted by going to Coppermine's groups control panel, checking the tickbox in front of the group you want to delete and finally clicking on the "Delete selected groups" button at the bottom of the screen. Deleting groups can not be undone. Deleting a group does not delete the members within that particular group.
When bridged, a similar thing that applies for the creation of groups applies to deleting them as well: Coppermine doesn't control groups any longer when being bridged, so you have to delete user groups in the app that you have bridged Coppermine with.
When Coppermine is being bridged, you create and delete custom groups using the application that you have bridged Coppermine with. However, each time you edit groups inside the app that you have bridged with, you should go to Coppermine's group control panel once to trigger a syncronisation between Coppermine and the app you have bridged with in terms of groups. In other words: you have to make Coppermine aware of the changes that have taken place in the other app.