Installing the Summit Events App

The Summit Events App (SEA) is a managed package and has been security reviewed by Salesforce. Installation, along with many other great Salesforce.org Open Source Commons applications, is done through Salesforce.org’s MetaDeploy installer.

Install the latest managed pacakge.
IMPORTANT: Confirm you are logged into the correct Salesforce org where you want to install Summit Events before you begin the installation process (Sandbox vs. Production).

Post Installation Instructions

There are a few steps after you install the SEA managed package to getting your Salesforce org configured to run SEA. Following along with this helpful post installation video and/org follow the steps below.

Confirm Summit Events is Installed

1. From Setup, search for and select Installed Packages.
2. Confirm you see Summit Events App as one of the installed packages.

Create a site subdomain

If your org does not already have a Salesforce “Site,” which is used to display public visual force pages, you will need to set up one. If your org has one set up, you may use the existing Site.

1. In Setup, go to User Interface -> Sites and Domains -> Sites.

2. Determine the name you want to use for the Site (it will be in the form of [site.force.com]) and click the “Check Availability” button to see whether or not it is available. Note: Each Site must be unique.

3. Click on the “Register My Salesforce Site Domain” button.

Once your domain has been registered continue:

1. Click the “New” button next to the site header.

2. Enter the following data in the form (label, name, and homepage can be adjust to whatever makes sense for your site):
   • Site Label: Summit Events
   • Site Name: Summit_Events
   • Active Site Home Page:
     • Select the magnifying glass look-up icon and search for and select SummitEvents.
   • Leave all other settings at their defaults and text areas blank.

3. Click “Save”.

4. Upon save, you will see the Site under the Sites section. Click the “Activate” button at the top of the page.

5. From Setup, search for sites. From the list of sites, find the Summit Events site. In the Site URL column, right-click on the Site URL link and copy the URL to your clipboard. You will need the Site URL in the next stage of post-installation set-up steps.

Set Custom Settings

Since each installation can have a different site URL, we need to define that URL for the event application to use as its root web presence. This is used for feed URLs, allowing external sites to access it, among other things. Learn more about other custom settings.

1. From Setup, search for Custom Settings.

2. Click on the “Manage” link next to the custom setting “Summit Events Settings”.

3. Click the “New” button at the top of the page just before the “Default Organization Level Value.” NOTE: There are two “New” buttons on the page, which can be confusing. You will know you are on the wrong one if you are asked to assign a user or a profile. You will know you are on the right one if you only need to enter the URL in the following step.

4. Paste the URL you copied from the “Create a site record” section (step 6 above) into the Community Base URL field.

5. Click the “Save” button.

Once you hit “Save” the “New” button will be replaced with “Edit.” (You will need to click the Edit button to make future adjustments to this setting.)

Set Sharing Rules

Salesforce Winter ‘20 and Spring ‘20 releases severely limited Guest User access to objects to ensure security. The Summit Events application requires the Guest User profile used by the event registrant to be able to read and upsert to the solution’s custom objects. To comply with these new security requirements, we need to create a sharing rule. Code has also been adjusted to allow for the required upserts. The following instructions will help you set up the required sharing rule. Unfortunately, we are not able to automate these steps yet due to limitations in SFDX.

Set Sharing Object Access:

1. In Setup, type “Sharing” in the quick-find box in Setup and click on “Sharing Settings”.

2. In the Organization-Wide Defaults section, find Summit Events (towards the bottom) verify it is set to Public Read/Write. If it is, skip to step 6.

3. If Summit Events is not set to Public Read/Write, click the “Edit” button.

4. Scroll down to “Summit Events” and select Public Read/Write in both the Default Internal Access column and the Default External Access column.

5. Click the “Save” button.

6. Under the “Sharing Rules” header (just below the Organization-Wide Default section), scroll down to the “Summit Events Sharing Rules” section and click the “New” button.

7. In the “Step 1: Rule Name” section, under Label field, enter “Guest User Read Access” and then use the tab key to tab to the next field. This will automatically populate the Rule Name field with “Guest_User_Read_Access.”

8. In the “Step 2: Select your rule type” section, select the “Guest user access, based on criteria” radio button.

9. In the “Step 3: Select which records to be shared” section, set the following:

   • “Criteria” to Field = Event Name
   • Operator = “not equal to”
   • Value = null (type the word ‘null’ for the value).

10. In the “Step 4: Select the users to share with” section, click the Share With drop-down arrow and select the Event Site Guest User, which is named Summit Events Site Guest User in our example.

11. Set Access Level to “Read Only”.

12. Click the “Save” button.

Note: The guest user gets created when the site is created and is named after the site name so your guest user may be named slightly different for example it may be called “Event Guest User”. There is usually only one guest user for the site so it’s pretty safe to assume the one you see is the one for which you should assign the Guest Registrant permissions set.

Apply Permission Sets

There are two permission sets provided in this application. These permission sets should be leveraged to ensure functionality persists between upgrades.

1. Summit Events Admin - allows users to create and maintain events
2. Summit Events Registrant - allows unauthenticated users and authenticated users in a community to register for an event

Summit Events Admin: Apply to admin users that need to create and maintain events.

Note: Users who are not system administrators but who will administer Summit Events will need this permission set. You do not need to add the Permission Set at this time, but follow the steps bulleted below if/when you need a user to administer Summit Events. It is recommended that the Summit Event Admin permission set is cloned so appropriate configurations can be made to reduce/expand access to various fields.

1. In Setup search for and select Permission Sets.
2. Click on Summit Events Admin or your cloned Summit Events Admin permission set.
3. Click on the “Manage Assignments” button.
4. Click the checkbox next to the user who will administer Summit Events and click the “Add Assignments” button.

Summit Events Registrant: This permission set needs to be applied to the Guest User profile of your site for the public to be able to access to registration forms. In addition, a custom permission set should be created to give additional access based on event configurations.

Create a Custom Permission Set for the Guest User

This custom permission set allows you to add additional permissions for the guest user without worrying about issues during upgrades. This permission set combined with the packaged Summit Events Registration permission set gives your organization the most flexibility. It ensures Summit Events App works seamless with any upgrade and the Guest User always has the appropriate access to recieve event registrations.

1. Create a new Permissions Set.
2. Label the permission set to align with the Summit Event Registration for Guest Users - Example: Summit Events Registrant Custom.
3. Go to Object Settings and grant “READ” access on the Account object. No additional fields needed.

Once you’ve create the Custom Permission set, apply it to the Guest User as outlined below. With this custom permission set, you’ll be able to grant appropriate access to any additional objects or fields being utilized for Summit Events as well as the following:

• Avoid disruptions and limit additional configurations during upgrades.

• Leverage Summit Event Questions and the Lookup options for improved data integrity.

  We recommend assigning users to the standard permission sets since they can change with each release as new features become available in Summit Events (SEA). Cloning the existing permission sets to create custom permission sets could result in users not having access to features or functionality when the standard SEA permission sets change. If you need to add additional permissions we recommend that you create a custom permission set to house those permissions and assign that permission set in addition to the standard permission set.

Apply Summit Events Registrant permission set and the custom permission set you created to the Guest User of your site

1. From Setup, Search for and select Sites.
2. Under the Sites section, click on the words Summit Events in the “Site Label” field.
3. Click on the “Public Access Settings” button at the top of the site definition page.
4. On the Summit Events Profile page, click the Assigned Users button.
5. Under the Full Name column, click on the Site Guest User name (Site Guest User, Summit Events - which is a link).
6. On the Summit Events Site Guest User page, scroll down to Permission Set Assignment and click the “Edit Assignments” button.
7. In the Available Permission Sets section, click on Summit Events Registrant and click the “Add” button. Repeat this process for the new custom permission set you created. This will move them both into the Enabled Permission Sets section.
8. Click the “Save” button.

Congrats! At this point, you should have a functioning Summit Events Package.

Check out Post-Installation Considerations for additional considerations you’ll want to make to ensure there is alignment with your organization.