Ironline protects service-business records through workspace scope, role-aware access, private customer paths, evidence-based financial state, visible support access, controlled provider integrations, and fail-closed operating boundaries.
Workspace-separated
Each business owns its operating records inside a workspace with membership and role checks.
Evidence-aware
Financial, provider, migration, and automation state is qualified by evidence and reconciliation.
Failure-visible
Uncertain or unsupported outcomes remain visible, paused, rejected, or reviewable instead of being silently called successful.
Current control model
Access
Customer and operating records are scoped to a workspace. Owners, managers, office/dispatch staff, technicians, and read-only users receive different permissions while staff, sales, and platform administration remain separate surfaces.
Customer and files
Private attachments use authorized application flows. Customer request, estimate, invoice, and Customer Center links use opaque routes, remain outside the public search index, and do not expose the internal workspace.
Financial integrity
A redirect or button click is not enough to mark an invoice paid. Provider-backed payments, refunds, and disputes retain provider identifiers and reconciliation state; authorized manual records remain visibly manual.
Accountability
Important actions preserve responsibility and history. Deeper Ironline support access is deliberate, purpose-limited, time-limited, and visible to the customer workspace rather than treated as routine browsing access.
Field continuity
Supported field actions queue on the device and replay in capture order after a secure connection returns. Ironline does not present that queue as a complete offline copy of the workspace.
Providers
Accounting, payments, communications, maps, calendars, and external workflows remain authorization-, configuration-, and proof-dependent. A saved connection alone is not treated as successful production operation.
Automation
Rules can be validated and dry-run before activation. Failures can pause, retry, reconcile, and remain visible to managers instead of silently creating uncertain operating state.
Platform separation
Provider events, subscription state, migration commits, support access, role changes, and outbound delivery use explicit validation paths. Unsupported or unverified state is rejected or held for review rather than assumed successful.
Buyer review areas
A Growth or Scale review should focus on the buyer’s actual access, field, financial, provider, migration, support, and policy requirements. Ironline will show the current behavior and identify anything that still needs a separate commitment or is not currently supported.
Authentication path, workspace membership, role permissions, invitation handling, support access, and administrative separation.
Customer links, private files, workspace ownership, exports, and the data a customer-facing route can access.
Payment evidence, refunds, disputes, accounting direction, provider authorization, webhook receipts, and reconciliation.
Supported queued actions, device scope, synchronization order, conflict handling, and workflows that still require a live connection.
Dry-run controls, supported commit scope, duplicate handling, retries, activity evidence, rule activation, pauses, and recovery.
Terms, privacy, cancellation, support channels, escalation expectations, and the current product or provider boundaries relevant to the buyer.
Published and reviewable
Not currently claimed
Direct accountability
A small vendor should not hide behind a sales maze. Describe the sensitive workflow, decision, provider, access pattern, or support expectation and ask for the exact current behavior before adoption.
Report a concern or review a requirement
Use the secure Support route for account-specific details. Do not place passwords, access tokens, payment credentials, or sensitive customer files in a public message.
Contact supportBring the access, field, financial, migration, provider, or support boundary that matters most. The review will show the current product behavior and name any gap directly.