Guard Sign-In

A Guard Sign-In puts a card in front of a public page. The visitor types their email, the CRM finds the matching record, and only then does the page open with that record's data already filled in.

What the guard does

  • Hides the page behind a sign-in card with your own title, subtitle and logo.
  • Looks the visitor up in your CRM, so nobody sees a page that is not theirs.
  • Fills document variables or form fields from the record it found.
  • Can add a one-time code by email, WhatsApp or a CRM field before the page opens.

Turning it on

  1. Open the document or Experience and choose the Guard Sign-In settings from the toolbar.
  2. Turn on Enable and give the page a title and subtitle.
  3. Add the login fields the visitor fills in, usually just Email.
  4. Pick the CRM integration, object and the field to match against the login field.
  5. Map CRM fields to the page's variables or fields, so the page arrives filled.
  6. Save and publish.

One-time codes

  • Email sends the code to the address on the record.
  • WhatsApp sends it to the phone number on the record.
  • CRM writes the code into a field you choose, leaving delivery to your existing automation.

Sessions

Session duration decides how long a visitor stays signed in: until they log out, for a set number of minutes, or every time, so the card returns on each visit or refresh.

Good to know

  • Test the guard on the published link, not inside the builder.
  • If the visitor is not found in the CRM, the card shows your error message instead of the page.
  • The popup design settings control the card only, not the page behind it.

Related tutorials

Keep going with these lessons.