Workplace & Facilities package

Visitor sign-in

A themed reception form signs visitors in, looks up their host, logs the visit, emails the host and has reception confirm an NDA when needed.

OfficialNo integrations neededStarts from a formStarter~5 min setupv1.0.0

Download .utpkg 10 KB How to install

About this package

What it does

Visitor sign-in puts a welcoming, branded form on the reception tablet. The visitor enters their name, company and contact details, starts typing who they are visiting and picks the host from the Staff directory table; the host's email and team fill in by themselves.

Signing in shows a success screen to the visitor and starts the Visitor arrival workflow through its Form submitted trigger: it creates a visit reference and a badge number, adds the visit to the Visitor log table and emails the host.

When the visitor will see confidential information, reception gets a task to confirm the NDA, with NDA signed and Visitor refused buttons. A 12-month retention policy is included for the visitor records. Everything is built in, so it works as soon as it is installed.

Starts from a form

Starts from a form page: open the Visitor sign-in form (/f/<id>) on the reception tablet; each sign-in starts the workflow.

Someone fills in a form to start it: the workflow start form (Run dialog in the app, or your own portal posting to the API) or a standalone form page (/f/<id>) whose Form submitted trigger starts the workflow. People complete User Task forms along the way.

The flow

Step by step

1
Visitor signs in
On the themed form the visitor enters their details and picks their host; the host's email and team fill in from the Staff directory.
2
Welcome screen
Sign in shows a success screen with the host's name and a Next visitor button.
3
Log and badge
The Form submitted trigger starts the workflow: a visit reference and badge number, and a row in the Visitor log.
4
Tell the host
The host gets an email that their visitor is at reception.
5
NDA when needed
If the visitor will see confidential information, reception confirms the signed NDA with the NDA signed or Visitor refused buttons.

Visitor signed in

When a reusable form is submitted (its own page, the API or as a task form)

Visit reference

Store a value

visit_ref = VIS-ƒ FORMAT_DATE(NOW(), "YYYYMMDD")-ƒ UPPER(LEFT(GUID(), 4))

Badge number

Store a value

badge = ƒ IF(form.purpose == "Contractor work", "C-", "V-"){{=UPPER(LEFT(GUID…

Host name

Store a value

host_name = form.host_item.name

Set title

Set the title for this workflow instance

Add to visitor log

Query, insert, update, or delete data store rows

insert → Visitor log

Email the host

Send an email via Resend

To: form.host_email

NDA needed?IF

If/else if/else branching

form.nda_required is_true

NDA

Else

Confirm NDA signed

Assign a task to a person and wait for action

NDA for {{form.visitor_na

Signed

Refused

No NDA needed

Stop execution immediately

Record NDA

Query, insert, update, or delete data store rows

update → Visitor log

Mark refused

Query, insert, update, or delete data store rows

update → Visitor log

Visitor arrival — A visitor signs in on the reception form: the visit is logged, the host is emailed and, when confidential information is involved, reception confirms the NDA. The same canvas you get in the designer after installing.

Forms

The start form and the task forms

People start it from a form page (/f/<id>) with its own header, theme and buttons; submitting it starts the workflow. User Tasks show their fields and outcome buttons to the assignee.

Form page · /f/<id>

Visitor sign-in

Welcome · 2-column grid · own header and theme · Its own page: share the link or open it on a tablet

Your name * visitor_name · text

Company company · text

Email visitor_email · emailname@company.com

Mobile visitor_phone · phone

Who are you visiting? * host · lookup

Host email host_email · emailname@company.com

Team host_team · text

Purpose of visit * purpose · choice

MeetingInterviewDeliveryContractor workEventOther

I will be shown confidential information (NDA) nda_required · boolean

I have read the site safety notice * agree · boolean

User Task

Confirm NDA signed

NDA for {{form.visitor_name}} ({{form.company}}) · 2-column grid · own header and theme

NDA version * nda_version · choice

Standard visitor NDA v3Mutual NDACustomer-specific

Witnessed by * witness · text

Notes notes · textarea

NDA signedVisitor refused

From your code

Start a run over the API

Every workflow can be started over REST, MCP or the CLI, whatever its trigger, with the sample input below. Runs start straight away on the published version; replace <workflow id> with the id the install created.

REST

shell

curl -X POST "$USERTASKS_URL/api/v1/workflows/start" \
  -H "Authorization: Bearer $USERTASKS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"workflow_id":"<workflow id>","variables":{"visitor_name":"Grace Kim","company":"Northwind Traders","visitor_email":"grace.kim@example.com","visitor_phone":"+1 555 0100","host":"ana.lopez@example.com","purpose":"Meeting","nda_required":true,"agree":true}}'

CLI

shell

usertasks workflows inputs <workflow id>          # the start form: keys, types, required
usertasks workflows run <workflow id> --input visitor_name="Grace Kim" --input company="Northwind Traders" --input visitor_email=grace.kim@example.com --input visitor_phone="+1 555 0100" … --wait

What's included

6 assets, ready to adapt

Type	Name	Details
Email template	Your visitor has arrived	Sent to the host when their visitor signs in.
Data table	Staff directory	People who can host visitors: the sign-in form looks the host up here and fills in their email and team.
Data table	Visitor log	Everyone who signed in: who they visited, when they arrived and left, and whether an NDA was signed.
Retention policy	Visitor log: 12 months	Visitor records are personal data: purge rows 12 months after they were created. Apply it to the Visitor log table after install.
forms	Visitor sign-in	The reception tablet form: visitors sign in, pick who they are visiting, and their host is told.
Workflow	Visitor arrival	12 steps — A visitor signs in on the reception form: the visit is logged, the host is emailed and, when confidential information is involved, reception confirms the NDA.

Staff directory · 6 sample rows

NameEmailTeamFloorActive

Visitor log · 2 sample rows

Visit referenceVisitorCompanyVisitor emailHostHost emailPurposeArrivedNDA requiredNDA signedBadgeStatus

Requirements

What you connect it to

Credentials never travel in a package. The install wizard asks for what your environment must provide, or installs it incomplete until you finish setup.

Needs

Email (optional) — Email delivery configured for the instance (EMAIL_PROVIDER), used for notifications.

After installing

Nothing to configure: install it and open the Visitor sign-in form from Forms (or share its /f/ link on the reception tablet).
Replace the sample people in the Staff directory table with your hosts (or import a CSV).
Optional: apply the "Visitor log: 12 months" retention policy to the Visitor log table, and set EMAIL_PROVIDER so host emails are delivered (the console provider logs them).

Asked for on install

Nothing: it installs complete.

Install

Install it in your workspace

Works on UserTasks cloud and on any self-hosted instance. Installing creates the assets above; nothing runs until you complete setup and start it.

In the app

Download visitor-sign-in-1.0.0.utpkg.
Open Automations → Packages and drag the file onto the page (or choose Import package). Browse gallery there lists every gallery package without downloading by hand.
Pick the file. The wizard verifies the checksum, every file hash and the signature, and shows the readme.
Review the changes (what is created) and the data rows.
Fill in the requirements, or tick Keep incomplete and finish later with Complete setup.
Done: the workflow is published and active once setup is complete.

With the CLI

shell

curl -fLO https://usertasks.com/gallery/visitor-sign-in-1.0.0.utpkg
usertasks packages inspect visitor-sign-in-1.0.0.utpkg       # offline: checksum, hashes, signature
usertasks packages install visitor-sign-in-1.0.0.utpkg --dry-run
usertasks packages install visitor-sign-in-1.0.0.utpkg       # prompts for each requirement
usertasks packages install visitor-sign-in-1.0.0.utpkg --keep-incomplete --yes   # in CI; finish with:
usertasks packages complete visitor-sign-in -f values.yaml

Verify the download

File SHA-256: 67985f7fd0dcca543fca4bd16cbba7b854e7512f59b178a00f53c06835f27db9
Package checksum (what is signed): sha256:ca3bd4cb116887c7c940aaf771601a4613a9645f3e289922194dcee373f16edb
Signer: Unsigned preview build — compare the SHA-256 above

shasum -a 256 visitor-sign-in-1.0.0.utpkg should print the file SHA-256. How gallery packages are signed.

Versions

Version 1.0.0

v1.0.02026-10-28First release.

Installing a newer version upgrades in place: local credentials and requirement values are kept, and changes you made are flagged first. How packages work

More packages

Browse the whole gallery

Visitor sign-in

What it does

Starts from a form

Step by step

The start form and the task forms

Visitor sign-in

Confirm NDA signed

Start a run over the API

6 assets, ready to adapt

What you connect it to

Needs

After installing

Asked for on install

Install it in your workspace

In the app

With the CLI

Version 1.0.0

Related

Asset register & check-out

Car-pool & fleet booking

Meeting room booking