Customer Portal
The Customer Portal is the protected operations surface for teams that need more than API access and CLI workflows. It is where enterprise users review approvals, inspect executions, manage operational settings, and coordinate governance work across engineering, platform, and compliance teams.
This public page is intentionally a teaser plus orientation page. It explains what the portal is for and why teams eventually ask for it, while the detailed setup and operating guides live in the protected docs estate.
What the Portal Adds
The Customer Portal is most valuable when AxonFlow is no longer a single-team trial and has become shared infrastructure across a larger organization.
Key portal workflows include:
- unified execution visibility for MAP and WCP activity
- approval queues for
require_approvaldecisions - policy-management workflows for platform and governance teams
- operational review of usage, incidents, and audit evidence
What Becomes Easier in the Portal
The portal changes the operating model for teams that would otherwise have to stitch together APIs, CLI workflows, dashboards, and audit lookups by hand.
Typical portal-driven workflows include:
| Workflow | Why teams care |
|---|---|
| Execution review | Engineers and operators can inspect governed workflow activity in one place |
| Approval review | Compliance and risk reviewers can handle require_approval decisions without custom tooling |
| Policy operations | Platform teams can manage governance workflows without making every change through raw APIs |
| Cross-functional visibility | Security, audit, and engineering teams can review the same operational evidence |
Typical Users
The portal is usually used by a mix of:
- platform engineers operating AxonFlow across teams
- security and compliance reviewers who need traceable approval and audit flows
- engineering leads who need execution visibility without stitching together raw APIs
Why Engineers Ask for It
Community and evaluation users can already do a lot through the Agent, SDKs, APIs, and CLI. The portal becomes attractive when teams want:
- a UI for reviewing governed executions
- an approval queue for higher-risk workflows
- protected operational workflows for platform teams
- a more approachable surface for cross-functional reviewers
In practice, this is often one of the strongest upgrade signals after a team has proven that AxonFlow works technically and starts preparing for wider rollout.
Typical Upgrade Trigger
The portal usually becomes important when the problem changes from:
- “can our engineers build with this?”
to:
- “can multiple teams operate this together with enough visibility, approval control, and governance context?”
That is why the Customer Portal is not just a nicer UI. It is part of the operational model for larger enterprise deployments.
What to Read Next
- Policy Management
- Human in the Loop
- Execution Viewer
- Execution Operations Playbook
- Enterprise Rollout Checklist
- Community vs Evaluation vs Enterprise
Already a licensed customer? The full portal documentation is in the protected docs, where the setup, navigation, and operations guidance can stay specific without exposing enterprise-only detail in the public site.
