What's new
Some government portals hold public records behind a login and show them only in a web interface. Portal accounts lets your organisation connect such an account once, so the Public Records section can read those sources too.
The first portal is NYC.ID, which unlocks FDNY's FIRES — fire-prevention permits and inspections for New York City.
How it works
- Settings → Third-Party Services → Portal accounts. Press Connect account, enter the username and password, optionally note where the records are inside the portal, and confirm that Relm may sign in on your behalf. Then Test connection.
- When a lookup matches a source that needs a login, Relm starts an isolated browser, signs in with the connected account, searches the property's address and reads the result table. Rows come back as the portal shows them, cited to the portal.
- With no account connected, the source is listed in coverage as needs a portal login, with a link to connect one. Nothing is fetched and nothing is charged.
- Org admins can share one login with everyone in the org and can add a portal Relm does not know yet.
Built to be safe with your credentials
- The password is sealed on the server with a key that exists only in the server environment, bound to that one login. It is written once, revealed only inside the isolated browser at sign-in, and never shown again — not in Settings, not in the API, not in logs.
- One rejected password pauses the login. Relm never retries on its own, so repeated attempts cannot lock the account; fix the password and test again to reinstate it.
- Two-factor accounts are detected and reported, not attempted — use an account with only a password for now.
Full guide: Portal accounts.