Structure
Who sees what, and where everything lives.
It is the part nobody watches in a demo and the one that decides whether the system holds up once you stop being ten people. Who gets in, what they see when they do, and which plant or which vessel each record belongs to. Set up once, then never thought about again.
Teams & Users
Each person with their own account and scope
Locations
Where each machine physically sits
Units
The site, the vessel, the plant
Teams & Users
Four roles, and none of them decorative.
They are not generic permission levels with nice names. Each one exists because there is a real person in a plant who works that way, and what they see when they open the app is different in all four cases.
Administrator
Runs the whole account. Configures, adds people, sees every site and decides what gets measured and against which target.
Web and mobileSite manager
Their site, all of it. Assigns the week's work, approves purchases, watches their dashboards and answers for their compliance.
Web and mobileTechnician
Maintenance. Executes what is assigned, closes orders with what was actually used and raises reports. On the web, only their own work.
Limited web and mobileOperator
Shop floor. Fills checklists, reports what they see, requests material and declares production. Never opens the web, and does not need to.
Mobile onlyAnd each with their own account, which is not a whim.
In a plant or on a vessel the operators are the overwhelming majority, and if adding each one were expensive, the ending is always the same: one account shared by everybody. And there the whole product collapses. The signature, the sealed dossier and the "completed by" on every record all depend on knowing who did what, which is literally what the standard requires. That is why operator access is priced so that sharing it never pays off.
- One person, one account
- Invited by link, no passwords over WhatsApp
- Teams to distribute work
- And the role changes when the job does
Locations
"It is in bay B" is not a location.
When an asset has no place, the technician loses ten minutes asking where the machine is, and the inventory has no idea which store it is deducting from. Locations are the physical map of the operation, arranged in two tiers: the large zone, and inside it the specific sub-zone.
And a sub-zone cannot hang off a zone belonging to another site. It sounds like a programmer's detail, and it is what stops Zaragoza's line 1 from ending up inside Barcelona's bay, which is the kind of error nobody spots until a dashboard returns a strange number.
- Zones and sub-zones per site
- The asset lives in a location
- The store knows where it deducts from
- And its document folder is created on its own
Unit
The site everything below belongs to
Zone or area
Blow moulding bay, engine room, deck
Sub-zone
Line 1, forward store, paint booth
Standalone
The one on its own, with no site assigned
Units
Two plants are not two programs.
A unit is a site: a plant, a vessel, a centre. Everything created in FluX knows which one it belongs to, which is why you can look at one alone or all of them together on the same dashboard, without mixing anything and without maintaining two parallel systems nobody ever reconciles.
- A site, a vessel, a centre
- Every record knows which one
- Look at one alone or all together
- And fleet-wide things are not duplicated
Unit selector
- All unitsThe whole company
- Zaragoza plant48 assets
- Barcelona plant31 assets
- Central warehouse13 assets
Example data. What you pick here filters the whole app
And what belongs to everyone, belongs to everyone.
Some things are not owned by one site: the supplier all three plants buy from, the form template the whole fleet fills in, the procedure that applies on any vessel. Those are marked as fleet-wide and appear everywhere, with no need to duplicate them once per site and end up with three versions that no longer say the same thing.
Why this gets decided at the start
Everyone sees theirs, and only theirs
Scope is not a screen preference: it is enforced in the database. A manager of one plant cannot read the other's data even by editing the address bar, because the permission does not live in the button hidden from them.
The data knows where it came from
Every record carrying its site is what lets a dashboard tell the truth. Without it, adding two plants gives a number that means nothing, and filtering by one leaves out things that did belong to it.
Growing does not mean starting over
Adding the third plant means creating a unit, not standing up another installation. What already works keeps working, and the new one enters the same dashboards from day one.
And whoever leaves stops getting in
The person is deactivated and their access ends, but what they did keeps their name on it. A history that loses its author when somebody changes jobs is worth nothing to an auditor.
Shall we map your structure on the call?
Tell us how many sites you have and who does what, and we will draw it in front of you. It takes half an hour, and it is what stops you rebuilding it a year from now.