Doorcom

The Doorcom manual

How to install Doorcom, set a building up, sign residents up, and run the door, the issues, the trades, the documents and the messages day to day. Each chapter names the real pages and fields, with screenshots of this build.

New to Doorcom? Start with Getting started. Running it on your own server? See Hosting and backups.

Getting startedInstall the binary, make the first owner login, create a building, add a door and the flats, and put the poster on the door. Buildings and doorsBuilding details, release modes, dial codes, rotating a door code and testing the release. Posters, stickers and claim cardsThe printable pieces: the A5 and A4 door poster, the door sticker and the per-flat claim cards. Flats and floorsAdding flats in bulk, labels, available, claimed and disabled, claim codes and floors. Signing residents upThe on-screen sign-up dialog, claim cards, texting or emailing the link, a second person in a flat, and moving out. The resident portalThe status hub, bell log, quiet hours and preferences, Telegram linking, documents and reporting a problem. Rings, Telegram and the phone lineHow a ring flows, first answer wins, keypress confirm, quiet hours, rate limits and messages left at the door. IssuesThe issues list, the thread, replying, the status board, marking fixed and the resident's confirmation. Trades and jobsAdding trades, the login QR, sending a job from an issue, the job page and job done. Staff loginsThe maintenance role: employees who do the jobs and see only their jobs, the issues and the board. Documents for rentersThe UK checklist, uploading against a flat or the building, the coverage table and expiry dates. MessagesTelling a floor, the whole building or chosen flats: the three-step wizard, templates and sending from an issue. Users, roles and permissionsOwner, manager and employee logins today, and what is being added. SettingsTelegram bot setup with BotFather, the SMS gateway, SMTP, the PBX fields, retention and rate limits. BillingClaimed flats, the monthly snapshot and the CSV export. The JSON APIThe bearer token per building and the ring, release and rings endpoints. Hosting and backupsRunning on Linux with systemd and Caddy, the database file, backups and upgrades.