Skip to main content

Cluster Approval Workflow

When an organization admin (non-owner) creates a cluster, the platform puts the request into an approval queue before provisioning begins. An org owner must approve or reject the request before any infrastructure is created.

Org owners bypass approval and go straight to provisioning.

Who triggers approval​

Caller's org roleBehavior
ownerProvisioning starts immediately — no approval required
adminCluster enters APPROVAL_PENDING state, approval email sent to org owners

The platform determines this automatically based on the caller's org role. Only org admins and owners can create clusters — org viewers and developers do not have cluster creation permissions.

Approval flow​

Admin submits cluster
  → Backend: org role is not owner → APPROVAL_PENDING
    → Approval email sent to all org owners
      → Owner approves or rejects (via email link or dashboard)
        → APPROVE: provisioning starts
        → REJECT:  cluster creation cancelled, requester notified

The approval email​

Org owners receive an email with two links — one to approve and one to reject — when any admin in their org submits a cluster. The links include a single-use token that authorises the decision.

Approving from the dashboard​

Org owners can approve or reject directly from the Infrastructure tab without leaving the console:

  1. A Pending Approval banner appears at the top of the Infrastructure tab listing all clusters awaiting a decision.
  2. Click Approve or Reject next to the cluster name.
  3. The cluster transitions immediately — no email link needed.

The banner is visible to all org members. Admins who submitted the request see a "waiting for owner" message; owners see the action buttons.

Clicking either link in the approval email opens a confirmation page at /notification/approval. You must be signed in as an org owner — the platform enforces this before accepting the decision.

Checking approval status​

Pending clusters appear in the Clusters tab under the Pending Approval filter with status APPROVAL_PENDING. The cluster cannot be modified until a decision is made.

astroctl infra k8s get <cluster-name>
# STATE: APPROVAL_PENDING

Timeouts​

The approval workflow has no hard timeout — the request stays pending until an owner acts. If the org has no reachable owners (e.g., email notifications not configured), contact support@astropulse.io to manually resolve a stuck approval.

Notification configuration​

Approval emails are sent via the platform notification system. If an org owner is not receiving them, check:

  1. Settings → Notifications — confirm the owner has an email channel and is subscribed to the Cluster Pipeline topic
  2. The owner's email is confirmed in their account settings

See Notification Overview for full configuration instructions.