This page shows common tasks for administrators when managing users.
Note that most user-related tasks can also be managed via occ commands for managing users.
The default view displays basic information about your users.
The Group filter on the left sidebar lets you quickly filter users by their group memberships, and create new groups.
Click the gear icon on the lower left sidebar to view the available settings.
User accounts have the following properties:
- Login Name (Username)
The unique ID of an ownCloud user. Note that it cannot be changed after creating the user. The user can log in either using the login name or the e-mail address.
- Full Name
The user’s display name that appears on file shares, the ownCloud Web interface and emails. Admins and users may change the full name anytime. If the full name is not set, it defaults to the login name.
The admin sets the new user’s first password. Both the user and the admin can change the user’s password at anytime.
The admin sets the new user’s e-mail. The user then gets an e-mail to set the password. Both the user and the admin can change the user’s e-mail at anytime.
You may create system (non-LDAP) groups and assign system group memberships to users. By default, new users are not assigned to any groups.
- Group Admin
Group admins are granted administrative privileges on system groups and can add new users, edit user properties, and remove existing users from those groups.
The maximum disk space assigned to each user. Any user that exceeds the quota cannot upload or sync data. You have the option to include external storage in user quotas.
To create a user account:
Enter the new user’s Login Name and their E-Mail
Optionally, assign Groups memberships
Click the Create button
Login names may contain letters (a-z, A-Z), numbers (0-9), dashes (-), underscores (_), periods (.) and at signs (@). After creating the user, you may fill in their Full Name if it is different from the login name, or leave it for the user to complete.
You cannot recover a user’s password, but you can set a new one:
Hover your cursor over the user’s Password field
Click on the pencil icon
Enter the user’s new password in the password field, and remember to provide the user with their password
If you have encryption enabled, there are special considerations for user password resets.
Each ownCloud user has two names: a unique Login Name used for authentication, and a Full Name, which is their display name. You can edit the display name of a user, but you cannot change the login name of any user.
To set or change a user’s display name:
Hover your cursor over the user’s Full Name field
Click on the pencil icon
Enter the user’s new display name
To delete a user, hover your cursor over their name on the Users page and click the trashcan icon that appears at the far right. You’ll then see a confirmation dialog appear, asking if you’re sure that you want to delete the user.
If you click Yes, the user is permanently deleted, including all the files owned by the user, including all files they have shared. If you need to preserve the user’s files and shares, you must first download them from their ownCloud Files page, (which compresses them into a zip file).
Alternatively, you can use a sync client to copy them to your local computer.
If you click No, the confirmation dialog will disappear and the user is not deleted.
|See File Sharing Configuration to learn how to create persistent file shares that survive user deletions.|
ownCloud has two types of administrators:
ownCloud Administrators have full rights on your ownCloud server and can access and modify all settings. To assign the ownCloud administrator role to a user, simply add them to the
Group Administrators. Group administrators have the rights to create, edit and delete users in their assigned system (non-LDAP) groups. Use the dropdown menus in the Group Admin column to assign group admin privileges.
You can assign new users to groups when you create them, and create new groups when you create new users. You may also use the Add Group button at the top of the left pane to create new groups. New group members will immediately have access to file shares that belong to their new groups.
In previous versions of ownCloud, files and folders could only be shared with individual users or groups created by administrators. This wasn’t the most efficient way to work. From ownCloud 10.0, users can create groups on-the-fly, through a feature called "Custom Groups", enabling them to share content in a more flexible way.
To enable Custom Groups:
From the ownCloud Market, which you can find starting from version 10.0 under the Apps menu, click Market.
Click Collaboration (1), to filter the list of available options and click the Custom groups application (2).
Click INSTALL in the bottom right-hand corner of the Custom Groups application.
With this done, Custom Group functionality will be available in your ownCloud installation.
Depending on your Custom Groups and ownCloud’s global settings, configured by the ownCloud admin, Custom Groups may behave differently depending on settings made via occ commands. See the details in occ for Custom Groups. Note that some settings shown in the examples below can also be set via
config/config.php. For best practice use the occ command where possible.
Creating or renaming a Custom Group using an existing name of another Custom Group can be allowed or not depending on administrative settings.
Custom Group creation can be limited to ownCloud group admins.
Disable administration of Custom Groups by ownCloud administrators:
'customgroups.disallow-admin-access-all' => true,
The app can be hidden from the user’s personal settings page if the user belongs to one or more disallowed groups,
To specify the disallowed groups, list them against the
customgroups.disallowed-groups key in
config/config.php, as in the following example.
// Hide the Custom Groups app for users in the // 'no_guest_app_users' and 'project5' group. 'customgroups.disallowed-groups' => ['no_guest_app_users', 'project5'],
Setting Custom Group admins can only be done via the browser. In case the group admin has left the company and you need to set a different one, you temporarily must allow the ownCloud instance admins access to groups if disallowed before, set one or more new group admins, and change the instance admin setting back.
There are 4 types of quota settings in ownCloud when dealing with LDAP users.
Found in, this setting overwrites the rest. If set, this is what will be set for an LDAP user’s quota in ownCloud.
This will be used if no quota is set and is found in. If the Quota is not set, but Default Quota is, and a systems administrator tries to set a quota for an LDAP user with User Quota, it will not work since it is overridden by Default Quota.
Click the gear icon on the lower left pane to set a default storage quota. This is automatically applied to new users. You may assign a different quota to any user by selecting a preset value from the Quota dropdown or by entering a custom value. When you create custom quotas, use the usual abbreviations for your storage values such as 500 MB, 5 GB, 5 TB, and so on.
You now have a configurable option in
config.php that controls whether external storage is counted against user’s quotas. This is still experimental and may not work as expected. The default is to not counting external storage as part of user storage quotas. If you prefer to include it, then change the default
'quota_include_external_storage' => false,
Metadata (such as thumbnails, temporary files, and encryption keys) takes up about 10% of disk space but is not counted against user quotas. Users can check their used and available space on their Personal pages. Only files that originate from a user, or are in a share owned by the user, count against that user’s quota, not file shares received from other users. For example, if you upload files to a different user’s share, those files count against that user’s quota. If you share a folder with other user’s and they add files to that folder, then those files count against your quota. If you re-share a file that another user shared with you, that file does not count against your quota, but the originating user’s.
Encrypted files are a little larger than unencrypted files; the unencrypted size is calculated against the user’s quota.
Deleted files that are still in the trash bin do not count against quotas. The trash bin is set to 50% of quota. Deleted file aging is set to 30 days. When deleted files exceed 50% of quota, then the oldest files are removed until the total is below 50%.
Usually, a user’s home folder is located in the
data/ directory, the location of which is defined in
config.php and defaults to
/var/www/owncloud/data. Usually in smaller installations, the data directory mounts to a physical drive of the server and in bigger installations the data directory is mounted via NFS. This can be less than optimal for very big installations with thousands of users and/or users with very big space consumption. This can result in a high load on a single mount point.
ownCloud offers moving the home folder location of single users from the default location to another path outside the data directory to distribute the load to different mount points. You can also move back a user’s home to the location defined in config.php.
|In general, moving a user’s home should be the last step after all optimizations of the mount point have been done. Carefully monitor over a period of time the changes made before moving a user’s home.|
For details of the occ user commands used below, see the User Commands section of the occ command reference. The examples use the user ID
lisa and the mount for the new home is
To report a users home, use the following command:
sudo -u www-data ./occ user:list lisa -a home - lisa: /var/www/owncloud/data/lisa
Here you can see, that the home of user
lisais located in
Prepare new mounts in advance for one or more users:
Use the OS methods to create one or more new mount points for users home directories not located as defined in config.php. You can create as many new homes as required containing as many new user homes as wanted - there is no ownCloud limitation. The mounts must be fully accessible by the webserver user (usually www-data).
Move the users home:
To move a users home, the target folder must not contain a subfolder with the user’s ID.
The target folder can contain other user folders.
sudo -u www-data ./occ user:move-home lisa /mnt/newhome_1
The user gets disconnected and the user’s home is now moved which may take a while depending on the load of the server and the bandwidth available on the mount points. When the move operation has finished,
all data from the user is copied to the new home,
the new path is set in the ownCloud database and
the user gets enabled again.
After checking, the old user’s home location can safely be deleted manually.
If you are using LDAP and the LDAP Home Connector app, update the user’s home mount in the attribute used accordingly.
To check the user’s new home, use the following command:
sudo -u www-data ./occ user:list lisa -a home - lisa: /mnt/newhome_1/lisa
Here you can see that the home of user
lisais now located in
To list the available user home root directories, use the following command:
The following command lists all available user homes. Note a home only gets listed, if it contains at least one user.
sudo -u www-data ./occ user:home:list-dirs - /var/www/owncloud/data - /mnt/newhome_1/lisa
To list all users from a users home root directory, use the following command:
The following command lists all users from a given home.
sudo -u www-data ./occ user:home:list-users /var/www/owncloud/data - admin - user01