Skip to content
Office

Office Engage feature

User identification (SSO)

Your app signs a token, and your users vote, post and comment as themselves with no extra sign in.

How it works

Your server signs a short token (a JWT with your widget secret) holding the user's id, email, name, avatar and, if you like, their company, plan and monthly revenue. Pass it to the widget or the portal sign-in link. We trust the token, so the person votes in one click and their email counts as confirmed.

Safe by default

Tokens expire within 24 hours. An unsigned user object is refused unless you turn that on. Call Engage('logout') when someone signs out so the next person on a shared computer doesn't vote as them. Rotating the secret keeps the old one working for 24 hours.

Emails that sign people in

Links in status and shipped emails sign the customer in for that one visit, valid for 7 days, so occasional voters don't hit a password screen. Team members never get these links, and you can turn them off under Security.

Example

A Node app in ten lines

A Next.js app signs { id: user.id, email, name, company: { id, name, mrr_cents } } with the widget secret on the server, puts the token in the page, and calls Engage('init', { workspace, token }). Every vote now carries the company and its revenue, and nobody types an email.

How to set it up

  1. 1

    Go to Settings, Widget and copy your widget secret.

  2. 2

    On your server, sign a token with the user's id, email and name (examples for Node, Python, Ruby and PHP are in the docs).

  3. 3

    Pass it to Engage('init') or Engage('identify').

  4. 4

    Call Engage('logout') when the user signs out.

User identification (SSO) is part of Office Engage and included on every plan.

Try Office Engage with your whole team

7-day trial with every feature. Cancel from the billing page whenever you like.