Security

Can I restrict users to only See and Edit their own events?

Definitely. Read our article on various ways you can ensure that individuals only see their events.

Hiding Administrative Tools and "Account Settings"

Only admins can see account settings, so you only need to decide who can be a DayBack admin.

Can I have some users with read-only access to the calendar?

Yes. Please read out article on how to make calendars or individual events read-only.

Hiding "Account Settings"

Only admins can see Account Settings. If you're one of the administrators for a DayBack group you can decide which group members have Admin access.

Salesforce Specific

Does DayBack store my Salesforce account name or password?

No. This is not used in any DayBack database, cookie, or server. Read more about DayBack's Architecture and Security in Salesforce.

Does DayBack respect Salesforce access privileges?

Yes, DayBack respects Salesforce access privileges. However, there are some nuances to be aware of:

  • Record-Level Access:
    • If a record's access privileges are set to be invisible to a given privilege set, that record will not show up in DayBack. This is handled seamlessly.
  • Conditional Edit Access:
    • If Salesforce security allows a privilege set to edit a record only under certain conditions, DayBack will initially display the record as editable to logged-in users. However, when users attempt to edit the record, DayBack cannot evaluate the access rights until the action is attempted. For example, if a user tries to drag an event to a new date, the change will initially appear to take effect. But it will be reverted, and a dialog will inform the user that the action is not permitted.

FileMaker Specific

Does DayBack store my FileMaker account name or password?

No. This information only resides in the PHP relay file you place on your FileMaker Server. It is not used in any DayBack database, cookie, or server.

Does DayBackOnline respect FileMaker Access Privileges?

Yes, DayBack respects FileMaker access privileges. However, there are some nuances to be aware of:

  • Record-Level Access:
    • If a privilege set is configured in FileMaker so that certain records are not visible, those records will not show up in DayBack. This is handled seamlessly.
  • Conditional Edit Access:
    • If FileMaker's record-level access permits a privilege set to edit a record only under certain conditions, DayBack will initially display the record as editable to logged-in users. However, when users attempt to edit the record, DayBack cannot evaluate the access rights until the action is attempted. For example, if a user tries to drag an event to a new date, the change will initially appear to take effect, but it will be reverted, and a dialog will inform the user that the action is not permitted.

Does running this in WebDirect make it any less secure?

No. 🙂

Related Articles