Calendars
The Gadka server connects to Google Workspace, Microsoft 365 and CalDAV. Calendar sync is off by default.
Calendar integration lets users see meetings in Gadka, receive reminders and automatically set their status during a meeting. It is off by default. Only the server connects to calendar providers.
Before you begin
- You need root access to the server.
- For Google and Microsoft, you need permission to register an OAuth application with the provider.
- The server needs outbound network access to the provider's hosts. See Firewall and ports.
Generate an encryption key
The server uses this key to encrypt tokens and app passwords.
openssl rand -base64 32 | tr -d '\n' | sudo tee /etc/gadka/calendar-key > /dev/null
sudo chown root:gadka /etc/gadka/calendar-key
sudo chmod 0640 /etc/gadka/calendar-keyRegister applications with the providers
Use the following redirect URI for both providers.
https://gadka.example.com:6543/v1/calendar/oauth/callback| Provider | Where to register | Required permissions |
|---|---|---|
| Google Cloud Console | calendar.events scope | |
| Microsoft | Entra ID | Calendars.ReadWrite, User.Read, offline_access |
Save each application's secret in a separate file under /etc/gadka, with ownership set to root:gadka and permissions set to 0640. CalDAV requires no registration.
Enable calendar integration
calendar:
enabled: true
sync_interval: 5m
google: { client_id: "<id klienta>", client_secret_file: /etc/gadka/google-calendar-secret }
microsoft: { client_id: "<id aplikacji>", client_secret_file: /etc/gadka/ms-calendar-secret, tenant: organizations }
caldav: { allowed_hosts: [cloud.example.com, caldav.icloud.com] }
crypto:
mfa_key_file: /etc/gadka/mfa-key
calendar_key_file: /etc/gadka/calendar-keyOnly configured providers appear in the app. Omit any you do not use. Set sync_interval to a value between 1m and 1h.
Check that you can connect a calendar
sudo systemctl restart gadkaIn the app, open Preferences and find Calendars. Each configured provider has a Connect button.
Allowed CalDAV servers
- A hostname on its own, such as
cloud.example.com, allows only HTTPS on port 443. - For another port, specify the full URL, such as
https://dav.example.com:8443. - An entry beginning with
http://allows an unencrypted connection. It sends the app password in plain text, so only use it on a trusted internal network.
Workspace policy
In Admin, under Calendar integrations, the owner or an administrator decides whether meeting titles can appear in users' statuses. See Workspace policies.
The server only stores events from the past 7 days and the next 7 days. These are the events that appear in Gadka.
- Calendar and meetings for users
- Workspace policies