The Sitemate Wallet field lets workers attach credentials they already hold - licences, ID documents and other cards - straight from their Sitemate Wallet into Dashpivot forms. Instead of collecting physical documents or chasing re-uploads at every induction, the card is attached digitally when the worker fills out the form, and you can view and export it from Dashpivot.
Prerequisites
Before you begin make sure you have the following:
Plan: All Plans
Permission: Org Controller
Skills Required: Dashpivot
Device Type: Computer
Subscription: Dashpivot
Before you start
Cards can only be attached in the Sitemate app.
Dashpivot Web and Dashpivot Mobile display the field and the attached card, but you cannot attach a card from either of them
Card types: Sitemate provides a set of ready-made card types. ID Proof (Passport, Government ID, Driver Licence), and Credentials which are grouped by region (Australia, New Zealand, North America, UK & Ireland).
Each Wallet field can collect one card. Add a separate Wallet field for every card you would like to collect.
Workers are provided notice of the Wallet behaviour and visibility before adding their first card
Step-by-Step Instructions
Step 1: Add a Sitemate Wallet field to your template
Open your template in the Template Editor
Under the Sitemate Wallet header, drag in the Sitemate Wallet field
Select the card type from the Link to a card dropdown, or start typing to search. Search covers every card type across both ID Proof and Credentials.
The field label renames itself to the card name once you select a card. You can still edit the label
Adjust the Field Settings. Two of the four settings are fixed and cannot be changed:
Required on Mobile - toggleable. It is labelled mobile-only because a card can only be attached in the app
Hide in Form PDF Exports - toggleable. Leaves the card out of the form PDF
Exclude in Cloning - always on and cannot be turned off. When someone clones a form, the card is not carried across
Exclude in AI Form Fill - always on and cannot be turned off
Tip: you can add as many Wallet fields to a template as you need, including two fields linked to the same card type.
Step 2: Turn on Save forms to Sitemate Wallet (optional)
Go to Template Settings > View Settings and turn on Save forms to Sitemate Wallet. When a worker completes this form in the Sitemate app, a copy is saved to their Wallet automatically, ready to access anytime.
This is useful for forms workers are asked to produce again later - inductions, VOCs and competency records - so they have them on hand at the next site.
The setting is off by default and appears on every template, not only templates that contain a Wallet field. It is separate from the Wallet field itself, so you can turn it on for a form that collects no cards at all.
Step 3: Workers attach their card in the Sitemate app
When a worker opens the form in the Sitemate app:
If they already have one matching card in their Wallet, it is attached automatically.
If they hold multiple cards of the same type, they are prompted to choose which one to attach.
If they don't, they can add the card while filling out the form - and it's saved to their Wallet for next time.
Step 4: View card details on the form
Once a card is attached, the form shows a card thumbnail with the card name, the credential number (licence number, passport number, document number, depending on the card) and the expiry date (where applicable)
Click on the thumbnail to open the full card details. The card photo can be opened from inside that view.
Card details are read-only in Dashpivot. The card is captured as it was at the moment the form was submitted - if the worker later updates that card in their Wallet, the form keeps the version it collected.
Step 5: Review cards in the register view and exports
Once forms start coming in, the Wallet field appears as a column in the register view, with sub-columns for the card name, licence number and expiry date.
To view a card, hover a cell for a snapshot of the submission, or click the card thumbnail to open the read-only card details
The form PDF renders the card details as a table. The register view PDF matches what's on screen, and the register CSV includes the Wallet sub-column data
What's coming up
Custom cards — set up your own card types in Dashpivot, rather than choosing from the ready-made Sitemate card types. (Currently on hold for Q4 pending initial feedback)
Request a card — users will be able to request any missing cards on Web and Mobile to be added to the standard set
Adding photos on Card Thumbnails
Sorting and filtering on Wallet field columns in the register view
A single view of every card collected across your workspace
Notes
Cards are a snapshot taken at submission, not a live link to the worker's Wallet.
Wallet fields can't be placed below the first Approval Signature in a workflow template
FAQs
Can I add more than one card to a single Wallet field?
No. Each Wallet field collects one card. Add a separate Wallet field for each card you need - you can add as many as you like, including two fields linked to the same card type.
What happens when someone clones a form that has a Wallet field?
The card is not carried over to the cloned form. Wallet fields are excluded from cloning for compliance reasons
What happens if a worker updates their card after submitting the form?
Nothing changes on the submitted form. The form keeps the card details as they were at submission. The updated card will be used the next time they fill out a form.
Can I edit the card details in Dashpivot?
No. Card details are read-only. Only the worker can update their card, in their Wallet.
Does the Wallet field work with logic fields?
Yes. A Wallet field behaves like any other field inside a logic section, and it renders correctly in the form PDF when nested in one.
What happens if a card is expired?
A worker can't submit the form with an expired card. They are asked to update the card in the Sitemate app first.