Keep repeatable decisions consistent
Bring the information together so it is easier to find and act on.
AURTIV / WORKFLOW RULES & APPROVALS
AURTIV Relay
Make the handoff part of the workflow. Internal rules, approvals and run history for teams using Corporate Suite.
Workflow rules & approvalsAURTIV Relay
FROM DAILY WORK TO YOUR NEXT MOVE
Give routine handoffs a rule, an owner and a history.
Coordinate internal conditions, approvals and reminders with a visible record of what ran.
STEP 01 / A SHARED WAY OF WORKING
Internal event
Keep the starting record, its owner and its next action together. Your team can work from the same context.
WORKFLOW SNAPSHOTSample data
See where work stands.
One view of the stages your team manages.
Internal event
16
Condition & branch
12
Approval or delay
8
Receipt & failure review
5
Illustrative records by stage. This is an example, not live customer data or a performance claim.
See failed runs and retry deliberately
Use structured stages, ownership and review points to keep work moving.
Retain a trace of internal workflow decisions
Use the records you already capture to plan your next action.
EXPLORE WHAT IS AVAILABLE
Less searching. More understanding.
The tools behind AURTIV Flow, grouped around the work they help you do. Availability depends on your plan, enabled modules and role.
Internal workflow control
- Typed triggers and validated conditions
- THEN/ELSE branches and dry runs
- Authenticated approvals
- Delay and timeout evaluation
- Run receipts, failure inbox, retries and explicit replay
Adapt the workspace to your business
- Typed custom fields for workspace details and permitted records
- Industry-specific starter fields that you can extend
- Reviewed CSV updates to existing custom details, up to 20 rows per batch
- CSV-assisted entry into supported business forms
- Review document details before filling supported business forms
- Cloudflare document extraction with your account AI allowance
Shared account essentials
- Private company or organization workspace
- Role-aware access and private file uploads
- Read-only Business Agent for permitted questions
- Customer-visible usage and renewal details
- Configurable seat, document, record and AI allowances
- Password login, Google sign-in and account recovery
Choose the capabilities your team needs during onboarding. Payment records do not verify online payments. External messaging, device connections and regulated or certified compliance workflows require a separately agreed scope.
Inside AURTIV Flow
Understand the system.
See how it helps.
Coordinate internal conditions, approvals and reminders with a visible record of what ran. Explore the operating flow, application architecture and access controls behind the workspace.
- STEP 01Internal eventCapture the starting information in the relevant workspace records.
- STEP 02Condition & branchCoordinate the people, resources and next actions using the enabled modules.
- STEP 03Approval or delayRecord progress and review the work within your assigned permissions.
- STEP 04Receipt & failure reviewUse permitted reports and records to review the outcome and next steps.
Keep repeatable decisions consistent
Relevant capability area: Internal workflow control. Typed triggers and validated conditions. THEN/ELSE branches and dry runs.
See failed runs and retry deliberately
Relevant capability area: Adapt the workspace to your business. Typed custom fields for workspace details and permitted records. Industry-specific starter fields that you can extend.
Retain a trace of internal workflow decisions
Coordinate internal conditions, approvals and reminders with a visible record of what ran.
How is this application structured?
The browser workspace presents the enabled AURTIV Flow modules. Requests go to application APIs on Cloudflare Workers, where the signed-in account, company scope and product permissions are checked. Structured business records are stored in D1; supported private file workflows use R2. A shared platform does not mean shared access to another company’s records.
Subscription, role and module access determine which functions a user can use. Linked Corporate Suite applications require the relevant access and supported integration; they are not automatically included in every product plan.
How are company records and user access protected?
Protected API routes apply company and role checks on the server. Session cookies use HttpOnly and SameSite restrictions, with the Secure flag on HTTPS. Write operations use origin and CSRF checks, and API responses use no-store cache controls. Administrators should assign only the access each person needs and remove accounts when access is no longer required.
These are implemented application controls, not a guarantee of security or a compliance certification. Your deployment configuration, data handling, staff practices and recovery requirements also need review.
How should we use AI and reports responsibly?
Use the product’s permitted reports and supported read-only Business Agent questions to understand company records. Available sources depend on your role and enabled features. AI outputs should be checked against the underlying records, especially before financial, legal, health or other consequential decisions.
A model’s explanation does not itself authorise a business change. Product actions and approvals remain in their supported workflows. Confirm AI processing requirements before entering sensitive information, and keep public demonstration workspaces limited to fictional data.
What should we confirm before a rollout?
Walk through your actual internal event to receipt & failure review process. Confirm the modules, roles, import requirements, data retention, supported integrations and support coverage. Test representative scenarios in a suitable workspace and agree who owns onboarding and ongoing administration.
Expected benefits depend on the quality of your records and adoption by your team. Use the existing product scope and pricing details on this page to agree the fit; specialist regulatory, accounting or clinical requirements need separate assessment.