Read Only Objects & Events

Making Calendar Completely Read-only

The method to designate a calendar or event as read-only varies based on your platform.

Salesforce system administrators can set any Salesforce calendar source to be read-only by enabling the "Read Only" setting in the Calendar Info tab.

To grant read-only access to individual users, set permission restrictions on the Salesforce object mapped to the calendar source for the specific user's profile or by using a permission set. DayBack will respect the access limitations you've set within your Salesforce objects for those users. The Group Menu used for managing users on other platforms (as in the screenshots that follow) will not apply for your Salesforce platform.

DayBack respects the calendar-specific access settings applied to your Google or MS365 calendars. To make a calendar read-only, configure it as such within the Google or MS365 settings, and DayBack will adhere to those settings..

Additionally, DayBack administrators can grant read-only access to individual users. This can be done in the calendar settings under the Group Menu by selecting the user account and toggling the yes/no radio button next to "Read Only."

Making Specific Events Read-Only

DayBack respects the privilege schemes of your original calendar sources, such as Salesforce or FileMaker. This means that if your source has specific access settings, DayBack will honor those.

For example, in Salesforce, DayBack will follow the access limitations of Salesforce objects. If an event is non-editable due to its state or user permissions, DayBack will prevent any edits and revert any attempted changes. This applies to visibility and editability rules set for certain profiles. DayBack makes edits by requesting Salesforce to perform them, ensuring all triggers and workflows are fired and maintaining the same access restrictions as in the regular Salesforce interface. Therefore, a Salesforce user in DayBack cannot do anything with your events that they cannot do in the regular Salesforce interface.

While DayBack adheres to these limitations, it is beneficial for its interface to clearly indicate which events or fields are locked to avoid user confusion. There are several ways to accomplish this:

Making Specific Fields Hidden or Read-only

Yes. You can designate individual fields as read-only or hidden in DayBack. Learn more about this feature here: Read-Only or Hidden Fields.