选择您的 Cookie 首选项

我们使用必要 Cookie 和类似工具提供我们的网站和服务。我们使用性能 Cookie 收集匿名统计数据,以便我们可以了解客户如何使用我们的网站并进行改进。必要 Cookie 无法停用,但您可以单击“自定义”或“拒绝”来拒绝性能 Cookie。

如果您同意,AWS 和经批准的第三方还将使用 Cookie 提供有用的网站功能、记住您的首选项并显示相关内容,包括相关广告。要接受或拒绝所有非必要 Cookie,请单击“接受”或“拒绝”。要做出更详细的选择,请单击“自定义”。

How Amazon Q Business connector crawls GitHub (Cloud) ACLs

聚焦模式
How Amazon Q Business connector crawls GitHub (Cloud) ACLs - Amazon Q Business
此页面尚未翻译为您的语言。 请求翻译

When you connect an GitHub (Cloud) data source to Amazon Q Business, Amazon Q crawls ACL information attached to a document (user and group information) from your GitHub (Cloud) instance. If you choose to activate ACL crawling, the information can be used to filter chat responses to your end user's document access level.

The user IDs are mapped as follows:

  • _user_id – User IDs exist in GitHub (Cloud) on files where there are set access permissions. They are mapped from the user emails as the IDs in GitHub (Cloud) if the email is public in a GitHub (Cloud) profile. If the email in a GitHub (Cloud) profile is not public, they are mapped from the username as the IDs.

For more information, see:

隐私网站条款Cookie 首选项
© 2025, Amazon Web Services, Inc. 或其附属公司。保留所有权利。