Sharing
DayBackOnline.Sharing History
Hide minor edits - Show changes to output
August 15, 2018, at 07:23 PM
by - Fixed broken bullets
Changed lines 12-15 from:
-> � Sending project schedules to your customers
->��Giving employees (resources) access to their schedules
->� Publishing the schedule for a conference or site visit
->� Sharing plans with your family and friends
->
->
->
to:
-> * Sending project schedules to your customers
-> * Giving employees (resources) access to their schedules
-> * Publishing the schedule for a conference or site visit
-> * Sharing plans with your family and friends
-> * Giving employees (resources) access to their schedules
-> * Publishing the schedule for a conference or site visit
-> * Sharing plans with your family and friends
Added lines 16-17:
Here's a video of this in action: %newwin% [[https://youtu.be/VF-oGgeOUJ0 | sharing in action]].
Changed line 76 from:
'''Can recipients edit shared events?''' No. Recipients of a share URL will be unable to edit those events.
to:
'''Can recipients edit shared events?''' No. Recipients of a share URL will be unable to edit those events. If you want someone to be able to edit your calendar they'll need a DayBack Online account in your group. Here's how to [[ManagingUsers | invite them]].
Deleted lines 1-2:
Added lines 89-90:
'''Can I style shared views differently from DayBack in Salesforce?''' Yes. By default your share will pickup any [[CSS | CSS modifications]] you've made to DayBack Online. But you can also make style changes that only effect shared pages by wrapping them in the class ".share-only"
Changed line 90 from:
to:
� SeedCode, Inc. 2017
Changed line 90 from:
%25center%25� SeedCode, Inc. 2017
to:
%25center%25 � SeedCode, Inc. 2017
Changed lines 88-90 from:
'''Can I remove the Share menu for all users?''' Yes. In Administrator Settings you'll see a section named "Views". Within that, simply enter "Share" beside "Hide menu items".
to:
'''Can I remove the Share menu for all users?''' Yes. In Administrator Settings you'll see a section named "Views". Within that, simply enter "Share" beside "Hide menu items".
%25center%25� SeedCode, Inc. 2017
%25center%25� SeedCode, Inc. 2017
Added lines 7-8:
%newwin, width=500% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/SharingAdSoloMed.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/SharingAdSoloMed.png]]
Changed line 84 from:
'''Who can create a share?''' By default, only [[administrators]] of your DayBack account can create shares. But Administrators can change this, enabling sharing for everyone, or turning off sharing completely.
to:
'''Who can create a share?''' By default, only [[administrators]] of your DayBack account can create shares. But Administrators can change this, enabling sharing for everyone, or turning off sharing completely. There is also an "allow sharing" in member settings that will allow administrators to disable sharing for specific members if the master "allow sharing" switch allows sharing for that type of user. However if the member setting is set to on it will not override the master switch settings. So the member setting can override to turn sharing off for them specifically but cannot override to turn sharing on for them specifically.
Changed lines 58-60 from:
To manually update a share, select it from Share / Manage Shares and click "Update". This will snap your view to the view and filters of the share and re-sync every event on it. This lets you refresh the share with edits made outside the DayBack interface. See "[[Update Share | updating]]" for more.
We hope DayBack ''is'' the place where you'll make all the changes toyou schedule as it's the place you can see all your calendars together, view resources side-by-side, and work at longer time scales so deadlines don't sneak up on you.
We hope DayBack ''is'' the place where you'll make all the changes to
to:
To manually update a share, select it from Share / Manage Shares and click "Update". This will snap your view to the view and filters of the share and re-sync every event in view. This lets you refresh the share with edits made outside the DayBack interface. See "[[Update Share | updating]]" for more.
We hope DayBack ''is'' the place where you'll make all the changes to your schedule as it's the place you can see all your calendars together, view resources side-by-side, and work at longer time scales so deadlines don't sneak up on you.
We hope DayBack ''is'' the place where you'll make all the changes to your schedule as it's the place you can see all your calendars together, view resources side-by-side, and work at longer time scales so deadlines don't sneak up on you.
Changed line 58 from:
To manually update a share, select it from Sharing / Manage Shares and click "Update". This will snap your view to the view and filters of the share and re-sync every event on it. This lets you refresh the share with edits made outside the DayBack interface. See "[[Update Share | updating]]" for more.
to:
To manually update a share, select it from Share / Manage Shares and click "Update". This will snap your view to the view and filters of the share and re-sync every event on it. This lets you refresh the share with edits made outside the DayBack interface. See "[[Update Share | updating]]" for more.
Changed line 14 from:
-> � Publish the schedule for a conference or site visit
to:
-> � Publishing the schedule for a conference or site visit
Added lines 31-32:
%newwin, width=500% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/newshare.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/newshare.png]]
Added lines 34-35:
%newwin, width=500% [[https://www.seedcode.com/rootimages/stikipad/daybackonline/newshare2.png | https://www.seedcode.com/rootimages/stikipad/daybackonline/newshare2.png]]
Added lines 57-58:
If you want to double check than an edit has been synced to your share, you can click on a share at any time from Share / Manage Shares to view that share as the recipient would see it.
Changed line 4 from:
!!Overview
to:
!!Overview: Sharing Your Schedule
Deleted lines 56-67:
'''Some Limitations to Syncing:'''
-> Deletes work great: delete an event in DayBack and it is deleted from the share.
-> DayBack only syncs events that were ''originally included'' in the share. Events created after you've shared are not synced.
-> %roadmap%''Roadmap: there will eventually be an option to "automatically share new events that match these filters". THAT will be cool.''
-> If you edit an event so that it no longer matches the filter criteria of a share, the event is still shared, but will just not show up on the recipients default share view where the filters are in place.
-> If you want to double check than an edit has been synced to your share, you can click on a share at any time from Share / Manage Shares to view that share as the recipient would see it.
Changed lines 52-54 from:
Once you create a share, any changes made to the shared events inside DayBack will be synced to that share. This only applies to changes made in DayBack's interface: changes made outside DayBack (in your FileMaker system, for example) won't be synced until that event is again edited in DayBack's interface.
%roadmap%''Roadmap: we're planning an "update" option that will let you select a share and then update re-sync every event on it. This would let you refresh the share with edits made outside the DayBack interface.''
%roadmap%''Roadmap: we're planning an "
to:
Once you create a share, any changes made to the shared events inside DayBack will be synced to that share. This only applies to changes made in DayBack's interface: changes made outside DayBack (in your FileMaker system, for example) won't be synced until that event is again edited in DayBack's interface or until you manually update the share.
To manually update a share, select it from Sharing / Manage Shares and click "Update". This will snap your view to the view and filters of the share and re-sync every event on it. This lets you refresh the share with edits made outside the DayBack interface. See "[[Update Share | updating]]" for more.
To manually update a share, select it from Sharing / Manage Shares and click "Update". This will snap your view to the view and filters of the share and re-sync every event on it. This lets you refresh the share with edits made outside the DayBack interface. See "[[Update Share | updating]]" for more.
Changed lines 6-7 from:
Sharing lets you send a read-only calendar to folks who might otherwise not have access to your FileMaker or Google calendars. When you make a share you'll be creating a URL that contains exactly what you currently see on screen in DayBack.
to:
Sharing lets you send a specific calendar view to folks who don't have access to your FileMaker or Google calendars. When you make a share you'll be creating a URL that contains exactly what you currently see on screen in DayBack.
Changed lines 14-15 from:
-> � Sharing plans with your friends
to:
-> � Publish the schedule for a conference or site visit
-> � Sharing plans with your family and friends
-> � Sharing plans with your family and friends
Changed lines 29-30 from:
to:
To share your view, click "Share" in the upper right of DayBack Calendar, and then click "+ Share this view". You'll be asked to name your share and then set an expiration date. The name you give your share will show up for share recipients where you see a list of your calendar sources.
Changed lines 37-40 from:
-> '''Date Ranges.''' The share captures exactly what's in view when you select "Share this view", so events before or after the visible dates aren't included in the share. So when you're sharing project plans, for example, she from the horizon view as it can show the longest date ranges in DayBack.
-> '''Views.''' Recipients will open the share to exactly the same view you shared, so if you share from month view, that's what they'll see first. They can then navigate to other views if they need to see hourly schedules, for example.
-> '''Views.''' Recipients will open the share to exactly the same view you shared, so if you share from month view, that's what they'll see first. They can then navigate to other views if they need to see hourly schedules
to:
-> '''Date Ranges.''' The share captures exactly what's in view when you select "Share this view", so events before or after the visible dates aren't included in the share. So when you're sharing project plans, for example, share from the horizon view as it can show the longest date ranges in DayBack.
-> '''Views.''' Recipients will open the share to exactly the same view you shared, so if you share from month view, that's what they'll see first. They can then navigate to other views if they need to see hourly schedules or focus on individual days.
-> '''Views.''' Recipients will open the share to exactly the same view you shared, so if you share from month view, that's what they'll see first. They can then navigate to other views if they need to see hourly schedules or focus on individual days.
Changed lines 45-46 from:
--> If you share a schedule with just the resource filter set to "Dr. Thomas" AND the status filter set to "confirmed", the doctor receiving your share could turn off the "confirmed" filter but no additional events would be revealed since items which don't match your filters are not shared.
to:
--> If you share a schedule with the resource filter set to "Dr. Thomas" AND the status filter set to "confirmed", the doctor receiving your share could turn off the "confirmed" filter but no additional events would be revealed since only confirmed events were shared.
Changed lines 56-57 from:
We hope DayBack is the place where you'll make all the changes to you schedule as it's the place you can see all your calendars together, view resources side-by-side, and work at longer time scales so deadlines don't sneak up on you.
to:
We hope DayBack ''is'' the place where you'll make all the changes to you schedule as it's the place you can see all your calendars together, view resources side-by-side, and work at longer time scales so deadlines don't sneak up on you.
Changed lines 64-65 from:
-> %roadmap%''Roadmap: there will eventually be an option to "automatically include new events that match these filters". THAT will be cool.''
to:
-> %roadmap%''Roadmap: there will eventually be an option to "automatically share new events that match these filters". THAT will be cool.''
Changed lines 78-79 from:
As you edit events in DayBack, the calendar looks to see if the event is part of a share. If the event is shared, DayBack re-exports the event to DayBack's server, keeping the share in sync with your changes to the event.
to:
As you edit events in DayBack, the calendar looks to see if the event is part of a share. If the event is shared, DayBack re-exports the event to DayBack's server, keeping the share in sync with your changes to the event. Shares themselves don't poll DayBack's sever for changes so someone viewing a share while you make a change would need to click "refresh" to see your change take effect.
Changed lines 82-88 from:
Can recipients edit shared events? No. Recipients of a share URL will be unable to edit those events.
Do recipients need to have accounts in my FileMaker Solution? No. Folks opening a share URL don't need any information from your FileMaker solution and DayBack never hits your FileMaker Server when folks open a share.
If an event is linked to a contact, is that contact information shared? The share only includes the information you can see in DayBack. So if you have linked a contact to an event, your share recipient will be able to see the contact's name when they click on the event, but they won't have access to any other facts about the contact unless you've included those in the event's display.
Can I password protect a share? No. Anyone with the share URL can open it. If you've shared something by mistake you can delete the share from Share / Manage Shares. The share URLS are not guessable and include random elements, so folks likely won't be able to find your shares withoutthe URL.
Do recipients need to have accounts in my FileMaker Solution? No. Folks opening a share URL don't need any information from your FileMaker solution and DayBack never hits your FileMaker Server when folks open a share.
If an event is linked to a contact, is that contact information shared? The share only includes the information you can see in DayBack. So if you have linked a contact to an event, your share recipient will be able to see the contact's name when they click on the event, but they won't have access to any other facts about the contact unless you've included those in the event's display.
Can I password protect a share? No. Anyone with the share URL can open it. If you've shared something by mistake you can delete the share from Share / Manage Shares. The share URLS are not guessable and include random elements, so folks likely won't be able to find your shares without
to:
'''Can recipients edit shared events?''' No. Recipients of a share URL will be unable to edit those events.
'''Do recipients need to have accounts in my FileMaker Solution?''' No. Folks opening a share URL don't need any information from your FileMaker solution and DayBack never hits your FileMaker Server when folks open a share.
'''If an event is linked to a contact, is that contact information shared?''' The share only includes the information you can see in DayBack. So if you have linked a contact to an event, your share recipient will be able to see the contact's name when they click on the event, but they won't have access to any other facts about the contact unless you've included those in the event's display.
'''Can I password protect a share?''' No. Anyone with the share URL can open it. If you've shared something by mistake you can delete the share from Share / Manage Shares. The share URLS are not guessable and include random elements, so folks likely won't be able to find your shares without you giving them the URL.
'''Who can create a share?''' By default, only [[administrators]] of your DayBack account can create shares. But Administrators can change this, enabling sharing for everyone, or turning off sharing completely.
'''Can I remove the Share menu for all users?''' Yes. In Administrator Settings you'll see a section named "Views". Within that, simply enter "Share" beside "Hide menu items".
'''Do recipients need to have accounts in my FileMaker Solution?''' No. Folks opening a share URL don't need any information from your FileMaker solution and DayBack never hits your FileMaker Server when folks open a share.
'''If an event is linked to a contact, is that contact information shared?''' The share only includes the information you can see in DayBack. So if you have linked a contact to an event, your share recipient will be able to see the contact's name when they click on the event, but they won't have access to any other facts about the contact unless you've included those in the event's display.
'''Can I password protect a share?''' No. Anyone with the share URL can open it. If you've shared something by mistake you can delete the share from Share / Manage Shares. The share URLS are not guessable and include random elements, so folks likely won't be able to find your shares without you giving them the URL.
'''Who can create a share?''' By default, only [[administrators]] of your DayBack account can create shares. But Administrators can change this, enabling sharing for everyone, or turning off sharing completely.
'''Can I remove the Share menu for all users?''' Yes. In Administrator Settings you'll see a section named "Views". Within that, simply enter "Share" beside "Hide menu items".
Changed lines 71-73 from:
to:
When you make a share, the calendar sends each of the visible events to DayBack's servers: almost like exporting your events. The calendar also records the current view, date range, and filters you have employed.
When a recipient opens a shared URL, DayBack reads the shared events from the "export" on our server instead of from your original data source (like Google or FileMaker). Share recipients have no access to your original data source and no access to events that weren't visible when you made the share.
When exporting an event, DayBack only sends the information you can see in the view you shared and the information you can see in the event's popover (what you see when you click on an event). Other attributes of the event, or attributes of records related to the event, aren't exported to the share.
As you edit events in DayBack, the calendar looks to see if the event is part of a share. If the event is shared, DayBack re-exports the event to DayBack's server, keeping the share in sync with your changes to the event.
When a recipient opens a shared URL, DayBack reads the shared events from the "export" on our server instead of from your original data source (like Google or FileMaker). Share recipients have no access to your original data source and no access to events that weren't visible when you made the share.
When exporting an event, DayBack only sends the information you can see in the view you shared and the information you can see in the event's popover (what you see when you click on an event). Other attributes of the event, or attributes of records related to the event, aren't exported to the share.
As you edit events in DayBack, the calendar looks to see if the event is part of a share. If the event is shared, DayBack re-exports the event to DayBack's server, keeping the share in sync with your changes to the event.
Changed lines 81-87 from:
to:
Can recipients edit shared events? No. Recipients of a share URL will be unable to edit those events.
Do recipients need to have accounts in my FileMaker Solution? No. Folks opening a share URL don't need any information from your FileMaker solution and DayBack never hits your FileMaker Server when folks open a share.
If an event is linked to a contact, is that contact information shared? The share only includes the information you can see in DayBack. So if you have linked a contact to an event, your share recipient will be able to see the contact's name when they click on the event, but they won't have access to any other facts about the contact unless you've included those in the event's display.
Can I password protect a share? No. Anyone with the share URL can open it. If you've shared something by mistake you can delete the share from Share / Manage Shares. The share URLS are not guessable and include random elements, so folks likely won't be able to find your shares without the URL.
Do recipients need to have accounts in my FileMaker Solution? No. Folks opening a share URL don't need any information from your FileMaker solution and DayBack never hits your FileMaker Server when folks open a share.
If an event is linked to a contact, is that contact information shared? The share only includes the information you can see in DayBack. So if you have linked a contact to an event, your share recipient will be able to see the contact's name when they click on the event, but they won't have access to any other facts about the contact unless you've included those in the event's display.
Can I password protect a share? No. Anyone with the share URL can open it. If you've shared something by mistake you can delete the share from Share / Manage Shares. The share URLS are not guessable and include random elements, so folks likely won't be able to find your shares without the URL.
Changed lines 40-43 from:
-> '''Filters.''' Shares respect your filters, enabling you to share ''just part of your calendar''. Events that are filtered out of view ''will not be included'' in your share. Recipients will see your list of filters (statues and resources) and will be able to filter your share further than you have. Here's an example:
--> If you share a schedule with just theresource filter set to "Dr. Thomas", the doctor receiving your share can still filter the share by status to see just their "confirmed" appointments.
--> If you share a schedule with just the
to:
-> '''Filters.''' Shares respect your [[filters]], enabling you to share ''just part of your calendar''. Events that are filtered out of view ''will not be included'' in your share. Recipients will see your list of filters (statues and resources) and will be able to filter your share further than you have. Here's an example:
--> If you share a schedule with just the [[Resources | resource]] filter set to "Dr. Thomas", the doctor receiving your share can still filter the share by status to see just their "confirmed" appointments.
--> If you share a schedule with just the [[Resources | resource]] filter set to "Dr. Thomas", the doctor receiving your share can still filter the share by status to see just their "confirmed" appointments.
Changed line 55 from:
We hope DayBack is the place where you'll make all the changes to you schedule as it's the place you can see all your calendars together and work at longer time scales so deadlines don't sneak up on you.
to:
We hope DayBack is the place where you'll make all the changes to you schedule as it's the place you can see all your calendars together, view resources side-by-side, and work at longer time scales so deadlines don't sneak up on you.
Changed lines 12-14 from:
--> � Sending project schedules to your customers
--> ��Giving employees (resources) access to their schedules
--> � Sharing plans with your friends
-
to:
-> � Sending project schedules to your customers
-> ��Giving employees (resources) access to their schedules
-> � Sharing plans with your friends
-> ��Giving employees (resources) access to their schedules
-> � Sharing plans with your friends
Changed lines 25-27 from:
[[#Creating]]
!!
!!
to:
!! [[#Creating]]Creating and Previewing a Share
Changed lines 48-49 from:
[[#Sync]]\\
!!Keeping Shares in Sync
!!
to:
!! [[#Sync]]Keeping Shares in Sync
Changed lines 25-27 from:
to:
[[#Creating]]
!! Creating and Previewing a Share
!! Creating and Previewing a Share
Changed lines 48-49 from:
to:
[[#Sync]]
!! Keeping Shares in Sync
!! Keeping Shares in Sync
Changed lines 2-3 from:
''Sharing public, read-only calendars is coming soon!''
to:
%roadmap%''Sharing public, read-only calendars is coming soon!''
Changed line 75 from:
fbsdfbf
to:
fbsdfbf
Changed lines 23-24 from:
to:
\\
Changed line 75 from:
fbsdfbf
to:
fbsdfbf
Changed line 1 from:
%define=bluegrass color=#009999% blue grass
to:
%define=roadmap color=#669999%
Changed lines 16-17 from:
'''In this article:'''
to:
[+'''In this article:'''+]
Changed lines 23-24 from:
to:
[[<<]]
Changed lines 51-52 from:
%bluegrass%''Coming: we're planning an "update" option that will let you select a share and then update re-sync every event on it. This would let you refresh the share with edits made outside the DayBack interface.''
to:
%roadmap%''Roadmap: we're planning an "update" option that will let you select a share and then update re-sync every event on it. This would let you refresh the share with edits made outside the DayBack interface.''
Changed line 61 from:
-> %bluegrass%''Coming: there will eventually be an option to "automatically include new events that match these filters". THAT will be cool.''
to:
-> %roadmap%''Roadmap: there will eventually be an option to "automatically include new events that match these filters". THAT will be cool.''
Added line 1:
%define=bluegrass color=#009999% blue grass
Changed lines 38-41 from:
-> '''Filters.''' Shares respect your filters, enabling you to share ''just part of your calendar''. Events that are filtered out of view ''will not be included'' in your share. Recipients will see your list of filters (statues and resources) and will be able to filter your share further than you have. Hers's an example:
--> If you share a schedule with just the resource filter set to "Dr. Thomas", the doctorcan still filter the share they received by status to see just their "confirmed" appointments.
--> If you share a schedule with just the resource filter set to "Dr. Thomas", the doctor
to:
-> '''Filters.''' Shares respect your filters, enabling you to share ''just part of your calendar''. Events that are filtered out of view ''will not be included'' in your share. Recipients will see your list of filters (statues and resources) and will be able to filter your share further than you have. Here's an example:
--> If you share a schedule with just the resource filter set to "Dr. Thomas", the doctor receiving your share can still filter the share by status to see just their "confirmed" appointments.
--> If you share a schedule with just the resource filter set to "Dr. Thomas" AND the status filter set to "confirmed", the doctor receiving your share could turn off the "confirmed" filter but no additional events would be revealed since items which don't match your filters are not shared.
-> '''Expiring and Deleting Shares.''' From the Share menu in DayBack, click "Manage Shares" and you'll see all the views your group has shared. Deleting a share here will prevent recipients from accessing the share again. The share will behave as if it's expired and users will see a note saying the share can't be found.
--> If you share a schedule with just the resource filter set to "Dr. Thomas", the doctor receiving your share can still filter the share by status to see just their "confirmed" appointments.
--> If you share a schedule with just the resource filter set to "Dr. Thomas" AND the status filter set to "confirmed", the doctor receiving your share could turn off the "confirmed" filter but no additional events would be revealed since items which don't match your filters are not shared.
-> '''Expiring and Deleting Shares.''' From the Share menu in DayBack, click "Manage Shares" and you'll see all the views your group has shared. Deleting a share here will prevent recipients from accessing the share again. The share will behave as if it's expired and users will see a note saying the share can't be found.
Changed lines 48-49 from:
to:
Once you create a share, any changes made to the shared events inside DayBack will be synced to that share. This only applies to changes made in DayBack's interface: changes made outside DayBack (in your FileMaker system, for example) won't be synced until that event is again edited in DayBack's interface.
%bluegrass%''Coming: we're planning an "update" option that will let you select a share and then update re-sync every event on it. This would let you refresh the share with edits made outside the DayBack interface.''
We hope DayBack is the place where you'll make all the changes to you schedule as it's the place you can see all your calendars together and work at longer time scales so deadlines don't sneak up on you.
'''Some Limitations to Syncing:'''
-> Deletes work great: delete an event in DayBack and it is deleted from the share.
-> DayBack only syncs events that were ''originally included'' in the share. Events created after you've shared are not synced.
-> %bluegrass%''Coming: there will eventually be an option to "automatically include new events that match these filters". THAT will be cool.''
-> If you edit an event so that it no longer matches the filter criteria of a share, the event is still shared, but will just not show up on the recipients default share view where the filters are in place.
-> If you want to double check than an edit has been synced to your share, you can click on a share at any time from Share / Manage Shares to view that share as the recipient would see it.
%bluegrass%''Coming: we're planning an "update" option that will let you select a share and then update re-sync every event on it. This would let you refresh the share with edits made outside the DayBack interface.''
We hope DayBack is the place where you'll make all the changes to you schedule as it's the place you can see all your calendars together and work at longer time scales so deadlines don't sneak up on you.
'''Some Limitations to Syncing:'''
-> Deletes work great: delete an event in DayBack and it is deleted from the share.
-> DayBack only syncs events that were ''originally included'' in the share. Events created after you've shared are not synced.
-> %bluegrass%''Coming: there will eventually be an option to "automatically include new events that match these filters". THAT will be cool.''
-> If you edit an event so that it no longer matches the filter criteria of a share, the event is still shared, but will just not show up on the recipients default share view where the filters are in place.
-> If you want to double check than an edit has been synced to your share, you can click on a share at any time from Share / Manage Shares to view that share as the recipient would see it.
Changed lines 11-14 from:
to:
--> � Sending project schedules to your customers
--> ��Giving employees (resources) access to their schedules
--> � Sharing plans with your friends
--> ��Giving employees (resources) access to their schedules
--> � Sharing plans with your friends
Changed line 17 from:
-> [[#Creating | Creating a Share]]
to:
-> [[#Creating | Creating and Previewing a Share]]
Changed lines 23-26 from:
!! [[#Creating]]Creating a Share
agawrg
to:
!! [[#Creating]]Creating and Previewing a Share
Click "Share" in the upper right of DayBack Calendar, and then click "+ Share this view". You'll be asked to name your share and then set an expiration date. The name you give your share will show up for share recipients where you see a list of your calendar sources.
Once you click "Create Share" your share is ready to go and you'll see a URL you can copy and email to anyone who needs to see this schedule.
Click "View Share" and you'll get a preview of exactly what your recipients will receive.
Click "Share" in the upper right of DayBack Calendar, and then click "+ Share this view". You'll be asked to name your share and then set an expiration date. The name you give your share will show up for share recipients where you see a list of your calendar sources.
Once you click "Create Share" your share is ready to go and you'll see a URL you can copy and email to anyone who needs to see this schedule.
Click "View Share" and you'll get a preview of exactly what your recipients will receive.
Changed lines 33-34 from:
-> asdgrg
to:
-> '''Date Ranges.''' The share captures exactly what's in view when you select "Share this view", so events before or after the visible dates aren't included in the share. So when you're sharing project plans, for example, she from the horizon view as it can show the longest date ranges in DayBack.
-> '''Views.''' Recipients will open the share to exactly the same view you shared, so if you share from month view, that's what they'll see first. They can then navigate to other views if they need to see hourly schedules, for example.
-> '''Filters.''' Shares respect your filters, enabling you to share ''just part of your calendar''. Events that are filtered out of view ''will not be included'' in your share. Recipients will see your list of filters (statues and resources) and will be able to filter your share further than you have. Hers's an example:
--> If you share a schedule with just the resource filter set to "Dr. Thomas", the doctor can still filter the share they received by status to see just their "confirmed" appointments.
-> '''Views.''' Recipients will open the share to exactly the same view you shared, so if you share from month view, that's what they'll see first. They can then navigate to other views if they need to see hourly schedules, for example.
-> '''Filters.''' Shares respect your filters, enabling you to share ''just part of your calendar''. Events that are filtered out of view ''will not be included'' in your share. Recipients will see your list of filters (statues and resources) and will be able to filter your share further than you have. Hers's an example:
--> If you share a schedule with just the resource filter set to "Dr. Thomas", the doctor can still filter the share they received by status to see just their "confirmed" appointments.
Changed lines 1-45 from:
to:
''Sharing public, read-only calendars is coming soon!''
!!Overview
Sharing lets you send a read-only calendar to folks who might otherwise not have access to your FileMaker or Google calendars. When you make a share you'll be creating a URL that contains exactly what you currently see on screen in DayBack.
And any changes you make in DayBack will be synced with the share so your URL is always up to date.
Sharing is great for:
* � Sending project schedules to your customers
* ��Giving employees (resources) access to their schedules
* � Coordinating plans with your friends
'''In this article:'''
-> [[#Creating | Creating a Share]]
-> [[#Sync | Keeping Shares in Sync]]
-> [[#Works | How it Works]]
-> [[#FAQ | Frequently Asked Questions]]
!! [[#Creating]]Creating a Share
agawrg
'''Some tips:'''
-> asdgrg
!! [[#Sync]]Keeping Shares in Sync
fbsdfbf
!! [[#Works]]How It Works
fbsdfbf
!! [[#FAQ]]Frequently Asked Questions
fbsdfbf
!!Overview
Sharing lets you send a read-only calendar to folks who might otherwise not have access to your FileMaker or Google calendars. When you make a share you'll be creating a URL that contains exactly what you currently see on screen in DayBack.
And any changes you make in DayBack will be synced with the share so your URL is always up to date.
Sharing is great for:
* � Sending project schedules to your customers
* ��Giving employees (resources) access to their schedules
* � Coordinating plans with your friends
'''In this article:'''
-> [[#Creating | Creating a Share]]
-> [[#Sync | Keeping Shares in Sync]]
-> [[#Works | How it Works]]
-> [[#FAQ | Frequently Asked Questions]]
!! [[#Creating]]Creating a Share
agawrg
'''Some tips:'''
-> asdgrg
!! [[#Sync]]Keeping Shares in Sync
fbsdfbf
!! [[#Works]]How It Works
fbsdfbf
!! [[#FAQ]]Frequently Asked Questions
fbsdfbf
Added line 1:
Sharing public, read-only calendars is coming soon!
