How do I set up document mappings for TempWorks?

Last updated: September 25, 2026

Completed forms sync to TempWorks automatically — every submission uploads to the employee's TempWorks profile, no mapping required. Document mappings are now optional overrides: add one only when a form should file under a specific TempWorks document type.

Before you start

  • Your TempWorks integration must already be connected and active (credentials saved). If you haven't done that yet, see How do I set up the TempWorks integration?

  • You need account-owner or admin permissions in Onboarded.

  • Forms without a mapping upload under a document type described as Documentation in your TempWorks account. Confirm that type exists — if it doesn't, unmapped forms are skipped silently.

  • The employee must be synced to TempWorks — if Onboarded hasn't pulled their record yet, the upload is skipped.

When to add a mapping

You don't need a mapping for a form to sync. Whenever a live TempWorks integration exists, every completed form uploads to the employee's TempWorks profile — mapped or not. Unmapped forms file under your Documentation document type.

Add a mapping when a form should file under a different document type — for example, filing your Federal I-9 form under TempWorks' I-9 type so it's grouped with the rest of your compliance documents.

If your TempWorks tenant has no Documentation document type, unmapped forms don't upload at all. Onboarded looks for a document type described as Documentation and files there when a form has no mapping. When that type is missing, the upload is skipped — nothing arrives in TempWorks, and nothing surfaces as an error to the employee. Either map every form explicitly, or confirm a Documentation type exists in TempWorks.

Where the document type list comes from

Onboarded asks TempWorks for your document types each time you open the picker rather than holding a fixed list, so you choose from the types configured in your own TempWorks tenant. Nothing is cached — if someone adds a document type in TempWorks, reopen the picker and it's there.

Those types come from your Onboarded account's TempWorks connection, and there's one connection per Onboarded account. The list isn't scoped per TempWorks client, per branch, or per hierarchy level — every mapping in your account draws from the same set. Mappings themselves are set per form, and one form can map to more than one document type.

Steps

Open the Configuration step

  1. Navigate to Account Settings → Integrations and click Configure next to TempWorks.

  2. Click through to Configuration (step 2 of the wizard). Document Mappings appear in the lower section of this step, below Field Mappings.

Add an override mapping

  1. Click New Mapping under Document Mappings. The New Document Mapping dialog opens with two fields.

  2. Choose a Form. Search for and select the Onboarded form whose document type you want to override — for example, Federal I-9.

  3. Choose a TempWorks Document Type. It's a searchable combo box that reads Select a document type… until you pick one — start typing to filter. Options are pulled live from your TempWorks connection, so what you see here matches what's configured in TempWorks.

  4. Click Create. The mapping appears in the list immediately and takes effect for any form completions going forward — no re-sync needed.

Repeat for each form you want to override.

Multiple mappings for one form. You can add more than one mapping for the same form. If you do, Onboarded uploads the document once per mapped document type every time the form is completed. Only set up multiple mappings if that's intentional.

Edit or remove a mapping

  1. To edit a mapping, click its row in the list. The Edit Document Mapping dialog opens with the current values pre-filled — update either field and click Save.

  2. To remove a mapping, open it and click Delete. The form keeps syncing — it goes back to uploading under the default Documentation type. Documents already uploaded to TempWorks are not affected.

How it works

When a form is completed, Onboarded uploads a PDF to the employee's TempWorks profile in the background — under each mapped document type, or under Documentation when no mapping exists.

Which PDF gets uploaded depends on the form:

  • If the form has a mapped PDF, TempWorks receives that filled PDF. This is the normal path.

  • If the form has no mapped PDF, Onboarded generates an audit PDF and uploads that instead. The audit PDF carries the submitted data plus an audit trail: a signed timestamp, IP, device and hash for each signature; a document metadata table; a submission timeline showing page, submitted-at time, IP and device; and a raw inventory of every field. It's the same audit PDF you can download from the completed task or pull from the task documents ZIP export — see 📄 How do I view and download PDFs for a completed task?

In TempWorks, the document's name is the form name (for example, Federal I-9.pdf), and its description carries an onboarded- prefixed filename so you can trace it back to the Onboarded submission.

Storage tip. If a form needs to present something long like a 35-page handbook, link to it from a content block rather than attaching it, so only the completed form artifact lands in TempWorks — 📄 How do I embed a PDF directly in a content block for inline viewing? covers the content-block options.

When the upload won't happen

  • Your TempWorks connection isn't active.

  • The employee isn't synced to TempWorks at the time of completion. The upload is skipped and won't retry once they sync later.

  • The form has no mapping and your TempWorks tenant has no document type described as Documentation.

  • The audit-PDF path specifically doesn't run for tasks copied from another task, or for tasks completed outside the normal flow.

Troubleshooting

Document types aren't loading in the dropdown. This means Onboarded can't reach TempWorks — usually a credential or network issue. Go back to step 1 of the wizard, confirm your credentials are saved correctly, and try again.

A completed form didn't upload to TempWorks. Check three things:

  • The employee has a TempWorks record (visible on their profile in Onboarded). If they weren't synced at the time of completion, the upload was skipped — upload the PDF manually in TempWorks for that submission.

  • If the form has no mapping, your TempWorks account has a document type described as Documentation. Without it, unmapped uploads are skipped.

  • The task wasn't copied from another task or completed outside of Onboarded — those don't upload.

"No active TempWorks configuration found" error. Your TempWorks integration has been disconnected. Re-enter your credentials in step 1 of the wizard, then return to Configuration to manage your mappings.

Related