Optional module
Ration Workflow
Tasks, approvals and structured processes that live beside the chat and mail that created them, rather than in a separate tool somebody has to remember to update.
Work that starts in a conversation should stay attached to it
Most work begins as a message. Someone asks for an approval in chat, a request arrives by mail, a decision gets made in a meeting. The work then gets retyped into a tracker that immediately starts drifting from the conversation that produced it.
Ration Workflow runs inside the same workspace as Message, Chat and Meet, so a request becomes a tracked item without leaving the context that explains it.
- Task management and tracking
- Approval workflows
- Process automation
- Deadline reminders
- Progress reporting
Approvals with a record
Approval is the process most often handled by mail and least well served by it. Who approved what, on which version, and when, tends to be reconstructable only by searching threads afterwards.
Structured approval chains make that explicit — the request, the approver, the decision and the timestamp are the record rather than something inferred from a mailbox.
Governed by the same policy as everything else
Workflow is not a bolt-on with its own permission model. The same policy engine that decides who can read a mailbox or join a meeting decides who can raise a request, approve it or see its history.
That means a leaver is out of the approval chain the moment their access is revoked, and grants and shares within workflow are written to the same audit trail as the rest of the platform.
Add it when you need it
Workflow is an optional module alongside Ration Storage and Ration Communication. Organisations typically start with the core workspace and add workflow once the informal version of a process has become load-bearing enough to be worth formalising.
Questions we get asked
Is Workflow included in the core platform?
Workflow is an optional module. It integrates with Ration Core and can be added as the organisation needs it, alongside Ration Storage and Ration Communication.
Can approvals be tied to forms?
Yes. Forms collect the structured request and Workflow routes it through the approval chain, so submission and approval are one process rather than two disconnected tools.
Who can see a workflow item?
Access is decided by the same policy engine that governs every other module, set from one admin console, with revocation taking effect immediately.
Explore further
Modules
Forms
Data collection that lands somewhere useful — governed by the same directory and policy as the rest of the workspace, and able to start a process rather than just fill a sheet.
Platform
Collaboration platform
Mail, chat, meetings, calendar, contacts, tasks, notes and forms in a single workspace — with one policy engine deciding access across all of them, and a choice of where the whole thing runs.
Platform
Enterprise collaboration
One workspace, one admin console and one policy engine across departments that have each been buying their own tools for years.
Platform
Corporate messaging
Internal communication that stays in one place, under one directory and one set of rules — instead of scattering across a chat tool, a mail provider and whichever consumer app filled the gaps.
Not sure where Ration fits?
We will scope it with you before you commit to anything.