Oprill / Agent governance
Set the boundaries before the first step.
Explore how ownership, permissions and review gates can make an agent workflow easier to understand and challenge.
Product concept · Interactive website preview
Authority stays with the person.
Make authority specific.
Reading a document does not imply permission to distribute it. Define allowed sources and permitted actions separately.
Explore scope
The boundary should apply to every step, including work delegated to another agent. A handoff must not quietly expand the original authority.
The workflow may draft a summary but cannot distribute it.
Illustrative examplePut review where consequences begin.
Show the reviewer what would change, who would receive it and which evidence supports it. Broad approval without a concrete action is hard to assess.
Explore approval
If the audience changes after approval, the decision needs to be revisited. Approval is tied to a specific version and destination.
External sharing is held for a named reviewer.
Illustrative exampleKeep the reasoning inspectable.
A review record should connect the request, selected inputs, proposed result and final decision. Record useful context without duplicating sensitive material.
Explore trace
This illustration describes a governance approach. Oprill does not claim a deployed policy engine, audit service or certification.
A compact trace explains why sharing was held.
Illustrative exampleAgent governance in context
A workflow proposes sharing a project summary.
Interactive illustration with synthetic content. No AI model or company system is connected.
Draft for internal review
The synthetic summary stays within the project team. A person still reviews the draft.
Changing this selection applies no real permissions and sends no information.
Knowledge keeps its context
Different sources. Distinct responsibilities.
Original source examples for agent governance. These symbols represent information types, not connected applications.
Questions about agent governance
Does sharing a workflow share its source permissions?
It should not. Permission to use a workflow and permission to read its sources are separate boundaries.
When should approval be revisited?
When the proposed action, destination, audience or material content changes after the original review.
Understand the concept. Keep the decision.
These original examples explain a possible approach to agent governance. Oprill’s website does not run AI agents, connect to company data or carry out external actions. Your selections stay in this page and reset when you reload.