Smartwaiver: Getting Started!

Brushfire connects with Smartwaiver so you can collect liability waivers from your attendees after they buy, track who has signed, and check for missing waivers at the door. You build your waivers in Smartwaiver; Brushfire handles when they're required and who needs to sign them.

Before you start

You'll need a Smartwaiver account with at least one waiver template.

Good to know: Your waiver's wording, signature type (typed or drawn), custom fields, minor/guardian sections, expiration, and styling are all set in Smartwaiver. For help with those settings, contact Smartwaiver support.

Step 1: Connect Smartwaiver to Brushfire

  1. In Smartwaiver, create an API key. 
  2. In your Brushfire dashboard, go to Integrations and choose Smartwaiver.
  3. Enter an Integration Name (for example, "Main Waivers") and paste your API Key.
  4. Click Save. Brushfire checks your key and connects to your Smartwaiver account.
If the integration won't save: Smartwaiver allows up to 3 connected apps (webhooks) per account. If you already have 3, remove one in Smartwaiver and try again. The error message on screen will tell you what went wrong.

You can connect more than one Smartwaiver account if you need to. Each API key can only be connected once.

Step 2: Choose Who Signs and Add Your Waivers

  1. Open your event and go to the new Waivers tab. (You'll only see it after Smartwaiver is connected.)
  2. Choose signs the waiver for the event:
    • Buyers – waivers assigned per order, signed by the buyer
    • Groups – waiver assigned per group, signed by the group leader
    • Attendee Types & Add-ons – waivers for each attendee, or for add-ons like parking. You can select which waiver applies to any or all attendees types or add-ons
Tip: Most events use Attendee Types & Add-ons, so every person who walks through the door has their own signed waiver.

       3.  Click to add a waiver and choose a template from your Smartwaiver account.

       4.  Give it a Display Name. This is what attendees see in Brushfire.

       5. Mark it Required or Optional.

       6. For attendee-level waivers, select which attendee types and add-ons it applies to.

       7. Save.

You can also choose waivers when you create or edit an attendee type or add-on. Look for the Fields & Waivers tab.

Setting What it means
Required Counts toward missing waivers. Can block check-in and hide tickets.
Optional Attendees can sign it, but it never blocks anything.

Step 3: Decide What Happens at Check-in

Waivers use the same settings you already use for signatures:

  • Check-in: If a session doesn't allow missing signatures, attendees with missing required waivers are blocked at check-in.
  • Tickets: If your event hides tickets for missing signatures, the ticket's QR code is also hidden until required waivers are signed.

Things to Know

  • Changes apply to everyone. Adding a required waiver after sales start means existing attendees will need to sign it too. Use the Waiver Eblast to let them know.
  • Removing a waiver lifts the requirement but keeps signed waivers on file. If you add it back, they count again.
  • Copying an event copies its waiver setup.
  • Waivers aren't available in Event Creator. Set them up from the Waivers tab.

Related Articles