Security and control
Autonomy where it helps. Approval where it matters.
This page describes Dryvn’s security posture in plain words. Which controls apply to a given workflow depends on the implementation; review them before relying on unattended execution.
The controls
What the system is designed to do, and not do.
- Authority is explicitDryvn acts only inside the permissions configured for your business. Anything outside them is proposed, not performed.
- Approval where it mattersMoney leaving, contracts, and anything irreversible are built as approval steps, not autonomous actions.
- Separation between businessesEach business's records, documents and context are isolated. One customer's data is never operating context for another.
- AuditabilityActions taken by Dryvn are recorded against the customer, job or document they affected, so you can see who or what did it.
- Connected systemsIntegrations use the access you grant and can be revoked by you at the provider at any time.
Before relying on it
Review the boundaries for the workflow.
An implementation needs clear authority for actions, named responsibility for exceptions and evidence that required steps were completed. Write down what may act without asking, what needs a named person’s yes, and what must never happen automatically, then check that the configuration matches.
Dryvn is early and we describe our posture plainly rather than claiming certifications we do not hold. Questions about a specific requirement: support@dryvn.ca, or use the contact page.