Your account, name and product

Your name

Set it under Account. It is what appears on ICS forms you file and beside your entries in incident logs; without it those records carry your email address. Changing it affects what you file from then on. Records already filed keep the name they were filed under, because that is what makes them a record.

Password

Change it on the same page without signing out. The new password applies the next time you sign in.

Two-factor authentication

Set up an authenticator app shows a QR code and a key. Add Calchis to Google Authenticator, Authy, 1Password, Microsoft Authenticator or any app that does time-based codes, then enter the six-digit code it shows to finish. From then on every sign-in — password or emailed link — stops for a code before anything else loads. Calchis never sees the key or the codes. Remove turns it off again; you need a current code to do that, which is the point. If you lose the app, sign out and contact support from the address on the account.

Export everything

Download account export builds one zip. It holds every incident with its boards, SITREPs, checklists, shift handoffs, after-action reports and attached files, plus your monitored areas, triggers, portfolios and settings, as JSON. You can take it at any time, not only when leaving.

Your product

Calchis serves different jobs: emergency management, insurance-linked securities, and facilities. Your Calchis product tidies the navigation down to the tools for your job and changes what your dashboard leads with: active incidents for emergency management, each site’s hazard vulnerability analysis for facilities, and positions with a live event in coverage for ILS. For a facility it also words each alert condition’s decision for a facility rather than a county emergency operations center. Each card on that page lists exactly which tools you will see. It does not change your plan or your price. Show me everything instead is the default and shows every tool your plan includes.

Demo data

A new account is empty. Demo data loads a worked example — a county river flood at full activation with its boards, wall display and ICS forms, a monitored county, a six-site portfolio and a readiness picture — so every page has something in it. Each part sits behind the same plan gate as building it yourself, and a part your plan does not include is listed as not included rather than loaded through the back door. The incident is always flagged as an exercise. Remove demo data takes out exactly the rows the demo wrote, found by the names it gave them, and nothing you made. The demo incident itself is closed and archived rather than erased, because an incident's record is kept; it drops off every list. Loading again replaces the demo with fresh clocks.

Closing the account

Close account removes your account and what is attached to it: saved areas, portfolios, triggers and API keys. Incident and audit records keep the entries you made, without your name on them, because a shared operational log is not one person’s to delete. Closing cannot be undone. Take the export first.