The project page
The project page is the main screen of Karizma One: it shows every branch of the project, lets you act on the selected branch (restart, connect to Odoo, Web IDE, merge request…) and opens its monitoring tabs. Opening a project from the projects list takes you straight to this page.
Every project collaborator, whatever their role. The buttons you can use depend on your role and on the branch type: a button you are not allowed to use stays visible but greyed out, with the tooltip You don't have permission to perform this action.
The page has four areas:
- the top bar, shared by the whole project;
- the branch list, on the left;
- the action bar of the selected branch (its name, its buttons and the Connect button);
- the branch tabs (HISTORY, SHELL, LOGS…), described in Working with a branch.
Navigate with the top bar
Inside a project, the top bar shows four links:
| Link | Content | Who sees it |
|---|---|---|
| Branches | The project page described here. | All collaborators |
| Status | The status page. A green or red dot tells you whether the project's Odoo service responds. | All collaborators |
| Audit Logs | The project's audit log. | Super Admin, Admin |
| Settings | The project settings, including services. | Super Admin, Admin |
To the right of these links:
- the Previous Project / Next Project arrows move from one project to the next;
- the projects menu (labelled with the open project's name) lists your projects with their Odoo version and GitLab repository, with a Search projects... box;
- then come the chat, the notifications and your profile menu.
Pick a branch
The left column lists the project's branches, grouped by type: PRODUCTION, STAGING, MIGRATION (only when a migration branch exists) and DEVELOPMENT. The Search for a branch... box filters the list. Click a branch to open it.
Each row shows the branch name, its Odoo version (for example 17.0) and a status dot:
| Indicator | Meaning |
|---|---|
| Green dot | Environment deployed and running (Deployed). |
| Red dot | No running environment (Not Deployed). This is always the case for a development or migration branch, which has no environment. |
| Spinner | Deployment in progress. |
| Info icon | On hover: creation date and last update. |
| Download icon (cyan) | Staging on a newer Odoo version than the project (after a version upgrade). |
| Lock (amber) | Locked staging: it cannot be destroyed. |
To create, deploy or delete branches, see Branches and environments.
Act on the branch: the action bar
Above the tabs, the action bar shows the branch name and its buttons. The branch's Git command is repeated underneath, with a copy icon.
| Button | Available | What it does |
|---|---|---|
| Stop | Production only; Super Admin, Admin | Stops the production Odoo server after confirmation (Stopping the server will interrupt ongoing services). There is no start button: if needed, contact your Karizma representative. |
| Restart | Production: Super Admin, Admin. Staging: Super Admin, Admin, Developer | Restarts the Odoo server after confirmation. The service may be briefly interrupted. |
| Web IDE | Depends on your role and Web IDE access | Opens the branch's Web IDE in a new browser tab. |
| Submodules | Production and staging; Super Admin, Admin | Adds or removes Git submodules. See Manage submodules. |
| Clone | Everyone | Copies the git clone --branch <branch> <GitLab repository> command to the clipboard. No environment is created. |
| Fork | Everyone | Copies the git fork --branch <branch> <GitLab repository> command to the clipboard, in the same format. No environment is created. |
| Merge Request | Super Admin, Admin | Opens the dialog to create a merge request. |
| Delete | Development branches; Super Admin, Admin, Developer | Deletes the branch, in GitLab too. See Delete a development branch. |
Every stop and restart is recorded in the audit log (Stop Container, Restart Container).
Log in to Odoo with Connect
The green Connect button, on the right below the action bar, opens the branch's Odoo instance in your browser. It is only active on a deployed production or staging branch.
- Staging: you are logged in automatically as the Odoo administrator.
- Production: you are logged in automatically as administrator if you are a Super Admin or Admin, or if Auto-Connect is enabled for you. Otherwise the Odoo login page opens.
Automatic login relies on the database token set in the CONFIG tab (Auto Connect Config).
Log in as another user
The arrow to the right of Connect gives access to Connect As. It is available on every staging and, on production, when Auto-Connect is enabled for you.
- Click the arrow, then Connect As.
- The Internal Users dialog lists the users of the Odoo database. Search for a login in Search with specific login (portal or internal user).
- Click the row's connect action: Odoo opens, logged in with that account.
Every such login is recorded in the audit log (Connect As User).
Open the branch tabs
The HISTORY, SHELL, LOGS, MONITORING, BACKUP, SQL INSIGHTS, UPGRADE, MCP and CONFIG tabs let you monitor and operate the branch. A development or migration branch only shows HISTORY and CONFIG.
During a deployment, every tab except HISTORY shows Deployment in Progress: the environment is being prepared, which usually takes a few minutes.
Each tab is described in Working with a branch.
Expired project subscription
When the project's subscription has expired:
- a red banner reads Your subscription has expired. Please renew your subscription to continue using the service.;
- the branch list and most buttons are disabled, with the tooltip This project subscription has expired.
To find out the expiry date or renew the subscription, contact your Karizma representative.