← All features
Enterprise & governance

Change governanceNEW

Touching schema, rules, pricing or access roles is too powerful to leave uncontrolled. With change governance, every configuration change becomes a request that only takes effect after a manager approves it. You get a full trail of authorship and a safe promotion of what was tested into production, with no surprises.

  • Mandatory approval: sensitive configuration changes only take effect after a manager signs off.
  • Full trail: who requested, who approved, what changed and when, all recorded.
  • Safe promotion from test to production, without editing directly in the environment customers use.
🎁

Free in Sellio, you only pay for the machine

Approval workflows and safe configuration promotion are typically enterprise-tier features. On Sellio they’re part of the free product.

Benefits

Zero accidental production changes

Since nothing takes effect without approval, a stray click or a miscalibrated test can’t take down the environment your customers rely on.

Clear accountability

Every request records its author and approver, so it’s always clear who asked for and who authorized a sensitive change.

Effortless auditing

The immutable trail delivers ready-made history for compliance, with no need to reconstruct by hand what was altered.

Confidence to experiment

With a test environment and controlled promotion, the team explores changes without fear of hitting live operations.

Fewer incidents, more stability

Mandatory review filters out mistakes before they become problems, cutting rework and unplanned downtime.

Why Sellio

Control over configuration, not just data: schema, rules, pricing and roles all pass through approval.

Separation of duties built in: whoever proposes need not be whoever approves, reducing error and risk.

An immutable trail of every decision, ready for audit and for reconstructing what happened.

Formal change governance is usually a costly enterprise feature; on Sellio it’s included.

Approve before it counts

Instead of a change hitting production the instant someone saves, it becomes a pending request. A manager reviews exactly what changes (the rate, the rule, the access role) and approves or rejects. Only then does the change take effect. That turns dangerous configuration into a predictable process.

From test to production, safely

You try configuration in a test environment, validate the behavior and promote the approved package to production as a controlled operation. No editing live and hoping nothing breaks; the promotion is deliberate, recorded and traceable in history.

How it works
  1. 1

    Someone proposes a configuration change (schema, rule, pricing or role).

  2. 2

    The change stays pending as a request, without taking effect.

  3. 3

    A manager reviews what changes and approves or rejects, leaving a trail.

  4. 4

    Once approved, the package is promoted to production in a controlled way.

Use cases

Someone changes a pricing rule

The change stays pending; the sales manager reviews the impact and only then approves, keeping a wrong price out of real quotes.

An access-role adjustment

A permissions change goes through approval before it takes effect, ensuring nobody widens sensitive access without a second pair of eyes.

A new configuration validated in test

The team tests the new schema in a separate environment, approves the package and promotes it to production as a single, traceable operation.

Frequently asked
Can whoever proposes a change approve their own change?

The system separates who proposes from who approves, so whoever requests doesn't have to be whoever authorizes.

Can I find out later who changed what?

Yes, the full trail records who requested, who approved, what changed and when.

What kinds of changes go through approval?

Sensitive configuration changes: schema, rules, pricing and access roles.

How does promotion from test to production work?

You validate the configuration in a test environment and promote the approved package to production as a controlled, recorded operation.

What happens if the manager rejects the request?

The change doesn't take effect; only what's approved becomes active in production.

Is this a costly enterprise-plan feature?

Usually yes in other systems, but on Sellio change governance already comes included.

Does the control apply only to data or also to configuration?

It applies to configuration: schema, rules, pricing and access roles go through approval, not just data.

Is this included in the free plan?

Yes. Sellio is free; you only pay for infrastructure usage above US$20 per month.

Can an audit reconstruct what happened?

Yes, the immutable trail delivers ready-made history for compliance, with no manual reconstruction.

Try it at no cost

Create free account
Change governance · Sellio