PAS Studio · Interactive demo
From idea to operation — forms, documents, workflow, approvals, service levels, work queues, integrations, oversight and audit.
Demonstration: every name, institution, number and record shown is fictional and does not represent real customers or systems.
Each step shows how PAS Studio handles it, who is involved and why it matters — with a label for what is available today.
Scenario: Corporate account opening with KYC due diligence — A demo bank (fictional)
“Available”: in the UAT-approved commercial release. “Partly available”: available with a stated limit. “In development”: being built, not yet released. “Planned”: on the roadmap, not built yet.
The example and terms change — the platform stays the same.
01 · The problem
A request that crosses several departments: it arrives by email, is tracked in spreadsheets, its documents travel as attachments — and nobody knows where it stopped.
Relevant to:
Six controls that work inside the service itself, not on top of it.
Signed, time-limited sessions; permissions are read from PAS Studio's own records — never from the identity token.
Sign-in with Microsoft Entra ID: in development.
Administrator, editor and viewer roles, plus field permissions by role and stage, enforced on the server.
Each institution's data is scoped to it in every query, and any cross-institution request is refused — proven by tests.
Human decisions: a duplicate approval is always refused; self-approval and other segregation rules are switched on per policy.
Request and task status changes are recorded in the same transaction that makes them.
Not yet recorded: the workflow engine's internal steps and draft edits.
Publishing only from “Ready for production” after a passing acceptance test of this version; a published version is never edited.
Each release exports a secret-free service package protected by a checksum; importing it into the institution's environment is planned.
We claim no certification or regulatory approval for PAS Studio.
Eighteen capabilities, each answering four questions: what is it, why does it matter, who uses it, and what does it connect to?
“Available”: in the UAT-approved commercial release. “Partly available”: available with a stated limit. “In development”: being built, not yet released. “Planned”: on the roadmap, not built yet.
Writing the idea as one sentence to pre-fill the questions: in development, rule-based — not artificial intelligence.
Validation rules apply to documents the platform produces; applying them to applicant submissions is planned. Attaching the form to a service is done through the platform's API today, not on screen.
Documents are accepted automatically when they pass the format and size checks, or reviewed by an administrator through the API when manual review is set. Upload and review screens, and linking documents to stages on screen: planned.
Timer, integration and sub-workflow steps: in development.
The organization model (units and positions, the requester's manager, acting cover, delegation, committees): in development.
Applying the deadline to live requests and tasks (none is timed today), pausing while the applicant is asked for information, a public-holiday calendar and tiered escalation: planned.
Rule sets are evaluated today in the acceptance-test simulation and on demand, not during live requests. Decision tables: planned.
The system must offer an HTTPS API at a public address (private-network addresses are blocked by design). The integration step inside the journey: in development. Other connector types (OpenAPI, SOAP, webhooks, SFTP, email): planned.
Applicants sign in with a one-time code, but the released version has no email or SMS delivery: codes cannot reach applicants in a live deployment until delivery is added. The portal is Arabic-only today. Messages, applicant notifications and on-screen document upload: planned. Plain-language statuses: in development.
Not available yet: showing the applicant's answers and uploaded documents on the task and request screens.
Aggregated indicators (unassigned work, team load, average handling time, bottlenecks): planned.
A second person's approval to publish a service: planned.
Not yet recorded: the workflow engine's internal steps, edits to a draft service, and an applicant's saved draft. The actor's platform role is recorded only for request start and task completion. Export and tamper-evident chaining: planned.
Separate development, test and production environments, and version comparison: planned.
The applicant portal is Arabic-only today.
Sign-in with Microsoft Entra ID: in development. Files are not scanned for malware in the released version — each upload is recorded as “not scanned”; a scanner can be added at deployment through a code-level hook.
Pick one complex process. We will show you how it becomes a governed digital service.
Before PAS Studio · Corporate account opening with KYC due diligence