New: the AI firewall watches the whole platform and explains each incident in plain words. See how it works

How a multi-organisation IoT platform keeps organisations apart: row-level security in practice

One forgotten filter can leak another customer's data. How Hermetry 2.0 keeps organisations apart in the database, the application and the device layer.

A multi-organisation IoT platform keeps organisations apart by enforcing the boundary in the database as well as in the application. In Hermetry, every table that holds organisation data has row-level security: a database session is bound to one organisation and can only read and write that organisation’s rows, even if application code asks for more.

Hermetry connects field devices to dashboards, rules and alerts: IoT telemetry and SCADA in one platform. Hermetry 2.0, released on 26 August 2026, lists “organisations kept apart in the database” among its highlights. The first thing I ask of any platform that holds many customers is where that separation is enforced, and an answer that relies only on a filter in application code is the one I trust least.

Why is an application filter not enough?

One forgotten filter is enough to leak. Every query that has to remember “and only this organisation” is a chance to forget it: in a new report, a new API endpoint, a fix written in a hurry.

OWASP put broken access control first in its Top 10 for 2021, up from fifth, and kept it first in the 2025 edition. Its list of examples includes “viewing or editing someone else’s account, by providing its unique identifier”, which in a multi-customer system can mean another customer’s devices.

What does row-level security do?

Row-level security moves the organisation check out of each query and into the database. A policy on the table decides which rows a session may see, and the database applies it to every read and write, whatever the query asks for.

How much a bug can leak depends on what the session is bound to. In Hermetry it is bound to one organisation, so a query that forgets its filter returns that organisation’s rows and nothing else, and the bug stays inside one customer’s data.

How does Hermetry keep organisations apart?

Hermetry enforces the separation at three levels, described in its security model:

LevelHow it is enforced
DatabaseRow-level security on every table that holds organisation data; a session is bound to one organisation.
ApplicationEvery request is resolved to one organisation and one membership; a member of one organisation has no rights in another.
DevicesA device belongs to one organisation; its credential, topics and commands are bound to it, and it never receives another device’s messages.

Jobs that must work across organisations, such as retention, usage counting and billing, list organisations through one guarded path and then work inside each organisation’s own boundary. I like that design, because the code that crosses organisations sits on one path that can be reviewed.

Can one person work in several organisations?

Yes, with a separate membership in each. One account can belong to several organisations, and the person picks the one to work in after sign-in. A session signed in to one organisation does not carry rights into another.

Each membership has its own role, so the same person can be an Owner in one organisation and a User in another (the built-in roles are Owner, Admin and User). A role change ends that member’s sessions in the organisation, so the new rights apply at once. When Hermetry suspends an organisation, every open session ends and its devices are disconnected and refused at login.

Isolation separates organisations; it does not decide who inside your own organisation may do what. That part stays with you: who you make a member and with which role, second factors, device credentials and API keys. I covered how to split those duties in least privilege in OT. Each organisation’s data also stays in the home region set when the organisation is created, in the EU, the US or Türkiye.

Frequently asked questions

Is an organisation the same as a tenant in Hermetry?

Yes. An organisation is your own space on Hermetry, and the API and some technical screens call it a tenant or a workspace. Everything you create belongs to it, including its devices, members, settings and audit log, and a session in one organisation carries no rights into another.

Can a device send data to two organisations?

No. A device belongs to exactly one organisation. Its credential, topics and commands are bound to that organisation, and it never receives another device’s messages or another organisation’s.

Does the routing directory know who my organisation is?

No. The global directory that routes requests knows only which region and node an organisation lives on. It holds no name, address, owner or setting of the organisation; those stay with the organisation’s data in its home region.

Share

See your field data live this week

Start a trial in your region with your first devices, or book a demo and bring your own use case.