WEBINAR RECORDING: Seize #GivingTuesday Success with Fundraising Wisdom and Salesforce. Watch >>

Blocking user accounts without a Salesforce Contact or Account

created

If your site has a password-protected area, you can require that any user attempting to login have a Contact and Account record in Salesforce associated with their web user account.

To enforce this requirement:

  1. Go to Components > Salesforce Dashboard > User Manager
  2. On the Authentication Options tab, for Allow Only Existing Contacts to Login, choose Yes if you wish to ensure that only web user accounts with an associated Contact in Salesforce can login

    sfdc-user-contact-account.png

  3. For Allow Only Contacts with an Account to Login, choose Yes if you wish to ensure that only web user accounts with an associated Account in Salesforce can login
  4. Click Save

What happens if an attempted login doesn't meet this requirement?

If a web user account does not have a Contact or Account when one or both are required, they will not be able to login and shown the Block Message defined under Components > Salesforce Dashboard > User Manager > Authentication Options tab.

Why require a web user account to have an associated Contact?

While web user accounts are associated with a Contact in Salesforce on initial registration, enforcing this requirement at login can safeguard against unexpected situations which remove this association. These could include manual deletion of the Contact record in Salesforce or manual removal of the Contact Id from the web user account under Site > User Manager.

Requiring that the web user has a Contact associated with their account will ensure that views granting them permission to view and / or edit their Contact information within Soapbox, or view and / or edit records related to the Contact in Salesforce will work as expected.

Why require a web user account to have an associated Account?

A web user account may not be associated with an Account record in Salesforce either because the association with the Contact record has been removed, as noted above, or because their Contact record in Salesforce is an orphan and not associated with a parent Account record.

Requiring that the Soapbox web user has a Contact in Salesforce associated with an Account record will ensure that views granting them permission to view and / or edit their Account record information within Soapbox, or view and / or edit records related to the Account in Salesforce will work as expected.

Have more questions? Submit a request
Article is closed for comments.