CCCV Infrastructure Documentation

Here, you’ll find all documentation needed to use the CCCV services which we use for the event organization. Plain accounts won't have any access rights. We'll provide ressources at our services for every crew. Accounts associated with a crew will be granted access to those ressources.

If you have any problems, you can contact the administration team at it [at] cccv dot de or in RocketChat at #infra-support.

uffd (Single Sign On)

uffd (UserFerwaltungsFrontend) is our Single Sign on based on LDAP. You can configure all settings for your user on on one central location. This is the user you can use to log in to all other services. If you need an account, please contact the administration team via the email address above. In your request, please include your nickname, an email address and the crews you are part of.

Dokuwiki The mighty wiki. You need a password for read only access and an SSO account for write access. The password can be found once per month at or by asking members of your team. If you are unable to get the password, contact the administration team at the email address above.

Please note: the amount of people with access is in the five digit range and the password is shared without much oversight. You should therefore consider anything you write there as public accessible. The wiki is still not intended for public sharing, you should not put anything written there on Twitter for example.

Depending if you are a member of a crew you will see a namespace for every group and three sub-namespaces within that group:

crew-internal and public should be self-explanatory, everything under orga-internal is visible to all other members of any crew, but not for users without a crew.


If your account grants access to the nextcloud, you can access it at You will find a shared group folder for every crew you are member of there.


The nextcloud provides you with calendars, everyone with access to the cloud should be able to create and share those. However, for team and shared calendars it is often not practical to have them tied to a personal account. You can therefore ask us to create such a calendar for you with our dedicated calendar user.

sharing / subscribing

Calendars can be shared (and subscribed) via CalDav (read and write access) or via a shared link (read only access). For some tools (iOS calendar for example) you need to replace the https:// in front of the shared url by webcal:// to make it work.

should I use a seperate calendar for my meetings?

We provide a general calendar for all kinds of appointments, if your meeting is not considered a secret, feel free to use the general calendar. This helps to prevent conflicts between meetings.


If your account grants access to the gitlab, you can access it at Crews get their own group at gitlab, but those are only used for managing access. If you need group projects, please create a new group at the root level and add your crew as member. This is needed to give you the most flexible way to manage access rights for your projects. In doubt, ask us, we are glad to help.

Please be aware that due to how group permissions are handled by gitlab it can take up to 15 minutes after your first login until your groups are synced and you are able to access the corresponding projects.


If you need a address please contact the administration team and explain the reason why.

If you have access to the mail server, configure your mail client with the following settings:


POP3 is not supported.

IMAP (read mails)

SMTP (send mails)


Hedgedoc (work in progress, not stable yet!!!)

We run a private Hedgedoc (a markdown alternative to Etherpad) at You need to login via SSO to create new pads. New pads are limited by default, this means user without an account can neither see nor edit them. You can change this on the View-tab on the top right. An explanation about the permission levels is located there as well.

Please note: Pads are not a place for permanent data storage. Because of this we delete pads after one month without change. When a pad is deleted, the creator gets a copy of it via email. Please archiv pads and especially protocolls in the wiki.

To convert from markdown to dokuwiki syntax, you can use pandoc: pandoc -o output.dokuwiki.txt -s -f markdown -t dokuwiki