# Identity verification

> Your site signs the customer's email with a secret so account actions only run for the right person. No developer? The assistant verifies by email code.

URL: https://office.greatwork.company/assist/features/identity-verification
Last updated: 2026-11-21

Your site tells the assistant who the customer is with a signed hash, so account actions only ever run for the right person. Sites without a developer can verify by email code.

## Signed identity from your site

When a customer is signed in, your server computes `HMAC-SHA256(secret, email)` and passes it with their email to the widget. The assistant treats the visitor as verified only when the hash matches. Code samples are in the app for Node, Python, PHP, Ruby, Rails and Laravel.

## Email code when you can't add code

For actions marked **Requires verified customer**, a visitor who isn't verified gets asked for their email, receives a 6-digit code, and types it in the chat. Three tries, ten minutes, then they can start again.

## Only the details you allow

Your site can pass any attributes it likes, but the assistant only sees the ones you list as visible (name, email and plan by default). Internal fields stay out of answers and out of the model's view.

## Example: Why typing someone else's email doesn't work

A visitor who isn't signed in types "Show me the subscription for bob@example.com". The Stripe action needs a verified customer and takes the email from the verified record, not from the chat, so the assistant asks the visitor to verify first. A code goes to Bob's inbox, not theirs, and nothing is shown.

## How to set it up

1. Copy the identity secret from the assistant's Security settings.
2. Compute the hash on your server for the signed-in user.
3. Pass it with Assist('identify', { email, user_hash }).
4. Check the playground with "pretend verified customer" on.

---

Office by Great Work. Questions or corrections: hello@greatwork.company
