Editing rules

You can edit an existing rule to change its approval requirements as your organization’s needs evolve. Since Porto rules are keyed to operation type (not amount, address, or time), editing a rule means changing who must approve that operation type and how many approvers are required — not adjusting thresholds or conditions.

​

When to edit rules

Consider editing rules when:

• Organization grows — You hire more approvers or change roles
• Rules aren’t working — A rule is creating bottlenecks (too many required approvers) or too little oversight (too few)
• Compliance changes — New regulatory requirements necessitate a different approval structure for an operation type

​

Edit a rule

​

Common edits

​

Change approver requirements

If you add new approvers, you can adjust requirements: Before: 2 of 2 (CEO + CFO) must approve withdrawals After: 2 of 3 (CEO, CFO, or COO) Edit the rule to change the base quorum member list and count.

​

Add or remove a subquorum

Before: Withdrawal rule with base quorum only After: Withdrawal rule with base quorum + a Compliance subquorum requiring 1 approver This makes withdrawals stricter by adding a mandatory group, without touching the base quorum.

​

Make approvals faster

Before: 3 of 3 admins must approve user-management changes After: 2 of 3 admins must approve user-management changes Edit the rule to reduce from 3 to 2 required approvers.

​

Editing without disruption

To edit a rule while minimizing disruption:

1. Review who’s affected — Confirm which operation type the rule governs and who currently approves it
2. Communicate first — Let affected approvers know the requirement is changing
3. Make the edit — Update the base quorum, approver count, or subquorums
4. Audit trail — The change is recorded showing old and new configuration

​

Before/after rule changes

Document the change: Keep this record for compliance and future reference.

​

Approval of rule changes

Rule edits themselves require approval:

• Who approves: Typically the same policy that governs vault operations
• Timing: Rule changes must be approved before taking effect
• Notice: Users should be notified of upcoming rule changes

​

Rolling back edits

If an edited rule causes problems:

1. Revert to previous configuration — Some systems allow rolling back recent changes
2. Edit again — Alternatively, edit the rule back to its prior base quorum/subquorum configuration
3. Notify users — Let them know the rule has changed back
4. Document reason — Record why the change was reverted

​

Communicating rule changes

When you edit a rule, notify affected users:

1. What changed — Which operation type’s rule was modified
2. Why it changed — Explain the business reason
3. Effective date — When does the new rule take effect?
4. Impact — How will this affect approvals? Faster/slower?

​

Audit trail of edits

All rule edits are recorded:

• Who changed it — The user who made the edit
• When — The exact time and date
• What changed — Base quorum, subquorum, or approver-count diff
• Approval — Who approved the rule change

​

Rule maintenance schedule

Establish a regular maintenance schedule:

• Quarterly: Review each operation type’s rule to ensure it still aligns with business needs
• After incidents: Review rules if security issues occur
• After org changes: Update rules when team structure or approvers change

See Managing rules for comprehensive rule maintenance.