Ryan,

Thanks for the update.

Regards,
Charlie


On Mar 14, 4:39 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote:
> Thanks Charlie.
>
> It turns out that the "root" access level is valid for Google Apps
> calendars.  It should be described in the documentation as:
> "The root for a Google Apps domain has the access level of owner for
> all calendars in his domain."
>
> I have filed a documentation bug for this issue, as well as the editor
> vs contributor issue you pointed out 
> earlier:http://groups.google.com/group/google-calendar-help-dataapi/browse_th...
>
> Thanks again!
>
> Cheers,
>
> -Ryan
>
> On Mar 5, 2:12 pm, "Charlie Wood" <[EMAIL PROTECTED]> wrote:
>
> > Done.
>
> > On Mar 5, 2:02 pm, "Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote:
>
> > > Hi Charlie,
>
> > > This appears to be a bug-- The access levels you should see for your users
> > > are those in the 
> > > documentation:http://code.google.com/apis/calendar/reference.html#gCalaccesslevel
>
> > > If you can send me (privately) the calendar address for which you are 
> > > seeing
> > > that accesslevel, we'll take a look it it.
>
> > > Thanks,
>
> > > -Ryan
>
> > > On 3/5/07, Charlie Wood <[EMAIL PROTECTED]> wrote:
>
> > > > One of our users has a calendar containing the element:
>
> > > > <gCal:accesslevel value="root"/>
>
> > > > I can't find this value documented anywhere, and haven't been able to
> > > > reproduce it using the web UI. Is it new? Can I assume that the user
> > > > has write access to that calendar? Any other new values I should know
> > > > about? :-)
>
> > > > Thanks,
> > > > Charlie


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to