skip to content

Assigning write permissions

To be able to receive write permission for web sites on our servers, you need to have a valid employee or student account. In case you don't have an account yet, please apply for one:

Application for student or employee accounts

Typo3 or Wiki

If you need write permissions for a TYPO3 website or an access restricted Wiki, please get in touch with the respective administrator at your institute. If you don't know the administrator or he/she is not available, please contact the TYPO3-Master (for Typo3s) or the Webmaster (for Wikis).
Note: For most TYPO3 websites, the person in charge is listed at the bottom of the web pages.

Web projects

Web projects created after March of 2018 use the NFS file system. In these newer web projects, write permissions are assigned by one of the project administrators through the uniKIM website. Take a look at our instructions for managing "permissions in NFS web projects".

Older, AFS based web projects

Until March of 2018, web projects were set up to use the AFS file system. For these older projects, the following instructions apply.

As a project administrator, you are able to assign write permissions to other users that will be updating the web project. To assign these privileges, login via SSH to the server and change directories to the respective project directory. The server is only accessible within the university network UKLAN, for access from outside please establish a VPN connection previously.

The first step is to find out the name of the project group in your web project. Use the command fs la inside the project directory. There will be a list of access permissions displayed similar to the following:


Access list for . is
Normal rights:
  webpro0:pro_xena_n rlidwk
  webpro0:pro_xena_a rlidwka
  wwwadm1:wm rlidwka
  system:administrators rlidwka
  wwwadm1 rlidwka
  webpro0 rlidwka
  w-xena rl


The name of the project group will usually be at the top of this list. Its name starts with “webpro0:pro_”.

There are different groups in the list. The one ending in “…_a” is for administrators and the one ending in “…_n” is for normal users. In this example, the name of the project group is “webpro0:pro_xena_n” for regular users and “webpro0:pro_xena_a” for project administrators. Note that this is an example, so the actual group names will be different in your project—take a close look at the output of the fs la command. Please also note that, as opposed to NFS projects, in AFS projects the project admin permissions include write permissions, so there is no need to assign normal users permissions to anyone who posesses admin permissions already.

Once you have found out the name of the project group, you can take a look at its current members like this (with the proper group name instead of the example name “webpro0:pro_xena_n”, of course):


  pts mem webpro0:pro_xena_n


To remove an account from the group, use a command like this (substituting the proper group name and the actual account name instead of the dummy value of “jdoe2”):


  pts removeuser -group webpro0:pro_xena_n -user jdoe2


To add a new accout to the group, use a command along these lines (of course, with the proper group name and the real account name instead of the “jdoe2” dummy value used in this example):


  pts adduser -group webpro0:pro_xena_n -user jdoe2


For further information about AFS access control, please refer to our web page “AFS permissions”.

In case of further questions or if you run into trouble assigning permissions for AFS web projects, please get in touch with RRZK’s Webmaster: contact form Webmaster

Write permissions for web service users in AFS projects

As an administrator of an AFS based web project, you can also assign write permissions to the internal web service user for certain directories. Usually, this becomes necessary when using a content management system or other such software that allows for remote users to upload files (e.g. images).

For more information, see Write permissions for web service users

If you have any questions or problems, please contact the RRZK-Helpdesk