Current validated local example
- tenantId = demo
- personId = person-1
- packageId = developer-standard
- packageVersion = 1.0.0
Demo
Show the product by proving the path.
The supported demo story is JIT privileged access. It shows how PF keeps request submission, policy evaluation, approval-aware planning, execution, verification, and evidence aligned.
Current scope: approval-aware supported flows, explainable evidence, and reconstructable request-to-evidence reads. This page points toward a PF Console demo experience; it does not imply a full product console exists today.
Expected end state
- requestStatus = COMPLETED
- planStatus = COMPLETED
- both execution steps are COMPLETED
- provision step dispatchStatus = SUCCEEDED
What the demo proves
- Request enters the supported runtime path
- PolicyOutcome is visible and explainable
- Awaiting Approval blocks planning until approval is satisfied
- Execution runs through access grant, verification, and evidence reads
What the demo does not imply
- No generalized workflow authoring
- No broad checkpoint enforcement claims
- No full SaaS product surface
- No replacement for policy engines or IAM systems
Interactive request path
Click through the validated supported path step by step.
This demo is fixture-based and aligned to the current supported scope. It is designed for reliable walkthroughs, recordings, and lightweight public evaluation.
Progress summary
Request path ready to walk through
Use Next Step for a guided walkthrough or click any unlocked step to revisit it.
Most systems tell you what happened. PolicyFabric tells you why.
That statement fits the demo because the explainability layer is real: policy-evidence and execution reads expose the governed path directly.
Console CTA
Next step: PF Console demo experience.
Use a PF Console demo experience to show the supported JIT privileged-access flow, inspect policy evidence and plan state, and walk through the final completed outcome without relying on a marketing-only story.