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 line

Augos is a hierarchical platform: a site contains its lines, and each line is a measurement point. Access is bound to the measurement point, not to a module or a screen, and it's granted point by point. Someone given a point can see that point; if they need others, those are granted too. No one sees a point they haven't been granted, so a supervisor over one line has no sight of another, and only a user with portfolio-level access can pull across the whole operation.

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, reading the dashboards and reports for their lines and nothing more. Others can also act, classifying a pending stop or changing certain settings. You tell us who needs access to which lines 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 isn't charged per user. There's no limit on the number of people who can have it, and adding another costs nothing. Most platforms in this space charge by the seat; Augos doesn't, so everyone who should see the numbers can, from the whole plant management team to a single line's operators, 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 can't pull a portfolio-wide export or payload, so there's no way around the permissions.

5 · Why it matters here

Manufacturing telemetry reveals output, shift patterns and named-operator performance, so isol