Tenant isolation
Ordinavo keeps operational data separated by tenant across customers, locations, targets, appointments, visit reports, timeline entries, imports and webhooks.
Trust topics
Ordinavo separates tenant workspaces, customer operations, mobile execution, integrations and webhook delivery so enterprise teams can reason about data flows clearly.
Role-based visibility
Managers, tenant admins and mobile employees see different levels of customer and operational data based on their role and context.
Webhook payload control
Webhook subscriptions can control whether customer context, contact details, summary previews and billing details are included.
Customer-controlled operations
Customers can choose how Ordinavo is used for customer records, recurring visits, reports, integrations and retention policies.
Integration security
Ordinavo Connect uses API keys, scopes, idempotency, mapping warnings and signed webhook deliveries for controlled system integration.
Customer Portal
Ordinavo can provide a controlled external portal for customer contacts to view shared appointments, requests, reports, attachments and timeline activity.
Cloud or on-premise options
Ordinavo can support cloud deployment or customer-controlled infrastructure depending on operational and compliance requirements.
Responsibilities
How Ordinavo separates responsibilities
For customer records, contact persons, targets, appointments, visit reports, timeline entries and imported operational data, the tenant customer typically determines why the data is entered, which people are added and how long records should be retained.
This page provides a technical and operational overview. Contractual documents, data processing agreements and customer-specific privacy notices define the binding legal details.
Processor-oriented SaaS architecture
Ordinavo is designed to act as a processor for tenant-controlled operational data, while the tenant customer remains responsible for the lawful basis, internal policies and user instructions for that data. Ordinavo may process website, trial, account administration, platform security and support data for its own operational purposes.
Responsibility matrix
This matrix is product and trust communication, not final legal advice.
| Area | Tenant customer | Ordinavo |
|---|---|---|
| Customer records | Decides content and purpose | Provides storage and access controls |
| Contact persons | Defines lawful use | Processes according to configuration |
| Visit reports | Defines report policy | Provides workflow and permissions |
| Timeline | Uses operational history | Aggregates tenant records |
| Connect imports | Controls source data | Validates and maps through API |
| Webhooks | Chooses endpoint and payload options | Sends signed event deliveries |
| Hosting model | Chooses deployment option | Provides software or managed operation if agreed |
Customer Operations Privacy
Customer, location, contact, visit report, attachment and timeline data explained for operational teams.
Open pageWebhook Security
Payload options, HMAC signatures, delivery behavior and receiver responsibilities.
Open pageConnect Privacy
Customer-aware imports, external IDs, mapping warnings, scopes and import logs.
Open pageHosting
Cloud and customer-controlled infrastructure in the context of operational customer data.
Open pageTrust FAQ
Is Ordinavo a CRM?
Ordinavo Customer Operations is CRM Light for operational teams. It focuses on customer context for field work, recurring visits, visit reports and operational history, not sales pipelines or marketing automation.
Who controls customer and contact data?
In a tenant workspace, the tenant customer typically decides which customer and contact data is entered and how it is used. Ordinavo provides the technical platform, access controls and workflows.
Can mobile employees see all CRM data?
No. Mobile views are designed to show operationally relevant information for assigned work, while administrative CRM, integration and billing data remain role-restricted.
Are visit report summaries sent in webhooks?
Not by default. Summary previews are controlled through webhook payload options and should only be enabled when the receiving system needs them.
Does Ordinavo create invoices?
No. Billing trigger events are operational signals for external billing or ERP systems. Invoice creation, pricing, taxes and accounting rules remain outside this workflow.
Can Ordinavo run on-premise?
Ordinavo can support customer-controlled infrastructure depending on the deployment model. Infrastructure security, backups and local retention policies may be governed by the customer setup.
Review Ordinavo for your enterprise requirements
We can walk through tenant isolation, role visibility, Connect scopes, webhook payload options and deployment boundaries for your rollout.