选择您的 Cookie 首选项

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

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

Jira approvals and access controls

聚焦模式
Jira approvals and access controls - AWS Service Management Connector
此页面尚未翻译为您的语言。 请求翻译

The following sections describe approvals and access controls that are available in Jira.

Approvals

The approval agent has access to a screen with the options to approve or reject the product request. For a rejection, the agent can add a comment explaining the rejection of the request. The requester is able to see the status of the request, such as Waiting for Approval, Scheduled, Launching, or Available.

Changes to approver group members do not impact approvers identified for pre-existing issues, but do affect whether we permit approval. Only approver users assigned to the issue at the time of issue creation can approve the request. The approver user must still be a member of the group to issue an approval. Otherwise, we reject the request.

As with Service Catalog, all post-provision actions, including termination, receive pre-approval for the user or group approved to provision it.

Access controls

You can set access controls on portfolios, as described earlier in this guide. Those access controls are in addition to the per-project enablement: users must have access to an AWS Connector-enabled project and belong to the groups enabled for a portfolio to provision products in that portfolio.

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