Product · Users and access
People can do only what their team is allowed to do.
And every decision is recorded with a name, a time and a reason. Pick a person to see where their access comes from.
Person
Team
Access profile
Permissions
- process.round.execute
- process.reading.record_human
- process.observation.record
- maintenance.work_request.submit
Person
Team
Access profile
Permissions
- maintenance.work_order.read
- maintenance.work_order.execute
- maintenance.work_order.task.record_outcome
- attachments.attachment.upload
- maintenance.work_request.submit
Person
Team
Access profile
Permissions
- maintenance.work_order.prepare
- maintenance.work_order.release
- maintenance.scheduled_work.defer
- inventory.replenishment_request.manage
- maintenance.work_request.submit
Person
Team
Access profile
Permissions
- inventory.movement.receipt
- inventory.movement.issue
- inventory.reservation.manage
- inventory.stocktake.count
- maintenance.work_request.submit
Person
Team
Access profile
Permissions
- maintenance.work_request.accept
- maintenance.work_order.release
- maintenance.work_order.verify_completion
- maintenance.work_order.close
- maintenance.work_request.submit
Person
Team
Access profile
Permissions
- process.condition.manage
- process.routine.manage
- process.operational_action.record
- process.outcome_assessment.record
- plant.plant.read
- maintenance.work_order.read
- reliability.reliability.read
- audit.event.read
A user never gets an access profile directly; access always comes through a team.
01 · Sign-in
Sign in with a mobile number and password.
Users sign in with an Iranian mobile number. Passwords are stored as non-recoverable hashes, and a password reset revokes every existing session.
Password reset · all previous sessions are revoked
02 · Teams and access profiles
Access comes from teams, not from names.
Teams are given access profiles, and each access profile is a published revision of permissions. Add someone to the stores team and they can do what a storekeeper does, and nothing more.
There is no direct link from a user to an access profile
03 · Approvals and decisions
A decision is a record that doesn’t change later.
Approvals, waivers, deferrals and skips are each a lasting decision with its authority, reason and effect.
04 · Separation of duties
Whoever did the work doesn’t verify it themselves.
For decisions that need independent approval, the person who performed the work can’t also be the approver, even if they belong to two different teams.
Independent verification not possible: you performed this work.
Verify work · WO-104205 · Change history
Who did what, when, on which record, and why.
Records are corrected, not overwritten. Every action is attributed to its real actor: a person, a defined machine integration, or a specific system job.
| Time | Actor | Action | Record | Reason | Outcome |
|---|---|---|---|---|---|
| 10:41 | Ms Ahmadi | Release | WO-1042 | — | Done |
| 11:02 | Mr Nouri | Issue | SK-45 · WO-1042 | — | Done |
| 11:20 | Integration SCADA-GW | Record reading | WW-MP-DO-1 | — | Accepted |
| 12:05 | Ms Ahmadi | Defer scheduled work | SW-0287 | Screen 2 under repair | Done |
| 13:30 | Mr Mousavi | Verify work | WO-1042 | — | Refused · separation of duties |
| 13:34 | Eng. Rezaei | Verify work | WO-1042 | — | Done |
06 · Access changes
Access changes take effect immediately.
When someone leaves a team or a team’s access profile changes, the affected sessions are revoked and their offline packages stop being valid.
If someone recommended Waiotech to you, the next step is a short conversation.
Tell us about your plant and how you work today, and we’ll show you Waiotech on work like yours.