Skip to main content

Approvals

One page, two hats. Requesters track, cancel, and execute their approval requests for gated certificate operations; admins and owners review the queue and approve or reject. Requests expire after 7 days if nobody acts.

Open it from the sidebar: Operations → Approvals. When you can review requests in the current project, the item shows how many are waiting.

When requests are created​

Each project has its own approval policy under Settings → Approvals (with the project selected): per operation — issue, reissue, renew, revoke, download, configuration changes (all operators by default) and distribution actions — it names which operators need approval: none, all operators, or selected users and groups (Approval workflow). Only an organization owner can change it. When a gated operation is attempted:

  • Operators the policy gates get an approval request instead of immediate execution — it lands here as pending_approval.
  • Admins and owners are never gated: the operation runs directly and an auto-executed approval record is written for the audit trail.

For the concept and design of the workflow, see Approval workflow.

Views​

An org-level admin or owner, or an admin of the currently selected project, sees a segmented switch in the header (an admin role held only in some other project does not show it — reviewing is a right in the request's own project):

  • My requests — requests you created, any status.
  • Pending reviews — requests awaiting review in the current project, with a live count (e.g. Pending reviews (3)).

A project admin whose role is limited to granted resources reviews only the requests about resources it administers (Resource grants). Non-admin users only see My requests. A second segmented control filters both views by status: All · Waiting for review · Approved · Rejected · Executed · Failed · Expired · Cancelled.

The request table​

ColumnContent
OperationColour-coded tag: issue (blue), reissue (cyan), renew (green), revoke (red), download (purple), config edit (geekblue), distribute (gold).
CertificateLink to the certificate detail (name, primary domain, or ID). A request raised in another project shows the name as plain text with a hint to switch to that project — the detail page reads the selected project.
Requested ByWho filed the request — shown in the Pending reviews view only.
StatusStatus tag; executing shows a live spinner.
RequestedRelative time (hover for the exact timestamp).
ReviewerApproved by X or Rejected by X once reviewed.
ActionsContext-dependent buttons — see below.

Expand a row for the full record: certificate, domain, operation, requester, the rejection reason (if rejected), and the execution error (if execution failed).

Statuses​

StatusMeaning
pending_approvalWaiting for a reviewer. Expires 7 days after creation.
approvedGreen-lit — the requester (or an admin) can now execute it.
rejectedDeclined by a reviewer; the reason shows in the expanded row.
executingExecution in progress.
executedDone — a View Job button links to the resulting job.
execution_failedApproved and executed, but the operation errored.
expiredNobody acted within 7 days. File a new request.
cancelledWithdrawn by the requester (or an admin).

As a requester​

  1. Trigger a gated operation from the certificate pages — you'll be told an approval request was created.
  2. Track it under My requests; you'll also be notified when it's reviewed (if notification rules are set up).
  3. While pending_approval or approved, you can Cancel it (confirmation dialog).
  4. Once approved, click Execute and confirm. Execution enqueues the operation as a job. For download requests the file is saved right away in the format you asked for, through a single-use download token; a PFX or JKS comes with a generated password, shown once — save it then.
  5. After executed, View Job jumps to the job detail with the run's logs.
  6. If it lands in execution_failed, hover Error for the message. A Retry button appears only for transient error classes (JOB_QUEUE_ERROR, CA_ERROR, STATUS_CONFLICT) — anything else needs a fresh request after fixing the cause.

Execute and retry are allowed for the original requester or a project admin.

As an approver​

  1. Switch to Pending reviews — its count (and the sidebar badge) is the number of requests waiting for a decision, whatever status filter the list shows.
  2. Expand a row to inspect the certificate, domain, operation, and requester. A configuration or distribution request names what it touches — a distribution as certificate → module (a rollback adds the version) — and lists every referenced module, target, credential or library by name. For an update, a table shows each changed field with its current and proposed value; the full proposed content (empty and unchanged fields left out) is one click away.
  3. Click Approve — the request flips to approved and the requester is notified. Execution is not automatic: the requester, or a project admin from this view, clicks Execute.
  4. Or click Reject — a dialog asks for an optional reason, which the requester sees in the expanded row.

Rules enforced by the backend:

  • Approve/Reject require the Admin project role or higher.
  • Self-approval is blocked — you cannot approve your own request, regardless of role (separation of duties).
  • Acting on an already-expired request marks it expired instead.
  • Approval actions are rate-limited (10 per minute per user).
note

Approve and Reject buttons appear only in the Pending reviews view. My requests lists your own requests, which the API refuses to self-approve, so no review buttons are shown there.

Notifications​

The workflow emits approval.requested, approval.approved, approval.rejected, approval.executed, and approval.expired events — route them to Email/Slack/Teams via notification rules. Pending requests in the project also show on the main dashboard.

See also​