Create environments and assign an approval policy to each. The environment of a certificate decides whether a signing request needs approval.
Select Create Environment and fill in the form.
| Field | Required | Description |
|---|---|---|
| Environment Name | Yes | For example Dev, Staging or Production |
| Policy Type | Yes | Certificate Owner, Quorum or No Approval |
| Status | Yes | Active or Inactive. Only active environments can be assigned to certificates. |
| Needs MFA | No | When selected, approvers must enter an emailed one-time code before they can approve or deny |
Certificate Owner: the owner of the certificate must approve or deny each signing request.
Quorum: the users set as quorum members approve the request until the required minimum number of approvals is reached.
No Approval: requests are signed without approval. Use it for automation in CI/CD pipelines and for test environments.
Note: Only users with the System Admin or Project Manager role can approve under the Certificate Owner and Quorum policies. An environment that shows No Policy Setup behaves as No Approval.
For recommended environments and how approvals affect pipelines, see Designing signing policies.
Right-click an environment:
View Details shows the environment’s name, status, creator, creation date, MFA setting and policy type.
Edit changes the environment’s settings.
Tip: When you create a certificate, you can choose only an active environment. To move a certificate to another environment later, use Edit Environment in Keys and Certificates.