An industry pack tunes one organization’s CRM for its niche: objects and fields, pipelines, views, a dashboard, extra screens and assistant guidance. Each pack installs into a single workspace, so it never changes another organization’s data model. The first pack is Real estate (module hermios.industry.real-estate): properties, inspections, buyer stages, agency views and dashboard, and a property map.

​
Who can turn a pack on

  • Enabling a pack again later does not reinstall it.
  • Disabling a pack, or letting its access expire, keeps every record and field. Reinstalling or upgrading needs active access again.
  • The generic “install app” API refuses packs the organization has not been granted.
To ask for a pack, contact support.

​
Reading and changing modules from an assistant

The Hermios MCP server exposes two tools for this:
  • read_hermios_modules: the modules available to the workspace, whether each is granted, enabled and installed, and the current revision.
  • configure_hermios_module: enable or disable a module and save its settings. Pass the expectedRevision you last read. A stale revision is refused so two admins cannot overwrite each other.
The caller needs permission to manage application settings in the workspace.

​
Operator endpoints

These are for Hermios staff and need a signed-in full-admin session in the operator workspace with the Security permission. API keys, apps and impersonated sessions are refused. Every change is audited with the operator’s identity.
The property map looks up addresses with OpenStreetMap’s public geocoder and loads OpenStreetMap map tiles, so property addresses are sent to those services.