🔗 Integrations

Use services like Nextcloud in a separate window – sign in once, then you're in with one click.

What it does for you

• Your web services are one click away inside DasDing – without typing a password every time.
• Credentials and session stay in the password vault on your device, never on a DasDing server.
• Each service runs in its own isolated window – foreign pages can't get in.

Who it is for: Everyone who regularly uses a web service such as Nextcloud, Forgejo or Lifecraft.
What you need: A password vault (tab 🔐 Passwords) and an account with the respective service.

Every morning you open your Nextcloud in the browser, type user name and password, confirm the two-factor code – and that for every service separately. With the 🔗 Integrations tab you sign in once, and from then on one click is enough.

How it works

Each service gets its own window that sees nothing else – like a browser that knows only this one site. There you sign in normally on the provider's sign-in page, two-factor code included. When you close the window, DasDing stores the session encrypted in your password vault. On the next “Open”, DasDing restores the session and you're in – without a password. Note for Windows: if several integration windows are open at the same time, they share one incognito profile there – “Disconnect” still removes only that service's session.

Important: DasDing never signs in for you and doesn't know your password with the service. It only remembers that you are signed in – like a browser that keeps you logged in.

Step by step

1. Open the 🔗 Integrations tab and unlock the vault.
2. Pick a service on the left. For a self-hosted service (e.g. Nextcloud), enter the address of your instance on the right, such as https://cloud.yourcompany.com.
3. Connect – a window with the provider's sign-in page opens. Sign in there as usual.
4. Close the window (or “Save session & close”). The tile now shows connected.
5. From now on: Open – and you're in.

Which services are there?

The catalogue has about 95 services in groups – find any of them with the search field at the top of the tab; click a group title to fold it in or out: Cloud & files (Nextcloud, Seafile, ownCloud Infinite Scale), Media & photos (Jellyfin, Immich, PhotoPrism, Navidrome, Komga, Kavita, Audiobookshelf), Documents & knowledge (Paperless-ngx, BookStack, HedgeDoc, Penpot, AFFiNE, Docmost, CryptPad), Business & projects (OpenProject, Odoo, Vikunja, Planka, Plane, Zammad, Kimai), Git & DevOps, Team chat, Social & Fediverse, Server & admin (Proxmox VE, Portainer, Grafana, Uptime Kuma, Cockpit, n8n), NAS & storage (Synology DSM, Synology Photos, Synology Drive, Proxmox Backup Server, TrueNAS, QNAP, OpenMediaVault, Unraid), Network & security (OPNsense, pfSense, Pi-hole, AdGuard Home, UniFi, Zabbix …), Smart home (Home Assistant, Node-RED, ESPHome, Frigate), Everyday & household (Firefly III, Actual Budget, Mealie, Tandoor, wallabag, Calibre-Web) and more. For almost all of them you enter the address of your own instance.

Server tools often run on their own port – then it belongs in the address, such as https://server.yourcompany.com:8006. Only addresses with https://, a domain and a valid certificate are allowed; http, self-signed certificates and local IP addresses (192.168…) deliberately don't work. Remedy: a reverse proxy or DDNS with a Let's Encrypt certificate in front of the service.

Synology (DSM, Photos, Drive)

1. In DSM under Control Panel → External Access → DDNS, create an address like mynas.synology.me (provider Synology) and choose “Get a certificate from Let's Encrypt” – or add one under Security → Certificate.
2. Forward port 5001 to the DiskStation in your router (or use a reverse proxy).
3. In DasDing, enter https://mynas.synology.me:5001 for Synology DSM and click Connect. You sign in yourself in the window, also with a two-factor code; afterwards the session stays in the vault.
4. Synology Photos and Synology Drive are separate tiles with the same address – they open the respective app directly. QuickConnect addresses (quickconnect.to) redirect several times and are not suitable.

Sign in from wallet (optional)

When a session expires, you have to sign in with the service again. If you like, store the service's user name and password in the vault (checkbox on the right). Then the 🔑 Sign in from wallet button fills the sign-in form – but only when you press it, and only on the provider's real sign-in page. You type a two-factor code yourself – or let the app insert it (next section).

2FA code from the vault (optional)

If you use two-factor sign-in with an authenticator app for the service (e.g. Proxmox, Synology, Nextcloud), you can store the 2FA key in the vault: tick “Store 2FA key in the vault”, then enter the text key the service shows below the QR code during setup (“enter key manually”), or the whole otpauth:// address. When the service later asks for the code, press 🔢 Insert 2FA code – the app computes the current 6-digit code and puts it into the code field (if that doesn't work, the code is shown in the message so you can type it).

• The key stays encrypted in the vault (field “otp”, as in KeePassXC) and is never shown again.
• It is only inserted into the service's window and only on the service's own address.
• Keep in mind: if password and 2FA key are in the same vault, your master password alone protects both. If you don't want that, keep the 2FA key in your authenticator app.

Frequent questions

Does DasDing see what I do in that window?

No. The window talks directly to the provider; nothing goes through a DasDing server, nothing is recorded.

What happens when I lock the vault?

Open integration windows close; the session is saved first. After unlocking you're back in with “Open”.

What does “Disconnect” do?

It deletes session, credentials and tokens from the vault and signs out with the provider where possible. Afterwards it's as if you had never connected the service.

My service isn't in the catalogue.

Tell the admin: a service with a normal sign-in page can be added in a few minutes. Further ones arrive with an update on request.

Why do some services say “coming soon”?

These services need a registration of DasDing with the provider that is still in progress. They will be enabled with an update.

If something doesn't work

• “Sign-in needed”: the session has expired – “Connect” and sign in again.
• A link opens in your normal browser: that's intended – foreign pages aren't allowed into the window.
• On Linux, passkeys don't work in the built-in window. Use a password with a two-factor code there.
• The instance address is rejected: it must be reachable via https:// and have a real domain name (no IP address, no “localhost”).

---

This guide is also available in the program under 📖 Guides – with jump links to the other guides.