Admin: Provision a Partner
This page is for ADMIN users only — internal AgentLane staff working from /admin/*.
Find the partner
/admin/agents shows, per partner, whether their agent control plane has been provisioned, and if so how many of their configured agents are enabled (N / M enabled). A partner that hasn’t been provisioned yet shows a Provision button — this is a one-time setup step per partner, independent of any single agent request.
Check their automation status
/admin/automation lists every partner’s provisioning status (Not provisioned / provisioning… / ready / error) with their provider and a link into each one.
Open their instance detail page
/admin/automation/[partnerId] renders the Activepieces partner resource: tenancy mode, project
ID, base URL, Provision / Reprovision / Deprovision actions, and a pipeline-steps breakdown of
the most recent provisioning attempt. The Portal does not proxy the underlying workflow editor to
partners or clients.
Provision, and watch the pipeline
Click Provision. Each attempt is broken into individually-timed pipeline steps, each recording success/failure, warnings, and both an internal error (admin-only) and a client-safe error message (what the partner sees on their own side if this fails). See Workflow Engine for the Activepieces pipeline step by step.
Handle a failed attempt
If a step fails, the instance shows failed with the recorded error. Click Provision again to retry — there’s no separate “retry” action, provisioning a failed instance re-runs the same pipeline. See Provisioning failures for the specific errors this can produce and how to resolve them.
Deprovision is destructive and irreversible — it removes the partner’s Activepieces project and provisioned resources entirely. Reprovision is safer when the goal is just “start over”: it rebuilds the resources in one action rather than leaving the partner unprovisioned in between.
For the full admin route reference, see Admin Panel. For the underlying access model — what isolation each tenancy mode actually gives a partner, the endpoints behind these buttons and who may call them, and every pipeline step in order — see Activepieces Access & Isolation.