Do Not Require All Users to Log Into Salesforce
If you're using DayBack's Salesforce Connect option to let customers book events with you on a public calendar showing your availability. You likely don't want those customers to have to log into Salesforce. They're likely not even Salesforce users. Similarly, you may use Salesforce Connect to let contractors keep tabs on their schedule--and you won't want to give them all their own Salesforce user accounts.
Fortunately, DayBack lets you dedicate a single Salesforce account that some or all of your DayBack users can share when making requests from outside Salesforce. For example, you may set up a "Public Calendar" user in Salesforce that is dedicated to visitors who are booking appointments with you. Any visitor who comes to your calendar will, under the hood, be talking to Salesforce as this "Public Calendar" user.
Here is how to set that up.
Note: you'll need to be able to see your Salesforce org from outside of Salesforce in order to complete these steps. This likely requires you to make a simple change in your org as described here: Granting Access to DayBack.
Setting Up a Shared Login
First, create the user in Salesforce. We recommend that this user have a new profile that has read-only access to most objects, and perhaps read-write access to the appointments object or, better yet, to a "pending appointments" object just used for receiving new appointments from your public calendar. Here's how Salesforce describes creating this user: Create a secure Salesforce API user
Click on your account at the top of the second column, right below where it says "Calendars," and turn "Do Not Require All Users to Log Into Salesforce" to "Yes":
You'll be asked to log into Salesforce--do NOT log in as the admin of your org, but log in as the "Public Calendar" user you created in step 1. This is the account that some or all of your DayBack users will share when asking Salesforce for your schedule.
Once you've signed in as this "Public Calendar" user, you'll see that user's account information displayed. In this example, you see "Evaluation User" is the username I've created for my mostly-read-only "Public Calendar" user.
Now that you have specified a Salesforce account that can be shared among your DayBack users, click on "Users and Billing" in the left-hand sidebar and click on any user who shouldn't be prompted to log into Salesforce. For that user, switch "Do not require Salesforce authentication" to "Yes" and they won't be prompted to log in to Salesforce: they'll be logged in automatically as the user specified in Step 3, "Evaluation User" in this example.