SECURITY & DATA HANDLING

Clear access.
Accountable workflows.

Understand how the showcase and demo enquiry workflow separate public information from developer-managed records.

Application access stays in the application.

Login and Sign Up open the existing OKRion workspace. The public website does not collect your application password.

  • Separate application destination
  • Existing registration and sign-in flows

Developer access to sales enquiries.

The demo inbox, recipient settings, and audit history require an authenticated developer account in the backend.

  • Server-side role checks
  • No public request-list or log endpoint

A record behind the enquiry.

Demo enquiries are stored before an email attempt. Delivery outcomes and routing changes have their own activity records.

  • Separate request and audit collections
  • Recorded delivery attempts and recipients

Public examples use sample data.

The website tour illustrates the workflow. It does not expose a live institution’s records or accept document uploads.

  • Clearly labelled sample views
  • No live institutional workspace in the tour

ASK ABOUT YOUR REQUIREMENTS

A useful security conversation
starts with specifics.

For hosting location, retention, backups, institutional access arrangements, or contractual requirements, contact OKRion to discuss your deployment. Details depend on the applicable service arrangement.