Configuration
The server configuration file holds the settings for authentication, calendars, files and federation.
The installer writes the settings to /etc/gadka/gadka.yaml. After saving your changes, restart the service with sudo systemctl restart gadka.
Topics
-
Configuration file and environment variables
Settings in the YAML file override the defaults. Environment variables override values in the file.
-
SSO with OIDC
Employees can use their company accounts in a browser or on macOS. The Windows and Linux apps require a Gadka password.
-
Signing in with Keycloak, Microsoft Entra ID and Google
Register the same Gadka redirect URI with any of these three providers. Each provider has its own issuer URL.
-
Account verification with an authenticator app (TOTP)
When signing in with a password, you can use a code from your authenticator app as your second factor. Save the recovery codes in case you lose your phone.
-
Outgoing email and invitations
Gadka displays an invitation link that works once. Send it to the person you want to invite. It expires after 7 days.
-
Calendars
The Gadka server connects to Google Workspace, Microsoft 365 and CalDAV. Calendar sync is off by default.
-
File storage and antivirus scanning
Attachments require storage that supports S3. ClamAV can scan each file before anyone downloads it.
-
Link previews and safety checks
By default, the server blocks domains on the CERT Polska warning list. You can enable page previews separately.
-
Federation with another organization
Two organizations using Standard or Enterprise can share channels once administrators on both sides confirm that they trust each other.