Sign in

Admin

Inbound SAML

Inbound SAML lets an identity provider (for example a university single sign-on) send a signed assertion to Forge so a guest arrives at registration already identified. Forge matches the assertion to a Salesforce Contact and prefills the form; a guest with no match keeps the name, email, and phone from the assertion.

Setup

Open Admin, then Inbound SAML. Give your identity provider the ACS URL shown on the page, then enter the IdP entity ID, your SP entity ID, and the IdP signing certificate. Turn on Enabled when you are ready. Assertions that fail signature, issuer, audience, expiry, or replay checks are rejected.

Donor ID Contact field

Pick the Contact field that holds the Donor ID. The list shows only real, filterable Contact fields read from Salesforce, and a field that does not exist is rejected on save. Leave it as None to match on Contact ID and email only.

Attribute mapping

For each of Donor ID, Contact ID, email, first name, last name, and phone, list the assertion attribute names to read, separated by commas. The first one present wins. When your identity provider's payload changes, edit the names here; nothing else needs to change.

How a Contact is matched

Forge tries Donor ID, then Contact ID, then email. If a step finds more than one Contact it stops and flags the guest for review instead of guessing. If nothing matches, the guest continues as a new person.