Google: Creates an access control rule — response body
Creates an access control rule.: response body. Complete fields and constraints for contract 2026-10-27.
API reference · Contract 2026-10-27
SDK schema: Creates an access control rule — response body
| Field | Type | Presence | Description and constraints |
|---|---|---|---|
$ | object | Root | |
etag | string | Optional | ETag of the resource. |
id | string | Optional | Identifier of the Access Control List (ACL) rule. See Sharing calendars. |
kind | string | Optional | Type of the resource (“calendar#aclRule”). Default: calendar#aclRule |
role | string | Optional | The role assigned to the scope. Possible values are: - “none” - Provides no access. - “freeBusyReader” - Provides read access to free/busy information. - “reader” - Provides read access to the calendar. Private events will appear to users with reader access, but event details will be hidden. - “writerWithoutPrivateAccess” - Provides read and write access to the calendar. Private events will appear to users with writerWithoutPrivateAccess access, but event details will be hidden. - “writer” - Provides read and write access to the calendar. Private events will appear to users with writer access, and event details will be visible. Provides read access to the calendar’s ACLs. - “owner” - Provides manager access to the calendar. This role has all of the permissions of the writer role with the additional ability to modify access levels of other users. Important: the owner role is different from the calendar’s data owner. A calendar has a single data owner, but can have multiple users with owner role. |
scope | Model | Optional | Expand Creates an access control rule — response body — scope |
Referenced models: Creates an access control rule — response body — scope