OrganizationDurandisse International Transport

Session-only perspective. Each organization has its own isolated operating environment; controlled cross-organization sharing is not enabled.

Illustrative data · no persistent tenant changes
RoleExecutive / CEO

Role switching is session-only. Organization roles remain inside the selected organization. Platform Administrator is distinct and never receives carrier records implicitly.

OrganizationDurandisse International Transport
BoundaryOrganization-scoped

Network health and outcome review with policy-bounded approvals.

Session-only role context
412

Role-aware operation · session context

Executive / CEO · Durandisse International Transport

Full navigation remains available. Role controls dashboard composition, sensitive fields, exception scope, and action authority inside the selected organization.

PermittedApproval requiredDenied with reasonRead-only
Workspace reference

Intelligence / governed workflow builder

Build organization-scoped workflows across the operating network, keep consequential work human-approved, and preserve one audit trail around every canonical record.

ELOHM Command Signal

Automation guardrails active

ELOHM can prepare work while D-ONE keeps approvals, dispatch holds, and money movement with named owners.

Review automations

Automation Engine / role boundary

Everyone can inspect. Editing and activation stay owned.

Workflow editing follows organization permissions. Consequential dispatch, finance, compliance, external communication, policy, and activation changes keep a human approval gate.

Session-only · no production authorization
RoleVisible / allowedBoundary
Read-only ViewerInspect workflows + run historyRead only
Dispatcher / Fleet / Maintenance / Compliance / FinanceConfigure permitted domainPermission-scoped
AdministratorManage org workflow permissions + ownersOrganization-scoped
Owner / ExecutiveApprove activation or consequential changeApproval required
Platform AdministratorPlatform availability / entitlements onlyNo carrier workflow records

Save workflow draft

Requires domain workflow permission

Request activation

Requires activation approval ownership · approval owner: Organization Owner / configured approver

Transparency: denied actions explain the required role / permission and, when relevant, the approval owner. Full navigation remains visible to every role.

Phase D · buildable control planePRODUCT PREVIEW · ILLUSTRATIVE DATA

Build the rule.
Own the outcome.

D-ONE is the operating environment and system of record. The Automation Engine executes explicitly configured workflows across the same load, driver, equipment, document, exception, and finance records already in the workspace.

Current organization · Durandisse International Transport

Templates are editable copies inside this organization. Nothing activates until validation and an authorized human review.

Mode: SIMULATIONNo live execution
ACTIVEWorkflow WF-DIT-001

Load Accepted → Dispatch Ready

Two loads are eligible for the next dispatch review.

Active version

v2

Edited draft

v3 · unsaved

Owner

Marcus Reed · Dispatch lead

Execution mode

HUMAN-APPROVED

Buildable canvas

Select a node to configure it in context. Stages keep the path readable.

01 · Triggerstarts the run
02 · Logicconditions + branches
03 · Actionwrites or prepares
04 · Controlguard + audit

Source → destination controls

Connect the path without dragging.

Keyboard-accessible alternative
Draft changes stay in this session.

Canonical workflow record

The configuration travels with the audit.

Workflow ID + tenant

Required on every organization record.

Trigger + conditions

Required on every organization record.

Actions + affected records

Required on every organization record.

Guardrails + approval

Required on every organization record.

Owners + permissions

Required on every organization record.

Run + step history

Required on every organization record.

Inputs + outputs + skips

Required on every organization record.

Version + timestamps

Required on every organization record.

Money Pod allocation rules remain a Finance-specific capability. A workflow can start or hold an allocation run with approval; it never replaces the Finance allocation engine or moves money automatically.

Contextual hooks

One engine across the workspace.