Browse Prior Art Database

Dynamic Calendar Authorization

IP.com Disclosure Number: IPCOM000111896D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 29K

Publishing Venue

IBM

Related People

Schell, DJ: AUTHOR

Abstract

In current calendar implementations, users are allowed to specify varying levels of calendar access to other users. For example, some users are allowed to see only non-classified events, while others may be allowed to see personal and/or confidential events as well. A drawback with these types of implementations is that they are all-or-nothing with no ability to specify authorization on an event by event basis, especially to others directly involved in a specific event.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 100% of the total text.

Dynamic Calendar Authorization

      In current calendar implementations, users are allowed to
specify varying levels of calendar access to other users.  For
example, some users are allowed to see only non-classified events,
while others may be allowed to see personal and/or confidential
events as well.  A drawback with these types of implementations is
that they are all-or-nothing with no ability to specify authorization
on an event by event basis, especially to others directly involved in
a specific event.

      Techniques are disclosed to dynamically and automatically alter
calendar access authorizations to include the event or meeting
participants.  If a user schedules a classified meeting with one or
more individuals, the user's calendar access authorization table is
automatically updated to grant access of that specific event to the
event participants.  Since they will be attending the event and
already know of the event, there is no reason for them not to be able
to see the event on the user's calendar.  The event remains
classified however to all non-participants as specified in the user's
authorization table.  No specific actions are required on the part of
the user to grant these event-specific authorizations; it is done
automatically when the event is added to the user's calendar.