Google Drive & Microsoft 365
Connect an organisation-owned Shared Drive or SharePoint library to controlled documents. Stratal retains the document record, revision and approval workflow.
Document control →Integrations
Stratal supports configured connections for documents, identity, mapping, fleet, workforce and streetworks, alongside file exchange and API workflows. Start with the data and decision each connection needs to support.
Connected services
These are integration areas in the Stratal portal. The available provider, permissions and direction of data flow are confirmed for each installation.
Connect an organisation-owned Shared Drive or SharePoint library to controlled documents. Stratal retains the document record, revision and approval workflow.
Document control →Configure the organisation’s identity provider, verify the connection and retain Stratal’s role and permission model for application access.
Security & access →Bring configured vehicle information and sync activity into the fleet context. Vehicle records and the connection state remain visible for review.
Fleet & plant →Connect an organisation-scoped workforce account, test visibility and confirm the intended data flow before enabling the service.
Workforce →Use configured Google Maps services or built-in mapping, and connect supported streetworks providers for the applicable territory and workflow.
Network & GIS →Map and validate CSV or XLSX files for occasional imports and exports. API tokens and webhooks support agreed service-to-service workflows.
Plan deployment →Implementation
Provider setup is only one part of a useful integration. The owner, records and recovery path need to be clear to the team that runs the operation.
Choose a real job, document, employee or vehicle record. Identify which system is authoritative for each field.
Agree provider credentials, permissions, fields, direction of travel and how duplicates or invalid rows are handled.
Run a sample, check the result in both systems and agree who reviews failed transfers or expired access.
Deployment scope
Not every provider or workflow is enabled by default. Supported services, credentials, data ownership and any implementation work should be agreed during deployment. Stratal’s file-based Data Exchange is useful when a live connector is not the right fit.
Coming soon
A dedicated hub for provider connections and automated data processing. The initial focus is ABAX, Depotnet and COINS ERP, bringing available fleet, operational and enterprise records into Stratal workflows.
Bring the systems together