The only event change that is propagated from attendees back to the However, these changesĪre only reflected on their own copy and might be lost if the organizer makes a These properties are controlled by theĪttendee's settings and not by the organizer calendar.Īttendees can also change the shared properties of the event. Some propertiesĪre private, such as reminders, colorId, transparency, or theĮxtendedProperties.private property. Not all information is shared between all the event copies. Organizer calendar, the changes are propagated to attendee copies. ThisĬalendar owns the shared event information (id, start and end The calendar where the event is created is the organizer calendar. Unresponded invitations on their calendar. Note: Users can indicate in their settings that they don’t want to see This sends an invitation email to the attendeesĪnd places the event on their calendar. You can share an event with other people (or group calendars andīy adding them as attendees. The details of this event are only visible to users with at least writer access to the calendar. The details of this event are visible to everyone with at least freeBusyReader access to the calendar. The visibility of the event is determined by the ACLs of the calendar.
Lists the possible values of the visibility property: Visibility This property has no meaning for non-shared calendars. Once the calendar is shared, you can adjust the access to individualĮvents on a calendar by changing the visibility Interact with the shared calendar, you will also need to call the CalendarList: insert() method. Note: Sharing a calendar with a user no longer automatically inserts theĬalendar into their CalendarList.
In this case, even if you grant writerĪccess to the public, users outside the domain will only see the free-busyĭetails. For example, suppose your domain has a setting that Up to 6,000 ACLs can be added per calendar.įor Google Workspace users, there are also domain This role has all of the permissions of the writer role with the additional ability to see and manipulate ACLs.īy default, each user has owner access to their primary calendar, and thisĪccess cannot be relinquished. Lets the grantee read and write events on the calendar. Lets the grantee read events on the calendar. Free/busy information can be retrieved using the freeBusy.query operation.
Lets the grantee see whether the calendar is free or busy at a given time, but does not allow access to event details. One of those listed in the following table: Role Each resource in the ACLĬollection grants a specified grantee a certain access role, which is The sharing settings of a given calendar are represented by the ACL The owners of a calendar can share the calendar by giving access to other Modify their copy of the event - for example, change the color it has in The invitee can then accept or reject the invitation, and to some extent also Inviting someone to an event will put a copy of that event on their calendar. You can also adjust the access to individual events on the shared calendar.Īlternatively, you can invite others to individual events on your calendar.