Roles & access (RBAC)
A person sees only the measurement points they should, and an access level sets what they can do with them. Everyone who needs the data can have it, with no limit on users and no per-user charge.
1 · Access is bound to the measurement point
Augos is a hierarchical platform: a site contains main switches, which contain sub-meters. Access is bound to the measurement point, the device or node in the hierarchy, not to a module or a screen, and it is granted point by point. Someone given a point can see that point; if they also need the points beneath it, access to those is granted as well. No one sees a point they haven’t been granted, including the ones alongside theirs, so a tenant given their own sub-meter has no sight of the neighbouring tenant’s meter or the building above them.
2 · Levels of access
Alongside the points a person can see, an access level sets what they can do with them. Some people are view-only, seeing the dashboards and reports for their points and nothing more. Others can also act, completing a bill verification, setting up a trigger, or changing certain settings.
You tell us who needs access to which points and at what level, and we set it up; changing it later works the same way.
3 · Add as many users as you need
Access is not charged per user. There is no limit on the number of people who can have access, and adding another costs nothing. Most platforms in this space charge by the seat; Augos does not, so everyone who should see the data can, from the whole finance team to a single tenant, and cost never limits who you give access to.
4 · The same boundary everywhere
The same access applies however the data leaves the platform. A report on screen, a file export, an AI-ready payload or an API call only ever returns the points that person is cleared for. Someone without portfolio-level access cannot pull a portfolio-wide export or payload, so there is no way around the permissions.
5 · Augos staff access
Access by Augos comes in two forms. Access to the underlying servers, databases and backups is tightly restricted to authorised Augos and data-centre staff on a need-to-know basis, with every access logged and reviewed. The full terms are in Data security & storage.
The platform itself is different. Augos staff who use it to support and run the service can see customer data across accounts; that access is not scoped to a single customer. The point and level controls above govern who in your organisation sees what, not what the Augos team running the platform can see.
6 · Common questions
How is access decided?
You decide. For each person you tell us which measurement points they need and which access level they should have, and we add the access from that. From then on they see only those points and can do only what their level allows.
How do I change someone’s access?
Let us know what should change, the points, the level, or both, and we update it.
Does it cost more to add users?
No. Access isn’t charged per user, so you can add as many people as you need, each with the right role, without a per-seat cost.
Can a tenant see the rest of the building?
No. A tenant or sub-user is scoped to their own point and is denied the points alongside it and the levels above. Access is bound to the point, so one tenant cannot see another’s meter.
Does the same access apply to exports and the API?
Yes. The same point-level permissions govern every surface: the platform itself, file exports, AI-ready payloads and the API. An export or an API call only returns the points the person behind it is cleared for.
Who at Augos can see my data?
Two different things. The underlying servers, databases and backups are reachable only by a small number of authorised staff on a need-to-know basis, and every access is logged. The platform itself is different: Augos staff who use it to support and run the service can see data across accounts, since that access isn’t scoped to one customer.