How it works
Add one Yes/No field to the Item, then let two groups of buttons watch it.
Then, in the Page Editor, put your internal buttons inside one
Container and the hire buttons inside another, and give each container a condition in the
Visibility group:
What goes where
The hire buttons are the point: a form on Jotform or
Google Forms can be filled in by anyone, so the hirer’s
crew can complete a pre-start check without you setting up a single account for them.
Set a default, or existing Items will surprise you
Add a Yes/No field to a Collection that already has Items and those Items have no value for it — notfalse, nothing. A condition testing == false would then hide your internal buttons on every
machine you already own.
Two things avoid it:
- Give the field a Field Default so no Item is ever unset.
- Write the internal condition as
item.on_hire != truerather than== false, so anything that is not explicitly ticked counts as in the yard.
What it needs
- One Yes/No field on the Collection, with a default
- Two Containers on the Page, one condition each
- A form the hirer can open without an account
- Somebody to tick the box. This is the real cost: it is a step in your hire-out process, and a machine that goes out with the box unticked shows the hirer buttons they cannot use