KeepOrg for Windows =================== keeporg-tray.exe is the tray application. keeporg.exe is the same program for a command prompt: administration commands, and the agent without a tray. First run --------- 1. Copy both files to %LOCALAPPDATA%\Programs\KeepOrg and start keeporg-tray.exe. A padlock appears in the notification area. 2. Choose Open Config from its menu, set "server_url" to your server, for example "https://keeporg.example.com", and save. 3. Choose Sign In... and approve the code in the browser that opens, with your password or single sign-on. Your databases appear in %UserProfile%\KeepOrg. Open them with KeePass, KeePassXC or any compatible application: every save is pushed to the server, and changes made by other people are applied to the files. The Databases submenu shows each one's state and opens it. Tick Start at Login to start KeepOrg when you sign in to Windows. Settings -------- %AppData%\keeporg\config.json holds every setting, and the tray applies an edit as soon as it is saved: server_url the server, as a browser sees it device_label this computer's name in the server's session list mirror_dir where the .kdbx files are kept poll_seconds how often local saves are looked for request_timeout_seconds the limit on one request to the server ca_file a PEM bundle, for a server behind a private CA log_file the log; empty means keeporg.log beside config.json notifications desktop notifications (not shown on Windows yet) username, token written by signing in Without the tray ---------------- keeporg.exe login -server https://keeporg.example.com -user you keeporg.exe run keeporg-task.xml starts `keeporg.exe run` at logon through Task Scheduler, for a machine where nobody uses the tray: schtasks /create /tn KeepOrg /xml keeporg-task.xml Only one agent synchronizes a directory at a time; a second one reports that the first is running and stops. Conflicts --------- If someone else saved first, your save is kept beside the file as .conflict-.kdbx and the server copy is restored. Open both in KeePass and merge them, or ask a group administrator to switch the database to another merge strategy.