Configure Waivers & Docusign

Event waivers let you require registrants to review and sign an agreement before they complete registration. WeGive supports two ways to handle waivers: a custom waiver you write and store directly in WeGive, or a Docusign-managed waiver that uses your connected Docusign account for embedded signing.

This article walks through configuring waivers on an event and, if you want signed documents handled through Docusign, connecting the Docusign integration that unlocks that option.

Before you start

• You need access to the event you want to configure, plus permission to edit event Settings.

• To use the Docusign option, you'll also need organization Settings access and a Docusign account (with Admin access in Docusign to retrieve the required IDs).

• If you only want a simple, text-based agreement, you can skip Docusign entirely and use a custom waiver created in WeGive.

Part 1 — Configure the event waiver

Step 1: Open the event's Waiver settings

1. Go to Events and open the event you want to configure.

2. Select the Settings tab at the top of the event.

3. In the left-hand settings menu, choose Waiver.

You'll land on the Event Waiver panel, where you manage all waiver settings for that event.

Step 2: Require a waiver signature

Turn on the Require Waiver Signature toggle. When this is enabled, registrants must sign the waiver before they can complete registration. If you leave it off, no waiver is shown and the other waiver settings are not applied.

Step 3: Choose a waiver type

Under Waiver Type, choose how the waiver is created and signed:

• Create a custom waiver in WeGive — You write the waiver text directly in WeGive (see Step 4). This is the default and requires no integration.

• Use Docusign integration to create and sign waivers — Waivers are created and signed through your connected Docusign account using embedded signing.

Note: The Docusign option is disabled until your account is connected. If you hover over it before connecting, you'll see the message: "This account is not integrated with Docusign. Navigate to Settings > Integrations to connect with Docusign." To enable it, complete Part 2 below, then return to this screen.

Step 4: Write the waiver content (custom waiver)

If you chose Create a custom waiver in WeGive, use the Waiver Content rich-text editor to write the agreement registrants will see and sign. The editor supports:

• Bold, italic, underline, and strikethrough text

• Headings

• Bulleted and numbered lists

• Text alignment and font selection

• Hyperlinks, comments, and embedded HTML for advanced formatting

Write the full text of your agreement here exactly as you want registrants to read it.

Step 5: Save your changes

Click Save Changes in the left panel to apply your waiver settings to the event. Until you save, your changes are not live on the registration flow.

Part 2 — Connect the Docusign integration

Complete this part only if you want to use the Use Docusign integration waiver type. This is an organization-level setup that applies across your WeGive account, not a per-event setting.

Step 1: Open Integrations

1. Go to Settings (organization settings).

2. Open the Integrations area and scroll to the Available integrations list.

3. Find Docusign ("Connect embedded signing with Docusign account credentials"). It will show Not Connected until setup is complete.

4. Select Docusign to open the Docusign Setup page.

Step 2: Gather your Docusign identifiers

On the Docusign Setup page you'll configure the identifiers WeGive uses for embedded signing. You'll need two values from Docusign:

• Docusign User ID

• Docusign API Account ID

Find both values inside Docusign under Admin > Apps and Keys. They are formatted as GUIDs (e.g., XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX).

Step 3: Enter the IDs and grant permission

1. Paste the Docusign User ID and Docusign API Account ID into their fields on the setup page.

2. Click Grant Permission. This saves the values you entered and then opens the Docusign authorization screen.

3. On the Docusign authorization screen, sign in with the same Docusign account that matches the User ID and API Account ID you entered. Signing in with a different account will cause the connection to fail.

4. Approve the consent request to complete the connection.

Good to know: The OAuth callback uses the legacy Docusign path from the previous dashboard, so an existing Docusign app registration will continue to work without re-registration.

Step 4: Confirm the connection

Once authorization succeeds, the Docusign integration status changes from Not Connected / Needs setup to connected. The Use Docusign integration to create and sign waivers option in your event's Waiver settings will now be selectable.

Step 5: Switch the event to Docusign

Return to your event's Settings > Waiver screen (Part 1) and select Use Docusign integration to create and sign waivers under Waiver Type, then Save Changes.

Troubleshooting

The Docusign waiver option is greyed out.
Your account isn't connected yet. Go to Settings > Integrations > Docusign and complete the connection (Part 2), then return to the event's Waiver settings.

"Docusign auth is not configured. Set VITE_DS_AUTH_SERVER and VITE_DS_CLIENT_ID before granting permission."
This message on the Docusign Setup page means the Docusign authorization environment isn't configured for your dashboard, and the Grant Permission flow can't launch yet. Entering your User ID and API Account ID alone won't resolve it. Reach out to WeGive support so the Docusign auth configuration can be enabled for your account.

"OAuth unavailable" / "Needs setup" badges remain after entering IDs.
Saving the IDs is only the first step — you must also complete the Grant Permission consent flow and sign in with the matching Docusign account. If the consent flow won't open, see the auth-configuration note above.

Authorization fails or connects the wrong account.
Make sure the Docusign account you sign in with during the consent flow is the exact account the User ID and API Account ID belong to. Re-check both IDs in Docusign under Admin > Apps and Keys.

Registrants aren't being asked to sign.
Confirm the Require Waiver Signature toggle is on and that you clicked Save Changes on the event's Waiver settings.

Quick reference