By default, as soon as you publish a Trumba® calendar, the calendar's events are publicly discoverable through a page hosted on www.qatrumba.com.
If your calendars contain proprietary information and other confidential data that you're providing to a limited group on the internet or on an intranet or secure server, you can take steps during the calendar setup and publishing process that will keep your data private. The steps are described below along with links to detailed how-to information.
Tip You either password protect a calendar or use a secure URL. As described below, the two solutions are useful in different contexts.
You can restrict access to a published calendar to specific email addresses by: 1) requiring visitor account sign in, and then 2) sharing the calendar with just those email addresses that should have access.
After you've secured your calendar, users who don't first sign in with their visitor account, and users who sign in but don't have sharing permissions set up, won't be able to access the calendar.
Use this option when your events are aimed at a relatively small and diverse group of people who don't all have access to the same securable computing environment.
By password protecting your calendars, you:
If you go with password protection, be sure to set a strong password. You can change or cancel the password at any time.
Use this option if you're publishing your calendar on a corporate network or other secure computing environment where you can use your organization's computing infrastructure to secure the webpages in which the calendar spuds are embedded.
Secure URL publishing uses a secure key to generate a unique hash and expiration time for how long the spud code can be used to access a calendar's spuds. This prevents:
To use secure URL publishing, you must be proficient with ASP.Net, PHP, or a similar web server scripting language and have access to an environment in which you can build and view pages in a browser.
By default, published calendars include a variety of calendar and event actions. The intention of the actions is to encourage viewers to attend and share the events they find.
However, if you're concerned about data security, you don't want your calendar visitors downloading event feeds, subscribing to calendar emails, adding events to their personal calendars, or sharing events with friends.
To prevent visitors from taking actions, for each secure calendar you publish, you can hide the calendar actions panel and you can hide event actions in both the main calendar and event detail views.
Tip These instructions assume that you have already published your calendar using either password protection or a secure URL.