[OGo-Users] Default Write Access

Peter Duda users@opengroupware.org
Thu, 13 Sep 2007 14:22:01 -0700


>Ah, so you are creating the appointments via GroupDAV/CalDAV (hence the
>mention of folders)?

Zidelook actually, but ZL 2.1 says it fully supports the default write
access of the scheduler (which is why I posted here - I hope that was right)

What I did was give the "oversight" team write access in everybody's
preferences and it works for me for now.  The oversight group can't read
private items therefore they can't change them, but in the public folder
(all-internet) they always have write authority, and if they are a member of
a group they have write authority there as well. 

What would be nice ;-) and what I was originally trying to ask is if teams
as well as individuals had configurable default write and read access in the
scheduler.  That way an oversight group could view and or change another
teams appointments without having to be a member of that team and have it
show up in personal calendars whenever the team was a participant. (which it
sounds like isn't possible)

Maybe I will post this idea in the discuss thread if it hasn't been talked
about already

Thanks for the help
Peter


-----Original Message-----
From: users-admin@opengroupware.org [mailto:users-admin@opengroupware.org]
On Behalf Of Adam Tauno Williams
Sent: Thursday, September 13, 2007 12:41 PM
To: users@opengroupware.org
Subject: RE: [OGo-Users] Default Write Access

> I am talking about write access on appointments. Can I give write access
to
> appointments created in group folders 

Ah, so you are creating the appointments via GroupDAV/CalDAV (hence the
mention of folders)?

> to other members of another group?

In recent versions of ZideStore the user's default write permissions
apply to appointments unless they are created in a specific group's
folder (then I think the write permissions are always specific to that
group).  I'm not aware of anyway to setup 'additive groups' when
creating appointments via ZideStore.

> One of the ideas is to have a group that "oversees" appointments of other
> groups - especially the public folder

I wonder if that isn't more of a non-participant participant use-case
than it is a permissions use case (as participants can always see
appointments they are participating in).  Perhaps adding the oversight
team as a non-participant and enabling overview folders would be a
solution?