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

Governance / organization + platform administration

Configure the carrier organization in context, then review the separate Durandisse One platform controls that govern capability, health, support, and tenant boundaries.

ELOHM Command Signal

Decision ownership visible

ELOHM keeps role, approval, notification, and audit context explicit around consequential operating actions.

Review guardrails

Administration / two distinct contexts

Organization administration is not platform administration.

A carrier Administrator manages the selected organization. A Platform Administrator manages Durandisse One internal tenant, entitlement, health, support, security, audit, and AI governance surfaces only.

Session-only · no production authorization
RoleVisible / allowedBoundary
AdministratorUsers, roles, permissions, policies, DIAL, ELOHM scopesSelected org only
Organization OwnerReview consequential org approvalsConfigured policy
Platform AdministratorCustomer orgs, plans, health, support, governancePlatform only
Platform Administrator + org contextCarrier records after explicit selectionNo implicit entry

Assign organization permission

Requires permission-assignment · approval owner: Administrator action is audited

Open platform tenant controls

Requires platform-admin

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

Organization administration

Your carrier context is the operating boundary.

Organization Administration belongs to the trucking company: profile, users, roles, fleet, policies, integrations, DIAL settings, ELOHM permissions, notifications, and plan information. Values here are configuration, not fixed D-ONE behavior.

Organization users

12

Current organization only

Drivers / trucks

18 / 24

Current organization only

DIAL policy

Configured

Current organization only

Notification items

4

Current organization only

ELOHM scope

Role-bound

Current organization only

Tenant-scoped operating snapshot

The data changes with the organization.

Drivers · trucks · lanes · customers / brokers

Sample drivers

Marcus Reed · Priya Shah · Alicia Grant

Sample lanes

Newark → Atlanta · Columbus → Dallas

Customers / brokers

Oakline Foods · Pine Ridge Retail

Operating scale

11 lanes · 36 relationships

Carrier configuration

Organization profile + access

Editable reference

Company identity

Durandisse International Transport

Legal name, operating name, authority, terminals, and service regions belong to this organization.

Subscription / plan

Enterprise Operations

Plan context is visible to the organization; platform entitlements are managed separately below.

Notification preferences

Priority alerts · in-app center · owner assignment

Delivery preferences are organization configuration, not a second notification system.

RolePermission scopeBoundary
Operations adminLoads · Dispatch · DIAL approvalsFull organization scope
Dispatch leadFreight Decisioning · Dispatch · CommunicationsOperational scope
Fleet managerDrivers · Trucks · Maintenance · HOSFleet scope
Finance reviewerInsights · Settlements · Broker historyFinancial scope

Organization administration / identity + access

Production controls, honestly staged.

These controls extend the existing organization, role, permission, and tenant context. The showcase has no authentication, no identity provider, no credentials, and no persistent security state.

Designed / session-only

MFA

Designed

Production policy supports required for administrators, optional or required by role, and per-organization enforcement. Showcase state: no MFA challenge or enrollment is active.

SSO / SAML / OIDC

Designed

An organization associates verified domains, selects a provisioning source, and configures a provider connection. No provider is connected in the showcase.

Session management

Simulated

Production design includes lifetime, idle timeout, concurrent-session limits, device/location context, and single/all-session revocation. Showcase sessions are illustrative and session-only.

API credentials

Designed

Organization-scoped credentials have existence, scope, age, last-used, rotation, and revoked states. Key values are never displayed after creation; no value exists here.

Service accounts

Designed

Non-human actors receive their own scopes, named owner, and audit identity, distinct from human users. No service account can exceed the serving user context.

Provisioning lifecycle

Designed

Invite, assign role, change role, suspend, and deprovision are defined against canonical users and roles. Deprovisioning removes access at the next authorization check and ends active sessions in production design.

Policy design

MFA enforcement options

Administrators

Required in production

Role policy

Optional / required by role

Organization policy

Carrier-level override

Showcase state: MFA is not enrolled or enforced here. No challenge is performed.

Organization connection concept

SSO / SAML / OIDC

Domain association
Verified domain required
Provisioning source
IdP or D-ONE invite
Connection
Not connected

An administrator would configure metadata, claims, domain ownership, role mapping, and deprovisioning behavior. No provider details are collected in this showcase.

Session management

Devices and sessions are visible by design.

Revocation simulated

Session lifetime

8 hours

Production policy concept

Idle timeout

30 minutes

Illustrative default

Concurrent sessions

5 maximum

Policy to be enforced server-side

Illustrative organization session list
DeviceLocationLast activityStateAction
Chrome · macOSAtlanta, GA · illustrativeNow · session contextActive
Safari · iPhoneNashville, TN · illustrativeToday · 07:42Active

No session is revoked in the showcase.

Organization-scoped credentials

API credentials + service accounts

D-ONE primary integration key

Existence: configured · Scope: loads.read, documents.read · Age: 42 days · Last used: never · Status: revoked

No value shown

ELOHM advisory service account

Owner: Platform Governance · Scope: permission-filtered reads · Audit identity: `service:elohm-advisory`

Designed

Design rule: key values are never displayed after creation. Rotate or revoke is an auditable workflow; this preview has no key value and no working rotation.

Canonical user + role lifecycle

Provisioning and deprovisioning

1Invite user
2Assign existing role
3Change role
4Suspend access
5Deprovision user
6Revoke all sessions

Production behavior: a deprovisioned user loses organization records, actions, credentials, and active sessions at the next authorization check. The showcase only presents this design; it does not provision anyone.

Organization isolation / canonical foundation

Every record carries its organization.

The existing `canonicalData.ts` organization-scoped accessors, organization IDs on canonical records, tenant-scoped session keys, and explicit role/context switcher define the intended boundary. Cross-tenant reads are prohibited, and a Platform Administrator must select explicit organization context before viewing carrier records.

01 · Record scope

Organization ID on canonical record

02 · Read guard

Cross-tenant reads denied by design

03 · Context

Explicit organization selection required

Existing action / permission matrix

Least privilege stays explicit.

Grant model

Role permissions are explicit grants inside the existing `roleData.ts` model.

Default

Deny by default; approvals remain separate from visibility.

Explanation

Denied actions preserve the existing “Why can’t I do this?” pattern.

No new permission system is introduced here. The role switcher remains session-only and continues to demonstrate the existing matrix.

Organization policy / retention

Set retention by data category.

Designed · not enforced

The organization Administrator configures these illustrative periods. Archive or deletion eligibility still checks operational close, legal hold, and compliance requirements; no records are archived or deleted in the showcase.

Organization retention policy controls
Data categoryIllustrative periodArchival / deletion ruleCompliance hold
Operational recordsIllustrative: 7 years after closeArchive eligible after operational closeRetain canonical lifecycle and ownership history required by policy
DocumentsIllustrative: 7 years after closeArchive or delete by document class and legal holdRetain proof-of-delivery and required evidence for the configured compliance period
CommunicationsIllustrative: 2 yearsConfigure channel and audience retention separatelyRetain business communications when required by policy or hold
Audit eventsIllustrative: 7 yearsAppend-only retention; deletion is not an operator actionRetain the event chain for governance and required review windows
Financial recordsIllustrative: 7 years after closeArchive only after close and configured hold checksRetain records required for financial and tax review

Configuration only: final periods are organization policy choices, not legal advice or a claim of compliance.

Platform administration / identity, governance + security

Oversight without implicit carrier access.

Platform governance reviews the architecture, tenant boundaries, audit design, retention policy, and AI guardrails. It does not inherit organization records until an explicit context is selected.

No production controls connected

Immutable events / existing audit concept extended

Security audit trail design.

Session-only showcase

Each event records actor (human or service account), organization, role, action, target canonical record, result, approval requirement, source, and timestamp. Production requires append-only, tamper-evident storage; immutability is not implemented here.

Allowed
Named approval and canonical target remain visible.

Denied
Cross-tenant and permission failures are retained as events.

Append-only target
Production storage still remains to be built.

Showing 9 of 9 events.

Filterable security audit events
Actor / roleOrganizationActionCanonical targetResultApprovalSourceTimestamp
A. MorganHuman user · read-onlyABCCross-organization read attemptload:DL-2051 · DITDeniedNo approval path · explicit organization context requiredUIToday · 09:14
Priya ShahHuman user · finance-managerDITApproved allocation proposalmoney-pod:POD-DIT-03AllowedFinance threshold owner confirmedUIToday · 09:06
Marcus ReedHuman user · dispatcherDITWorkflow activation requestworkflow:dit-load-readyPendingExecutive approval requiredUIToday · 08:58
Jordan DavisHuman user · administratorDITException assignmentexception:EX-1042AllowedAssigned owner role recordedUIToday · 08:51
Jordan DavisHuman user · administratorDITAPI key rotation requestedcredential:dit-primaryPendingProduction approval and secure issuance requiredUIToday · 08:47
Jordan DavisHuman user · administratorDITSession revocation requestedsession:illustrative-device-02AllowedSimulated action · no live session revokedUIToday · 08:46
ELOHMService account · service-accountDITRecommendation visibilityexception:EX-1042VisibleRead permitted by serving user context; no action takenELOHMToday · 08:45
D-ONE decision contextService account · service-accountDITDIAL recommendation recordedload:DL-2051VisibleExisting session-only audit entry preservedautomationAug 18 · 09:12
Sam OrtegaHuman user · finance-managerDITSettlement approved / posted in showcase statesettlement:SET-2047AllowedExisting session-only audit entry preserved; no funds movedUIAug 22 · 14:18

Data retention + governance

Retention is policy, not enforcement yet.

Organization administrators configure retention by data category. Archival/deletion eligibility is checked against close state, legal hold, and compliance requirements. This showcase does not enforce, archive, or delete anything.

Designed retention controls by data category
CategoryPolicy conceptCompliance retention
Operational recordsArchive eligible after operational closeRetain canonical lifecycle and ownership history required by policy
DocumentsArchive or delete by document class and legal holdRetain proof-of-delivery and required evidence for the configured compliance period
CommunicationsConfigure channel and audience retention separatelyRetain business communications when required by policy or hold
Audit eventsAppend-only retention; deletion is not an operator actionRetain the event chain for governance and required review windows
Financial recordsArchive only after close and configured hold checksRetain records required for financial and tax review
Designed · not enforced in showcase

DIAL / organization configuration

Policy decides the recommendation.

ELOHM → DIAL → decision

DIAL evaluates each organization’s own policies and operating situation. DIT’s illustrative $3.50 per total mile and 500–600 miles/day range belong to DIT only. ABC Transport demonstrates a margin-based option; it never receives DIT’s settings.

Decision model

Total-mile economics

Minimum RPM

$3.50 / total mile

Minimum gross

$3,200

Required margin

28%

Max deadhead

75 mi

Operating range

500–600 mi / day

Trailer type

Dry van + reefer

Driver availability

Available within 2 hours of pickup

HOS constraints

Appointment fit + legal drive time

Home-time requirements

Respect 7-day home-time preference

Broker credit threshold

≥ 85

Days to pay

≤ 30 days

Fuel assumptions

$3.82 / gal · 7.2 MPG

Risk tolerance

Medium; critical risk blocks

Approval requirements

Human approval for rate below floor or medium+ risk

Negotiation thresholds

Counter below target; reject below minimum

Preferred lanes / markets

Southeast and Midwest reload markets

Restricted lanes

Dead markets under 45% reload

Decision states

ACCEPT · NEGOTIATE · REVIEW REQUIRED · REJECT

Recommendation ranking

#1 · #2 · #3 Recommended

Execution boundary

Freight Decisioning determines what should be booked. Dispatch executes what is booked.

Durandisse One platform administration

Platform owner controls

A separate administration context for customer organizations, feature entitlements, product configuration, integration availability, platform health, support, security, audit, AI governance, tenant management, and system incidents.

Customer organizations
Subscription plans
Integration availability
Platform health + usage
Support + security
Audit + AI governance
Tenant management
System incidents

Capability catalog

Entitlements vary by organization.

No pricing defined in this showcase
CapabilityDITABC TransportXYZ Logistics
Core OperationsEnabledEnabledEnabled
FleetEnabledEnabledAvailable to provision
Safety & ComplianceEnabledAvailable to provisionEnabled
FinanceEnabledAvailable to provisionAvailable to provision
ELOHM AIEnabledAvailable to provisionAvailable to provision
DIAL Freight IntelligenceEnabledAvailable to provisionAvailable to provision
Advanced AutomationEnabledAvailable to provisionAvailable to provision
Advanced AnalyticsEnabledAvailable to provisionAvailable to provision
Enterprise IntegrationsEnabledAvailable to provisionAvailable to provision

Capability is a platform concern; whether an organization receives it is an entitlement configuration. Future capabilities are not assumed to be included for every carrier.

ELOHM permissions

Intelligence respects the operator’s access.

ELOHM operates within the currently authenticated organization and the same permission boundaries as the user. A user cannot obtain through ELOHM information they would not otherwise be permitted to access.

ELOHM

Platform intelligence layer across permitted records.

DIAL

Specialized freight-decisioning logic using this organization’s policy.

D-ONE

Commercial transportation operations platform for many carriers.