.svg "QFlowLogo_Full-3-1 (1)")
Open it. Edit it. Never download it.
QAction's in-app document engine, powered by OnlyOffice, opens 81 file formats directly in the browser — Word, Excel, PowerPoint, PDF, Visio diagrams and images — and lets the right person edit them in place, without a local copy, a desktop application, or a trip outside your governed repository.
Every download is a copy you stop governing
When a reviewer has to pull a file down to read it, the controlled copy stops being the only copy. Version history forks, the audit trail goes quiet, and the document now lives somewhere your retention policy cannot reach.
The copy leaves the boundary
A downloaded file sits on a laptop, in a mail attachment, or in a personal drive — outside the permissions, retention schedule and audit log that governed it a moment earlier.
Format roulette stalls the work
Legacy .wpd-era files, Apple .pages and .numbers, Visio diagrams, HWP documents. If the reviewer's desktop can't open it, the approval waits on a software request.
Context switching breaks the trail
Reading in one application and acting in another means the decision and the evidence behind it are recorded in two different places — if they're recorded at all.
OnlyOffice, running inside QAction
What OnlyOffice is
OnlyOffice is a document engine that renders and edits Office, OpenDocument, PDF and diagram files with high fidelity in a browser. QFlow embeds it directly in QAction, so the viewer is not a separate destination your users navigate to — it is the document surface of the platform they already work in.
The engine runs inside your QAction environment, so the file is never handed off to an external service or a desktop application to be read or changed.
inside the system that already governs it.
Open
A user selects a document anywhere in QAction — a case, a task, a folder, a search result.
Render in place
The file opens in the in-app viewer at full fidelity, with no download and no local application.
Permissions apply
Access is evaluated against the same QAction rules that govern the document itself.
Edit and check in
Changes are made in the browser and checked back in, so the document and its history stay in one place.
81 formats. One viewer.
Word processing, spreadsheets, presentations, PDFs, diagrams and images — including the legacy and non-Microsoft formats that usually force a download.
Word processing
28Spreadsheets
16Presentations
18PDF & documents
6Diagrams
6Images
7What "supported" means. Viewer support refers to displaying the file in QAction's in-app viewer. It does not mean every feature or editing capability of a given format is supported. The current list is maintained in the QFlow support documentation.
What users can do with a file, without leaving QAction
All 81 documented formats render in the browser at full fidelity, including legacy, OpenDocument and Apple formats.
IncludedPDF, XPS, OXPS and DjVu open in the same viewer as Office files, so reviewers use one interface for the whole case file.
IncludedMake changes to a document, spreadsheet or presentation without a desktop application and without a local copy. The edit is written back to the governed document, not to a duplicate.
IncludedOne editor at a time, by design. Checking a document out makes the intent to change it explicit and visible; checking it in closes the loop with a clean version boundary and a named owner for the change.
IncludedReviewers annotate and mark up without altering the approved text, and the markup stays attached to the record.
ConfirmOpen and fill .oform and .docxf form documents in the browser as part of an intake or approval step.
Produce a PDF or an alternative format from a source document without a desktop application.
ConfirmOne editor at a time is the point. QAction does not put several people into the same live document at once. In a governed environment, a document with an unbroken chain of single, attributable edits is easier to defend than one assembled by simultaneous authors — and the version history reads as a sequence of decisions rather than a merge.
The viewer inherits your controls. It does not create new ones.
A document surface is only useful in a regulated environment if it is bound by the same rules as the repository behind it.
Your permissions, enforced
Access is evaluated against the same QAction rules that govern the document itself. If a user cannot open a document in QAction, they cannot open it in the viewer — and there is no second access model to administer or audit.
Inside your boundary
The document server runs within your QAction environment. Files are never handed to a third-party cloud service to be rendered or edited.
Recorded in the audit trail
Viewing and editing activity is written to the document's audit history, so the record shows who opened a file, who changed it, and when.
Controlled change
Editing runs through check-out and check-in, so a document has one accountable editor at a time and every change lands on a clean version boundary.
Where in-app viewing changes the work
Approvals that don't stall
An approver opens the attachment from the task itself, reads it, and approves — instead of downloading it, opening a desktop application, and returning to the queue.
Records review at scale
A records team works through a mixed backlog of legacy and modern formats in one interface, without staging files or requesting software installs.
Inherited and legacy content
Files acquired from a prior system, another agency, or a migration open on day one, including OpenDocument, WPS, HWP and Apple formats.
Locked-down workstations
Users on managed or thin-client devices read the full range of case material through the browser, with no local application footprint to approve.
A viewer is a feature. A system of record is the point.
Plenty of products can render a document. QAction is where the document, the task it belongs to, the decision made about it, and the retention rule that governs it all live in the same place — which is why reading it in place matters at all.
See it open your files
Bring the formats your team actually deals with. We'll open them in the viewer on the call.
▼▼ DROP HUBSPOT FORM MODULE HERE ▼▼
Or delete this box and place a Form module directly beneath this section.