Branch configuration
The CONFIG tab gathers settings specific to a branch. It is made of panels; each one only appears when the branch's stage and your role allow it.
CONFIG tab of any branch. It is hidden when no panel is available to you.

The panels
| Panel | Stages | Roles |
|---|---|---|
| Auto Connect Config | prod, staging | Super Admin, Admin |
| Immediate update of modules | prod, staging | Super Admin, Admin; Developer on staging |
| Manage Staging Domain | staging | Super Admin, Admin |
| Update Odoo Version | prod, staging | Super Admin, Admin |
| Manage Python Requirements | all | Super Admin, Admin; Developer on staging |
On a dev or migration branch, only the Manage Python Requirements panel can appear.
Set up auto-connect
The toolbar's Connect button can log you straight into Odoo, without typing credentials. It uses a token from the Odoo database to do so.
- In Auto Connect Config, paste the token into the Odoo Database Token field.
- Click Save changes. The message Access token added successfully. Auto Connect is now available. confirms it.
Update modules
The Immediate update of modules panel updates Odoo modules on the branch, without waiting for a new deployment.
- Pick the modules in Select modules from repository..., or type a module's technical name in Or add custom.
- Click Update.
The update runs as a job in the branch's pipeline; follow it in HISTORY.
| Message | Cause |
|---|---|
| No pipeline found for this branch | The branch has never had a pipeline. |
| Latest pipeline is canceled. | The latest pipeline was canceled: retry it first. |
| Pipeline jobs have failed | The latest pipeline failed: fix it first. |
| The branch '…' is currently running another submodule operation. Please wait. | Another operation is running on the branch. |
To update some modules automatically on every deployment, contact your Karizma representative instead to add them to the project's Update List.
Customize a staging domain
On a staging branch, the Manage Staging Domain panel gives the branch a Karizma subdomain of the form https://<project>-<your-text>.karizma.one.
- Type the free part in the field.
- Click Save changes.
For production domains, contact your Karizma representative.
Apply the latest Odoo build
The Update Odoo Version panel applies the latest build of the same Odoo version: security patches, bug fixes and optimizations. It does not change the major version; for that, see Odoo upgrade.
The Version Status block shows the current version (Current Version) and the date of the last update (Last update).
- Click Update to Latest Build. The button is disabled when no update is available.
- Enter the reason in Motif (required).
- Click Confirm.
Depending on your role, the update is applied directly or sent as a request to the project manager. To get it approved, contact your Karizma representative.
The instance is briefly unavailable while the update is applied. Schedule it outside business hours.
Manage Python dependencies
The Manage Python Requirements panel edits the branch's requirements.txt file, which lists the Python libraries your modules need.
- Click Update Requirements. The Edit requirements.txt editor opens; the file is created if it does not exist.
- Add or change libraries, one per line. Check their names carefully.
- Click Save Changes. The message Branch requirements updated successfully! confirms it.
Saving creates a commit on the branch, visible in HISTORY, which starts a pipeline.

Locked staging environments
A staging environment can be locked so that it cannot be destroyed; an orange padlock icon marks it in the sidebar. Locking is handled by the Karizma team: contact your Karizma representative to lock or unlock a staging environment.
See also
- Odoo upgrade to change the major version.
- Branches and environments