Authenticating the Frontend Builder

To use the GoMeddo Frontend Builder, you must authenticate an API user. This user is used to facilitate communication between Salesforce and the frontend component running outside of Salesforce.

Everything your frontends can read and write is determined by this user's permissions.

Recommended User Setup

This setup requires a dedicated integration user with:

• A Salesforce Integration User license

• The Salesforce API Integration permission set license

• A valid GoMeddo package license

• The GoMeddo Frontend Builder Integration User permission set

Using a dedicated user helps restrict data access, improves security, and makes auditing and troubleshooting easier.

The GoMeddo Frontend Builder Integration User permission set contains everything the Frontend Builder needs, including the GoMeddo objects and fields it reads. You do not need to assign the GoMeddo Integration User permission set.

Steps

1. Navigate to Setup, open Users, and click New User.

2. Set the User License to Salesforce Integration, then set the Profile to Minimum Access - API Only Integrations. Select the User License first, as the Profile list depends on it.

3. Save the user.

4. On the user detail page, open the Permission Set License Assignments related list and click Edit Assignments. Enable Salesforce API Integration and save.

5. On the same page, open the Permission Set Assignments related list and click Edit Assignments. Enable GoMeddo Frontend Builder Integration User and save.

6. Navigate to Setup, open Installed Packages, and click Manage Licenses next to GoMeddo. Click Add Users and assign a license to the integration user.

Steps 4 and 5 must be completed in that order. If the permission set license is missing, Salesforce returns an error such as "The user license doesn't allow the permission: Read Contacts". This message refers to the user license, but the permission set license is what is actually missing.

This user cannot log in to Salesforce through a browser. This is expected, the user exists only to serve your frontends.

Authentication Steps

1. Navigate to GoMeddo Settings and open Frontend Builder.

2. Click Authenticate User.

3. A pop-up window opens.

4. Click “Not you”

5. Log in with the dedicated API user and click Authorize.

6. This usually requires you to re-login with your regular user afterwards.

Once authorized, the Frontend Builder can securely communicate with Salesforce using this user's permissions.

Sharing for Sign-Up Mode

Permissions determine which objects and fields the integration user can access. They do not determine which records it can see — that is controlled by sharing.

Reservations are private by default, so the integration user can only see Reservations it created itself. If your frontend offers Reservations created by your staff, those records must be shared with it.

Without sharing, the frontend does not show an error. The step simply displays no available Reservations, as though none are scheduled.

Marking Reservations as bookable

Sharing rules can only filter on certain field types, and Reservation Type and Status are not among them. We recommend adding a checkbox to indicate which Reservations may be offered through a frontend.

1. Navigate to Setup, open Object Manager, and select Reservation.

2. Open Fields & Relationships and click New.

3. Choose Checkbox as the data type, set the Field Label to Available in Frontend, and leave the Default Value as Unchecked.

4. Save, and add the field to your Reservation page layout.

5. Check the field on the Reservations you want your frontend to offer.

Leaving the default unchecked means nothing is exposed to a public frontend unless it is deliberately opted in.

If your org already separates bookable Reservations by Record Type, you can use that as the sharing criterion instead and skip this field.

Creating the sharing rule

Sharing is granted to groups, not to individual users, so the integration user is placed in a public group first.

1. Navigate to Setup, open Public Groups, and click New.

2. Set the Label to GoMeddo Frontend Builder Integration, add the integration user under Search: Users, and save.

3. Navigate to Setup and open Sharing Settings.

4. Select Reservation under Manage sharing settings for.

5. In Reservation Sharing Rules, click New and configure:

6. Save. Salesforce recalculates sharing in the background, so allow a few minutes before testing.

Additional Configuration

The GoMeddo Frontend Builder Integration User permission set covers the standard steps and the fields the Frontend Builder ships with. The following require additional access.

Payments access is not granted by the Frontend Builder permission set because GoMeddo Payments is a separate package.

Record Types

If your org uses Record Types on Reservation, the integration user needs access to them, or creating a Reservation fails with "record type missing for: Reservation".

The Frontend Builder never sends a Record Type. Salesforce populates it from the running user's default Record Type before any Apex runs, and GoMeddo's trigger then replaces it with the Record Type configured on the Reservation Type. If the integration user has no default, the first step fails and the trigger never runs, so configuring the Reservation Type does not fix this on its own.

Defaults come from the profile; permission sets can make Record Types visible but cannot set a default.

Setup → Profiles → the integration user's profile → Object Settings → Reservation → Edit → tick --Master-- under Assigned Record Types, and save.

That is enough. GoMeddo immediately replaces Master with the Record Type from the Reservation Type, so Reservations still end up correct.

Object Settings are normally editable even on the standard Minimum Access - API Only Integrations profile. If that page really is read-only, clone the profile, set it there, and reassign the user.

If your org uses Person Accounts, leads created without a company name are assigned the Person Lead Record Type, which the integration user also needs access to.

Verifying the Setup

Complete a booking through one of your frontends from start to finish, then confirm in Salesforce that:

• The Reservation was created

• The Contact or Lead was created and linked to the Reservation

• If you use Payments, the Transaction is linked to the Reservation

• If you use Sign-Up mode, the list of available Reservations is populated

A missing Payments permission does not produce an error. The booking completes and the payment link is returned, but the Transaction is never linked to the Reservation. Always check this explicitly after a test payment.

Troubleshooting