Contact sales

Security and access controls

Ordinon protects the order workflow with workspace authorization, controlled file access and explicit approval.

Visible controls.
Explicit decisions.

Security controls

Workspace authorization

Access is checked for the customer workspace on order records, source files, approvals and exports. A link to a file does not replace that check.

Scope: account and record access

Controlled file handling

Uploads are checked against supported types and size limits before entering the workflow. Original files remain available to authorized reviewers.

Scope: incoming documents

Explicit approval

Required exceptions must be resolved before approval. Approval records the saved version and the person who approved it.

Scope: order decisions

Consistent exports

CSV downloads use the values fixed at approval. Spreadsheet values that could be interpreted as formulas are escaped on export.

Scope: outgoing order data

Your team’s responsibilities

Ordinon provides the review workflow. Your organization decides who can access it, which reference records are authoritative and when an order is ready to approve.

  • Give access only to authorized people and remove it when roles change.
  • Keep customer, product and delivery references accurate.
  • Resolve the meaning of an exception before approving the order.
  • Protect ERP credentials and agree the required access scope.

Security review before implementation

A security review should cover the workflow you intend to operate: document sensitivity, authorized users, extraction providers, ERP connectivity and retention. We use those requirements to define the implementation and agreement.

This page describes product controls. It does not assert an independent certification, audit opinion or contractual service level. Ask us for the information needed by your procurement or security team.

Data handlingFollow the document and its derived records.PrivacyInformation used by the site and service.

Report a security issue

Include the affected page or feature, what you observed, and steps to reproduce it. Start with a description; do not send credentials, customer documents or other sensitive data.

[email protected]

A useful initial report

  1. A short description of the issue.
  2. The affected feature and approximate time.
  3. Reproduction steps using non-sensitive examples.
  4. A contact address for follow-up.