openDesk
anymize reads the modules of your openDesk instance: files, projects, knowledge, calendar and contacts, each with its own credentials.
5 Min
What you can do with it
openDesk is the sovereign workplace that ZenDiS publishes for the Federal Ministry of the Interior. Once connected, you ask across the modules in chat.
- “Search the wiki for the records-management instruction.”
- “Which work packages in the Digitalization project are open?”
- “What is in the Templates folder?”
- “What is in my calendar next week?”
Why openDesk needs several logins
openDesk is not a single product but a bundle: files sit in a Nextcloud, projects in OpenProject, knowledge in XWiki, calendar and contacts in the Open-Xchange App Suite. There is no shared interface across everything.
That is why the connection dialog first asks for your openDesk domain, for example behoerde.de, and then per module for its own access detail. We derive the module addresses from the domain, files., projects., wiki. and dav. in front. If an address differs for you, you can override it per module.
| Module | Runs on | What you need |
|---|---|---|
| Files | Nextcloud | Username and an app password |
| Projects | OpenProject | API key from your profile |
| Knowledge | XWiki | Username and password |
| Calendar and contacts | Open-Xchange App Suite | One login opens both |
openDesk does contain Nextcloud, but it is not the Nextcloud connector. Anyone who uses both connects both separately. In openDesk the calendar expressly does not come from Nextcloud but from Open-Xchange, otherwise it would be empty.
How to connect openDesk
- 01Open Apps, then Connectors, and choose openDesk.
- 02Enter your openDesk domain at the top, host name only, for example behoerde.de.
- 03Turn on the modules you need and enter the access per module: app password from Nextcloud, API key from OpenProject, login for XWiki, login for Open-Xchange.
- 04Click Connect. Each module is checked separately.
- 05Under each section it then says whether it worked. What does not work stays off; the rest still connects.
Adding a module later is the same path: the dialog reads the stored state when it opens, shows connected sections as connected and leaves the fields empty. Leaving empty means: access stays as it is. Only turning a section off removes it.
What if our instance only allows SSO?
Then exactly that module stays off, and the dialog tells you so instead of a generic error. In practice that mainly affects XWiki and Open-Xchange: if sign-in with username and password is rejected there, files and projects still connect.
A module without stored access gets no tools at all. The assistant then does not see that area and does not try it either, instead of giving you an error in the middle of the conversation.
Does anymize write to openDesk?
No. All five modules are read-only, by design: there are no tools that store a file, create a work package or change a wiki page. The connector is therefore on the list of connections that may only read.
And what is read is anonymized: people's names in files and work packages, addresses in contacts, file references in wiki pages and participants in appointments are replaced by placeholders before an AI model sees them.