Re: Access Rights According to CSA

["William P. Spencer" <bill@xxxxxxxxxxxxxx>]

On 29 Jul 1996, Frank Dawson wrote:

> ... long note ...


Whew.  Frank, that's alot of stuff in the CSA document. The access list
is a great way of controlling access to a calendar.  And it is very 
important to understand that users can take on different roles with 
respect to certain events, which might give them different access rights 
to those events.

It did take me a while to map out the roles, and the access rights, and in
general what's what.  I'm still not sure I've got it all. Perhaps some
concrete examples, using sponsors, owners, users, and calendars would be
good. 

As a test of my understanding, here's one example.  George is the organizer
of a meeting to which John is invited, and is a confirmed attendee.  If an
agenda is included as a description of the meeting, and George wishes to
change the agenda after having already scheduled it, he should be allowed
to do that, and have the change appear in John's schedule.  This should be
true even if George (as a calendar owner) does not normally have MODIFY 
permission to John's schedule. This is what is set up with ORGANIZER_RIGHTS.

I also had a question regarding what I call INVITE permission within SWTP. 
Does that correspond with the INSERT_ENTRIES access permission in the CSA
documents?  Physically, an insertion is what happens on the SWTP server
when someone is invited to a meeting.  While I was trying to do a 1-1
correspondance between SWTP and the CSA stuff, I just wanted to make sure
there was an access permission that prevented an invitation from being
sent. 

Bill   <bill@p2software.com>