With a signature, the receiving person confirms the handover right on the device. Sometimes it is still missing: things had to move fast, or the person was not there when the action was booked. Then you add the signature afterwards.
History: opening an entry without a signature, adding a signature, entering the name and signing
What a signature consists of
For every signature, Log+Key stores the signature image, the date and the name the signing person enters in a text field. In the History, the Signature column shows whether an action was signed.
Adding a signature afterwards
You need the permission Add Signature Retroactively – admins and owners by default. In the standard role User, the history entry has no More actions button.
- Open the History and find the event, for example via the object name. The Signature column shows where a signature is missing.
- Click the event. The History entry page opens.
- At the bottom, choose More actions → Add signature. The Confirm with signature dialog opens.
- The Name field is prefilled with your own name – if someone else signs, enter their name. Have the person sign in the signature pad.
- Click Confirm with PIN and enter your personal PIN.
The history entry then shows a Signature block with the date, time and name of the person who signed. In the list, the Signature column fills in; Log+Key does not create an additional entry.
Having people sign right at take-out
The simplest way is to capture the signature straight away:
- In the web app, switch on Confirm action with signature in the Take object or Assign object dialog. After confirming, the Confirm with signature step follows: it names the action and the object, for example Take: Funkgerät 02, with the signature pad and the Name below – prefilled with the signed-in person’s name at take-out, and with the receiving person’s name when assigning.
- At the terminal, switch on Confirm action with signature in the Confirm action dialog; the button then reads Continue. The same Confirm with signature step follows as in the web app, with the action and object, the signature pad and the name. If the email receipt is switched on too, you choose the recipients first.
Making signatures mandatory
Whether signatures are offered or required is set by permissions per role – separately for the browser and the terminal. An owner sets them under Settings → Role Management → Manage permissions:
| Permission | Effect | Default |
|---|---|---|
| Signatures in Browser | signature switch in the web app | all three standard roles |
| Signatures Required in Browser | signature in the web app is mandatory | no role |
| Signatures in Terminal | signature switch at the terminal | Admin, Owner |
| Signatures Required in Terminal | signature at the terminal is mandatory | no role |
| Add Signature Retroactively | add a signature later | Admin, Owner |
How to grant permissions is described in Managing roles and permissions.