Support access
Support access should carry an explicit purpose, approved scope and expiry. Platform owner and employee actions need an audit trail.
Trust starts with boundaries
Understand ShipOnBoard principles for organization boundaries, role access, sensitive fields and accountable support.
Explore Interactive DemoACCESS IS A SERIES OF DECISIONSA deliberate boundary.
A deliberate boundary.
At every layer.
These are the principles that guide the product: isolate organizations, grant actions deliberately, narrow record scope and control sensitive fields.
OrganizationWhose operation?
RoleWhich actions?
ScopeWhich records?
Field permissionsWhich details?
One customer's work must not become another customer's visibility.
VISIBLE ACCOUNTABILITYAccess needs a reason.
Access needs a reason.
Actions leave a record.
Credentials
Handle credentials through protected configuration. They do not belong in shipment tables, exported files or browser storage.
Exports and documents
Check the actor, organization, permitted action and intended audience when requesting and retrieving a result.
Finance and sensitive fields
Keep balances and financial decisions within their permitted audience. Record the reason and attribution for changes.
Data portability
Usable exports and retained evidence help an organization keep control of its own operational records.
Questions deserve specific answers.
Review access, data handling and deployment requirements with us before adoption. This page explains product principles; it is not a certification or a contractual security assurance.
Discuss your requirements ↗