Acl: update
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
更新访问控制规则。
立即试用。
请求
HTTP 请求
PUT https://www.googleapis.com/calendar/v3/calendars/calendarId/acl/ruleId
参数
参数名称 |
值 |
说明 |
路径参数 |
calendarId |
string |
日历标识符。如需检索日历 ID,请调用 calendarList.list 方法。如果您想访问当前登录用户的主要日历,请使用“primary ”关键字。
|
ruleId |
string |
ACL 规则标识符。
|
可选的查询参数 |
sendNotifications |
boolean |
是否发送有关日历共享更改的通知。请注意,我们不会就移除访问权限发送通知。可选。默认值为 True。
|
授权
此请求需要获得以下至少一个范围的授权:
范围 |
https://www.googleapis.com/auth/calendar |
https://www.googleapis.com/auth/calendar.acls |
如需了解详情,请参阅身份验证和授权页面。
请求正文
在请求正文中,提供具有以下属性的 Acl 资源:
属性名称 |
值 |
说明 |
备注 |
必需属性 |
scope |
object |
此 ACL 规则授予的日历访问权限范围。 |
|
scope.type |
string |
镜的类型。可能的值包括: - “
default ”- 公开范围。这是默认值。 - “
user ”- 将范围限制为单个用户。 - “
group ”- 将范围限制为一个群组。 - “
domain ”- 将范围限制为一个网域。 注意:授予“default ”(公开)范围的权限适用于任何用户(无论是否经过身份验证)。 |
|
可选属性 |
role |
string |
分配给该镜的角色。可能的值包括: - “
none ”- 不提供访问权限。 - “
freeBusyReader ”- 对空闲/忙碌信息提供读取权限。 - “
reader ”- 提供对日历的读取权限。不公开活动会向拥有读者访问权限的用户显示,但活动详情将被隐藏。 - “
writer ”- 提供对日历的读写权限。不公开活动会向具有创作者访问权限的用户显示,并且系统会显示活动详情。提供对日历 ACL 的读取权限。 - “
owner ”- 提供日历的所有权。此角色具有 Writer 角色的所有权限,还可以操控 ACL。 |
可写入 |
scope.value |
string |
用户或群组的电子邮件地址,或域名(具体取决于范围类型)。针对类型“default ”省略。 |
可写入 |
响应
如果成功,此方法将在响应正文中返回一项 Acl 资源。
试试看!
使用下面的 API Explorer 对实际数据调用此方法,然后查看响应。
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-25。
[null,null,["最后更新时间 (UTC):2025-07-25。"],[],[],null,["# Acl: update\n\n| **Note:** Requires [authorization](#auth).\n\nUpdates an access control rule.\n[Try it now](#try-it).\n\nRequest\n-------\n\n### HTTP request\n\n```\nPUT https://www.googleapis.com/calendar/v3/calendars/calendarId/acl/ruleId\n```\n\n### Parameters\n\n| Parameter name | Value | Description |\n|---------------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **Path parameters** |||\n| `calendarId` | `string` | Calendar identifier. To retrieve calendar IDs call the [calendarList.list](/workspace/calendar/api/v3/reference/calendarList/list) method. If you want to access the primary calendar of the currently logged in user, use the \"`primary`\" keyword. |\n| `ruleId` | `string` | ACL rule identifier. |\n| **Optional query parameters** |||\n| `sendNotifications` | `boolean` | Whether to send notifications about the calendar sharing change. Note that there are no notifications on access removal. Optional. The default is True. |\n\n### Authorization\n\nThis request requires authorization with at least one of the following scopes:\n\n| Scope |\n|-------------------------------------------------|\n| `https://www.googleapis.com/auth/calendar` |\n| `https://www.googleapis.com/auth/calendar.acls` |\n\nFor more information, see the [authentication and authorization](/workspace/guides/configure-oauth-consent) page.\n\n### Request body\n\nIn the request body, supply an [Acl resource](/workspace/calendar/api/v3/reference/acl#resource) with the following properties:\n\n| Property name | Value | Description | Notes |\n|---------------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|\n| **Required Properties** ||||\n| `scope` | `object` | The extent to which [calendar access](https://developers.google.com/workspace/calendar/concepts/sharing#sharing_calendars) is granted by this ACL rule. | |\n| scope.`type` | `string` | The type of the scope. Possible values are: - \"`default`\" - The public scope. This is the default value. - \"`user`\" - Limits the scope to a single user. - \"`group`\" - Limits the scope to a group. - \"`domain`\" - Limits the scope to a domain. Note: The permissions granted to the \"`default`\", or public, scope apply to any user, authenticated or not. | |\n| **Optional Properties** ||||\n| `role` | `string` | 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. - \"`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 ownership of the calendar. This role has all of the permissions of the writer role with the additional ability to manipulate ACLs. | writable |\n| scope.`value` | `string` | The email address of a user or group, or the name of a domain, depending on the scope type. Omitted for type \"`default`\". | writable |\n\nResponse\n--------\n\nIf successful, this method returns an [Acl resource](/workspace/calendar/api/v3/reference/acl#resource) in the response body.\n\nTry it!\n-------\n\n\nUse the APIs Explorer below to call this method on live data and see the response."]]