Create Policy Control
POST /policies/policy-controls
Policy Controls determine how Policy Executions are handled. The type of policy control applied is determined by the kind
field in the nested configuration
object. These are the supported kinds:
RequestApproval
: Require a specified number of approvals from a list ofUsers
.More control kinds coming soon...
User action signature required. See User Action Signing for more information.
Request headers required. See Request Headers for more information.
Authentication required. See Authentication Headers for more information.
Required Permissions
Name | Conditions |
---|---|
| Always Required |
Request body
The following fields are common to all kinds of Policy Controls:
Request body fields | Required/Optional | Description | Type |
---|---|---|---|
| Required | A name for the control | String |
| Required | A description for the control | String |
| Required | A nested object specifying details of the Policy Control | Object |
Approval Control
Use the following fields in the nested configuration
object to create a Policy Control which requires a specified number of approvals from a list of Users:
Request body fields | Required/Optional | Description | Type |
| Required | Specify: "RequestApproval" | Enumerated Type |
| Required | The user IDs of the designated approvers. See List Users to get IDs. (See Note below re: legacy authentication) | Array of Strings |
| Required | The amount of time in minutes after which the policy execution can no longer be approved. | Integer |
| Required | The number of required approvals. Must be less than or equal to the | Integer |
Note: For legacy authentication, please specify an array of email addresses in the approverUsernames
field like ["bob@example.com", "dan@example.com"]
Request Example
Response
Response example
If successful, the response contains, among other things, a status indicating whether the rule has been enabled:
Last updated