DayBackOnline

Read Only

DayBackOnline.ReadOnly History

Hide minor edits - Show changes to output

July 20, 2017, at 04:47 PM by KC Embrey - Added instructions on setting read only
Added lines 4-5:

The read-only option can be set in the calendar settings under the group menu. From there, select the user account you'd like to set and click the yes/no radio button next to Read Only.
July 01, 2015, at 06:30 PM by 142.4.217.187 -
Changed lines 1-17 from:
!! Can I make the WebDirect Calendar completely read-only.

Yes.

Obviously you
can do this with access privileges so that users can't edit the events table if the log in with a generic account (or open the file without logging in). That's functionally locked down, but it may be frustrating for users without making a few changes to smooth things out. I'd also make the following (simple) changes:

-> In Access Privileges, allow editing of all tables besides the events (and ToDo list, if you use that).

-> Pull (or conditionally hide) the "+" button from the WebDirect layouts so users don't try to create new events.

-> Edit the event popovers and pull all the buttons from the bottom besides "cancel". Rename that one "close"

-> Make all the fields on the event popover unenterable and pull the up/down buttons next to the event time.

When combined with access privileges, these changes will not only prevent users from editing events in WebDirect, it will stop them from thinking events *can* be edited.

Some tips for editing those popovers can be found [[ .EventPopovers | here]].
to:
!! Can I make the calendar completely read-only.

Yes. [[Administrators]] can designate individual users as having read-only access.

DayBack also respects your FileMaker Access privileges so you can control access there as well. More on that here: [[security]]
.
June 03, 2014, at 03:54 PM by 50.132.85.96 -
Added lines 1-17:
!! Can I make the WebDirect Calendar completely read-only.

Yes.

Obviously you can do this with access privileges so that users can't edit the events table if the log in with a generic account (or open the file without logging in). That's functionally locked down, but it may be frustrating for users without making a few changes to smooth things out. I'd also make the following (simple) changes:

-> In Access Privileges, allow editing of all tables besides the events (and ToDo list, if you use that).

-> Pull (or conditionally hide) the "+" button from the WebDirect layouts so users don't try to create new events.

-> Edit the event popovers and pull all the buttons from the bottom besides "cancel". Rename that one "close"

-> Make all the fields on the event popover unenterable and pull the up/down buttons next to the event time.

When combined with access privileges, these changes will not only prevent users from editing events in WebDirect, it will stop them from thinking events *can* be edited.

Some tips for editing those popovers can be found [[ .EventPopovers | here]].
(855) SEEDCODE
support@seedcode.com
Follow us: