Overview

Solvren ensures that revenue-impacting changes receive appropriate oversight before implementation.

Approval workflows ensure that:

• relevant stakeholders review changes
• cross-team dependencies are addressed
• governance policies are enforced

Approval Roles

Approvals are assigned based on roles, not individuals.

Examples include:

• Engineering Lead
• Finance
• Revenue Operations
• Product

Users are mapped to these roles in the organization settings.

Approval Routing

Approval routing is determined by the system based on:

• change type
• domain
• systems involved

For example:

| Change | Approvers | |------|------| | Pricing configuration | Finance + Product | | Billing logic | Engineering + Finance | | CRM routing | RevOps |

This mapping ensures the correct teams are always involved.

Reviewer Actions

Reviewers can take several actions.

Approve

Indicates that the reviewer agrees the change is safe to proceed.

Request Changes

Indicates issues must be addressed before approval.

Reviewers may leave comments explaining their concerns.

Approval Visibility

Each change displays:

• pending approvals
• completed approvals
• reviewer comments

This allows teams to quickly understand the review status.

Approval Best Practices

Recommended practices include:

• requiring multiple reviewers for high-risk domains
• including finance for pricing or billing changes
• ensuring engineering reviews technical changes

Proper approval configuration dramatically reduces operational risk.