VNCworkflow
The suite template-and-approval engine: model a route of stations once, then run every request through it with role-based routing, parallel and conditional steps, delegation and an immutable audit trail.
Templates and approvals
Templates fix the route once. Stations can run in sequence, in parallel or only when a condition over the request form holds, routed by organisational unit and role or pinned to a person, with delegation when someone is away. Attachments live on the request, and every request carries a human reference and a tamper-evident audit trail.
- ✓Reusable templates with an ordered list of stations
- ✓Four station types: review, statement, approval and release
- ✓Role-based routing by unit and role, or a pinned person
- ✓Parallel and conditional stations, with cascade skipping
- ✓Delegation with a scope and an optional date window
- ✓An immutable, hash-chained audit trail, with JSON and PDF export
Template editor
Define the route of stations, station types, conditions, dependencies and form fields, and grant authoring rights to domain experts.
Role-based routing
Assign a station to an organisational unit and role, so any holder may act, or pin it to a single person.
Parallel and conditional stations
A station can wait for named earlier stations, and run only when a rule over the request form fields holds, with cascade skipping.
Create wizard and drafts
A step-by-step wizard for type, text and attachments, route and summary. Save as a draft then submit; each request gets the reference V-YYYY-NNN.
Approvals with accountability
Per-request permissions, by default the applicant, the involved stations and admins, mirrored to the suite directory access grants. Involved units see the request.
Delegation
Let another person act on your stations, scoped to all tasks, approvals only or statements only, with an optional date window.
Audit trail
An append-only, hash-chained log with a verify check and JSON or PDF export. Content is immutable after submit.
Cross-app requests
Start a request from a VNCfiles file, a VNCtask task or a VNCchannels topic, and follow it back with a status chip.
Model the route once
The process is a reusable template, not per-request emailing.
Decisions you can prove
A tamper-evident, hash-chained audit trail and immutability after submit.
Access that follows your org
Rights are the suite directory grants, and involved units see the request.
Approvals where the work lives
Start and follow a request from files, tasks and channels.
Templates: stations and station types · Routing: role-based, parallel and conditional, with delegation · Audit: hash-chained, immutable after submit, JSON and PDF export · Requests: reference V-YYYY-NNN
Integrated across the suite · single sign-on via VNCdirectory
VNCdirectory
Identity, units, roles and access grants come from the suite directory, which stays authoritative.
VNCfiles
Start a request from a file and follow it back; the source item carries a Workflow chip with the reference and state.
VNCtask
Start a request from a task and follow it back.
VNCchannels
Start a request from a topic and follow it back.
VNCmail
In-app notifications, with outbound mail and chat delivery.