# Proposals and GitOps

> The console never changes the gateway. From a screen (policies, upstreams...), an operator prepares a proposal: a diff of the configuration, checked by the…

Concept - Since version 1.2.0 - Flexway v1.6.3 - https://flexway.io/en/docs/product-proposals-gitops/

> Product guide: what the capability brings, for whom, its limits and the version that delivered it - no configuration syntax.

| | |
| --- | --- |
| **What it does** | The console **never** changes the gateway. From a screen (policies, upstreams...), an operator prepares a **proposal**: a diff of the configuration, checked by the real loader, then opened as a pull request on your repository (GitHub). Each step goes to an audit log, up to its application |
| **Why it matters** | Git stays the only source of truth: every change is reviewed, traced, reversible. No click bypasses the review, and the console needs no write access to production |
| **Use cases** | An SRE adjusts a timeout from an upstream's screen and lets the owning team approve; an auditor reads who proposed what and when |
| **Limits** | Automatic proposal rules and AI for operations (which proposes, never decides) come in `1.10.0`; a traced, bounded emergency break-glass in `1.11.0` |
| **Since** | `1.2.0` |
| **Configure** | [Proposing a change from the console](https://flexway.io/en/docs/operations-proposals/) |