Instruction manuals

The same credentials apply to all your participations in project spaces at the Projektablage. This means that if you have the login details for one IT-service/project space, you can use them to log in to all others.

If this is not the case: The administrative persons of the project spaces involved are responsible for managing their users. Therefore, please contact any administrative person of a project space which you are a member of with a request for getting a reset link.

Once you have reset your password, it is immediately valid for all your project spaces and their IT-services (e.g. Seafile, ...).

If you do not know the administrative persons of your project spaces, you can find the e-mail address of the person who invited you into a project space in the respective invitation e-mail.

The respective administrative persons are responsible for managing the project spaces at the Projektablage. Therefore, please contact any administrative person of a project space which you are a member of. They can send you a new link to set your password.

If you do not know the administrative persons of your project spaces, you will find the e-mail address of the person who invited you into a project space in the respective invitation e-mail.

The name of a project space at the Projektablage cannot be changed afterwards, as many of the automatic processes running in the background use the project space's name.

If it is nevertheless necessary to give your project space a new name, you must switch to a new project space:

1. You request a new project space at the Projektablage with the desired name. In order to do so it suffices to send an email to the LUIS Support stating the desired name for the project space.
2. You manually migrate the data from the old project space to the new project space.
3. You invite  the coworkers of the old project space into the new project space.
4. Once you have ensured that everything works as desired (data is complete, all coworkers have been invited, etc.), you can set the expiry date of the old project space to the current day in the project administration. It will then be automatically deactivated the following night.

In rare cases, the sync client may enter a state in which synchronisation fails.

In this situation, you should first ensure that you are using the latest version of the Desktop Syncing Client. The latest version can be downloaded from the manufacturer's download page. As newer versions usually fix bugs, the problem may already be solved after the update.

If the error still persists after the update, you can try the following steps:

1. Please back up all modified files that have not yet been synchronised to a separate folder on your local computer.
2. Initiate a manual synchronisation. To do this, right-click on the relevant library in the client and select the sub-item ‘Synchronise manually’.
3. If the problem persists: Initiate a new synchronisation by right-clicking and selecting ‘Resynchronise’.
4. If the problem persists: Uninstall the sync client. During the uninstallation process, please answer the question ‘Do you really want to remove the account information for Seafile’ with ‘Yes’. Then reinstall the sync client in the latest version and set up your account again. You can find help on setting up your account in the articles on Cloud Seafile, Project-Seafile and High-Seas.

If the problem still persists, please report it to the LUIS support by e-mail. Please describe as precisely as possible how the problem manifests itself and since when it has been occurring. Please also send the log files of your client. In MS-Windows, these can be found by right-clicking on the client icon in the taskbar and then selecting ‘Log folder’. An Explorer window should open in which you can see the log files (‘seafile.log’ and ‘applet.log’).

In rare cases, the Desktop Drive Client may enter a state in which synchronisation fails, as a result of which changes are not transferred.

In this situation, you should first ensure that you are using the latest version of the Desktop Drive Client. The latest version can be downloaded from the manufacturer's download page. As newer versions usually fix bugs, the problem may already be solved after the update.

If the error still persists after the update, you can try the following steps:

1. Please back up all modified files that have not yet been synchronised to a separate folder on your local computer.
2. Initiate a new synchronisation. To do this, right-click on the Desktop Drive Client's icon in the taskbar. Under ‘Accounts’, navigate to your account and select ‘Resynchronise’.
3. If the problem persists: Uninstall the Desktop Drive Client. During the uninstallation process, please answer the question ‘Do you want to delete the SeaDrive account information?’ with ‘Yes’. Then reinstall the Desktop Drive Client in the latest version and set up your account again. You can find help on setting up your account in the articles on Cloud-Seafile, Project-Seafile and High-Seas.

If the problem persists, please report it to LUIS support by e-mail. Please describe as precisely as possible how the problem manifests itself and since when it has been occurring. Please also send the Desktop Drive Client's log files. In MS-Windows, these can be found by right-clicking on the Desktop Drive Client icon in the taskbar and then selecting ‘Log folder’. An Explorer window should open in which you can see the log files (‘events.log’, ‘seadrive.log’ and ‘seadrive-gui.log’).

Applications usually contain sensitive, personal data. We therefore recommend the following procedure for processing application procedures with Project-Seafile:

1. Applications are usually received by e-mail (functional e-mail address)
2. A separate project space is created at the Projektablage for each position to be filled
3. The duration of the project space is limited to 6 months
4. Applications are stored as a password-protected ZIP in the project space
5. Parties involved in the process are added to the project space
6. The password is sent by e-mail (encrypted where possible) to the parties involved. It is also advisable to point out in this e-mail the obligation to delete any locally stored data after the procedure has been completed
7. Delete all associated data (mail, project space, local storage) at the end of the process