Update Home

Home.md

@@ -1,5 +1,3 @@
-# Not complete - Complete help in app!
-
 # oAI-Web - Help
 
 ---
@@ -23,6 +21,9 @@
   - [Inbox](#inbox)
   - [Email Accounts](#email-accounts)
   - [Telegram](#telegram)
+  - [DAV (CalDAV / CardDAV)](#dav)
+  - [Pushover](#pushover)
+  - [Webhooks](#webhooks)
   - [Profile](#profile)
   - [Personality](#personality)
   - [2nd Brain](#2nd-brain)
@@ -260,6 +261,38 @@ For handling accounts, you can also configure:
 - **Default Agent**: agent dispatched for messages that don't match any trigger rule
 - **Trigger Rules**: same keyword-matching logic as email inbox
 
+### DAV (CalDAV / CardDAV)
+
+Configure your personal CalDAV and CardDAV connection. Admin users see this as the **DAV** tab; regular users see it as the **CalDAV / CardDAV** tab. There is no system-wide fallback — each user configures their own credentials independently.
+
+- **CalDAV**: server URL, username, password, and calendar name for reading and writing calendar events
+- **CardDAV**: tick "Same server as CalDAV" to reuse the same credentials, or enter separate CardDAV URL, username, and password
+- **Allow contact writes**: when enabled, agents can create, update, and delete contacts (not just read them)
+- **Test buttons**: verify your CalDAV and CardDAV connections without leaving the settings page
+
+### Pushover
+
+Pushover sends push notifications to your iOS or Android device.
+
+- **Admin tab**: sets the shared **App Token** (registered once for the oAI-Web installation) and the admin's personal **User Key**
+- **User tab**: set your personal **User Key** — the App Token is provided by the admin and shared by all users
+
+Each user's User Key maps to their own Pushover account and devices. The App Token is shared across all users of the same oAI-Web instance — this is the standard Pushover model (one app, many users).
+
+To get your User Key: log in to [pushover.net](https://pushover.net) — it's shown on the dashboard immediately.
+
+### Webhooks
+
+Inbound webhooks let external services (iOS Shortcuts, GitHub, Home Assistant, IFTTT) trigger agents via HTTP.
+
+- **Create a webhook**: give it a name, description, and assign an agent. The token is shown **once** at creation — copy it immediately.
+- **Trigger via POST**: `POST /webhook/{token}` with body `{"message": "your message"}`
+- **Trigger via GET**: `GET /webhook/{token}?q=your+message` (useful for iOS Shortcuts URL actions)
+- **Rotate token**: generates a new token and invalidates the old one
+- **Enable/disable**: toggle without deleting the webhook
+
+Outbound webhook **targets** (for agents to call external services) are managed in the same tab under "Outbound Targets".
+
 ### Profile
 
 Available to all users. Contains:
@@ -270,7 +303,6 @@ Available to all users. Contains:
 - **Two-Factor Authentication (TOTP)**: enable/disable TOTP-based MFA. On setup, a QR code is shown to scan with any authenticator app (e.g. Aegis, Google Authenticator). Once enabled, every login requires a 6-digit code.
 - **Data Folder**: shows the path of your personal folder used by agents and the Files page.
 - **Telegram Bot Token**: per-user Telegram bot token (optional). Overrides the global token for your sessions.
-- **CalDAV**: per-user CalDAV server, credentials, and calendar name. Overrides the global CalDAV config.
 
 ### Personality