The permit is a form linked to a job type. Its sections are tagged for check-in or check-out, so one permit can be read on the way in and closed on the way out. A job type without a tagged permit shows no gate step at all.
On the job, the employee who plans the work opens the permit and fills it in. At the kiosk, each worker reads it before check-in and agrees, or reports a problem. Either way they continue, and the answer is recorded against that worker. On the way out, a worker fills in the end-of-works section. A worker who is not the responsible person can leave it empty and just confirm. Check-out answers go into one shared permit for the job.
The kiosk can only write what the permit declares for that step. A permit from another zone, or a worker who is not on the job, is refused. Every sign-off goes on the job’s log with who did it, what they were shown and the reason they gave.
How it plays out
What it uses
Apps involved in this scenario.
Developers
Jobs and events are available through the API and webhooks.
Developer reference →Try this scenario yourself
A seeded sandbox tenant with a reset button.
About the partner area →Want to see it on your own site?
Tell us what the gate has to do. We show you the matching flow.