Can you please clarify what the various privacy options mean for those of us using LiveWhale Calendar but NOT the LiveWhale CMS? I read the Privacy Options documentation but it is still not clear to me what folks need to be "logged into"to view the event and exactly how visibility is impacted. For example:
Does “logged in user” mean anyone logged into the LiveWhale CMS, or calendar admins logged into LiveWhale Calendar, or something else? Our units are understanding this to mean an event will appear in a widget or calendar that is on web page protected by SSO in our own CMS, which does not seem possible if the CMS is not LiveWhale?
Do all privacy options other than “Everyone” suppress the event from calendars and widgets? So an event coded “Anyone with the link” would not appear anywhere but if I send someone the event URL and they click it, they can see the event page?
Hi folks – there is a bit more to this (we’re talking about updating our docs to clarify, but I’ll briefly mention here).
“Any logged-in user” covers any Calendar/CMS manager (someone with a user account in LiveWhale to edit content) as well as any SSO user. So, if someone tries to visit a private event url /event/1234-my-any-logged-in-user-event, they’ll get redirected through the LiveWhale SSO connection and then—if any successful login handshake is made (even if their username doesn’t match up with a LW user account) we show them the content.
This is true on front-end calendars as well, but the only tricky thing is in order to show the private content, we need to have a successful LiveWhale-SSO handshake (it’s not enough to arrive at the calendar with an existing login session from elsewhere in your ecosystem).
That’s why you’ll see some designs include a login link, e.g. the “IU Only Events Login” on IU Bloomington Calendar – that sends folks to SSO, then on a successful login they’re redirect back to the page where “Any logged in user events” now appear.
Widgets and API results though, yes, those wouldn’t show “Any logged-in user events” so putting a widget on one of your private/SSO pages wouldn’t make a difference. It’s conceivable to do something fancy with a widget via customization to show private events, feel free to reach out if that would be useful to discuss further.